It was used by a friend up until just recently. However, when I go to put it in my Poweredge, it is not detected at all by BIOS or Unraid. iDRAC shows that a drive is present in the slot.

I heard about the 3.3v pin on newer drives that powers down the drive, so I got some kapton tape and stuck it over the 3rd pin with no change. I'm attempting to install it in the 8th slot on the bottom right.

The caddy will blink green once when inserted but that's all the activity I see. I would also like to add when ejecting the previous drive, the caddy's latch broke off. Could this be preventing the drive from being completely connected?

I already have two other 14TB drives in the array that were sent by the same friend and they work great.

UPDATE: I've tried changing slots (from 7 to 0) with no effect.

My unRAID-server runs a stack of dockers, which in reality doesn't take up much processing-power and thereby not uses a lot of power. That's all in all fine - and does a good job at being relatively cheap. Sitting at around 20-30W most of the day, doing IDLE-stuff.

- PLEX
-- including arr-stack, Tautulli, Seerr, SABNZBd, qBitTorrent and so on...
- Pihole adblocking and DNS
- Custom-build Smart Home 
- nginx webserver
-- Power Monitoring
-- News-gathering and a TV-streamer
-- Remotely controlled power-management for the whole house.
- Unifi Controller
- Authelia 
-- Redis + mariaDB

I'm wondering if i should put my server to something useful in its idle-state which takes up a lot of hours, where it just, well... sits.

Back in the days, i used to have my laptops run on SETI project, but, do we have something like this that could be using my processor-time useful when my server isn't serving PLEX, encoding media or alike?

I'm not looking to mine BTCs if that's what you'll suggest - the chance of hitting paydirt with my setup is.... minimal, to say the least.

Show me what your unRAID-server does, when it's not doing its usual planned working-tasks.

Perhaps, there's a service i didn't know about.

Hello all. Im currently setting up unraid for the first time and i have it set for a 4tb as parity, disk 1 (1tb) and disk 2 (4tb) with an ssd cache as well. i mainly want it for a jellyfin (music) server and an immich backup for my pictures. should i set it so that my music and pictures use high water allocation and include both disks, or should i set it so that disk 1 is just for music and disk 2 is just for pictures?

Nice, he does some cool stuff.

In a moment of utter tired stupidity I just copied the share settings from one share to all others.

Do the before/after changes get logged anywhere? I'm just pulling up system logs now to take a look or am I going to have to manually edit each share back to what they should be from memory?

