Ubuntu是否正在破坏我的内部硬盘？

40

我有一个预装Windows 8.1的Inspiron 3521。我决定同时启动Windows和Ubuntu，并且运行良好。但是，当使用Ubuntu时，在使用Windows的过程中，我的笔记本电脑发出很多噪音，几乎没有声音。另外，在使用Ubuntu大约2-3周后，由于Windows变得非常慢，我无法使用Windows。现在我要更换硬盘，因为它出现了故障。那么，安装Ubuntu并使用它会破坏我的HDD吗？因为在安装之前，Windows运行良好，但是在运行之后，它几乎变得不可用。因此，我应该在新磁盘上安装Ubuntu还是不要使用它。请帮忙，因为我比Windows更喜欢Ubuntu，但是我不能冒险一遍又一遍地购买新的HDD。此外，完全删除Windows也不是选择。

请让我知道我是否应该同时安装Ubuntu？

输出smartctl -a /dev/sda：

=== START OF INFORMATION SECTION ===
Device Model:     ST500LT012-1DG142
Serial Number:    W3P8Y9MR
LU WWN Device Id: 5 000c50 07c643db0
Firmware Version: 0001SDM1
User Capacity:    500,107,862,016 bytes [500 GB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Tue Feb 17 15:58:15 2015 IST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82) Offline data collection activity
                    was completed without error.
                    Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0) The previous self-test routine completed
                    without error or no self-test has ever 
                    been run.
Total time to complete Offline 
data collection:        (    0) seconds.
Offline data collection
capabilities:            (0x7b) SMART execute Offline immediate.
                    Auto Offline data collection on/off support.
                    Suspend Offline collection upon new
                    command.
                    Offline surface scan supported.
                    Self-test supported.
                    Conveyance Self-test supported.
                    Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                    power-saving mode.
                    Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                    General Purpose Logging supported.
