Windows 8.1과 함께 사전 설치된 Inspiron 3521이 있습니다. Windows와 Ubuntu를 이중 부팅하기로 결정했는데 제대로 작동했습니다. 그러나 우분투를 사용할 때 Windows를 사용하는 동안 랩톱에서 많은 소음이 들렸지 만 거의 침묵했습니다. 또한 우분투를 2-3 주 정도 사용한 후에 Windows가 매우 느려서 사용할 수 없었습니다. 이제 HDD가 고장 나서 교체하고 있습니다. 그렇다면 우분투를 설치하고 사용하면 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에서 얻은 것으로 우분투를 실행하는 동안 우연히 파괴되었다고 생각합니다.
출력 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
답변
TL; DR
아니요, 우분투는 HDD를 파괴하지 않습니다! 🙂
긴 대답 :
HDD는 암과 같이 느리고 고통스러운 죽음으로 죽지 만 SSD는 갑자기 심장 마비처럼 작동을 멈 춥니 다. SMART 기술 을 사용하여 두 가지 모두를 진단 할 수 있습니다.
Windows가 아닌 Ubuntu에서 소음이 들리는 이유는 Windows가 먼저 설치되어 밀도가 높은 포장 지역의 하드 드라이브 내부에 있고 Ubuntu는 소음이 더 두드러지는 외부 지역에 설치되어 있기 때문입니다. 찾는 것.
그리고 나는 하드 디스크의 파티션 테이블을 보거나 시스템을 어떻게 설치했는지 알지 않고도 증상 설명 에서이 모든 것을 유추 할 수 있습니다 …
답변
어떤 소리를 내나요? 클릭 소리가 나면 OS가 실제로 HDD를 파괴하는 것일 수 있습니다. 문제는 오래되었으며 Advanced Power Management 기능으로 디스크를 너무 적극적으로 주차 / 해제합니다. hdparm을 사용하여 APM 값 (-B param)을 확인하십시오. 254보다 작 으면 254로 설정하고 잡음에 도움이되는지 확인하십시오. 그렇다면 항상 값을 254로 유지하십시오. Linux에서이를 확인하는 좋은 방법 중 하나는 tlp를 사용하는 것입니다. 기록을 위해이 문제는 Windows 및 특정 랩톱 모델에서 발생하지만 Linux에서는 더 일반적입니다.
답변
반복되는 오류를 일으키는 불량 블록 (LBA 5642528)이 하나 이상 있습니다. 당신은 시도 할 수 있습니다 :
- 전체 하드 디스크 백업
- LONG 방법을 사용하여 디스크를 재 포맷 / 재 파티션하여 불량 블록을 매핑하십시오. 완료하는 데 몇 시간이 걸릴 수 있습니다.
- 하드 디스크를 복원
또는
- 하드 디스크 교체
업데이트 # 1 :
HDD에 불량 블록이 있는지 테스트하려면 …
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.