February 8, 201016 yr Feb 7 20:03:11 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x280000 action 0x0 Feb 7 20:03:11 Tower kernel: ata3.00: BMDMA2 stat 0x686d0009 Feb 7 20:03:11 Tower kernel: ata3: SError: { 10B8B BadCRC } Feb 7 20:03:11 Tower kernel: ata3.00: cmd 25/00:00:6f:5f:49/00:04:5f:00:00/e0 tag 0 dma 524288 in Feb 7 20:03:11 Tower kernel: res 51/04:df:6f:5f:49/00:00:00:00:00/f0 Emask 0x1 (device error) Feb 7 20:03:11 Tower kernel: ata3.00: status: { DRDY ERR } Feb 7 20:03:11 Tower kernel: ata3.00: error: { ABRT } Feb 7 20:03:11 Tower kernel: ata3.00: configured for UDMA/33 Feb 7 20:03:11 Tower kernel: ata3: EH complete It repeats this over and over. Guessing there might be something with that disk?
February 8, 201016 yr Author Ok thanks, I figured that due to another thread I finally found. So I replaced the cable, and now a different disk is saying it's missing. I replaced the power cable to it, and it's still missing. Odd. I'll replace the sata cable to it now too in hopes it shows up. Figures I get another error on a different disk than the original problem.
February 8, 201016 yr Author It's back up now. Maybe the drive that went missing after I replace the cable on a different drive, was the one with the bad cable in the first place? It was disk 8, but ata3 was the error. Perhaps disk 8 was ata3 or are they the same numbers? How would I know?
February 8, 201016 yr It's back up now. Maybe the drive that went missing after I replace the cable on a different drive, was the one with the bad cable in the first place? It was disk 8, but ata3 was the error. Perhaps disk 8 was ata3 or are they the same numbers? How would I know? Which physical disk was mapped to which unRAID slot? That can be found from your syslog. (which you haven't posted here)
Archived
This topic is now archived and is closed to further replies.