Hi all, I'm new to unraid.  I hope to confirm that I'm understanding things, and what I'm understanding is that:  unraid is telling me a drive is no longer usable and I should physically remove and replace it.  And the drive should be trashed; no longer suitable for storage at all, right?

 

I am running Unraid 6.9.1 , I have 3 12TB WD shucked drives, 2 cache SSDs.  Parity, Disk1 are normal/active.  Disk2 is disabled (red x) and has "16" errors.  (in the errors column).

 

I'm getting write errors, such as this (from syslog, and same things are showing up if I click the disk log button on Main tab):

Aug 30 20:31:02 HQ-NAS kernel: Buffer I/O error on dev sdf1, logical block 23437770501, async page read
Aug 30 20:31:02 HQ-NAS kernel: sd 6:0:0:0: [sdf] tag#30 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=0s
Aug 30 20:31:02 HQ-NAS kernel: sd 6:0:0:0: [sdf] tag#30 CDB: opcode=0x88 88 00 00 00 00 05 74 ff ff 46 00 00 00 01 00 00
Aug 30 20:31:02 HQ-NAS kernel: blk_update_request: I/O error, dev sdf, sector 23437770566 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Aug 30 20:31:02 HQ-NAS kernel: Buffer I/O error on dev sdf1, logical block 23437770502, async page read
Aug 30 20:31:02 HQ-NAS kernel: sd 6:0:0:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=0s
Aug 30 20:31:02 HQ-NAS kernel: sd 6:0:0:0: [sdf] tag#0 CDB: opcode=0x88 88 00 00 00 00 05 74 ff ff 47 00 00 00 01 00 00
Aug 30 20:31:02 HQ-NAS kernel: blk_update_request: I/O error, dev sdf, sector 23437770567 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Aug 30 20:31:02 HQ-NAS kernel: Buffer I/O error on dev sdf1, logical block 23437770503, async page read

 

(I will attach the whole syslog).

 

Smart report can't run, it seems (not sure why?  total failure?  actually just disconnected for some reason?).  I'm just not sure what I'm looking at 🤷‍♂️.

 

Are there some other steps I should try to confirm?  I did try to run fast and slow smart reports, but like this post, I don't think it's telling me anything (I didn't try without the check-only flag though).

 

Thanks for your help,

Jeff

hq-nas-diagnostics-20210830-2031.zip

I found a thread with similar issue that suggested rebooting to see if disk is recognized, so I did.

 

Now in Main tab, disk 2 still has the red X, but the dropdown shows "unassigned" and there's no disk to assign to that slot.  So makes me think something somehow physically is disconnected (or cable spontaneously bad—or drive completely fried; can't even be recognized as plugged in)? 

 

The server is remote to me in an area no one should enter, so really...hopefully no one has gone and knocked it over 😅.  But I guess I'll have to go physically check it out to move much forward.

 

Would still greatly appreciate anyone's advice on best next steps!

Apr 11 12:18:54 HQ-NAS kernel: ata5.00: ATA-9: WDC WD120EDAZ-11F3RA0, 5PJDZTND, 81.00A81, max UDMA/133

Apr 11 12:19:23 HQ-NAS kernel: md: import disk2: (sdf) WDC_WD120EDAZ-11F3RA0_5PJDZTND size: 11718885324 

Aug 21 09:32:15 HQ-NAS kernel: ata5: link is slow to respond, please be patient (ready=0)
Aug 21 09:32:44 HQ-NAS kernel: ata5: COMRESET failed (errno=-16)

Aug 22 04:40:18 HQ-NAS kernel: md: disk2 write error, sector=10738557176

At that point Unraid disables the disk.

 

No SMART for disk2 so can't tell anything about the disk itself.

 

Check connections to see if you can get Unraid to see the disk again.

 

Then post new diagnostics.