Drive Failed & Errors

[tredman]

I'm new to unraid, so please go easy..

 

My system was set to do a parity check last night.  I woke up this morning to see a ton of read errors and one drive disabled.  I've since pulled the disabled drive and am in the process of rebuilding.  I've previously had read errors on the array, but a reboot has usually cleared them (the drives are oldish and I am about to start slowly swapping them out).

 

I downloaded the diagnostics - they are attached.  Could someone with more knowledge than me advise if there is something more serious than one drive failing?

 

Thanks for any help.

tower-diagnostics-20200609-1125.zip

[JorgeB]

Same error on multiple disks:

 

Jun  9 05:48:00 Tower kernel: sd 1:1:0:3: [sde] Unaligned partial completion (resid=56, sector_sz=512)

 

Googling this it looks like it's a bug/firmware issue, there was a fixed for the standard Linux LSI driver, no idea about your HP RAID controller, note also that RAID controllers are not recommended for Unraid.

[tredman]

12 minutes ago, johnnie.black said:

Same error on multiple disks:

 

Jun  9 05:48:00 Tower kernel: sd 1:1:0:3: [sde] Unaligned partial completion (resid=56, sector_sz=512)

 

Googling this it looks like it's a bug/firmware issue, there was a fixed for the standard Linux LSI driver, no idea about your HP RAID controller, note also that RAID controllers are not recommended for Unraid.

Yeah, that happens all the time - from what I see its not a problem and can be stopped with a bios upgrade.

 

I have a microserver gen 8, I'm not using its RAID functionality and the drives are passed straight through

[JorgeB]

5 minutes ago, tredman said:

I'm not using its RAID functionality and the drives are passed straight through

But are still using a RAID controller with a RAID driver, most likely wouldn't have the same problem with an LSI HBA.

[tredman]

5 minutes ago, johnnie.black said:

But are still using a RAID controller with a RAID driver, most likely wouldn't have the same problem with an LSI HBA.

That is true, but I have a microserver gen 8 so I think I don't have that option.  I don't think this will cause the issue I had though - with a drive marked as failed and read errors?

[JorgeB]

2 minutes ago, tredman said:

I don't think this will cause the issue I had though

Those messages are the start (cause) of the read errors, that then turn into write errors (on only one disk because Unraid only disables as many disks as there are parity devices.

 

Jun  9 05:48:00 Tower kernel: sd 1:1:0:3: [sde] Unaligned partial completion (resid=56, sector_sz=512)
Jun  9 05:48:00 Tower kernel: sd 1:1:0:3: [sde] tag#546 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jun  9 05:48:00 Tower kernel: sd 1:1:0:3: [sde] tag#546 Sense Key : 0x3 [current]
Jun  9 05:48:00 Tower kernel: sd 1:1:0:3: [sde] tag#546 ASC=0x11 ASCQ=0x0
Jun  9 05:48:00 Tower kernel: sd 1:1:0:3: [sde] tag#546 CDB: opcode=0x88 88 00 00 00 00 01 06 66 d6 48 00 00 02 f0 00 00
Jun  9 05:48:00 Tower kernel: print_req_error: critical medium error, dev sde, sector 4402370120
Jun  9 05:48:00 Tower kernel: md: disk3 read error, sector=4402370056
Jun  9 05:48:00 Tower kernel: md: disk3 read error, sector=4402370064
Jun  9 05:48:00 Tower kernel: md: disk3 read error, sector=4402370072
Jun  9 05:48:00 Tower kernel: md: disk3 read error, sector=4402370080
Jun  9 05:48:00 Tower kernel: md: disk3 read error, sector=4402370088
Jun  9 05:48:00 Tower kernel: md: disk3 read error, sector=4402370096

 

Jun  9 05:48:18 Tower kernel: sd 1:1:0:1: [sdc] Unaligned partial completion (resid=16344, sector_sz=512)
Jun  9 05:48:18 Tower kernel: sd 1:1:0:1: [sdc] tag#567 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jun  9 05:48:18 Tower kernel: sd 1:1:0:1: [sdc] tag#567 Sense Key : 0x3 [current]
Jun  9 05:48:18 Tower kernel: sd 1:1:0:1: [sdc] tag#567 ASC=0x11 ASCQ=0x0
Jun  9 05:48:18 Tower kernel: sd 1:1:0:1: [sdc] tag#567 CDB: opcode=0x88 88 00 00 00 00 01 06 6b 24 08 00 00 04 00 00 00
Jun  9 05:48:18 Tower kernel: print_req_error: critical medium error, dev sdc, sector 4402652168
Jun  9 05:48:18 Tower kernel: md: disk1 read error, sector=4402652104
Jun  9 05:48:18 Tower kernel: md: disk1 read error, sector=4402652112
Jun  9 05:48:18 Tower kernel: md: disk1 read error, sector=4402652120
Jun  9 05:48:18 Tower kernel: md: disk1 read error, sector=4402652128
Jun  9 05:48:18 Tower kernel: md: disk1 read error, sector=4402652136
Jun  9 05:48:18 Tower kernel: md: disk1 read error, sector=4402652144