wazkaren Posted January 28, 2017 Share Posted January 28, 2017 I have a drive that has been disabled (red ball). But it appears to be healthy, no smart errors, and data appears intact on the drive. I understand that once the drive is red balled I have to rebuild the array. But there is no option to do a parity rebuild, only start/stop array and reboot. I'm not sure what to do next. Any thoughts? I attached the syslog Thanks, Greg syslog-2017-01-28.txt Quote Link to comment
SSD Posted January 28, 2017 Share Posted January 28, 2017 A drive is not kicked from an array randomly. It is done when unRaid loses contact with the drive our a write fails. Although a failed drive can be the reason, more often it is a bad our loose cable, our something else in the connection chain, causing it to happen. It is a little optimistic to think that the drive connectivity is fine because is looks fine after a reboot. When a drive is kicked from the array, unRaid simulates the drive contents. So you should be seeing its data just fine, albeit a little slower than normal. If the drive is perfectly healthy and you have corrected the connectivity issue, you could stop the array, resign the failed disk to its slot, and have it's contents rebuilt. You do not want to rebuild the array because you'd lose your ability to rebuild your drive right when you need it most! Quote Link to comment
wazkaren Posted January 28, 2017 Author Share Posted January 28, 2017 Thanks. I did replace the drive 2 weeks ago so bad cabling does seem likely. When I checked the contents of the drive the array was stopped (I checked from a the shell). The drive is assigned to it's slot so I'm puzzled as to why the rebuild button is missing? I will double check the cabling and reboot. And thanks for the warning about not rebuilding the parity disk. Thanks, Greg Quote Link to comment
JorgeB Posted January 28, 2017 Share Posted January 28, 2017 To rebuild to the same disk you need to unassign it, start the array, stop the array, reassign it and start the array to begin the rebuild. Quote Link to comment
trurl Posted January 28, 2017 Share Posted January 28, 2017 In order to get unRAID to rebuild the disk to itself you will have to start the array with the disk unassigned and then stop and reassign it again so unRAID thinks you have replaced it. Then it will let you rebuild the disk. After you get it working again, you should consider upgrading to a supported version of unRAID. Quote Link to comment
wazkaren Posted January 28, 2017 Author Share Posted January 28, 2017 Ok, thanks. My current processor is not 64-bit. I'm looking into upgrading so I can move to the latest version of unRaid Quote Link to comment
wazkaren Posted January 28, 2017 Author Share Posted January 28, 2017 Turns out I'm not really awake yet. I double checked and the array WAS started when I checked to see if the files are there. Glad I listened to you guys and did not start a rebuild. I still can't figure out what's wrong the the drive though. Smart test passes Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.