October 4, 200817 yr I recently had a disk go offline. I replaced everything in the chain except the disk.. It ended up being the cable. (which was the last thing I replaced, then the disk came online). I know the drive is good.. Smartctl shows 9 Power_On_Hours 0x0032 097 097 000 Old_age Always - 2857 SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 2857 - My problem now is the disk is in DISK_DSBL state, and it's not being rebuilt. When I stop the array, the RE-STORE button comes up. but there is no check button. When the array is started, the disk is being virtually read from all the disks, so the failed disk is not online or being rebuilt. Do I need to unassign it, then re-assign it in the devices page in order to trigger a rebuild?
October 4, 200817 yr What you need to do is Stop, Power down, physically remove the disk, power up and Start. Now Stop, and Power down again, re-install the disk, and power up. You should now see that Start will cause a rebuild of the disk. What's happening is that the system notices that the same disk is still plugged in that it has previously disabled. By removing the disk and starting, it erases past knowledge of the disk model/serial no. Then when you power down second time & re-install the disk, system thinks you installed a new replacement disk. Make sense?
October 4, 200817 yr Author Hmmm seems to be a wiki entry there already, but this is the text... Okay, the cable was loose, or I think the failure was a fluke - how can I get unRAID to reuse this same disk that it thought had failed? You can re-enable the hard drive and try to reconstruct it as follows: * Stop the array, go to the Devices page and un-assign the disk. * Reboot * Stop the array, go to the Devices page and re-assign the disk * Go to Main - system should detect a "new" drive for the one disabled, click Start to start parity-reconstruct of the disk.
October 5, 200817 yr WeeboTech - Hope you are back up and running. Did you try the device unassign / reboot / reassign method and find that it didn't work? If so, the wiki definiitely needs updating!
October 5, 200817 yr Author I'm all good now. I did as Tom suggested. Physically removed the drive, rebooted, Physically put the drive back, Rebooted. Tom, can you comment if just un assigning the device and rebooting would have been good enough? (like the wiki suggested).
October 5, 200817 yr I'm all good now. I did as Tom suggested. Physically removed the drive, rebooted, Physically put the drive back, Rebooted. Tom, can you comment if just un assigning the device and rebooting would have been good enough? (like the wiki suggested). Doh! [slaps hand to forehead], that would have worked as well....
October 5, 200817 yr Author Doh! [slaps hand to forehead], that would have worked as well.... OK, we know for the future!
October 5, 200817 yr Doh! [slaps hand to forehead], that would have worked as well.... OK, we know for the future! If I understand this correctly then in order to actually remove a disk and all it's data from unraid you would have to redo parity after removing the disk. Am I following correctly?
October 5, 200817 yr Author If I understand this correctly then in order to actually remove a disk and all it's data from unraid you would have to redo parity after removing the disk. Am I following correctly? Correct.
October 5, 200817 yr Doh! [slaps hand to forehead], that would have worked as well.... Whew! I wrote that part of the wiki and was worried there for a minute . My research at the time indicated that either would work, but the technique in the wiki seemed easier to do (no opening of the server required).
Archived
This topic is now archived and is closed to further replies.