Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #241539
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Sata Hard drive testing |
| Date | 2021-10-21 04:40 +0200 |
| Message-ID | <Daw9P-4CA-1@gated-at.bofh.it> (permalink) |
| References | <D9DQ5-4X6-5@gated-at.bofh.it> <D9Ej8-5mk-9@gated-at.bofh.it> <Datvk-2Va-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
> On 10/18/21 6:52 PM, Reco wrote: >> Hi. >> >> On Mon, Oct 18, 2021 at 06:25:19PM +0200, Thomas Anderson wrote: >>> I have been having problems with a drive (non-SSD) for a while now, >>> but I would like to "identify" the problem specifically, so that I may >>> perhaps be able to get the drive replaced. >> Assuming it's SATA/IDE drive, all you need to do is: >> >> apt install smartmontools >> smartctl -t long <ur_drive_here> >> # wait for the test to finish >> smartctl -a <ur_drive_here> >> >> Please post the output of the last command. >> >> Reco On 10/20/21 4:45 PM, Thomas Anderson wrote: > Here are the results, of my smartctl test: Please use inline posting style, not top posting. > I am trying to parse them myself, to see if I can learn anything. But, > immediate glance > > and queries did not reveal anything that could help me determine if the > drive is good or not. > > > smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.19.0-18-amd64] (local build) > Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org > > === START OF INFORMATION SECTION === > Device Model: ST8000DM004-2CX188 So, an 8 TB desktop drive. Here is the datasheet: https://www.seagate.com/www-content/datasheets/pdfs/3-5-barracudaDS1900-11-1806US-en_US.pdf Here is the SMART attributes specification: http://t1.daumcdn.net/brunch/service/user/axm/file/zRYOdwPu3OMoKYmBOby1fEEQEbU.pdf > Serial Number: ZCT1706V > LU WWN Device Id: 5 000c50 0c2b1cd83 > Firmware Version: 0001 > User Capacity: 8,001,563,222,016 bytes [8.00 TB] > Sector Sizes: 512 bytes logical, 4096 bytes physical > Rotation Rate: 5425 rpm > Form Factor: 3.5 inches > Device is: Not in smartctl database [for details use: -P showall] > ATA Version is: ACS-3 T13/2161-D revision 5 > SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) > Local Time is: Wed Oct 20 14:36:49 2021 CEST > 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 "PASSED" is a good thing. > General SMART Values: > Offline data collection status: (0x00) Offline data collection activity > was never started. > Auto Offline Data Collection: Disabled. > Self-test execution status: ( 0) The previous self-test > routine completed > without error or no self-test has ever > been run. No self-test errors ia a good thing. > Total time to complete Offline > data collection: ( 0) seconds. > Offline data collection > capabilities: (0x73) SMART execute Offline immediate. > Auto Offline data collection on/off 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: ( 987) minutes. > Conveyance self-test routine > recommended polling time: ( 2) minutes. > SCT capabilities: (0x30a5) SCT Status supported. > SCT Data Table supported. > > SMART Attributes Data Structure revision number: 10 Decoding SMART attributes can be a challenge. In addition to the Seagate spec above, see: https://wiki.unraid.net/Understanding_SMART_Reports#SMART_attributes_section > 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 064 051 006 Pre-fail > Always - 7226480 > 3 Spin_Up_Time 0x0003 093 091 000 Pre-fail > Always - 0 > 4 Start_Stop_Count 0x0032 100 100 020 Old_age > Always - 361 > 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail > Always - 0 > 7 Seek_Error_Rate 0x000f 080 060 045 Pre-fail > Always - 104115990 > 9 Power_On_Hours 0x0032 084 084 000 Old_age > Always - 14558 (99 41 0) AIUI your drive had been powered up for a total of 14,558 hours over its lifetime when the report was generated. Spec is 2,400 hours per year (8,760 hours). > 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail > Always - 0 > 12 Power_Cycle_Count 0x0032 100 100 020 Old_age > Always - 77 > 183 Runtime_Bad_Block 0x0032 095 095 000 Old_age > Always - 5 AIUI your drive has experienced 5 bad blocks. I do not see any indication of data loss. So, I would not worry. > 184 End-to-End_Error 0x0032 100 100 099 Old_age > Always - 0 > 187 Reported_Uncorrect 0x0032 001 001 000 Old_age > Always - 1334 AIUI the drive has reported 1,334 uncorrectable errors to the host over its lifetime. The VALUE of 001 is the worst possible rating (bad news). But, it looks like they were ATA bus errors; not internal errors (good news). See below. > 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 070 052 040 Old_age > Always - 30 (Min/Max 28/33) > 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age > Always - 0 > 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age > Always - 25 > 193 Load_Cycle_Count 0x0032 099 099 000 Old_age > Always - 3362 Spec is 600,000 cycles. You are well below that. > 194 Temperature_Celsius 0x0022 030 048 000 Old_age > Always - 30 (0 16 0 0 0) > 195 Hardware_ECC_Recovered 0x001a 069 064 000 Old_age > Always - 7226480 AIUI the value of 69 is getting close to the failure threshold of 64. > 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 198 000 Old_age > Always - 15 > 240 Head_Flying_Hours 0x0000 100 253 000 Old_age > Offline - 2368 (67 0 0) > 241 Total_LBAs_Written 0x0000 100 253 000 Old_age > Offline - 54984038154 AIUI 54,984,038,154 * 512 bytes = ~27 TB have been written to the drive. > 242 Total_LBAs_Read 0x0000 100 253 000 Old_age > Offline - 185155335586 AIUI 185,155,335,586 * 512 bytes = ~92 TB have been read from the drive. The drive is rated for 55 TB/year. > SMART Error Log Version: 1 > ATA Error Count: 1334 (device log contains only the most recent five errors) Note that the value "1334" matches the 187 Reported_Uncorrect attribute, above. AIUI this means 1,334 data transfers over the ATA bus failed, indicating a bad drive interface, a bad drive-cable connection, a bad cable, a bad cable-adapter connection, and/or a bad adapter. > 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 1334 occurred at disk power-on lifetime: 10525 hours (438 days + > 13 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 53 00 ff ff ff 0f Error: UNC 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 > -- -- -- -- -- -- -- -- ---------------- -------------------- > 60 00 08 ff ff ff 4f 00 15d+00:06:46.256 READ FPDMA QUEUED > ef 10 02 00 00 00 a0 00 15d+00:06:46.247 SET FEATURES [Enable SATA > feature] > 27 00 00 00 00 00 e0 00 15d+00:06:46.220 READ NATIVE MAX ADDRESS EXT > [OBS-ACS-3] > ec 00 00 00 00 00 a0 00 15d+00:06:46.217 IDENTIFY DEVICE > ef 03 46 00 00 00 a0 00 15d+00:06:46.205 SET FEATURES [Set transfer > mode] > > Error 1333 occurred at disk power-on lifetime: 10525 hours (438 days + > 13 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 53 00 ff ff ff 0f Error: UNC 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 > -- -- -- -- -- -- -- -- ---------------- -------------------- > 60 00 08 ff ff ff 4f 00 15d+00:06:46.090 READ FPDMA QUEUED > ef 10 02 00 00 00 a0 00 15d+00:06:46.081 SET FEATURES [Enable SATA > feature] > 27 00 00 00 00 00 e0 00 15d+00:06:46.054 READ NATIVE MAX ADDRESS EXT > [OBS-ACS-3] > ec 00 00 00 00 00 a0 00 15d+00:06:46.051 IDENTIFY DEVICE > ef 03 46 00 00 00 a0 00 15d+00:06:46.039 SET FEATURES [Set transfer > mode] > > Error 1332 occurred at disk power-on lifetime: 10525 hours (438 days + > 13 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 53 00 ff ff ff 0f Error: UNC 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 > -- -- -- -- -- -- -- -- ---------------- -------------------- > 60 00 08 ff ff ff 4f 00 15d+00:06:45.922 READ FPDMA QUEUED > ef 10 02 00 00 00 a0 00 15d+00:06:45.912 SET FEATURES [Enable SATA > feature] > 27 00 00 00 00 00 e0 00 15d+00:06:45.886 READ NATIVE MAX ADDRESS EXT > [OBS-ACS-3] > ec 00 00 00 00 00 a0 00 15d+00:06:45.883 IDENTIFY DEVICE > ef 03 46 00 00 00 a0 00 15d+00:06:45.871 SET FEATURES [Set transfer > mode] > > Error 1331 occurred at disk power-on lifetime: 10525 hours (438 days + > 13 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 53 00 ff ff ff 0f Error: UNC 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 > -- -- -- -- -- -- -- -- ---------------- -------------------- > 60 00 08 ff ff ff 4f 00 15d+00:06:45.692 READ FPDMA QUEUED > ef 10 02 00 00 00 a0 00 15d+00:06:45.683 SET FEATURES [Enable SATA > feature] > 27 00 00 00 00 00 e0 00 15d+00:06:45.656 READ NATIVE MAX ADDRESS EXT > [OBS-ACS-3] > ec 00 00 00 00 00 a0 00 15d+00:06:45.654 IDENTIFY DEVICE > ef 03 46 00 00 00 a0 00 15d+00:06:45.641 SET FEATURES [Set transfer > mode] > > Error 1330 occurred at disk power-on lifetime: 10525 hours (438 days + > 13 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 53 00 ff ff ff 0f Error: UNC 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 > -- -- -- -- -- -- -- -- ---------------- -------------------- > 60 00 08 ff ff ff 4f 00 15d+00:06:45.526 READ FPDMA QUEUED > ef 10 02 00 00 00 a0 00 15d+00:06:45.517 SET FEATURES [Enable SATA > feature] > 27 00 00 00 00 00 e0 00 15d+00:06:45.491 READ NATIVE MAX ADDRESS EXT > [OBS-ACS-3] > ec 00 00 00 00 00 a0 00 15d+00:06:45.488 IDENTIFY DEVICE > ef 03 46 00 00 00 a0 00 15d+00:06:45.475 SET FEATURES [Set transfer > mode] AIUI it looks like you had a rash of data transfer errors at a lifetime hours of 10,525. As the drive now has over 14,558 hours, whatever the problem was, it went away. Perhaps this was when you moved the drive between computers and/or re-patched the cables? > SMART Self-test log structure revision number 1 > Num Test_Description Status Remaining > LifeTime(hours) LBA_of_first_error > # 1 Extended offline Completed without error 00% 14551 - > # 2 Extended offline Completed without error 00% 14530 - > # 3 Conveyance offline Completed without error 00% 10165 - > # 4 Conveyance offline Completed without error 00% 10165 - > # 5 Short offline Completed without error 00% 10163 - > # 6 Extended offline Completed without error 00% 9997 - > # 7 Short offline Completed without error 00% 0 - > > 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. Have you tested your cables, adapters, and/or other drives? The red SATA cable issue is real. I migrated my data from desktop hardware with a single data drive to server hardware with RAID a few years ago, and had a rash of storage issues. Once replaced all of my SATA cables with new, black, 6 Gbps cables with locking connectors, was able to troubleshoot everything else. Since then, storage has been stable: https://www.amazon.com/dp/B018Y2LF5O/ref=twister_B07D556K66?_encoding=UTF8&psc=1 https://www.amazon.com/dp/B018Y2LDGK/ref=twister_B07D581GYH?_encoding=UTF8&psc=1 David
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Sata Hard drive testing Thomas Anderson <thomas.anderson@little-beak.com> - 2021-10-18 18:40 +0200
Re: Sata Hard drive testing Felix Miata <mrmazda@earthlink.net> - 2021-10-18 18:50 +0200
Re: Sata Hard drive testing Reco <recoverym4n@enotuniq.net> - 2021-10-18 19:10 +0200
Re: Sata Hard drive testing Thomas Anderson <thomas.anderson@little-beak.com> - 2021-10-18 19:30 +0200
Re: Sata Hard drive testing Thomas Anderson <thomas.anderson@little-beak.com> - 2021-10-21 01:50 +0200
Re: Sata Hard drive testing Gene Heskett <gheskett@shentel.net> - 2021-10-21 02:40 +0200
Re: Sata Hard drive testing piorunz <piorunz@gmx.com> - 2021-10-21 03:20 +0200
Re: Sata Hard drive testing Andrei POPESCU <andreimpopescu@gmail.com> - 2021-10-21 10:40 +0200
Re: Sata Hard drive testing David Christensen <dpchrist@holgerdanske.com> - 2021-10-21 04:40 +0200
Re: Sata Hard drive testing piorunz <piorunz@gmx.com> - 2021-10-21 16:30 +0200
Re: Sata Hard drive testing Reco <recoverym4n@enotuniq.net> - 2021-10-21 07:50 +0200
Re: Sata Hard drive testing Dan Ritter <dsr@randomstring.org> - 2021-10-21 14:40 +0200
Re: Sata Hard drive testing Gene Heskett <gheskett@shentel.net> - 2021-10-21 15:00 +0200
Re: Sata Hard drive testing David <bouncingcats@gmail.com> - 2021-10-21 15:10 +0200
Re: Sata Hard drive testing Gene Heskett <gheskett@shentel.net> - 2021-10-21 16:30 +0200
Re: Sata Hard drive testing Kenneth Parker <sea7kenp@gmail.com> - 2021-10-21 18:10 +0200
Re: Sata Hard drive testing Thomas Anderson <thomas.anderson@little-beak.com> - 2021-10-24 17:00 +0200
Re: Sata Hard drive testing Andrei POPESCU <andreimpopescu@gmail.com> - 2021-10-21 15:10 +0200
Re: Sata Hard drive testing Andrei POPESCU <andreimpopescu@gmail.com> - 2021-10-21 15:20 +0200
Re: Sata Hard drive testing basti <mailinglist@unix-solution.de> - 2021-10-18 19:50 +0200
Re: Sata Hard drive testing David Christensen <dpchrist@holgerdanske.com> - 2021-10-18 20:40 +0200
Re: Sata Hard drive testing Stefan Monnier <monnier@iro.umontreal.ca> - 2021-10-18 21:30 +0200
csiph-web