xthursdayx Posted February 23, 2019 Share Posted February 23, 2019 I'm having a confusing issue that I hope someone here might be able to help me with. I recently pre-cleared a new, larger hard drive with the intention of replacing one of the existing drives in my array. After stopping the array and replacing the old drive with the new one the data began rebuilding from parity as usual. However, after a number of hours, my server became inaccessible via the (online) GUI or ssh. I don't have a monitor hooked up to the machine directly, but the indicator LED on the front of my server showed no sign of operation. Unsure what to do, I waited long enough for the rebuild to have theoretically completed and then restarted my server by pressing the power button. After this reboot, I accessed the GUI and found that the disk data rebuild was starting over (or perhaps starting over where it had previously stopped?), so I left it alone and let it do its thing. However, once again the server is now inaccessible and the LED is solidly black. I'm going to wait again until the end of the day before taking any action (the last estimate I saw before losing access to the server showed that the parity rebuild should finish around 7pm today), but I was just wondering if anyone has any idea why this is happening, if the disk data is actually being rebuilt despite the fact that the server seems to be frozen, or what I might be able to do to fix/solve/avoid this? Thanks for any help or suggestions. Quote Link to comment
Frank1940 Posted February 23, 2019 Share Posted February 23, 2019 First tell us what version of Unraid you are running? You should also provide information on what plugins, Dockers and VM's you have installed. One thing I would suggest to install a monitor and keyboard (temporarily) on the server. Then, when you reboot, select the 'Safe Boot' option from the Boot Menu. The rebuilt will start again. Let it run to see if it will finish the rebuilt. It appears that you have another problem but let's see if the rebuilt can be finished so that we have only one problem to deal with. Quote Link to comment
JorgeB Posted February 23, 2019 Share Posted February 23, 2019 5 hours ago, zandrsn said: or perhaps starting over where it had previously stopped? If interrupted it will always start from the beginning. Quote Link to comment
xthursdayx Posted February 24, 2019 Author Share Posted February 24, 2019 4 hours ago, Frank1940 said: First tell us what version of Unraid you are running? You should also provide information on what plugins, Dockers and VM's you have installed. One thing I would suggest to install a monitor and keyboard (temporarily) on the server. Then, when you reboot, select the 'Safe Boot' option from the Boot Menu. The rebuilt will start again. Let it run to see if it will finish the rebuilt. It appears that you have another problem but let's see if the rebuilt can be finished so that we have only one problem to deal with. I'm running the most recent rc, a bunch of dockers and plugins (e.g. community apps, user scripts, CA backup, Speedtest, Sonarr, Plex, Radarr, ruTorrent, NZBget, etc), and one VM (but it is off), however nothing has really changed with my dockers or plugins in months. I'm going to follow your advice about hooking up a monitor and keyboard, but I'm wondering when/if I should do a hard restart of the server. It's been 'rebuilding' since yesterday afternoon and apparently frozen/unresponsive/inaccessible since I woke up this morning. Any ideas? Quote Link to comment
xthursdayx Posted February 24, 2019 Author Share Posted February 24, 2019 Okay, just to update. Did a hard reboot, booted into safe mode. I've been running 6.7.0-rc2 though I now see that 6.7.0-rc5 is available. I've attached the server's diagnostics here. I will try to allow the rebuild to complete while in safe mode for now, but hopefully we can figure out what is at the root of the problem. vulftower-diagnostics-20190223-2016.zip Quote Link to comment
xthursdayx Posted February 24, 2019 Author Share Posted February 24, 2019 (edited) 51 minutes ago, BRiT said: If I understood the kernal bug discussions properly, you should update to latest RC before trying anything disk intensive because of the massive regressions in earlier Kernals. Thanks for the heads up @BRiT! I upgraded to the latest RC before beginning the rebuild, so hopefully that helps. Edited February 24, 2019 by zandrsn 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.