Parity disk in error state


Recommended Posts

Well, this just happened. I did parity check a couple of days ago with no errors. System is still running, but no parity is obvs not good. What should be my first step? Reboot and hope it works until I can get a replacement disk?

 

Thanks

 

 

Partial log file when it happened. Full diagnostics attached.

 

Jan  5 13:00:08 unRaid5 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0


Jan  5 13:00:08 unRaid5 kernel: ata1.00: irq_stat 0x40000001
Jan  5 13:00:08 unRaid5 kernel: ata1.00: failed command: READ DMA
Jan  5 13:00:08 unRaid5 kernel: ata1.00: cmd c8/00:48:f0:a4:00/00:00:00:00:00/e0 tag 0 dma 36864 in
Jan  5 13:00:08 unRaid5 kernel:         res 51/40:48:f0:a4:00/00:00:00:00:00/e0 Emask 0x9 (media error)
Jan  5 13:00:08 unRaid5 kernel: ata1.00: status: { DRDY ERR }
Jan  5 13:00:08 unRaid5 kernel: ata1.00: error: { UNC }
Jan  5 13:00:17 unRaid5 kernel: ata1.00: qc timeout (cmd 0x27)
Jan  5 13:00:17 unRaid5 kernel: ata1.00: failed to read native max address (err_mask=0x5)
Jan  5 13:00:17 unRaid5 kernel: ata1.00: HPA support seems broken, skipping HPA handling
Jan  5 13:00:17 unRaid5 kernel: ata1.00: revalidation failed (errno=-5)
Jan  5 13:00:17 unRaid5 kernel: ata1: hard resetting link
Jan  5 13:00:22 unRaid5 kernel: ata1: link is slow to respond, please be patient (ready=0)
Jan  5 13:00:26 unRaid5 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan  5 13:00:35 unRaid5 kernel: ata1.00: qc timeout (cmd 0xef)
Jan  5 13:00:35 unRaid5 kernel: ata1.00: failed to enable AA (error_mask=0x4)
Jan  5 13:00:35 unRaid5 kernel: ata1.00: revalidation failed (errno=-5)
Jan  5 13:00:35 unRaid5 kernel: ata1: limiting SATA link speed to 3.0 Gbps
Jan  5 13:00:35 unRaid5 kernel: ata1: hard resetting link
Jan  5 13:00:40 unRaid5 kernel: ata1: link is slow to respond, please be patient (ready=0)
Jan  5 13:00:44 unRaid5 kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Jan  5 13:01:04 unRaid5 kernel: ata1.00: qc timeout (cmd 0xec)
Jan  5 13:01:04 unRaid5 kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Jan  5 13:01:04 unRaid5 kernel: ata1.00: revalidation failed (errno=-5)
Jan  5 13:01:04 unRaid5 kernel: ata1.00: disabled
Jan  5 13:01:09 unRaid5 kernel: ata1: link is slow to respond, please be patient (ready=0)
Jan  5 13:01:13 unRaid5 kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Jan  5 13:01:13 unRaid5 kernel: sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jan  5 13:01:13 unRaid5 kernel: sd 1:0:0:0: [sdb] tag#0 Sense Key : 0x2 [current]
Jan  5 13:01:13 unRaid5 kernel: sd 1:0:0:0: [sdb] tag#0 ASC=0x4 ASCQ=0x21
Jan  5 13:01:13 unRaid5 kernel: sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 00 00 a4 f0 00 00 00 48 00 00
Jan  5 13:01:13 unRaid5 kernel: print_req_error: I/O error, dev sdb, sector 42224
Jan  5 13:01:13 unRaid5 kernel: md: disk0 read error, sector=42160
Jan  5 13:01:13 unRaid5 kernel: md: disk0 read error, sector=42168
Jan  5 13:01:13 unRaid5 kernel: md: disk0 read error, sector=42176
Jan  5 13:01:13 unRaid5 kernel: md: disk0 read error, sector=42184
Jan  5 13:01:13 unRaid5 kernel: md: disk0 read error, sector=42192
Jan  5 13:01:13 unRaid5 kernel: md: disk0 read error, sector=42200
Jan  5 13:01:13 unRaid5 kernel: md: disk0 read error, sector=42208
Jan  5 13:01:13 unRaid5 kernel: md: disk0 read error, sector=42216
Jan  5 13:01:13 unRaid5 kernel: md: disk0 read error, sector=42224

unraid5-diagnostics-20210105-1319.zip

Link to comment

No luck with the cable. When I booted I could hear one of the drives grinding and stopping. Unplugged it and that noise went away. Seems like a truly dead drive.

 

Except for one, my other drives are also WD Red ERFX. I see those in a lot of setups. Should I still trust them and get another one or is there a consensus on a better drive for unRaid?

 

 

Link to comment

Thanks! But, I had to get it ordered to get here quickly. I went with a Seagate IronWolf 8TB. A little better price and delivery time. It's 7200 rpm, so maybe that will give a little better performance. Probably not noticeable, though. Anyway, hopefully it lasts awhile.

 

Rebuilding parity now. After about 15 minutes, running at 122MB/s with a estimate of 18hrs to finish.

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.