VulpesDormiens

I am struggling to get the server running. After installing, the logs do not show an admin password for me to use. I also noticed that the docker has no point assigned: But I am unsure how or what port should be configured. Perhaps these are related? I tried to telnet to the docker to get another login as another comment suggested, but assume it having no port number is not going to let that work. Any suggestions? ts3server_2026-03-22__14_17_56.894186_0.log

@DrPeril , unfortunately no. I've just been dealing with the annoyance and just hoping I don't have to reset the server too often. I also feel like it should just work. Perhaps we are the only two that have ran into this.

Whenever I reboot the unraid server itself, I have to reconfigure the USB devices for my home assistant VM: After a reboot, these are all unchecked. Not an issue when only rebooting the VM. Is there anyway to prevent this setting from being cleared?

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.

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

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

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

Thank you so much Jorge! You're a life saver. I remade the docker image following those instructions, and didn't even need to do the second part. All of my apps (and my VM which I don't understand how) reappeared and all seem to be working as they were before.

Awesome! Looks like it was just my VM that had corrupted files, which fortunately I do have backups for. Now I can just re-install and restore that VM. That leaves me with the docker images now. The appdata is still there on the drive, but looks like unraid does not know they are installed. Do you know how I would go about repairing that?

Ran a few different tests to determine 1 of my 4 sticks was bad. Ran a final test on the 3 good ones (will switch to a more optimal setup later) to confirm they were good. Ran the scrub again and looks the same: What would the next step be?

Ahh, that makes sense. I ran the scrub and here are the results: Attaching diagnostics just in case, because I'll be gone at work. Running memtest while I'm gone at work, but I'm getting some errors within the first minute: thearchive-diagnostics-20250610-0809.zip

Thanks for the reply! I ran that command, and attached are the new diagnostics. Out of curiosity, where in the diagnostics are you looking? I tried to go through them, but was lost. thearchive-diagnostics-20250609-1802.zip Edit: I realized after starting the array again that the cache drive mounted! And it looks like I can see the files and everything that should be there. I'm not sure what changed from all the messing around I did earlier that it works after re-staring the array this time. Maybe the diagnostic can reveal an issue with the drive I can address. However, the dockers and my VM are still not appearing, so I need to figure out how repair that.

Reading the documentation here: https://docs.unraid.net/legacy/FAQ/check-disk-filesystems/ It states: If the file system is XFS or ReiserFS (but NOT BTRFS), then you must start the array in Maintenance mode, by clicking the Maintenance mode check box before clicking the Start button. This starts the Unraid driver but does not mount any of the drives. If the file system is BTRFS, then make sure the array is started, and NOT in Maintenance mode. However, I am only able to run the check in maintenance mode, although it shows that the drive is btrfs. That documentation also says that the scrub command should be used for btrfs, but I can't as it shows it is only available when the filesystem is mounted, and not being able to mount it is my problem. I'm given this warning about running the Check with --repair But I can't find anything else that I can do. Is there any other step I can take before doing this?

When I woke up this morning, my home assistant VM was being odd, clicking some menus in the UI would not open anything. I decided to reboot the unraid server to see if that would fix it. While rebooting, it showed the message: Array Stopping Retry unmounting disk share(s). I waited it out and eventually it was able to reboot after a minute or so. When it came back online, the cache drive was showing a size of 0B and a file system problem. I did get an alert after rebooting that an unclean shutdown was detected, and it starting running a parity check that seemed to stall out. I stopped and started the array in maintenance mode to run a check on the drive. It showed this: The cache drive is NVME and formatted for btrfs. Attached are the diagnostics. Any advice on how to fix/recover the drive? I tried following this but got lost pretty quickly: thearchive-diagnostics-20250608-1334.zip

OK, awesome. I think I'm getting it. So now everything new will start on the cache, and be moved to the array whenever the mover runs? So having a share use the array as primary storage is just not the proper way to do it?