LGFS

The problem I have with that : - It's manual, and not automatic on a schedule, like the plugin (I backup my dockers & flash every month) - I like the way I could choose a specific path - and thus could backup to a ready-made-usb if I wanted (especially for internal boot crash mitigation for example) I thus intend to migrate to TPM+Internal Boot with monthly backups to the old USB key, so I can restore to internal boot or boot from USB easily if need be. BTW, "Yes. Internal boot SSD/NVMe devices count toward your attached device limit." >> This is quite sad and should be changed.

I can confirm that backup + quick-formatting the same exact key in Windows + [manually copying 7.3.0 + old config folder] + "makebootable.bat" solved the problem for me, I now am on a stable 7.3.0 without any pb. Special thanks to @JorgeB for the diagnostics help !

Did you skip the "makebootable.bat" step by any chance ?

Yes, I just did a quickformat in windows and now it works... Complete mystery, just happy it's quite easy to just move the config folder tho.

I can confirm that backup + quick-formatting the same exact key in Windows + [manually copying 7.3.0 + config folder] + "makebootable" solved the problem. I chose manual copy because the unraid creator tool didn't work with my usb key (Sandisk) - the same USB key that perfectly works and holds my licence when inserted into my NAS... Thanks @JorgeB for helping diagnose the problem, I'll crosspost into 7.3.0 as well.

Added the last two, absolutely didn't see the file upload bar at the bottom of the posts, shame on me... Thanks !

I had the exact same problem.... Just tried to upgrad my DXP6800Pro to 7.3 and: - I can't connect to the GUI despite the terminal/console showing the right IP adress - Booting into Safe mode (no plugins) with or without GUI doesn't work...so it's not plugins ? It gives me the "Unraid Login" with the hypervisor error - but I don't think it's the VMBackup plugin errors because...safe mode ? - RE-updating fails every time. Thank the lord of the "previous folder" and easy rollback, I was able to simply plug my USB key into another computer and restore 7.2.5... Can it also be the USB partitionning ? Thanks for the help ! unraid-diagnostics-20260513-2101.zip unraid-diagnostics-20260513-2109.zip

You're lucky 😭 Just tried to upgrad my DXP6800Pro to 7.3 and: - I can't connect to the GUI despite the terminal/console showing the right IP adress - Booting into Safe mode (no plugins) with or without GUI doesn't work...so it's not plugins ? It gives me the "Unraid Login" with the hypervisor error - but I don't think it's the VMBackup plugin errors because...safe mode ? - RE-updating fails every time. Thank the lord of the "previous folder" and easy rollback, I was able to simply plug my USB key into another computer and restore 7.2.5... This makes me think, with the new internal boot : I plan on migrating to an NVME SSD that is absolutely a nightmare to access (Ugreen hidden OS SSD) Is there a functionnality like "when updating, backup boot to USB device" ? If this would have happened with only the internal device, I would have LOST IT Here are a bunch of diagnostics from all attemps (safe mode etc) Help is appreciated :-)

I just modified the IPV6 prefix. Since I'm using a custom br0 using "docker network create" this might not matter until the next update, will post & update OP to add this.

Here are: The 7.1.3 diagnostics, with the problem (lost the initial 7.1.2) The 7.1.4 with my manual fix I saw that in the diagnostics there was the "previous syslog" so you might be able to piece the puzzle together ? Since I fixed it, the only culprit to me was "just updating FROM 7.1.2" (whatever the final version : 7.1.3, 7.1.4_RC1, 7.1.4) Maybe there was a bug in 7.1.2 that allowed something that was removed.... NOTE: I was scared my effing IPV6 was leaked in the syslogs although I clicked "anonymyze", so you might see 2a01:e0a:xxx:xxxx with way more XXXX, I did a find-replace, need to educate myself on IPV6 unraid-diagnostics-20250625-2006_7.1.4 manually fixed.zip unraid-diagnostics-20250609_2247_7.1.3_br0 gone.zip

