On 11/2/26 12:49, Mark Millard wrote: > On 11/2/26 12:17, bob prohaska wrote: >> A few more tests were tried on the offending hard disk, with mixed >> results. Then the disk was re-connected and booted up. The root >> partition came up clean, but the /usr partition would not, failing >> fsck repeatedly even after reporting "filesystem is clean". >> >> Finally I gave up and ran diskroaster, which reported five errors. >> Then I tried dd, sending output to /dev/null. That reported success. >> >> Eventually I stumbled on the correct incantation of smartctl, which >> didn't report any obvious faults. In particular "current pending >> sectors", which I understand to be indicative of problems, was zero. >> >> The results of diskroaster, dd and smartctl are in >> http://www.zefox.net/~fbsd/rpi2/disktrouble/ >> if anybody's willing to have a look. At this point >> dd and smartctl seem to see nothing wrong, diskroaster >> reports five errors but the last has an extra byte in >> the block offset, which seems odd. Also, the runtime >> values given were wildly off, two hours turned into >> all day and into the night. >> >> At this point >> smartctl -t long /dev/da1 is running. Any guidance in >> what to look for would be much appreciated. It'll finish >> in about three hours' from this writing. >> >> Thanks for reading, >> >> bob prohaska >> >> >> > > I copied and dropped the following text into a google search AI that I > started with just a smartctl search: > > QUOTE > 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 083 056 006 Pre-fail Always > - 196488624 > 3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always > - 0 > 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always > - 928 > 5 Reallocated_Sector_Ct 0x0033 099 099 036 Pre-fail Always > - 386 > 7 Seek_Error_Rate 0x000f 088 060 045 Pre-fail Always > - 689807869 > 9 Power_On_Hours 0x0032 069 069 000 Old_age Always > - 27803 (180 183 0) > 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always > - 0 > 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always > - 466 > 184 End-to-End_Error 0x0032 100 100 099 Old_age Always > - 0 > 187 Reported_Uncorrect 0x0032 095 095 000 Old_age Always > - 5 > 188 Command_Timeout 0x0032 100 093 000 Old_age Always > - 12885098515 > 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always > - 0 > 190 Airflow_Temperature_Cel 0x0022 077 049 040 Old_age Always > - 23 (Min/Max 23/43) > 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always > - 11 > 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always > - 106 > 193 Load_Cycle_Count 0x0032 001 001 000 Old_age Always > - 1114296 > 194 Temperature_Celsius 0x0022 023 051 000 Old_age Always > - 23 (0 16 0 0 0) > 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always > - 0 > 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age > Offline - 0 > 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always > - 0 > 240 Head_Flying_Hours 0x0000 100 253 000 Old_age > Offline - 22728 (60 98 0) > 241 Total_LBAs_Written 0x0000 100 253 000 Old_age > Offline - 23880627479 > 242 Total_LBAs_Read 0x0000 100 253 000 Old_age > Offline - 41354991467 > 254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always > - 0 > END QUOTE > > Its reply included: > > QUOTE > Your hard drive is failing and should be replaced as soon as possible. > While the "pass/fail" status might technically show a pass because no > individual attribute has crossed its threshold yet, the drive has > physically degraded and is actively damaging your data. > > Critical Concerns > > • ID 5: Reallocated_Sector_Ct (Raw Value: 386) – This is the most > damning metric. The drive has found 386 bad sectors and has moved data > out of them to a backup area. This means the magnetic platters are > physically deteriorating. > • ID 187: Reported_Uncorrect (Raw Value: 5) – The drive encountered 5 > read errors that its internal error correction code (ECC) could not fix. > These are permanent data corruptions. > • ID 193: Load_Cycle_Count (Raw Value: 1,114,296) – The drive's > read/write heads have parked and unparked over 1.1 million times. > Mechanical drives are typically rated for around 300,000 to 600,000 > cycles. Your drive is at 1 (worst possible normalized value), meaning it > has vastly outlived its mechanical design limits. > > Less Critical (Seagate Specifics) > > • ID 1 & 7: Raw_Read_Error_Rate & Seek_Error_Rate – The raw values look > huge (196M and 689M), but this is actually normal for Seagate drives. > Seagate packs multiple metrics (like total operations vs. actual errors) > into these raw numbers. The normalized VALUE columns (83 and 88) are > well above their THRESH safety lines (6 and 45), meaning these aren't > your primary issues. > > Summary of Drive State > > Your drive has been running for 27,803 hours (about 3.1 years of > continuous operation). It is a heavily used drive that is reaching the > end of its mechanical lifespan and has started dropping sectors. > END QUOTE
As for diskscan the latency graph that had 300000 |_ at the top: QUOTE (of google search again) When your graph scales all the way up to 300,000 and draws a flat line at the bottom, your storage drive is experiencing a severe physical failure. • The Drive is Hanging / Dropping Offline: A normal, healthy drive reads blocks in under 10ms to 50ms. When diskscan hits a severely degraded or physically dead sector, the drive's internal firmware enters a deep retry loop trying to recover the data. If it completely chokes, the Linux kernel's storage subsystem will hit a maximum I/O timeout—which typically defaults to a massive 30 seconds to several minutes (hence the 300,000ms scale). • Why it looks empty (|_): Because a 300,000ms delay is so massive, your drive's normal healthy read speeds (like 5ms) are mathematically squished down to 0% of the graph height. All your normal operations are completely flattened into that single bottom row (_), hiding any normal variations. END QUOTE -- === Mark Millard marklmi at yahoo.com
