April 4, 201115 yr Hello, I've had an MD-1510 array for a little over a couple years. In that time, I've added drives but haven't had any failures until now. Now, one of drives (a WD10EADS) has a red ball next to it in the web interface (and 8 errors in the last column). In the Troubleshooting wiki, it suggests running the smartctl command. I ran 'smartctl -a -d ata /dev/sdg' and got the following: smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, 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. sdg is listed as the device of this failed disk. Smartctl works property on other drives like sda for example. I'm using unRAID 4.7 and I'm not sure how long ago the drive failed but I don't think it's been more than a few days. Any advice on getting the smartctl command to work on this device? Should I attempt to reconstruct one the same drive or just replace it and then reconstruct? Thanks for any help offered.
April 4, 201115 yr Capture a full syslog and post it. Then shutdown the server, check the SATA cables to and from this disk, and then power back up. Try your syslog again. Unless you are running a not-fully-supported controller (like the BR10i for example) the smartctl syntax you used should work.
April 4, 201115 yr Author Thanks bjp I've attached the before and after reboot syslogs. After rebooting, the smartctl command worked and I've attached the output of that as well. syslog-2011-04-03.txt syslog-2011-04-03-afterreboot.txt smart.txt
April 4, 201115 yr SMART report looks good... may just have been a misbehaving cable. Someone else may be able to help interpret the syslog... not a forte of mine! I'd say, keep a close eye on the drive, but you're probably ok!
April 4, 201115 yr Author No, it is not green. Should I unassign, reassign, and reconstruct the disk?
April 4, 201115 yr No, it is not green. Should I unassign, reassign, and reconstruct the disk? It appears the drive was having trouble coming out of standby when unRAID was telling it to. The reports on the drive look fine to me. You will need to stop array, unassign drive, start array, stop array, assign drive back, start array. That should start a rebuild of the drive.
April 4, 201115 yr Author Thanks prostuff1! Data-Rebuild is in progress. Update: After about 400 minutes the rebuild finished and all is green Thanks everyone!
Archived
This topic is now archived and is closed to further replies.