January 2, 201610 yr After all my recent parity check issues, it finally finished. I did not recover my user shares, nor my dockers, nor my VM, so I figured I needed to reboot the server. I tried to stop the server, and it's gotten stuck, with this showing along the bottom... /unassigned.devices/include/lib.php on line 66Unmounting disks... I then tried to force it to reboot using Putty (shutdown -r now), but that didn't do anything. I then opened another/separate putty window, and tried (shutdown now), but that also didn't do anything. I really don't want to have to hard boot, and risk screwing up parity after suffering all day, but I don't know what else I can do to get my server working again.
January 2, 201610 yr After all my recent parity check issues, it finally finished. I did not recover my user shares, nor my dockers, nor my VM, so I figured I needed to reboot the server. I tried to stop the server, and it's gotten stuck, with this showing along the bottom... /unassigned.devices/include/lib.php on line 66Unmounting disks... I then tried to force it to reboot using Putty (shutdown -r now), but that didn't do anything. I then opened another/separate putty window, and tried (shutdown now), but that also didn't do anything. I really don't want to have to hard boot, and risk screwing up parity after suffering all day, but I don't know what else I can do to get my server working again. Something is keeping your disks busy.. Try: PS -elf | grep disk This will show you what processes are doing something to the disks.. See if you can find out what it is and kill it.. If you cannot find what it is then do a kill <procid> (the procid is the number that is reported by PS -elf). If that does not work kill -9 <procid> (that allways works and forcefully terminates processes.. Als something you'd rather not do but better then for rebooting the whole system..
January 2, 201610 yr Author thanks for the advice. I'll keep this bookmarked for use later, but I ended up hard-booting the server to get it responsive again. Of course it resulted in needing another parity check; which is what caused the problem in the first place. So, I'll just have to hope the parity is okay, until I get some help with what caused the server to get jacked up during the last parity check.
January 2, 201610 yr Community Expert There is a plugin called Open Files which will let you see what processes have which files open and let you kill them if you want.
January 2, 201610 yr Author There is a plugin called Open Files which will let you see what processes have which files open and let you kill them if you want. Sounds good, but the server was completely locked, so I couldn't have opened that plugin anyway[emoji34]
Archived
This topic is now archived and is closed to further replies.