Ubuntu是否会破坏我的内置硬盘?

我有一台预安装了Windows 8.1的Inspiron 3521。 我决定双启动Windows和Ubuntu,它运行良好。 但是,当使用Ubuntu时,我在使用Windows时听到笔记本电脑发出很多噪音,它几乎是无声的。 此外,在使用Ubuntu约2-3周后,我无法使用Windows,因为它变得非常慢。 现在我正在更换我的硬盘,因为它失败了。 那么,安装Ubuntu并使用它破坏我的硬盘吗? 因为在安装它之前,Windows运行良好,但在它之后,它几乎无法使用。 那么,我应该在我的新磁盘上安装Ubuntu还是应该避免使用它。 请帮助,因为我比Windows更喜欢Ubuntu,但我无法一次又一次地购买新硬盘。 此外,完全删除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 

硬盘驱动器会像癌症一样缓慢而痛苦地死亡,而固态硬盘突然就像心脏病一样停止工作 :您可以使用SMART技术进行诊断。

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

我可以根据您对症状的描述推断所有这些,而无需查看硬盘的分区表,也不知道如何安装系统……


简而言之就是:

不,Ubuntu不会破坏你的硬盘! 🙂

它会发出什么样的声音? 如果它点击你听到,那么你的操作系统可能会破坏你的硬盘 。 这个问题已经很久了,涉及高级电源管理function,过于积极地停放/取消停放磁盘。 尝试使用hdparm检查APM值(-B param)。 如果它小于254,则将其设置为254并检查它是否有助于产生噪音。 如果是,请确保该值始终保持为254。 在Linux下确保这一点的一个好方法是使用tlp。 为了记录,我已经看到这个问题出现在Windows以及某些笔记本电脑型号中,但它在Linux中更常见。

您(至少)有一个坏块(LBA 5642528)导致重复错误。 您可以尝试:

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

要么

  1. 更换硬盘