ttoni

I replace it.

Same here

In the last couple reboots I did i have not able to boot back up, it fails see picture (boot2.png, boot4.png). It passes the unraid blue screen (boot1.png) but it fails to mount /boot ?!, Even if i reboot again still stay at screen (boot3.png) The fix was to unplug the usb drive and plug in back in and it booted normally, but right now it doesn't boot , it shows the same errors. I tried on current server to boot and reboot other usb drive with unraid and it boots fine. I tried to put the problem usb drive it in other server and it boot fine. I plug in the problem usb drive in my computer and it shows fine all the files and no errors detected. Is the usb drive failing ? Should i replace it ? Please let me know what diagnostics i can provide.

I'm well avare of it may lead to broken backups, i'm wiling to take that risc. I'm not asking to be a default behaviour, just a optional flag that can enable the feature, and maybe allow it only on snapshot enabled filesystem like ZFS and BTRFS. In my particular usecase, I have databases and long running workloads on some LXC containers, by stopping the container to do a backup may lead to more problems to the running container state because the process inside is killed unexpectedly. It would be great for me for the backup process to do a snapshot and backup that without restarting the container or some other way to do the backup. I use ZFS for my unraid setup and take snapshots without stoppings any VMs or containers. I have this exact situation on certain of my docker containers and VMs running on my unraid server, the backup plugin Appdata Backup has a toggle "Skip stopping of container?" and VM Backup has this feature "List VMs to backup while running" -> "VMs backed up via snapshot will not be shutdown" which i use to skip only certain items. Of course both have big warnings that it may lead to broken backup.

Very great plugin! I have been using it since you release it and it runs flawlessly One thing i wish it had: To do backup without restarting the container.

I wanted to setup a second unraid instance into a virtual machine on my unraid server. I plugged the usb drive and left it planning to setup later remotely. After some hours i logged into the server and i was greeted by this message: I'm still on unraid 7.1.1 and avoided upgrading due the docker network and other issues that where on next versions Here when i have both plugged in It seems is taking the wrong usb (the usb 2.0 is the new one inserted) and the correct one is the Samsung Fit I just plugged in no reboot, no stopping / starting the array. tardis-diagnostics-20251008-0917.zip

Sorry to hijack this thread but i was ready to make a thread regarding this similar issue , should i post here or create a new thread ?

I can also confirm in my case that downgrading from 7.1.3 -> 7.1.2 still didn't fix the connectivity issue for me. Almost immediately after reboot or after a few minutes the outbound connectivity got lost on host , but strangely not inside docker containers, lxc containers , or VMs. For me disable "Host access to custom networks" is not a solution since the feature is used. What fixed for me was to downgrade back to 7.1.1.