September 30, 201015 yr Hello, i'm troubleshooting my friends server and i need your assistance. Right now when I start a parity check i get the following in my syslog; Sep 30 14:06:36 matinee kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 Sep 30 14:06:36 matinee kernel: ata2.00: BMDMA stat 0x25 Sep 30 14:06:36 matinee kernel: ata2.00: failed command: READ DMA EXT Sep 30 14:06:36 matinee kernel: ata2.00: cmd 25/00:00:37:14:a1/00:04:00:00:00/e0 tag 0 dma 524288 in Sep 30 14:06:36 matinee kernel: res 51/84:4f:37:14:a1/84:01:00:00:00/e0 Emask 0x10 (ATA bus error) Sep 30 14:06:36 matinee kernel: ata2.00: status: { DRDY ERR } Sep 30 14:06:36 matinee kernel: ata2.00: error: { ICRC ABRT } Sep 30 14:06:36 matinee kernel: ata2: soft resetting link What I had done was the following (Unraid 4.5.6); Firstly, we noticed the parity checks kept correcting errors so we did a reiserfs. One disk had errors and recommended a fix-fixable. We ran that command and then did a reiserfs again. Everything checked out fine. Now all hard drives are ok. We then ran a memtest for 12 hours = passed. What do the ATA errors mean above? It only happens during parity check, if i stop it the error does not show up.
September 30, 201015 yr It is more than likely a bad connection of the SATA cable. Also check the PSU cable that is attached to the drive when you are in there just to make sure it is connected correctly.
October 1, 201015 yr Author Ok so I replaced all of the cables with fresh ones. 2 Sata cables and 1 ide cable. Now the parity disk is showing red. Oddly enough it still tried a parity sync. So i then shut down the server and did the following; Swapped the sata ports and cables. When I booted back up I had to adjust the disk configuration but the parity is still showing red which leads me to believ something is wrong with that hard drive. It still tries to parity sync and i see the % going up so i'll let that finish but the errors remain; Oct 1 10:33:32 matinee kernel: ata1.00: cmd 25/00:00:3f:92:04/00:04:00:00:00/e0 tag 0 dma 524288 in Oct 1 10:33:32 matinee kernel: res 51/84:0f:3f:92:04/84:03:00:00:00/e0 Emask 0x10 (ATA bus error) Oct 1 10:33:32 matinee kernel: ata1.00: status: { DRDY ERR } Oct 1 10:33:32 matinee kernel: ata1.00: error: { ICRC ABRT } Oct 1 10:33:32 matinee kernel: ata1: soft resetting link Oct 1 10:33:32 matinee kernel: ata1.00: configured for UDMA/33 Oct 1 10:33:32 matinee kernel: ata1: EH complete Oct 1 10:34:04 matinee kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 Oct 1 10:34:04 matinee kernel: ata1.00: BMDMA stat 0x25 Oct 1 10:34:04 matinee kernel: ata1.00: failed command: READ DMA EXT Oct 1 10:34:04 matinee kernel: ata1.00: cmd 25/00:00:3f:d8:1b/00:04:00:00:00/e0 tag 0 dma 524288 in Oct 1 10:34:04 matinee kernel: res 51/84:bf:3f:d8:1b/84:00:00:00:00/e0 Emask 0x10 (ATA bus error) Oct 1 10:34:04 matinee kernel: ata1.00: status: { DRDY ERR } Oct 1 10:34:04 matinee kernel: ata1.00: error: { ICRC ABRT } Oct 1 10:34:04 matinee kernel: ata1: soft resetting link Oct 1 10:34:05 matinee kernel: ata1.00: configured for UDMA/33 Oct 1 10:34:05 matinee kernel: ata1: EH complete
October 1, 201015 yr Ok so I replaced all of the cables with fresh ones. 2 Sata cables and 1 ide cable. Now the parity disk is showing red. Oddly enough it still tried a parity sync. So i then shut down the server and did the following; Swapped the sata ports and cables. When I booted back up I had to adjust the disk configuration but the parity is still showing red which leads me to believ something is wrong with that hard drive. It still tries to parity sync and i see the % going up so i'll let that finish but the errors remain; Oct 1 10:33:32 matinee kernel: ata1.00: cmd 25/00:00:3f:92:04/00:04:00:00:00/e0 tag 0 dma 524288 in Oct 1 10:33:32 matinee kernel: res 51/84:0f:3f:92:04/84:03:00:00:00/e0 Emask 0x10 (ATA bus error) Oct 1 10:33:32 matinee kernel: ata1.00: status: { DRDY ERR } Oct 1 10:33:32 matinee kernel: ata1.00: error: { ICRC ABRT } Oct 1 10:33:32 matinee kernel: ata1: soft resetting link Oct 1 10:33:32 matinee kernel: ata1.00: configured for UDMA/33 Oct 1 10:33:32 matinee kernel: ata1: EH complete Oct 1 10:34:04 matinee kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 Oct 1 10:34:04 matinee kernel: ata1.00: BMDMA stat 0x25 Oct 1 10:34:04 matinee kernel: ata1.00: failed command: READ DMA EXT Oct 1 10:34:04 matinee kernel: ata1.00: cmd 25/00:00:3f:d8:1b/00:04:00:00:00/e0 tag 0 dma 524288 in Oct 1 10:34:04 matinee kernel: res 51/84:bf:3f:d8:1b/84:00:00:00:00/e0 Emask 0x10 (ATA bus error) Oct 1 10:34:04 matinee kernel: ata1.00: status: { DRDY ERR } Oct 1 10:34:04 matinee kernel: ata1.00: error: { ICRC ABRT } Oct 1 10:34:04 matinee kernel: ata1: soft resetting link Oct 1 10:34:05 matinee kernel: ata1.00: configured for UDMA/33 Oct 1 10:34:05 matinee kernel: ata1: EH complete If parity is "red" then writes to it have failed. You'll probably need to stop the array, un-assign it, start the array without it, stop the array once more, then re-assign it, and re-start it to get it to be recognized as its own replacement, even if it was just a loose cable. Joe L.
October 1, 201015 yr Author Ok so I replaced all of the cables with fresh ones. 2 Sata cables and 1 ide cable. Now the parity disk is showing red. Oddly enough it still tried a parity sync. So i then shut down the server and did the following; Swapped the sata ports and cables. When I booted back up I had to adjust the disk configuration but the parity is still showing red which leads me to believ something is wrong with that hard drive. It still tries to parity sync and i see the % going up so i'll let that finish but the errors remain; Oct 1 10:33:32 matinee kernel: ata1.00: cmd 25/00:00:3f:92:04/00:04:00:00:00/e0 tag 0 dma 524288 in Oct 1 10:33:32 matinee kernel: res 51/84:0f:3f:92:04/84:03:00:00:00/e0 Emask 0x10 (ATA bus error) Oct 1 10:33:32 matinee kernel: ata1.00: status: { DRDY ERR } Oct 1 10:33:32 matinee kernel: ata1.00: error: { ICRC ABRT } Oct 1 10:33:32 matinee kernel: ata1: soft resetting link Oct 1 10:33:32 matinee kernel: ata1.00: configured for UDMA/33 Oct 1 10:33:32 matinee kernel: ata1: EH complete Oct 1 10:34:04 matinee kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 Oct 1 10:34:04 matinee kernel: ata1.00: BMDMA stat 0x25 Oct 1 10:34:04 matinee kernel: ata1.00: failed command: READ DMA EXT Oct 1 10:34:04 matinee kernel: ata1.00: cmd 25/00:00:3f:d8:1b/00:04:00:00:00/e0 tag 0 dma 524288 in Oct 1 10:34:04 matinee kernel: res 51/84:bf:3f:d8:1b/84:00:00:00:00/e0 Emask 0x10 (ATA bus error) Oct 1 10:34:04 matinee kernel: ata1.00: status: { DRDY ERR } Oct 1 10:34:04 matinee kernel: ata1.00: error: { ICRC ABRT } Oct 1 10:34:04 matinee kernel: ata1: soft resetting link Oct 1 10:34:05 matinee kernel: ata1.00: configured for UDMA/33 Oct 1 10:34:05 matinee kernel: ata1: EH complete If parity is "red" then writes to it have failed. You'll probably need to stop the array, un-assign it, start the array without it, stop the array once more, then re-assign it, and re-start it to get it to be recognized as its own replacement, even if it was just a loose cable. Joe L. I had already done that but it's still red. The parity check is at 70% right now so i'm guessing it's been doing something all of this time. I'll let it finish and restart the server to see the results. The drive error in the logs is still concerning me though.
Archived
This topic is now archived and is closed to further replies.