Running Unraid 7.0.0. Been on unraid for a while, but not super tech savvy. Recently my docker containers all stop working and wouldn’t start back up. I shut my server down and it wouldn’t boot back up. Removed my flash drive, put it in my Mac and saw a FSCK0000.REC file. So, I backed up my flash drive, replaced all bz files, and deleted the FSCK0000 file. My server booted up initially, but crashed again. Now when I try to boot up I get a line that says “FAT-fs (sda1) volume was not properly unmounted. File may be corrupted.” It also suggests that I run fsck. I don’t know what fsck is, how to run it, nor could I run it on my server because it won’t even boot in safe mode. If there is anyone that can help me, please explain it like you’re talking to a noob. Pic below, Ty.

Edited February 17Feb 17 by weezysteel
Added more information

The config folder from your flash drive or flash backup is all you need to get your configuration going again on whatever version.

I have the config folder on my flash drive. Is there a file that’s corrupt, or a file I need to delete?

fsck is linux check for FAT. You can put it in your Mac and let it check it instead.

I did the fsck check on my Mac. It reported 4263 files and 1,749,755 clusters. I purchased a new flash drive, installed a fresh Unraid 7.0, and copied my config folder from my last drive. Now it’s not giving me the FATfs error, but it’s still not booting and stopping at the same spot. Also tried booting from a different usb port (2.0). (Pic below)

Edited February 18Feb 18 by weezysteel
Added more details

Willl it boot if you don't put your config on it?

Yes, it boots with a clean config folder. Is it possible that I downloaded the wrong version of Unraid? Like I ‘m booting version 7.0, but my config folder is for 6.12 or something else? If that’s the issue is there a way for me to determine what version my configuration is for?

Edited February 18Feb 18 by weezysteel
More information

UPDATE: So far I’ve been adding one file at a time to the config folder. Flash drive was booting with each file until I added “vfio-pci.cfg” and “vfio-pci.cfg.bak.” I was going to delete those files then reboot, but I dropped the flash drive in a cup of tea (worst luck in the world).

I put the flash drive in some rice. Now I’m waiting 48 hours to resume troubleshooting. If you have anything to add I’m all ears (or eyes).

6 hours ago, weezysteel said:

“vfio-pci.cfg”

That is about VM passthru devices. Do you have any?

Yes, I do. I’ve had that vm set up with pass through for months. What would make it act wonky now?

Have you changed any hardware at all recently?

No, not at all. I’ve added two hard drives to my array, but my vm stores data on my ssd.

All systems go. It was the vfio-pci.cfg file. Deleted it and everything is working fine. Thanks for your help.

Soooo, I’m still having issues. After getting Unraid to boot I updated my plugins and docker containers while my system did a parity check, which took 2 days. I decided to do some cpu pin isolations to optimize performance. This required me to reboot the system. The tower shutdown, but now I can’t get it back up again. This time the boot seems to complete, but I can’t open the login page on any of my devices. I’m getting the message again that says “volume was not properly unmounted some data may be corrupt.” I’m also getting a new error message (screenshot below) and I have no idea what it means.

Can you get diagnostics from command line?

Tried logging in again and was successful, but I’m assuming I’ll have the same issue if I shut it down again. Anyway, I grabbed a diagnostic.

tower-diagnostics-20260222-2028.zip

Fix this and see if it helps

Feb 22 15:18:09 Tower root: Fix Common Problems: Error: Docker Application Plex-Media-Server has multiple CPUs pinned to isolated CPUs

You should also run memtest since btrfs is detecting data corruption on both pool devices

Fixed the cpu pinning situation, but still having the same issue on initial boot. Grabbed another diagnostic (below), and now I will do a memtest as suggested.

tower-diagnostics-20260223-1843.zip

Edited February 24Feb 24 by weezysteel
More information