Hi,

Sorry for going against protocol here, I'll add the syslog tonight when I'm with the server again - but maybe it's a problem that there is a quick solution to.

I am running unRAID 6.3.2 on a server with a cache pool (2×525 GB SSDs), one parity disk and 7 data disks (formatted with XFS, ranging from 500 GB to 1.5 GB). After getting rid of a faulty RAM chip, everything has been running smoothly over the past month or so.

 

The one problem I have (which wasn't there from the get-go but started occuring a few weeks back) is that the server won't properly reboot/shutdown, neither from the GUI nor the command line (via SSH). From what I recall, the syslog stated that drives could not be unmounted. I either have to hard-reset/hard-poweroff the server, or shut it down using a force switch with the shutdown command (again, not at the server ATM, I'll add that info later tonight). The problem, of course, is that this invokes a parity check on the next boot.

 

Any quick suggestions on what the problem might be here? I'll have to shut down the server tonight, as I need to install an additional SATA controller card, re-run a few SATA cables and move it to another physical location in my home office and would like to avoid the parity check running over the next 24+ hours afterwards. I'll try any suggestions anybody may have until then and will post log files and diagnostics if the problem still occurs tonight.

 

Thanks for any suggestions anyone may have!

Are you logged into an ssh session with the current directory within /mnt?

Barring that the other issue I've seen is with a corrupted docker.img file where it can't umount it

Sent from my LG-D852 using Tapatalk