June 28, 201214 yr I recently had a hard drive making the click of death so I began the process of backing it up. I had an extra drive empty of the same size so I copied the data over and then removed the drive. I followed the process described here: http://lime-technology.com/wiki/index.php/FAQ_remove_drive When I booted the system back up I mounted the disks at first without a parity drive to make sure I knew which drive was the parity one. Once I verified this I stopped the array and designated the parity drive and started again. Since this moment I have not been able to access the unRaid GUI, I get timeout error when access it through the browser. I am able to telnet the system and the drives are mounted and I can access them through the network. I do not see a parity drive in the /mnt/ directory but I cannot remember if it is supposed to be shown there. I don't want to restart the system since I'm worried it doing it's parity check and I do not want to interrupt that. Any suggestions to fixing this issue? I guess if it is doing the parity calculations currently then that is fine but I'm worried the system is just sitting there doing nothing. I am on version 5.0-rc3 I ran the permissions script when upgrading from 4.7 and everything was working fine prior to removing the failing drive.
June 28, 201214 yr Parity does not appear under /mnt. Give it 30 min and if the gui doesn't respond I'd restart via telnet. See here: http://lime-technology.com/wiki/index.php/Console#To_cleanly_Stop_the_array_from_the_command_line After the array is stopped enter: "shutdown -r now" The disk rebuild should restart when the array is started.
June 28, 201214 yr Author Thanks for the advice and now the GUI is responding and doing the parity sync.
June 28, 201214 yr I recently had a hard drive making the click of death so I began the process of backing it up. I had an extra drive empty of the same size so I copied the data over and then removed the drive. I followed the process described here: http://lime-technology.com/wiki/index.php/FAQ_remove_drive I wonder why you wanted to go through this complicated process rather than just replacing the failed drive and allowing unRAID to rebuild the data onto the new drive?
June 29, 201214 yr Author I recently had a hard drive making the click of death so I began the process of backing it up. I had an extra drive empty of the same size so I copied the data over and then removed the drive. I followed the process described here: http://lime-technology.com/wiki/index.php/FAQ_remove_drive I wonder why you wanted to go through this complicated process rather than just replacing the failed drive and allowing unRAID to rebuild the data onto the new drive? Yeah I see your point and it really has to do with the order that the events occurred. I added two new drives and then a week later one of the old drives began to fail with the clicking. I see what you are saying which would be replacing the failing drive with one of the new ones but I had already added them to the array and began writing data to them. I guess I could have copied over the data from one of the new ones and then removed it from the array and had it replace the failing one but I didn't think of that.
Archived
This topic is now archived and is closed to further replies.