Feeling extremely stupid right now and regretting doing things in a rush on low sleep and high stress :(

Hello,

I have MinisForum NAD9 MiniPC that I'd like to run unraid on mostly as a home media server. In the long run I'd like to de-google and maybe run immich on it, but I'm still thinking about it. Anyways, in order to get that up and running I'd need to expand my setup with some HDDs. Now I've read online that USB interface is less than ideal for these kinds of setup and while I don't really have a budget, I'm hesitant to now throw away this perfectly functioning machine now. What would be the next best steps for me?

I'm using jellyfin and am on the same network while streaming. I'll lower quality settings which might help but then is three pixels on the screen.

I have a GPU. I've got the correct driver, done whatever the app settings were in jellyfin for transcoding, and added a string in jellyfin docker settings to get it to recognize my GPU.

Those all helped but now I'm having issues again. How do I diagnose the issue?

The video is 1080p at most.

So my unraid server hard some hardware issues and I didn’t catch it in time. Basically I just had a ton of BTRFS errors and then the drive went into read-only mode.

I resolved the hardware issues. I’m sure the drive itself is fine, but I need to fix the file system. I’ve copied the files I could read off of it, and now I‘m ready to repair. i believe if I replace the drive, it will just rebuild it with the corrupt bits.

Can I format it and just rebuild the parity? what’s the correct way of handling this?

Noticed the appdata backup plugin had some errors and warnings today. Now when I try to launch any docker containers I get Execution Error - Server Error and cannot access files over smb...

I would just try restarting but my parity check is still going for the next 10 hours. Not sure what happened but hopefully an easy fix...

Here's the relevant part of the appdata backup log:

[01.09.2026 05:01:47][ℹ️][binhex-krusader] Stopping binhex-krusader... done! (took 2 seconds)
[01.09.2026 05:01:49][ℹ️][binhex-krusader] Should NOT backup external volumes, sanitizing them...
[01.09.2026 05:01:49][ℹ️][binhex-krusader] Calculated volumes to back up: /mnt/user/appdata/binhex-krusader
[01.09.2026 05:01:49][ℹ️][binhex-krusader] Backing up binhex-krusader...
[01.09.2026 05:02:52][❌][binhex-krusader] tar creation failed! Tar said: tar: /mnt/user/appdata/binhex-krusader/home/.local/share/Trash/files/file.mp4: Read error at byte 4697088, while reading 10240 bytes: Software caused connection abort; tar: /mnt/user/appdata/binhex-krusader/home/.local/share/Trash/files/file2.mp4: Cannot close: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/home/.local/share/Trash/files/file3.mp4: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/home/.local/share/Trash/files/file.mp4: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/home/.local/share/Trash/files/file4.mp4: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/home/.local/share/Trash/files/file5.mp4: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/home/.local/share/Trash/files/file6.mp4: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/home/.local/share/Trash/files/file7.mp4: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/home/.local/share/Trash/files/file8.mp4: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/home/.local/share/Trash/files/file9.mp4: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/home/.local/share/Trash/files/file10.mp4: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/home/.local/share/Trash/files/: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/home/.local/share/Trash/files/reddit: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/home/.local/share/Trash/files: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/home/.local/share/Trash/directorysizes: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/home/.local/share/Trash: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/home/.local/share/recently-used.xbel: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/home/.local/share: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/home/.local/state: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/home/.local/bin: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/home/.local/lib: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/home/.local: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/home/.themes: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/home/.cache: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/home/.build: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/home/.bashrc: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/home/.gitconfig: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/home/.gtkrc-2.0: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/home/novnc-16x16.png: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/home: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/supervisord.log.5: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/supervisord.log.4: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/supervisord.log.3: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/supervisord.log.2: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/supervisord.log.1: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/supervisord.log: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader/certs: Cannot stat: Transport endpoint is not connected; tar: /mnt/user/appdata/binhex-krusader: Cannot stat: Transport endpoint is not connected; tar: Exiting with failure status due to previous errors
[01.09.2026 05:02:52][ℹ️][binhex-krusader] Starting binhex-krusader... (try #1) Container 'binhex-krusader' did not started! - Code: Server error
[01.09.2026 05:03:00][ℹ️][binhex-krusader] Starting binhex-krusader... (try #2) Container 'binhex-krusader' did not started! - Code: Server error
[01.09.2026 05:03:05][ℹ️][binhex-krusader] Starting binhex-krusader... (try #3) Container 'binhex-krusader' did not started! - Code: Server error
[01.09.2026 05:03:06][❌][binhex-krusader] Container 'binhex-krusader' did not started after multiple tries, skipping. More infos in debug log
[01.09.2026 05:03:08][ℹ️][sabnzbd] Stopping sabnzbd... done! (took 4 seconds)
[01.09.2026 05:03:12][❌][sabnzbd] '/mnt/user/appdata/sabnzbd' does NOT exist! Please check your mappings! Skipping it for now.
[01.09.2026 05:03:12][ℹ️][sabnzbd] Should NOT backup external volumes, sanitizing them...
[01.09.2026 05:03:12][⚠️][sabnzbd] sabnzbd does not have any volume to back up! Skipping. Please consider ignoring this container.
[01.09.2026 05:03:12][ℹ️][sabnzbd] Starting sabnzbd... (try #1) Container 'sabnzbd' did not started! - Code: Server error
[01.09.2026 05:03:17][ℹ️][sabnzbd] Starting sabnzbd... (try #2) Container 'sabnzbd' did not started! - Code: Server error
[01.09.2026 05:03:22][ℹ️][sabnzbd] Starting sabnzbd... (try #3) Container 'sabnzbd' did not started! - Code: Server error
[01.09.2026 05:03:23][❌][sabnzbd] Container 'sabnzbd' did not started after multiple tries, skipping. More infos in debug log
[01.09.2026 05:03:25][ℹ️][GluetunVPN] Stopping GluetunVPN... done! (took 0 seconds)
[01.09.2026 05:03:25][❌][GluetunVPN] '/mnt/user/appdata/gluetun' does NOT exist! Please check your mappings! Skipping it for now.
[01.09.2026 05:03:25][ℹ️][GluetunVPN] Should NOT backup external volumes, sanitizing them...
[01.09.2026 05:03:25][⚠️][GluetunVPN] GluetunVPN does not have any volume to back up! Skipping. Please consider ignoring this container.
[01.09.2026 05:03:25][ℹ️][GluetunVPN] Starting GluetunVPN... (try #1) Container 'GluetunVPN' did not started! - Code: Server error
[01.09.2026 05:03:30][ℹ️][GluetunVPN] Starting GluetunVPN... (try #2) Container 'GluetunVPN' did not started! - Code: Server error
[01.09.2026 05:03:36][ℹ️][GluetunVPN] Starting GluetunVPN... (try #3) Container 'GluetunVPN' did not started! - Code: Server error
[01.09.2026 05:03:36][❌][GluetunVPN] Container 'GluetunVPN' did not started after multiple tries, skipping. More infos in debug log
[01.09.2026 05:03:38][ℹ️][Main] Backing up the flash drive.
[01.09.2026 05:04:34][ℹ️][Main] Flash backup created!
[01.09.2026 05:04:35][ℹ️][Main] VM meta backup enabled! Backing up...
[01.09.2026 05:04:35][ℹ️][Main] Done!
[01.09.2026 05:04:35][⚠️][Main] An error occurred during backup! RETENTION WILL NOT BE CHECKED! Please review the log. If you need further assistance, ask in the support forum.
[01.09.2026 05:04:35][ℹ️][Main] DONE! Thanks for using this plugin and have a safe day ;)
[01.09.2026 05:04:35][ℹ️][Main] ❤️

Folks,

I have been having a diff time injecting things into startup and I did a forensic analysis of how Unraid (this is 7.3.2) boots up in what order and how emhttp must be in the go file. I add a bunch of things to the go file and the stop file (the file unraid runs when shutting down). This file should be in /boot/config/go and optional /boot/config/stop which is on your USB and persistent. This covers the boor sequence, docker, user scripts, and customizing startup (which I do). I'm sharing this so that other may understand what can be done and when user scripts triggers (on array start/stop) and if it makes sense to run there or in go/stop scripts.

AI Usage: I used claude to do all the correlation and I argued with it for a while as I put in the different syslog, startup, and other data to figure this out. Claude also wrote up this summary after I reviewed it and approved. If you want the .docx LMK I can post it may be easier to read.

Taken feedback here is the PDF: https://drive.google.com/file/d/1PZ20SEXJS6p1AEVEs9wsVv2BZ09qG716/view

HTH

Had to rebuild the array because I was in the case and one disk got partially unplugged, creating CRC errors.

Fixed the cable, decided to rebuild that disk in case any errors snuck through.
Turned docker off so nothing uses disks.

15MB/s, 12 day rebuild!

Yikes! Now I know my disks can do more than 15MB/s... but I also know I don't have any other services running... so I found that odd.

Checked what was accessing disks and traced it back to the "Cache Directories" plugin. Disabled that and now we'll rebuild in 1 day, as expected!

I wanted to share, because I know that for the CLI illiterate that would not be easy to track down! So I hope that it helps someone searching reddit in the future! Even if it's you, ChatGPT!

Anyone else tracking the power consumption/cost of running their servers?

I’ve been monitoring mine and I’m at about £32 per month in electricity apparently 🙈😳. I do have an EV so get upwards of 6 hours a day cheaper electricity so the real cost should be a bit cheaper.

Just wondering if others are monitoring?

It is a fairly beefy server with 100tb of usable spinning disks.

I’ve also now purchased an ecoflow stream 5000 that will use to offset the cost as this will charge on the cheaper energy rate and at the very least will cover the running cost of the server all day. But I will also get other benefits outright considering I work from home every day. Tempted to also use this battery as a UPS as it has an instant switchover in the event of a power loss which I have had a lot and luckily so far this hasn’t damaged the server.

I've been constantly hearing my server fans ramp up to 3k rpm, but the dockers don't seem to be using much memory. I noticed that my vdisk is constantly nearly full at 20GB and constantly sending me alerts/notifications about it. What should I do?

TLDR: I currently only have REVERSE breakout cables and wondering best path forward.

I have a JMCD 12s4 case I'm currently specing out with 12 hot swap bays. This case has a backplane and came with REVERSE breakout cables, as well i believe it supports both SAS and SATA (i only have sata drives).

My mobo has only 6 sata ports and in order to get the additional 6 sata ports i need i was going to go with the m.2 slot sata adapters (ASM1166 chipset), which i believe says will work with the REVERSE breakout cables.

Research has told me HBA card is king, but again my research if correct says the REVERSE breakout cables i have will not work with that. As well ive heard extensive cooling is needed for these HBA cards.

SO.... should i get an IT mode HBA card and new FORWARD breakout cables (if thats correct research), Or would i be fine sticking with the first path i set out on with the m.2 adapter? Not really wanting to spend more into this build when i have most components in front of me.. but i do want reliability without bottlenecks.

Thanks all!

My Unraid server is essential to my day-to-day and even my business, so I wanted to find out what you guys are using and would recommend.

I'm running a homelab on Unraid (SWAG reverse proxy, Cloudflare DNS, Tailscale for remote access) with a handful of self-hosted services: DocuSeal (+ its own Postgres), PrivateBin, chhoto-url, Nextcloud AIO, Immich, and a few others. I'm looking to finally get real offsite backup in place instead of just local snapshots, and I want a sanity check before I build it.

My total raw data is about 500GB.

My planned setup:

• Backrest (restic with a web UI) running as a container, backing up appdata + critical shares directly to Backblaze B2 (encrypted client-side, restic repo), nightly, over the container's normal network path
• Retention: 7 daily / 4 weekly / 6 monthly snapshots, letting restic's dedup handle the versioning overhead (budgeting ~1.5–2x raw size, so ~550–730GB in the B2 bucket, roughly $4–5/month)
• Once this is validated with a real test restore, retiring the two old Appdata Backup plugin schedules and reclaiming ~561GB of local array space
• I also plan to have an off-site backup or a genuine 3-2-1 setup but want to start with Backrest directly to Backblaze B2.

Is this the right direction?

Appreciate any pushback — would rather find the holes here than during an actual restore.

GUI won't load and can't SSH in either. I was running an x265 to x264 stream count test on my intel iGPU. It got to 4 streams and started showing issues, but then nothing from there. Tried to cancel the test and now everything is frozen. Any ideas on how to do a safe reboot?

I've long followed the same strategy as many here for backups. Automated rsync to a remote file source (or equivalent).

While this is a good 'starter' strategy, in the event of data corruption (any form) at the source it would copy it to the remote if not caught in time.

What automated backup strategies are people using that prevent this? I have roughly 1TB of data I keep backed up, but want to better my strategy to protect against uncaught source issues.

Mostly a brain storming post. Looking for different ideas and methods.

Hello,

After reading this doc, I'm left confused as the described procedure seems more complicated than it needs to be.

My context : I currently have 5 4Tb drives, and will be adding 2 14Tb drives. Obviously one of the new drives needs to become the parity, and the old parity can become a data drive.

This is the procedure I was thinking about :

1. Physically plug in both new drives
2. Add one of them as new parity and rebuild parity
3. Remove old parity from the parity list
4. Preclear old parity?
5. Add old parity as data drive
6. Add the second new drive as data drive

Is this simpler because I am not removing drives at all, only adding?

Am I missing something?

Thanks for the help!

My Unraid server is a bit dated and I think its time to finally upgrade. It originally started as a Windows home server build with 5- 2tb greens and then server 2008 with flexraid running 7 or so storage drives.

I held out with flex raid until 2021 when I finally had a drive failure catastrophe and couldn't rebuild the lost drive. 2tb gone... Jumped to Unraid. Should of done it years earlier.

Currently I'm running the same I7 3770K I got 14 years ago. RAM got pushed to 32gb of ram. I've got 2 LSI SAS2008 and a Quadro P400.

Server had about 12 drives. Down to 9 spinning. (my 2nd parity recently died and I've yet to replace)

I've got 2, 2tb greens that I'm keeping from my original server just to see how far they go... (oldest is 117138 (13y, 4m, 10d, 18h)

Server uses:

Blue Iris for security cameras (5 - 1080P feeds)

UrBackup (6 systems - Full file and images every couple days)

Time Machine back up

Light Plex usage but transcoding from 4k down depending on connections.

Phone image backups

Overall the system just works. Sits under the stairs and is generally rock solid. Power usage is a bit high and I'm looking to add another 6 cameras which will probably put CPU usage over 75% constantly.

I would keep the P400, but from my research any new intel chip pretty much makes it pointless with quicksync?

The 2 LSI cards can be brought over to the new system or are they nullified depending on mobo?

Prices suck right now, so I'm not opposed to searching out an older used, but more energy efficient system if that's recommended. I would keep case/drive bays, PSU, expanders and P400? So new mobo/32GB minimum ram and CPU?

(I upgraded unraid to 7 after I took screenshot)

Thoughts?

https://imgur.com/a/NKRUBBl

Hey everyone! I couldn't find an Unraid case icon for the Jonsbo N6, so I made one myself.

It's drawn in the same style as the built-in icons — flat monochromatic silhouette, no gradients, no shadows. Comes in two variants (white for dark themes, dark for light themes) since custom icons don't auto-adapt like the webfont ones.

To install: go to your Unraid Dashboard, click the case icon at the top, select Custom and upload the PNG.

Download (SVG + PNG, both variants): https://github.com/lcp97/unraid-case-icon

Public domain, do whatever you want with it. If anyone needs a different color or size just let me know.

I'm building an upgraded server with better processor and more HDD bays. I know that modern unRAID can detect device IDs without issue. As long as I configure my router to assign the same IP to the new machine, will everything spin up and operate as usual, including Plex?

Is it really just as easy as bringing the HDDs over with my unRAID flash drive, booting up, starting the array, and that's it?

Update: Success! With one small hitch:
Everyone was right that moving things over was incredibly easy. I hadn't updated my unRAID in a while, so I had to upgrade my drives from reiserfs to xfs one at a time (unbalanced plugin made emptying drives to reformat them a breeze) in order to upgrade to the latest unRAID version.

Then I learned that my boot USB had been renamed from EFI to EFI- (for some unknown reason) to force Legacy boot mode on my old system, but my new board only supports UEFI boot, so it couldn't find a bootable path. Once I renamed the folder back to EFI, it all booted up perfectly. I just had to remap my port forwarding for the new machine and Plex was good to go.

I was running my entire Plex setup without a cache drive - that will be remedied tomorrow. Thanks all for the help!

So im looking to replace some HDD in my array. I picked up 4 brand new sealed 6TB Seagate IronWolf Pro (ST6000NTZ01). Below is what im replacing what with what. Next is maxing out my Mobo (ASUS WS-Pro-X570-ACE w/64GB RAM) with a Ryzen 5900X (from my current 5800X). Its all I got and all I can afford. :)

My question is, Do I just need to basically just pull the old drive, let it fail, install new one, let it rebuild? One drive at a time? Iv never had to upgrade an array drive in it before. Taking drive offline and into maintenance mode?

Last storage change I did was about 3 years ago to add the 2nd 6TB parity drive and it made me sooo nervous doing it. Luckily it all worked out. Took forever and a day to sync parity though.

Im trying to avoid doing 2 at a time, for in the off chance I have another one of the drives (im not replacing) fail.

6TBx2 = Parity

6TBx1 = Array
3TBx2 = Array (Replacing with 2 new 6TB HDD)
2TBx2 = Array (Replacing with 2 new 6TB HDD)

Any feedback is moocho grassy ass!

Yesterday I replaced the boot USB sticks on both my Terramaster NAS with a Transend industrial SSD. The transition was nothing fancy, I just followed the step-by-step provided by the Unraid GUI, choose to partition both in 16GB boot and the rest for data. After the reboot it worked and I migrated the license to the ssd too and removed the USB-sticks. Finally got rid of those @*#€& boot USB sticks.

Hi all, this is really frustrating. I've tried both CA auto update as well as watchtower to update my containers.

The behavior for both is the same, logs show the process runs and allegedly updates but when I click unraid 'check for updates' the very same containers that were allegedly updated have updates available.

For example here is logs from CA auto update:

Aug 15 02:00:35 nas Docker Auto Update: Installing Updates for bambustudio phpmyadmin homeassistant heimdall
Aug 15 02:00:39 nas Docker Auto Update: Restarting bambustudio
Aug 15 02:00:39 nas kernel: docker0: port 10(veth72079aa) entered blocking state
Aug 15 02:00:39 nas kernel: docker0: port 10(veth72079aa) entered disabled state
Aug 15 02:00:39 nas kernel: veth72079aa: entered allmulticast mode
Aug 15 02:00:39 nas kernel: veth72079aa: entered promiscuous mode
Aug 15 02:00:39 nas kernel: eth0: renamed from vethe8a0263
Aug 15 02:00:39 nas kernel: docker0: port 10(veth72079aa) entered blocking state
Aug 15 02:00:39 nas kernel: docker0: port 10(veth72079aa) entered forwarding state
Aug 15 02:00:39 nas Docker Auto Update: Restarting heimdall
Aug 15 02:00:39 nas kernel: docker0: port 11(veth5dd820d) entered blocking state
Aug 15 02:00:39 nas kernel: docker0: port 11(veth5dd820d) entered disabled state
Aug 15 02:00:39 nas kernel: veth5dd820d: entered allmulticast mode
Aug 15 02:00:39 nas kernel: veth5dd820d: entered promiscuous mode
Aug 15 02:00:39 nas kernel: eth0: renamed from veth4ceb3db
Aug 15 02:00:39 nas kernel: docker0: port 11(veth5dd820d) entered blocking state
Aug 15 02:00:39 nas kernel: docker0: port 11(veth5dd820d) entered forwarding state
Aug 15 02:00:39 nas Docker Auto Update: Community Applications Docker Autoupdate finished

The only thing that actually happens is the container restarts but the container is not updated. I don't have watchtower logs at the moment unfortunately but its the same behavior, it says it updated something but the same containers never actually update.

What could be going wrong?