I have a 7.2.5 UNRAID system that had just started a drive rebuild. I noticed that the Parity drive was generating a ton of read errors so I was going to Stop, Reboot the array and restart the rebuild. After issuing the Stop it has been in the "Array Stopping - Sync filesystems" status for a couple of hours. No disk activity is indicated but it shows very high CPU usage on all four cores.

Any recommendations on what to do next ? Reboot, Shutdown, power off ? I suspect I am screwed no matter what but any advice on how to recover from this would be greatly appreciated.

See if you can get the diagnostics, or at least the syslog, then type "reboot" in the CLI, if it doesn't start to reboot after 5 minutes, you may need to force it.

I hooked up a monitor to my server and this what it shows.

My attempt to get diagnostics hung.

Another console pic.

That last line in your photo suggests you have additional things to be concerned about.

Force reboot then

Attach Diagnostics ZIP to your NEXT post in this thread.

It does, it suggests filesystem issues on disk9, check filesystem on that disk after rebooting You will also need to think about moving on from reiserfs, Unraid 7.3 no longer supports it.

OK, as indicated above I have tried to get diagnostics but I don't know how much will be in the file. I will check the USB drive and also retry after I get the server running again.

I have already tried a CLI REBOOT and a console SHUTDOWN, neither of which worked. I will force a power down and see where that leaves me.

I was about halfway through converting this servers' 15 drives to xfs. Disk9 had just been cleared to an xfs disk in preparation for its own conversion to xfs. However, using the MOVE function of the Web Interface stopped actually moving files after just a few GB. It did keep on copying so all files remaining on it are duplicates. I had tried to use the Web Interface to DELETE them but that failed as did trying to do it from an SMB share. So I agree, it's file system is hosed and I was just going to let the reformat take care of it.

Hopefully back shortly with diagnostics.

Copy is faster and safer than move, then you can just reformat after everything is copied. You can't move files from a disk if the disk is readonly since the source files can't be deleted.

Just exclude the disk to be formatted from user shares, and the duplicates won't appear in user shares.

Alright, first I want to sincerely thank everyone for your responses. I was very worried I had an unrecoverable situation with inevitable data loss. Your advice helped put me at ease and encouraged me to push forward.

I was most concerned that a power off from the state my server was in would leave me with an unusable parity disk. Thankfully, I now have a disk rebuild running that looks promising :-) Currently at 270GB with 14TB to rebuild it's estimated to be 4 days (old hardware) so I will return with the results then.

Thanks again !