this post was submitted on 12 Jul 2025
1 points (100.0% liked)

It's A Digital Disease!

23 readers
1 users here now

This is a sub that aims at bringing data hoarders together to share their passion with like minded people.

founded 2 years ago
MODERATORS
 
The original post: /r/datahoarder by /u/abyssea on 2025-07-11 20:23:46.

One of the disks in my Unraid server is giving off these types of errors, meaning that portion of the drive is not accessible:

Jul 9 21:13:30 Tower kernel: sd 1:0:16:0: [sdr] tag#239 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=7s

Jul 9 21:13:30 Tower kernel: sd 1:0:16:0: [sdr] tag#239 Sense Key : 0x3 [current] [descriptor]

Jul 9 21:13:30 Tower kernel: sd 1:0:16:0: [sdr] tag#239 ASC=0x11 ASCQ=0x0

Jul 9 21:13:30 Tower kernel: sd 1:0:16:0: [sdr] tag#239 CDB: opcode=0x88 88 00 00 00 00 03 7f 2f 26 10 00 00 02 00 00 00

Jul 9 21:13:30 Tower kernel: critical medium error, dev sdr, sector 15018698736 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 0

DiskSpeed reports back with:

|| || |Temperature Celsius||26| |Raw Read Error Rate||0| |Spin Up Time||9833| |Start Stop Count||903| |Reallocated Sector Ct||0| |Seek Error Rate||0| |Power On Hours||27295 [3 Years, 42 Days, 7 hours]| |Spin Retry Count||0| |Calibration Retry Count||0| |Power Cycle Count||20| |Power-Off Retract Count||17| |Load Cycle Count||897| |Reallocated Event Count||0| |Current Pending Sector||0| |Offline Uncorrectable||0| |UDMA CRC Error Count||0| |Multi Zone Error Rate||1094|

I know some data systems will mark bad sectors and avoid them, meaning less of the drive is useable but the drive isn't dead in the water. I've moved all the data from the drive on to another drive and performed an extended SMART test with Unraid, which came back without any issues.

Device Statistics (GP Log 0x04)

Page Offset Size Value Flags Description

0x01 ===== = = === == General Statistics (rev 1) ==

0x01 0x008 4 20


Lifetime Power-On Resets

0x01 0x010 4 27291


Power-on Hours

0x01 0x018 6 40039298553


Logical Sectors Written

0x01 0x020 6 42197995


Number of Write Commands

0x01 0x028 6 296149816379


Logical Sectors Read

0x01 0x030 6 417669825


Number of Read Commands

0x01 0x038 6 3758319488


Date and Time TimeStamp

0x03 ===== = = === == Rotating Media Statistics (rev 1) ==

0x03 0x008 4 21972


Spindle Motor Power-on Hours

0x03 0x010 4 21933


Head Flying Hours

0x03 0x018 4 914


Head Load Events

0x03 0x020 4 0


Number of Reallocated Logical Sectors

0x03 0x028 4 48008


Read Recovery Attempts

0x03 0x030 4 0


Number of Mechanical Start Failures

0x03 0x038 4 8


Number of Realloc. Candidate Logical Sectors

0x03 0x040 4 17


Number of High Priority Unload Events

0x04 ===== = = === == General Errors Statistics (rev 1) ==

0x04 0x008 4 7


Number of Reported Uncorrectable Errors

0x04 0x010 4 0


Resets Between Cmd Acceptance and Completion

0x05 ===== = = === == Temperature Statistics (rev 1) ==

0x05 0x008 1 34


Current Temperature

0x05 0x010 1 29


Average Short Term Temperature

0x05 0x018 1 24


Average Long Term Temperature

0x05 0x020 1 45


Highest Temperature

0x05 0x028 1 15


Lowest Temperature

0x05 0x030 1 40


Highest Average Short Term Temperature

0x05 0x038 1 18


Lowest Average Short Term Temperature

0x05 0x040 1 32


Highest Average Long Term Temperature

0x05 0x048 1 22


Lowest Average Long Term Temperature

0x05 0x050 4 0


Time in Over-Temperature

0x05 0x058 1 65


Specified Maximum Operating Temperature

0x05 0x060 4 0


Time in Under-Temperature

0x05 0x068 1 0


Specified Minimum Operating Temperature

0x06 ===== = = === == Transport Statistics (rev 1) ==

0x06 0x008 4 35


Number of Hardware Resets

0x06 0x010 4 0


Number of ASR Events

0x06 0x018 4 0


Number of Interface CRC Errors

And

SATA Phy Event Counters (GP Log 0x11)

ID Size Value Description

0x0001 2 0 Command failed due to ICRC error

0x0002 2 0 R_ERR response for data FIS

0x0003 2 0 R_ERR response for device-to-host data FIS

0x0004 2 0 R_ERR response for host-to-device data FIS

0x0005 2 0 R_ERR response for non-data FIS

0x0006 2 0 R_ERR response for device-to-host non-data FIS

0x0007 2 0 R_ERR response for host-to-device non-data FIS

0x0008 2 0 Device-to-host non-data FIS retries

0x0009 2 0 Transition from drive PhyRdy to drive PhyNRdy

0x000a 2 1 Device-to-host register FISes sent due to a COMRESET

0x000b 2 0 CRC errors within host-to-device FIS

0x000d 2 0 Non-CRC errors within host-to-device FIS

0x000f 2 0 R_ERR response for host-to-device data FIS, CRC

0x0012 2 0 R_ERR response for host-to-device non-data FIS, CRC

0x8000 4 908014 Vendor specific

Because the array is reporting 288 errors from the device, I'm not sure if the drive should be replaced, considering the other results. Looking for advice, thanks.

no comments (yet)
sorted by: hot top controversial new old
there doesn't seem to be anything here