February 2, 201016 yr Once again... Parity Errors. 1) Parity drive is fine (Passes large offline SMART test) 2) Tried 3 SATA cables 3) Updated BIOS to latest Feb 2 15:04:58 Server kernel: ata22.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Feb 2 15:04:58 Server kernel: ata22.00: cmd 25/00:00:2f:19:d8/00:04:a3:00:00/e0 tag 0 dma 524288 in Feb 2 15:04:58 Server kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 2 15:04:58 Server kernel: ata22.00: status: { DRDY } Feb 2 15:04:58 Server kernel: ata22: hard resetting link Feb 2 15:05:08 Server kernel: ata22: softreset failed (device not ready) Feb 2 15:05:08 Server kernel: ata22: hard resetting link Feb 2 15:05:18 Server kernel: ata22: softreset failed (device not ready) Feb 2 15:05:18 Server kernel: ata22: hard resetting link Feb 2 15:05:29 Server kernel: ata22: link is slow to respond, please be patient (ready=0) Feb 2 15:05:53 Server kernel: ata22: softreset failed (device not ready) Feb 2 15:05:53 Server kernel: ata22: limiting SATA link speed to 1.5 Gbps Feb 2 15:05:53 Server kernel: ata22: hard resetting link Feb 2 15:05:59 Server kernel: ata22: softreset failed (device not ready) Feb 2 15:05:59 Server kernel: ata22: reset failed, giving up Feb 2 15:05:59 Server kernel: ata22.00: disabled Feb 2 15:05:59 Server kernel: ata22.00: device reported invalid CHS sector 0 Feb 2 15:05:59 Server kernel: ata22: EH complete Feb 2 15:21:14 Server kernel: md: disk0: ATA_OP_STANDBYNOW1 ioctl error: -5 Google claims the error is because of buggy ACPI. I've disabled it (in both unRAID and BIOs) and it still happens. What exactly is ata22, I thought hard drives went ata1, ata2, ata3, etc. In that case there isn't even anything hooked up to ata22. I'm very close to just selling unraid because I can't get it to work, on a rather common setup. One guy said his problem was resolved by using higher quality SATAII cables, however I cannot use them on my setup because my SATA cards have the ports to close together... I can't find a single quality cable that fits. syslog.zip
February 2, 201016 yr Author More errors happened after the original post (this isnt the entire syslog) More_Errors.txt
February 2, 201016 yr It is your parity drive /dev/sdh that is giving all the errors... It is "freezing" and becoming unresponsive. Feb 1 22:03:33 Server kernel: md: import disk0: [8,112] (sdh) WDC WD15EADS-00P WD-WCAVU0381827 offset: 63 size: 1465138552 The Linux kernel tries to reset it, but it cannot. Feb 2 15:04:58 Server kernel: ata22.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Feb 2 15:04:58 Server kernel: ata22.00: cmd 25/00:00:2f:19:d8/00:04:a3:00:00/e0 tag 0 dma 524288 in Feb 2 15:04:58 Server kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 2 15:04:58 Server kernel: ata22.00: status: { DRDY } Feb 2 15:04:58 Server kernel: ata22: hard resetting link Feb 2 15:05:08 Server kernel: ata22: softreset failed (device not ready) Feb 2 15:05:08 Server kernel: ata22: hard resetting link Feb 2 15:05:18 Server kernel: ata22: softreset failed (device not ready) Feb 2 15:05:18 Server kernel: ata22: hard resetting link Feb 2 15:05:29 Server kernel: ata22: link is slow to respond, please be patient (ready=0) Feb 2 15:05:53 Server kernel: ata22: softreset failed (device not ready) Feb 2 15:05:53 Server kernel: ata22: limiting SATA link speed to 1.5 Gbps Feb 2 15:05:53 Server kernel: ata22: hard resetting link Feb 2 15:05:59 Server kernel: ata22: softreset failed (device not ready) Feb 2 15:05:59 Server kernel: ata22: reset failed, giving up Feb 2 15:05:59 Server kernel: ata22.00: disabled Feb 2 15:05:59 Server kernel: ata22.00: device reported invalid CHS sector 0 Feb 2 15:05:59 Server kernel: ata22: EH complete Feb 2 15:05:59 Server kernel: sd 22:0:0:0: [sdh] Unhandled error code Feb 2 15:05:59 Server kernel: sd 22:0:0:0: [sdh] Result: hostbyte=0x04 driverbyte=0x00 Once the reset fails, all subsequent I/O fails Feb 2 15:05:59 Server kernel: end_request: I/O error, dev sdh, sector 2748848431 Feb 2 15:05:59 Server kernel: md: disk0 read error Feb 2 15:05:59 Server kernel: handle_stripe read error: 2748848368/0, count: 1 Feb 2 15:05:59 Server kernel: md: disk0 read error Feb 2 15:05:59 Server kernel: handle_stripe read error: 2748848376/0, count: 1 Feb 2 15:05:59 Server kernel: md: disk0 read error Some things you can try: Move the parity drive to a different power cable. Move it to a different disk controller port. Do not bundle its SATA cable with other cables. (to reduce crosstalk and induced noise) Use a different brand of SATA cable for that drive. Use as short an SATA cable as possible for that drive. Joe L.
February 2, 201016 yr Author Do not bundle its SATA cable with other cables. (to reduce crosstalk and induced noise) That actually makes sense, because when I replaced a SATA cable it was outside of the "ziptied" SATA cables, and I no longer got errors. However after rebuilding the system (after getting my SATA cards) the errors came back. That seems like the most logical thing that could be going wrong. I'll try that and see what happens.
February 2, 201016 yr Author 1. Move the parity drive to a different power cable. 2. Move it to a different disk controller port. 3. Do not bundle its SATA cable with other cables. (to reduce crosstalk and induced noise) 4. Use a different brand of SATA cable for that drive. 5. Use as short an SATA cable as possible for that drive. Alright i've went ahead and did #1, #2, and #3. All new port, all new power and SATA cables. I'll report back in a few days, or sooner, if it errors again.
Archived
This topic is now archived and is closed to further replies.