June 30, 201313 yr Hello I would apreciate some help and guidance please, my box was built for me so I have very little understanding of it technically. it has worked flawlessly so even more reason. I am running 4.7, currently in the array 12 T and parity drive all are WDC WD20EARX my routine is normally a monthly parity check which normally runs without error. Today I ran my check and noticed the check stopped on checking found DISK_DSBL and a red ball dispayed against the parity drive. I have read some of the posts concerning the above issue and I am a little confused as to what my next move should be to keep things safe. System log shows; Jun 30 23:19:39 Tower kernel: ata2: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) Jun 30 23:19:39 Tower kernel: ata2: status=0x51 { DriveReady SeekComplete Error } (Errors) Jun 30 23:19:39 Tower kernel: ata2: error=0x04 { DriveStatusError } (Errors) Jun 30 23:19:39 Tower kernel: ata2: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) Jun 30 23:19:39 Tower kernel: ata2: status=0x51 { DriveReady SeekComplete Error } (Errors) Jun 30 23:19:39 Tower kernel: ata2: error=0x04 { DriveStatusError } (Errors) Jun 30 23:19:39 Tower kernel: ata2: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) Jun 30 23:19:39 Tower kernel: ata2: status=0x51 { DriveReady SeekComplete Error } (Errors) Jun 30 23:19:39 Tower kernel: ata2: error=0x04 { DriveStatusError } (Errors) Jun 30 23:19:39 Tower kernel: ata2: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) Jun 30 23:19:39 Tower kernel: ata2: status=0x51 { DriveReady SeekComplete Error } (Errors) Jun 30 23:19:39 Tower kernel: ata2: error=0x04 { DriveStatusError } (Errors) Jun 30 23:19:39 Tower kernel: ata2: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) Jun 30 23:19:39 Tower kernel: ata2: status=0x51 { DriveReady SeekComplete Error } (Errors) Jun 30 23:19:39 Tower kernel: ata2: error=0x04 { DriveStatusError } (Errors) I did HDParm Info and nothing appeared to happen. Then tried to run Smart Status report and got the following; smartctl -t short -d ata /dev/sdc 2>&1 smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. I have not pressed anything else or done anything else any advice would be very welcome but please understand my knowledge is very limited. Thanks Peter
July 1, 201313 yr Power down and check the power and SATA connections to the drive. Use a new SATA cable. Power on and get a SMART report.
July 1, 201313 yr Author Hello Thank you for your response, I have powered the machine down and checked cables all appeared in place and secure. I have re-started the server and now have a blue ball, the parity drive is now described as New Disk in blue. The array is stopped and parity is still describe as not valid. There does not appear to be the option to restart the array. Peter syslog-2013-07-01.txt
July 2, 201313 yr Hello I would apreciate some help and guidance please, my box was built for me so I have very little understanding of it technically. it has worked flawlessly so even more reason. I am running 4.7, currently in the array 12 T and parity drive all are WDC WD20EARX my routine is normally a monthly parity check which normally runs without error. Today I ran my check and noticed the check stopped on checking found DISK_DSBL and a red ball dispayed against the parity drive. I have read some of the posts concerning the above issue and I am a little confused as to what my next move should be to keep things safe. System log shows; Jun 30 23:19:39 Tower kernel: ata2: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) Jun 30 23:19:39 Tower kernel: ata2: status=0x51 { DriveReady SeekComplete Error } (Errors) Jun 30 23:19:39 Tower kernel: ata2: error=0x04 { DriveStatusError } (Errors) Jun 30 23:19:39 Tower kernel: ata2: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) Jun 30 23:19:39 Tower kernel: ata2: status=0x51 { DriveReady SeekComplete Error } (Errors) Jun 30 23:19:39 Tower kernel: ata2: error=0x04 { DriveStatusError } (Errors) Jun 30 23:19:39 Tower kernel: ata2: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) Jun 30 23:19:39 Tower kernel: ata2: status=0x51 { DriveReady SeekComplete Error } (Errors) Jun 30 23:19:39 Tower kernel: ata2: error=0x04 { DriveStatusError } (Errors) Jun 30 23:19:39 Tower kernel: ata2: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) Jun 30 23:19:39 Tower kernel: ata2: status=0x51 { DriveReady SeekComplete Error } (Errors) Jun 30 23:19:39 Tower kernel: ata2: error=0x04 { DriveStatusError } (Errors) Jun 30 23:19:39 Tower kernel: ata2: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) Jun 30 23:19:39 Tower kernel: ata2: status=0x51 { DriveReady SeekComplete Error } (Errors) Jun 30 23:19:39 Tower kernel: ata2: error=0x04 { DriveStatusError } (Errors) I did HDParm Info and nothing appeared to happen. Then tried to run Smart Status report and got the following; smartctl -t short -d ata /dev/sdc 2>&1 smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. I have not pressed anything else or done anything else any advice would be very welcome but please understand my knowledge is very limited. Thanks Peter Those are all symptoms of a disk that is not responding too commands. The possible causes are a failed disk, OR a loose cable to the disk from the disk controller, or a bad disk controller port. Most likely is a loose/intermittent cable. (It is why others asked you to power down and re-seat the cables)
July 2, 201313 yr Hello Thank you for your response, I have powered the machine down and checked cables all appeared in place and secure. I have re-started the server and now have a blue ball, the parity drive is now described as New Disk in blue. The array is stopped and parity is still describe as not valid. There does not appear to be the option to restart the array. Peter unRAID forgot the make/model/serial number of the parity when you started it with the disk not-responding. Now that you have re-seated the cables it thinks it is a replacement drive. (The blue indicator says it thinks the drive is "new") Is there a "I'm sure" checkbox under the start button? If so, check it to enable the start button and start the array. It will perform an initial parity calc. Joe L.
July 3, 201313 yr Author Hi Thank you for your reply, Sorry i have not replied sooner but I have sadly now lost my windows OS after a corrupted boot sector and bad disk. Joe, as you stated I clicked the box and a parity check started immediately, fortunately i was able to instigate that before i lost windows. It does seem to still be doing bits now as i notice individual different drives display a red led outside the box. I am not able as yet to check its progress as i do not yet have a usable machine. not sure how long it should take to rebuild completely. Thank you for your valuable assistance. Peter
July 4, 201313 yr Author Update I now have my windows desktop back after a re-install and unraid parity is ok thanks again. Peter
Archived
This topic is now archived and is closed to further replies.