Hi guys,

 

I have 4 x 4tb hard drives and just swapped out the parity drive for a 10tb western digital white drive that I shucked. The parity rebuild started and seemed to complete after about 20 hours but during the rebuild I was unable to load the dashboard page but could load other tabs. After the build completed I was unable to also load the docker page and eventually couldn’t load the GUI at all. I eventually hard rebooted the server and it came back up and everything seems fine, the issue now is that it had to start doing another parity check because of the hard reboot and again I can’t load only the dashboard page. 

 

I really could use some help on this. Ps I can still mount my shares and still have access to the CLI. Before the hard reboot I tried restarting Nginx and that didn’t work. 

At a minimum does someone have steps to gracefully shutdown the server via CLI so it won’t try to do another parity check after the reboot. 

Try getting the diags on the console, during or after the parity check, by typing diagnostics

 

23 minutes ago, nanoblock said:

steps to gracefully shutdown the server via CLI

poweroff

or

reboot

 

I started running the diagnostics but its still running and has been going about 7 or 8 minutes so far "Starting diagnostics collection" is that typical or does it normally only take a minute or two.

Looks like it finished but it was just sitting at that screen in terminal. Any insight you guys have based on the logs.

tower-diagnostics-20190313-0828.zip

I also tried the reboot command and it does not seem to actually fully reboot the server.

3 minutes ago, nanoblock said:

Looks like it finished but it was just sitting at that screen in terminal. Any insight you guys have based on the logs.

tower-diagnostics-20190313-0828.zip

Those are old diagnostics (from 13th March).    I suspect that the diagnostics command did not actually complete (it gives feedback when it does).    That normally means that something is ‘hanging’ (which would also explain your dashboard problems).

1 minute ago, nanoblock said:

I also tried the reboot command and it does not seem to actually fully reboot the server.

Do you mean that it never rebooted at all or something else?

when i issue the reboot command i get this

 

Broadcast message from root@Tower (pts/3) (Tue Apr  2 09:57:36 2019):

 

The system is going down for reboot NOW!

 

but it does not actually reboot. The parity check is still running so could it be preventing it from rebooting. I have no way in the gui to stop the parity check because i cant get to the dashboard tab to stop it or issue a reboot from there,

ALso tried shutdown -r now and same message but after a couple minutes i log back in to the cli and look at uptime i see this

 

root@Tower:~# uptime

 10:09:48 up 14:49,  2 users,  load average: 137.49, 134.82, 127.46

i hard rebooted the server again and everything comes up fine. I stopped the parity check from running and downgraded to rc5 instead of 6. I am going to try and reboot gracefully and see if the parity check needs to run again and let it run. 

seems like there is something seriously wrong. I re added my second cache drive back and accidently blew away the other and now lost all my dockers etc... but now i am rebuilding them and to downlaod 1 docker image is taking a lifetime i do not understand why. I am uploading a current diagnostics.

tower-diagnostics-20190402-2227.zip

Diags are just after rebooting, so nothing to see, cache is already formatted as a pool.

Yes the cache is a pool but I think when I added the second cache drive back and it tried to add it back to the pool  i formatted the wrong one.  I have rebuilt everything and all seems to be working for now. I have not run another parity check on the new parity drive i added so I will see what happens when that runs again. Thanks all for the help for now.