A continuation of my issue from this thread: https://forums.unraid.net/topic/191010-rebooted-unraid-server-after-vm-issues-cache-server-not-mounting-due-to-filesystem-issue-btrfs-on-nvme-drive/#comment-1560780

I had a RAM stick fail which caused file corruption on my cache drive which then wouldn't mount.

After fixing the RAM, deleting the bad files which belonged to my VM (or so I thought), and rebuilding the docker image, everything started working again.

I realize now though that my VM came back automatically because it seems I never deleted those files. Running a scrub again now shows the same bad files in the syslog.

I stopped the VM and tried to run the scrub again, but it immediately aborts:

So now I am trying to remove the VM from my server through the UI, but it just hangs and does nothing. If I refresh, it seems nothing happened at all.

If I try this:

It will just stay stuck like this:

And if I refresh it just goes back to saying stopped.

How can I make sure this corrupted VM and it's files are completely removed?

Attached are diagnostics.

Also running another memory test just to verify the RAM is good again.

thearchive-diagnostics-20250612-1415.zip

Update
I let memtest86 complete 2 runs and there were no errors.

Started the server back up, and manually deleted the offending files by navigating to the folder for the VM and deleting them from my Windows machine. They seemed to delete fine without giving an error.

I then decided to stop the array to see if that or putting it in maintenance mode would help.

Now the server is stuck trying to stop the array. It seems that it can't unmount the cache because it's busy:

I'm not sure where to go from here.

New diagnostics attached.

thearchive-diagnostics-20250612-1621.zip

Edited June 12, 20251 yr by VulpesDormiens
typo

Update again

Found that running the command umount -l /dev/loop2 allowed the cache drive to be unmounted.

Started the array in maintenance mode, but don't think I can do much there I realize.

Started the array normally, and those files I thought I deleted for the VM are right back there. Perhaps during my previous issue the docker image was never deleted either.

Attempting to scrub the drive still aborts immediately , and I still need to run that command to be able to stop the array.

Also, the docker tab shows: Docker Service failed to start., and the VM tab shows: Libvirt Service failed to start. Not sure if this is expected or can point towards the issue.

thearchive-diagnostics-20250612-1811.zip

If the scrub is aborting, there's an issue with the filesystem, recommend backing up and reformatting.

5 hours ago, JorgeB said:

If the scrub is aborting, there's an issue with the filesystem, recommend backing up and reformatting.

Yes, late last night I decided I was going to have to just reformat the drive. Fortunately with your help the other day I was able to get backups of everything, and I'm running again without too much hassle.

Switched to xfs for the cache, although honestly not too sure if it makes a significant difference for me.