Short self-test routine 
recommended polling time:    (   1) minutes.
Extended self-test routine
recommended polling time:    (  97) minutes.
Conveyance self-test routine
recommended polling time:    (   2) minutes.
SCT capabilities:          (0x1035) SCT Status supported.
                    SCT Feature Control supported.
                    SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   117   080   006    Pre-fail  Always       -       158207928
  3 Spin_Up_Time            0x0003   099   099   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       414
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       16
  7 Seek_Error_Rate         0x000f   064   060   030    Pre-fail  Always       -       38678857862
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       772 (87 233 0)
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       384
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       1465
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   059   052   045    Old_age   Always       -       41 (Min/Max 29/43)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       195
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       14
193 Load_Cycle_Count        0x0032   096   096   000    Old_age   Always       -       8566
194 Temperature_Celsius     0x0022   041   048   000    Old_age   Always       -       41 (0 17 0 0 0)
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       8
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       8
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   100   000    Old_age   Offline      -       276333900858102
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       2960885917
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       5374462826
254 Free_Fall_Sensor        0x0032   100   100   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 2175 (device log contains only the most recent five errors)
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 2175 occurred at disk power-on lifetime: 758 hours (31 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 20 19 56 00  Error: UNC at LBA = 0x00561920 = 5642528

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 00 ff ff ff 4f 00      00:15:34.369  READ FPDMA QUEUED
  61 00 68 ff ff ff 4f 00      00:15:34.369  WRITE FPDMA QUEUED
  61 00 10 ff ff ff 4f 00      00:15:34.369  WRITE FPDMA QUEUED
  60 00 08 20 19 56 40 00      00:15:34.368  READ FPDMA QUEUED
  60 00 40 ff ff ff 4f 00      00:15:34.368  READ FPDMA QUEUED

Error 2174 occurred at disk power-on lifetime: 758 hours (31 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 20 19 56 00  Error: UNC at LBA = 0x00561920 = 5642528

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 20 19 56 40 00      00:15:31.814  READ FPDMA QUEUED
  60 00 20 ff ff ff 4f 00      00:15:31.814  READ FPDMA QUEUED
  61 00 08 ff ff ff 4f 00      00:15:31.813  WRITE FPDMA QUEUED
  ea 00 00 00 00 00 a0 00      00:15:31.813  FLUSH CACHE EXT
  27 00 00 00 00 00 e0 00      00:15:31.787  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

Error 2173 occurred at disk power-on lifetime: 758 hours (31 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 20 19 56 00  Error: WP at LBA = 0x00561920 = 5642528

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 10 ff ff ff 4f 00      00:15:29.177  WRITE FPDMA QUEUED
  61 00 08 ff ff ff 4f 00      00:15:29.177  WRITE FPDMA QUEUED
  61 00 08 ff ff ff 4f 00      00:15:29.177  WRITE FPDMA QUEUED
  60 00 08 20 19 56 40 00      00:15:29.176  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      00:15:29.176  READ FPDMA QUEUED

Error 2172 occurred at disk power-on lifetime: 758 hours (31 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 20 19 56 00  Error: WP at LBA = 0x00561920 = 5642528

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 08 ff ff ff 4f 00      00:15:26.514  WRITE FPDMA QUEUED
  61 00 18 ff ff ff 4f 00      00:15:26.513  WRITE FPDMA QUEUED
  60 00 08 20 19 56 40 00      00:15:26.513  READ FPDMA QUEUED
  60 00 40 ff ff ff 4f 00      00:15:26.513  READ FPDMA QUEUED
  61 00 08 ff ff ff 4f 00      00:15:26.513  WRITE FPDMA QUEUED

Error 2171 occurred at disk power-on lifetime: 758 hours (31 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 20 19 56 00  Error: UNC at LBA = 0x00561920 = 5642528

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 40 ff ff ff 4f 00      00:15:18.647  READ FPDMA QUEUED
  60 00 20 ff ff ff 4f 00      00:15:18.641  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      00:15:18.629  READ FPDMA QUEUED
  60 00 20 ff ff ff 4f 00      00:15:18.619  READ FPDMA QUEUED
  60 00 20 ff ff ff 4f 00      00:15:18.607  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%       760         5642528
# 2  Short offline       Completed: read failure       90%       759         5642528
# 3  Short offline       Completed: read failure       90%       759         5642528
# 4  Short offline       Completed: read failure       90%       758         5642528
# 5  Short offline       Completed: read failure       90%       756         5642528
# 6  Short offline       Completed: read failure       90%       752         5642528
# 7  Extended offline    Completed: read failure       90%       752         5642528
# 8  Short offline       Completed: read failure       90%       752         5642528

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0): 
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

注意：上面的测试来自旧的HDD，我认为它在运行Ubuntu时被巧合所破坏。

输出sudo parted --list：

Model: ATA ST500LT012-1DG14 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End    Size    File system     Name                          Flags
 1      1049kB  316MB  315MB   ntfs            Basic data partition          hidden, diag
 2      316MB   419MB  104MB   fat32           EFI system partition          boot
 3      419MB   554MB  134MB                   Microsoft reserved partition  msftres
 4      554MB   237GB  236GB   ntfs            Basic data partition          msftdata
10      237GB   289GB  52.4GB  ext4
 7      289GB   293GB  4096MB  linux-swap(v1)
 8      293GB   314GB  20.5GB  ext4
 9      314GB   342GB  27.9GB  ext4
 5      342GB   395GB  53.7GB  ntfs            Basic data partition          msftdata
 6      395GB   500GB  105GB   ntfs            Basic data partition          msftdata

dual-boot hard-drive

— LakshyaAg
source

评论不作进一步讨论；此对话已转移至聊天。

— fossfreedom

在我的学校，我帮助修理了损坏的七年级笔记本电脑，因为我学校今年提供了整个七年级笔记本电脑。前几天，我看到一台损坏的笔记本电脑掉落了，硬盘损坏了。它仍然可以工作，但实际上大约需要20分钟才能启动并登录。在按[Ctrl] + [Shift] + [Esc]五分钟后，任务管理器终于打开了，我可以看到磁盘使用情况一直保持在100％处理器和内存使用均正常。然后，我关闭计算机（使用不正确的方法）并进入Lenovo Diagnostics。它表明有几个坏道。

— Hitechcomputergeek

@Hitechcomputergeek，我从来没有丢过我的笔记本电脑。一点也不。

— LakshyaAg 2015年

@ XZYoda12我正在说明损坏的硬盘驱动器如何因非常慢（或其他类似的怪异）而失败，而不是像BIOS消息“ CRITICAL：HARD DRIVE FAILURE（关键：硬盘故障）”这样更明显的故障。实际上，我猜您的计算机如果装有Windows 8.1，则硬盘有问题。

— Hitechcomputergeek

81

TL; DR

不，Ubuntu不会破坏您的硬盘！:-)

长答案：

HDD会像癌症一样死于缓慢而痛苦的死亡中，而SSD却像心脏病发作一样突然停止工作 ：您可以使用 SMART技术进行诊断。

为什么在Ubuntu而不是Windows下听到噪音的原因是因为Windows是首先安装的，所以它位于硬盘驱动器的内侧，位于密集区域，而Ubuntu则安装在噪音较明显的外部区域。寻求。

我可以仅根据您对症状的描述来推断所有这些信息，而无需查看硬盘的分区表或不知道如何安装系统...

— 法比
source

2

评论不作进一步讨论；此对话已转移至聊天。

— fossfreedom

Windows不太可能安装在板的内侧，因为它是第一个，因此很可能安装在较低的逻辑块地址（LBA）上。HDD上较低的LBA通常对应于外部部件，因为那里的表面线速度更高，因此读/写速度也更高（因此新HDD的执行速度更快）。此外，现代硬盘在内部的数据密度没有在外部的数据密度高-这就是在较低的LBA上加速的原因。有关HDD布局的相关讨论，请参见此问题。

— Ruslan 2015年

4

它发出什么样的声音？如果单击它，您会听到声音，则您的操作系统可能实际上正在销毁您的HDD。该问题源远流长，涉及“高级电源管理”功能过于主动地停放磁盘。尝试使用hdparm检查APM值（-B参数）。如果小于254，则将其设置为254，然后检查是否对噪音有所帮助。如果是这样，请确保该值始终保持在254。确保在Linux下执行此操作的一种好方法是使用tlp。作为记录，我已经看到在Windows和某些笔记本电脑型号中都出现了此问题，但是在Linux中这种情况更为常见。

— 卡考
source

将其设置为254并没有帮助。我在以前的HDD上尝试过，但仍然无效。

— LakshyaAg 2015年

1

好的，这排除了停车/停车问题。我想您那时硬盘出了问题……

— kaqqao 2015年

好吧，我来看看这个硬盘是否还活着。:)

— LakshyaAg 2015年

3

您（至少）有一个坏块（LBA 5642528），它会引起重复的错误。您可以尝试：

备份整个硬盘
使用LONG方法重新格式化/重新分区磁盘，以尝试将其映射出坏块。这可能需要许多小时才能完成。
恢复硬盘

要么

更换硬盘

更新＃1：

要测试硬盘是否有坏块...

Note: do NOT abort a bad block scan!

Note: do NOT bad block a SSD

Note: backup your important files FIRST!

sudo e2fsck -fcky /dev/sdXX ＃只读测试

要么

sudo e2fsck -fccky /dev/sdXX＃无损读/写测试（推荐）

-k很重要，因为它保存了先前的坏块表，并将任何新的坏块添加到该表。如果没有-k，则将丢失所有先前的坏块信息。

-fccky参数...

   -f     Force checking even if the file system seems clean.

   -c     This option causes e2fsck to use badblocks(8) program  to  do  a
          read-only  scan  of  the device in order to find any bad blocks.
          If any bad blocks are found, they are added  to  the  bad  block
          inode  to  prevent them from being allocated to a file or direc‐
          tory.  If this option is specified twice,  then  the  bad  block
          scan will be done using a non-destructive read-write test.

   -k     When combined with the -c option, any existing bad blocks in the
          bad blocks list are preserved, and any new bad blocks  found  by
          running  badblocks(8)  will  be added to the existing bad blocks
          list.

   -y     Assume  an answer of `yes' to all questions; allows e2fsck to be
          used non-interactively.  This option may not be specified at the
          same time as the -n or -p options.

— 血淋巴瘤
source

关于什么原因导致坏块的任何想法？

— LakshyaAg 2015年

坏块自然会出现在所有硬盘上。大量坏块表示可能发生磁头碰撞。在对磁盘的整个表面进行WRITE测试之前，您将不知道遇到哪个问题。您有READ错误，如果是WRITE错误，则坏块只会被永久标记为坏，因此需要进行测试。

— heynnema

2

另外，如果硬盘驱动器确实损坏，请不要尝试使用发生故障的驱动器。立即备份您的东西。

— Hitechcomputergeek