아래 결과에 따르면 SATA 하드 드라이브를 폐기해야 합니까 smartctl?
시작 시 파일 시스템 오류가 계속 발생하고 fsck지난 번에는 이를 수정하지도 못했습니다. 그런 다음 라이브 USB(Fedora)를 사용하고 디스크 유틸리티를 사용하여 확인했는데 2500개 이상의 불량 섹터가 표시되었습니다.
온라인에서 수정 사항을 검색한 결과 "전체 형식과 제로 패딩"이 불량 섹터를 수정할 수 있다는 사실을 발견했습니다. 저는 그렇게 했는데 SATA 하드 드라이브에서는 12시간 이상이 걸렸습니다. 불량 섹터는 사라지지 않았지만 776개로 줄었습니다(디스크 유틸리티에 표시됨).
그런 다음 자세한 결과를 얻기 위해 SMART 테스트를 하기로 결정했습니다 smartctl. 짧은 SMART 테스트는 통과했지만 확장 테스트는 실패했습니다(아래 로그 구조 참조). 가능한 수정 사항을 설명하기가 어렵다는 사실이 밝혀져 여기에 질문을 가져오기로 결정했습니다.
이제 하드 드라이브를 사용해야 합니까?
아래의 세부 결과를 확인하시고 제안해 주시기 바랍니다.
[liveuser@localhost-live ~]$ sudo smartctl -a -d ata /dev/sda
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.3.7-301.fc31.x86_64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Mobile HDD
Device Model: ST1000LM035-1RK172
Serial Number: ZDE6YPLW
LU WWN Device Id: 5 000c50 0a5ef85fb
Firmware Version: LCM2
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-3 T13/2161-D revision 3b
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Fri May 22 09:37:52 2020 EDT
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: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 121) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: ( 0) seconds.
Offline data collection
capabilities: (0x71) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
No 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: ( 163) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x3035) 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 080 037 034 Pre-fail Always - 190487919
3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 098 098 020 Old_age Always - 2272
5 Reallocated_Sector_Ct 0x0033 095 095 036 Pre-fail Always - 784
7 Seek_Error_Rate 0x000f 080 060 045 Pre-fail Always - 107066354
9 Power_On_Hours 0x0032 095 095 000 Old_age Always - 5196 (144 134 0)
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 099 099 020 Old_age Always - 1855
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 33763
188 Command_Timeout 0x0032 100 098 000 Old_age Always - 107375951904
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 061 050 040 Old_age Always - 39 (Min/Max 26/45)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 20
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 167
193 Load_Cycle_Count 0x0032 067 067 000 Old_age Always - 67875
194 Temperature_Celsius 0x0022 039 050 000 Old_age Always - 39 (0 10 0 0 0)
196 Reallocated_Event_Count 0x0032 095 095 000 Old_age Always - 784
197 Current_Pending_Sector 0x0012 100 078 000 Old_age Always - 8
198 Offline_Uncorrectable 0x0010 100 078 000 Old_age Offline - 8
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 26
240 Head_Flying_Hours 0x000f 095 095 030 Pre-fail Always - 4839 (0 13 0)
254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 36087 (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 36087 occurred at disk power-on lifetime: 5164 hours (215 days + 4 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 ff ff ff 0f Error: WP at LBA = 0x0fffffff = 268435455
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 20 ff ff ff 4f 00 00:02:19.673 WRITE FPDMA QUEUED
60 00 08 ff ff ff 4f 00 00:02:18.472 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 00:02:18.378 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 e0 00 00:02:18.351 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 00 00:02:18.349 IDENTIFY DEVICE
Error 36086 occurred at disk power-on lifetime: 5164 hours (215 days + 4 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 ff ff ff 0f Error: WP at LBA = 0x0fffffff = 268435455
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:02:15.945 WRITE FPDMA QUEUED
61 00 08 ff ff ff 4f 00 00:02:15.945 WRITE FPDMA QUEUED
61 00 08 ff ff ff 4f 00 00:02:15.945 WRITE FPDMA QUEUED
61 00 08 ff ff ff 4f 00 00:02:15.944 WRITE FPDMA QUEUED
61 00 08 ff ff ff 4f 00 00:02:15.944 WRITE FPDMA QUEUED
Error 36085 occurred at disk power-on lifetime: 5164 hours (215 days + 4 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 ff ff ff 0f Error: WP at LBA = 0x0fffffff = 268435455
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 38 ff ff ff 4f 00 00:02:02.115 WRITE FPDMA QUEUED
61 00 f0 ff ff ff 4f 00 00:02:02.114 WRITE FPDMA QUEUED
61 00 20 ff ff ff 4f 00 00:02:02.114 WRITE FPDMA QUEUED
61 00 08 ff ff ff 4f 00 00:02:02.114 WRITE FPDMA QUEUED
61 00 08 ff ff ff 4f 00 00:02:02.113 WRITE FPDMA QUEUED
Error 36084 occurred at disk power-on lifetime: 5164 hours (215 days + 4 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 ff ff ff 0f Error: WP at LBA = 0x0fffffff = 268435455
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:01:53.737 WRITE FPDMA QUEUED
60 00 08 ff ff ff 4f 00 00:01:53.736 READ FPDMA QUEUED
ea 00 00 00 00 00 a0 00 00:01:53.707 FLUSH CACHE EXT
61 00 38 ff ff ff 4f 00 00:01:53.688 WRITE FPDMA QUEUED
60 00 08 ff ff ff 4f 00 00:01:53.678 READ FPDMA QUEUED
Error 36083 occurred at disk power-on lifetime: 5164 hours (215 days + 4 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 ff ff ff 0f Error: WP at LBA = 0x0fffffff = 268435455
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:01:53.049 WRITE FPDMA QUEUED
61 00 10 ff ff ff 4f 00 00:01:53.049 WRITE FPDMA QUEUED
61 00 08 ff ff ff 4f 00 00:01:53.049 WRITE FPDMA QUEUED
61 00 08 ff ff ff 4f 00 00:01:53.049 WRITE FPDMA QUEUED
61 00 08 ff ff ff 4f 00 00:01:53.049 WRITE FPDMA QUEUED
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed: read failure 90% 5196 318795064
# 2 Short offline Completed without error 00% 5194 -
# 3 Extended offline Aborted by host 90% 5194 -
# 4 Short offline Completed without error 00% 5194 -
# 5 Extended offline Completed: read failure 90% 5164 808789760
# 6 Extended offline Completed: read failure 90% 5164 808789760
# 7 Extended offline Completed: read failure 90% 5158 1348112200
# 8 Extended offline Completed: read failure 90% 5158 1348112200
# 9 Short offline Completed: read failure 80% 5143 1348112200
#10 Extended offline Completed: read failure 90% 5139 344992248
#11 Short offline Completed: read failure 90% 5139 344992248
#12 Short offline Completed: read failure 90% 5139 344992248
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.
답변1
SMART 속성을 해석하려면 해당 속성이 100으로 정규화되어 있으며 값이 낮을수록 더 나빠진다는 것을 알아야 합니다.
원시 읽기 오류율도 높고, 탐색 오류율도 높으며, 게다가 상당수의 섹터가 재배치되었습니다. 다른 속성은 단순히 약간의 마모를 나타내지만 처음 언급된 두 속성은 하드 드라이브가 더 이상 드라이브에 있는 데이터의 비트스트림을 제대로 읽을 수 없음을 의미합니다. 잘못된 정렬을 유발하는 기계적 오류, 읽기 또는 쓰기 회로의 전자적 오류, 표면의 일부 결함 또는 기타 이유일 수 있습니다.
이것이 내 하드 드라이브라면 즉시 백업을 만든 다음 버릴 것입니다. 하드 드라이브는 다시는 어떤 데이터도 안정적으로 저장하지 않습니다. "새것처럼" 구매한 경우 반품하고 불만을 제기하면 SMART 값이 새것이 아님을 분명히 보여줍니다.