Ubuntu是否会损坏我的内部硬盘？

Question

我有一台预装了Windows 8.1的Inspiron 3521。我决定在上面双系统安装Windows和Ubuntu，一开始运行得很好。但是，在使用Ubuntu时，我的笔记本发出很多噪音，而在使用Windows时几乎没有声音。而且，大约使用Ubuntu两三周后，Windows变得非常慢，无法使用。现在我要更换硬盘，因为它已经出现故障。所以，是安装Ubuntu并使用它导致了我的硬盘损坏吗？因为在安装之前，Windows运行良好，但安装之后，几乎无法使用。那么，我应该在新的硬盘上安装Ubuntu还是不要安装呢？请帮忙，因为我更喜欢Ubuntu而不是Windows，但我不能冒着一次又一次购买新硬盘的风险。另外，完全删除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.

注意：上述测试来自旧的硬盘驱动器，我认为在运行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

- LakshyaAg

---

评论不适合进行长时间的讨论；此对话已被移至聊天室。 - fossfreedom

在我的学校，我帮助修理坏掉的七年级笔记本电脑，因为今年学校给了整个七年级学生笔记本电脑。前几天，我看到一个被摔坏且硬盘损坏的笔记本电脑。虽然它还能勉强工作，但是启动和登录需要大约20分钟的时间。终于在按下[Ctrl]+[Shift]+[Esc]五分钟后，任务管理器打开了，我发现磁盘使用率一直保持在100%。处理器和内存使用都正常。然后，我以不正确的方式关闭了电脑，并进入了联想诊断。显示有几个坏扇区。 - Hitechcomputergeek

@Hitechcomputergeek，我从未摔过我的笔记本电脑。甚至一点也没有。 - LakshyaAg

@XZYoda12 我是在说明一个损坏的硬盘可能会变得非常慢（或者出现其他奇怪的问题），而不是像BIOS消息那样明显地显示“关键：硬盘故障”。实际上，如果你的电脑是预装了Windows 8.1的话，我猜测它可能带有一个有缺陷的硬盘。 - Hitechcomputergeek

Answer 1

太长没读

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

---

长篇回答：

硬盘驱动器像癌症一样慢慢死去，痛苦不堪，而固态硬盘则像心脏病发作一样突然停止工作：你可以通过使用SMART技术来诊断两者。

为什么你在Ubuntu下听到噪音而在Windows下没有听到，是因为Windows先安装，所以它位于硬盘的内侧，即密集包装区域，而Ubuntu安装在外部区域，由于寻道操作，噪音更加明显。

我可以根据你对症状的描述推断出所有这些，而无需查看你的硬盘分区表或了解你如何安装系统...

- Fabby

---

评论不应做为长时间讨论使用；此对话已移至聊天室。 - fossfreedom

Windows很可能没有安装在盘片的内侧，因为它是第一个安装的，所以很可能位于较低的逻辑块地址（LBA）。硬盘驱动器上较低的LBA通常对应外部部分，因为那里表面的线速度更高，因此读写速度更快（使新的硬盘驱动器执行更快）。此外，现代硬盘驱动器的内部部分与外部部分的数据密度并不高——这就是较低LBA时速度加快的原因。有关硬盘驱动器布局的相关讨论，请参阅此问题。 - Ruslan

Answer 2

如果你听到的声音是咔哒声，那么你的操作系统可能会实际上破坏你的硬盘驱动器。这个问题已经存在很久了，涉及到高级电源管理功能过于激进地停放/解锁磁盘。尝试使用hdparm来检查APM值（-B参数）。如果它小于254，请将其设置为254，并检查是否有助于减少噪音。如果有帮助，请确保该值始终保持在254。在Linux下，确保这一点的一个好方法是使用tlp。值得一提的是，我也曾看到这个问题在某些笔记本型号的Windows中出现，但在Linux中更为常见。

- kaqqao

---

将其设置为254没有帮助。我在之前的硬盘上尝试过，但它仍然坏了。 - LakshyaAg

好的，这就排除了停车/解锁问题。我猜你只是有一个有问题的硬盘... - kaqqao

好的，我会看看这个硬盘是否还能用。 :) - LakshyaAg

Answer 3

你至少有一个坏块（LBA 5642528），导致重复错误。你可以尝试以下方法：

1. 备份整个硬盘。 2. 使用长时间的格式化/重新分区方法来尝试映射出坏块。这可能需要很多小时才能完成。 3. 恢复你的硬盘。

或者

4. 更换硬盘。

更新 #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.

- heynnema

---

有没有想法是什么导致了那个坏块？ - LakshyaAg

所有硬盘上都会自然产生坏块。大量的坏块可能意味着可能发生磁头碰撞。除非对整个磁盘表面进行写入测试，否则您将无法确定具体问题所在。您遇到了读取错误，只有在发生写入错误时，坏块才会被永久标记为坏，因此需要进行测试。 - heynnema

此外，如果硬盘确实损坏，请不要尝试使用故障的驱动器。立即备份您的文件。 - Hitechcomputergeek