Hello I've been having issues with docker lately. The service eventually fails to start so I've been deleting the Docker vDisk. Now it's saying "Unable to write to Docker Image" to write.

tower-diagnostics-20251209-1617.zip

Dec 9 05:20:51 Tower kernel: reservation conflict error, dev loop2, sector 14407040 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 2

Dec 9 05:20:51 Tower kernel: BTRFS: error (device loop2) in btrfs_commit_transaction:2540: errno=-5 IO failure (Error while writing out transaction)

Dec 9 05:20:51 Tower kernel: BTRFS info (device loop2 state E): forced readonly

Dec 9 05:20:51 Tower kernel: BTRFS warning (device loop2 state E): Skipping commit of aborted transaction.

There's a problem with the Docker image. Recreate the Docker image, reboot to clear the logs, and post new diags if it happens again.

P.S. logs are full of spam related to the rootshare, so disable that for now.

Here you go, disabled SMB, deleted the docker image and did a reboot.

tower-diagnostics-20251210-0246.zip

No need to disable SMB, just the root share; remove all the entries from SMB extras, that's not stock and was causing log spam.

Docker Engine appears to have started correctly. If it fails again, post new diags before rebooting.

Sorry, not quite sure what was the original Samba Extra Configuration. I made those changes to harden the settings after some research. What should I removed?

[rootshare]
 path = 
 comment =
 browseable = yes
 valid users = 
 write list = 
 vfs objects =
# Secure
 public = no
 valid users = nanuk
 writeable = yes
 vfs objects =
#disable SMB1 for security reasons
[global]
   min protocol = SMB2

I changed it to this. Should this work?

[rootshare]
 path = /mnt/user
 comment =
 browseable = yes
 valid users = nanuk
 write list = nanuk
 writeable = yes
 vfs objects =

# Secure
 public = no

# disable SMB1 for security reasons
[global]
 min protocol = SMB2

Edited December 9, 2025Dec 9 by Nanuk_

Anyway, here is the new diagnostic with the rootshare above.

orion-diagnostics-20251210-0326.zip

12 hours ago, Nanuk_ said:

What should I removed?

IMHO everything, if you still want to use a root share, which I don't recommend, use the UD plugin functionality for that; it's less of a hack

22 minutes ago, JorgeB said:

IMHO everything, if you still want to use a root share, which I don't recommend, use the UD plugin functionality for that; it's less of a hack

Sorry what's the UD plugin's full name so I can search for it in community app? Also will using that mess up the settings of my tdarr, plex, etc.?

Also I'm still getting the error.

Wait are you talking about the "Unassigned Devices" plugin? so leave Samba extra configuration blank? Even this bit?


 browseable = yes
 valid users = nanuk
 write list = nanuk
# Secure
 public = no

# disable SMB1 for security reasons
[global]
 min protocol = SMB2

41 minutes ago, Nanuk_ said:

Also will using that mess up the settings of my tdarr, plex, etc.?

That would be just for the root share. Again, if you are using that, that is not stock.

36 minutes ago, Nanuk_ said:

 so leave Samba extra configuration blank? Even this bit?

All of it.

orion-diagnostics-20251211-2235.zip

There's again a problem with the Docker image:

Dec 11 04:01:55 Orion kernel: reservation conflict error, dev loop2, sector 18208640 op 0x1:(WRITE) flags 0x101000 phys_seg 4 prio class 2

Dec 11 04:01:55 Orion kernel: reservation conflict error, dev loop2, sector 18732928 op 0x1:(WRITE) flags 0x101000 phys_seg 4 prio class 2

Dec 11 04:02:00 Orion kernel: BTRFS error (device loop2 state A): Transaction aborted (error -5)

Dec 11 04:02:00 Orion kernel: BTRFS: error (device loop2 state A) in btrfs_finish_one_ordered:3267: errno=-5 IO failure

### [PREVIOUS LINE REPEATED 1 TIMES] ###

Dec 11 04:02:00 Orion kernel: BTRFS info (device loop2 state EA): forced readonly

I can't see what is causing the errors. Try recreating the Docker image on an array disk, just for testing, in case it's an issue with the pool devices.

Tdarr no longer workes without the samba extra configurations. Is there a walkthrough to mount the root share using UD?

I would recommend consulting the UD help, or asking in its support thread, but I'm pretty sure root share is not required for Tdarr, though I've never used it, coudl be how it's currently configured.