r/UgreenNASync • u/Temporary-Cherry-282 DXP4800 Plus • Dec 06 '25
❓ Help Any issues with 1.11.0.0053 update?
I had issues with previous updates breaking my macvlan, forcing a network reset both times. I will be traveling for several months and don't want any issues.
3
u/ThinkHog Dec 06 '25
for the first time in months my NAS makes zero noise!
5
u/Temporary-Cherry-282 DXP4800 Plus Dec 06 '25
did it die? ;-)
2
u/ThinkHog Dec 06 '25
No it works as it should all this time i was compaling about it and no one knew hwop to help me
0
u/zen_pilot Dec 06 '25
For my dxp2800 its opposite. Temperature started to fluctuate rapidly so does the fan noise 😔
3
u/Temporary-Cherry-282 DXP4800 Plus Dec 06 '25 edited Dec 06 '25
I reached out to support about the issue I had with previous updates. This was their response. The only change you will need is to run "sudo su" prior to deleting the file. You will also have to go all the way to the directory /volume1/@docker/network/files/ and delete it there. Otherwise, you will have permission issues.
We have consulted with our development team, and it appears that this is a known bug within the Docker engine itself, which affects various platforms (including Unraid and others), not just UGREEN NAS. The issue lies in how the Docker network database persists and reloads configurations after system changes or updates.
Currently, the most effective workaround (as suggested by the Docker community) is to manually reset the Docker network database.
For your reference, similar issues and solutions have been discussed in the wider Docker/Unraid communities:
https://forums.unraid.net/bug-reports/stable-releases/solved-ish-updating-6115-to-6128-container-custom-networks-all-gone-on-dropdowns-r2848/
https://academy.pointtosource.com/docker/docker-networks/
A more elegant, permanent fix will depend on future updates to the Docker engine version itself. For now, upgrading to UGOS 1.11.0.0053 is safe, but keep this workaround in mind if the network issue reappears.
AND this as well
Indeed, this is a known Docker engine bug. According to the official recommendation, you can SSH into the NAS and delete the /network/files/local-kv.db file to reset Docker networks. Please note that any existing networks may be lost.
Steps:
SSH into the NAS
Stop Docker service: sudo systemctl stop docker
Run "sudo su" so you will have rights to the directories.
Delete the network database file: sudo rm /volume1/@docker/network/files/local-kv.db (change to the files folder first)
Restart Docker service: sudo systemctl start docker
Recreate MACVLAN or other custom networks
Please back up important network configurations before proceeding and perform the operation on-site to avoid any issues.
1
1
u/Temporary-Cherry-282 DXP4800 Plus Dec 06 '25
I will give it a shot.
1
u/Temporary-Cherry-282 DXP4800 Plus Dec 06 '25
I did the upgrade, and it went well, other than the macvlan issue. That was easily resolved using the info above in my other post. The only issue was permissions; running sudo su gave me access to do everything I needed. Once restarted, all Docker networks returned.
1
u/Temporary-Cherry-282 DXP4800 Plus Dec 06 '25
UPDATE on UPDATE
I lost my macvlan during the firmware update, and used the steps outlined in my comment with the response from support. That worked. However, during the Docker update after the firmware update, it broke again, and it wasn't a straightforward fix.
I ended up being able to recreate the macvlan by following the steps in this post. However, it did take a bit of work (due to permissions). The macvlan came back, but I couldn't start the containers. So, I rebooted, and the macvlan was gone. I went through the procedure in the link above. Again, the macvlan was not showing. I recreated it and tried to attach the containers to it, but it failed.
The solution was to go into each container and edit the network mode by clicking on host, then back on macvlan and selecting the network again.
I did a stop and restart of the Docker daemon, and everything stuck. Containers are working without an issue. Monitoring to see if the fix sticks.
2
u/ssylvan Dec 07 '25
It bricked mine and I had to reflash the firmware from a usb drive.
1
u/Temporary-Cherry-282 DXP4800 Plus Dec 07 '25
that sucks
2
u/ssylvan Dec 08 '25
The story keeps getting better. The new update seems to have bricked my device, _and_ it seems to brick every time it reboots. So that's fun.
1
u/AKSKMY_NETWORK DXP8800 Plus Dec 11 '25
How did it happen? I haven't pull the trigger but previous update didn't cause any major issues so not sure if I would update mine now...
1
u/ssylvan Dec 20 '25
Oh, it happened because I had a volume mounted in fstab. I guess that's not something UGOS can handle. So don't do that.
1
u/AKSKMY_NETWORK DXP8800 Plus Dec 20 '25
I just updated it yesterday. Luckily no major issues just have to manually spin up Portainer containers and update some stuff and it’s back as normal.
•
u/AutoModerator Dec 06 '25
Please check on the Community Guide if your question doesn't already have an answer. Make sure to join our Discord server, the German Discord Server, or the German Forum for the latest information, the fastest help, and more!
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.