I did provide 7.1.3 diagnostics a while ago and removed them (here https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-714-rc1-available-r3912/?&tab=comments#comment-34470) My belief is that I might have been using a custom br0 with an IPV6 prefix that was NOT /64 everywhere in the system (like it ended up being /128 in the diagnostics but not in the GUI of the docker manager). Somehow, by removing and creating a new br0 with the correct prefix, it is working again. Since I fixed the problem, I don't think "fixed" diagnostics will help any more ? I'll try to provide my old 7.1.2 "working" diagnostics, 7.1.3 "failed" diagnostics and again, "fixed" 7.1.4 diagnostics to help the team, asap

Yes, this problem is also happening when going from 7.1.2 to 7.1.4, in my case. I'm also listing all those 3 versions for people that will also eventually end up destroying their custom networks by deleting network.cfg or docker.cfg in their USB/Flash folder like I did see sometimes. I did : 7.1.2 > 7.1.3 : lost br0 revert back to 7.1.2 : restored br0 7.1.2 > 7.1.4_rc1 : lost br0 revert back to 7.1.2 : restored br0 7.1.2 > 7.1.4 stable release : lost br0 (lost my patience there) revert back to 7.1.2 : restored br0 7.1.2 > 7.1.4 stable release : lost br0 again and my mind with it, decided to fix it myself There should be a simple check to backup custom docker networks OR to allow creating them in the GUI..... Right now, I don't know of any other way than to do it via terminal

For a reason unknown, going from 7.1.2 to 7.1.3, back and forth, removed the "Custom : br0" network I had in docker, to attribute to containers a custom IP. Worse, when you go into Settings > Docker, you can see for example that br0 seems to be enabled... Long story short, that's because the br0 is "available", but is not "enabled". This might be because of static IP adresses and netmasks, that didn't pose a problem before and suddently, any netmask other than /24 for IPV4 and /64 for IPV6 is a problem.... I solved it by doing the following. Remove all custom networks from your dockers, set them to "none" Make sure to stop VMs, stop Docker. Have your Network Settings setup to "Enable Bridging = Yes" Bridging members of br0:eth0 if that is your interface Prefer a static ip address for IPV4 and ipV6 !! Make sure your static IPV6 address has a /64 netmask and your IPV4 a /24 netmask Go back to Settings > Docker > choose IPVLAN Enable IPV4 custom network and IPV6 if needed Start/enable the docker service Make a first assesment in your docker templates to see if the custom networks went back online automatically just by correcting netmasks. Please report this if it did for you. If the network didn't create itself : Enter the terminal This last docker command is valid for IPV6 and IPV4 as well Go back into your docker templates and select the new "Custom" network Remember in the docker template to enter the "IPV4,IPV6" addresses separated by a comma Example for my adguard (IPV6 hidden for privacy purposes, but I use the same last numbers as the IPV4 address to help) 192.168.8.252,xxxx:xxx:xxx:xxxx::252 You should be good to go. REMEMBER this is now a "custom network" that will NOT be preserved if you don't change that

The loss of Internet (local still works) and connectivity issues has been acknowledged in https://docs.unraid.net/unraid-os/release-notes/7.1.3/ Version 7.1.3 2025-06-04 This is a small bugfix and security update release. UpgradingKnown issuesSome users are losing internet connectivity after updating to this release. We are working on a fix, but if you are affected please roll back to 7.1.2 for now (Tools → Downgrade OS will get to your previous release)

I'm on the "tit-WAN-nic" will all the users that have lost some form of docker connectivity (link to https://forums.unraid.net/bug-reports/stable-releases/713-unraid-connect-error-r3898/) I would not recommend this update

Merci pour la solution. Je dirais également de vérifier tout ce qui ethernet aussi, non? Genre, attention à activer le DHCP - ou faire attention que l'adresse statique soit définie par le routeur et pas par la machine ? Faire une capture d'écran des configuration de connectivité des dockers (qui est en host, en bridge, etc) pour ensuite bien les remettre avec les nouvelles cartes réseau ?

Just open your router to find the new IP address of your NAS. If it's the same as before, check for ports that might not be open. Unraid GUI uses port 80.

Native Cloud Backup. Coming from a Synology and it's the ONLY feature I'm missing. I have to use CloudBerry inside a Docker container to upload to backblaze, because: - I failed to setup rclone, it is WAY too difficult, even with a few tech skills - I want file-by-file, unencrypted backups (and not blocks like duplicacy or other solutions) (i only upload photos of my holidays, not worried about privacy AND won't have to decrypt using a method I might have forgotten)

T.H.I.S. Coming from a synology, I was shocked at how difficult it was to set up a simple backup solution. I had to buy a cloudberry backup key, set-up the docker properly, set up the backup themselves... Not a nightmare, but way, way harder than synology's. We should have a native plugin, with: - connexions to all major cloud API/providers, including S3/Backblaze - the choice of encryption or not : i chose not to encrypt files, so as if my server crashes, I don't have to buy a new one and look for file decryption when downloading them. - bloc uploading of changes of course (partial uploads) - file-by-file uploading or .PART files (for people that want to encrypt everything) : i'd like the ability, like synology, to download only one file if needed Thanks!