meyerj31

Hello, I have a Syncthing docker container on my remote seedbox that has two folders in "Send Only" mode. The other side is my unraid server where another Syncthing container is configured to "Receive Only". When files sync, their owner is Nobody and permission is drwxr-x--- which prevents my user account 'JPM' from deleting or modifying the files via Windows File Explore. When I attempt to delete the directory, I'm met with error "You require permission from 'nobody'. Running the "Docker safe new perms" tool fixes existing files but doesn't fix it permanently for new files. Things I've tried Delete folder sync within Syncthing and re-create. Enable "Ignore Permissions" setting in Syncthing. Open console and ran umask=000 in attempt to have Syncthing set permission to allow all users to write/modify but the container seems to ignore the command since the umask value is still 0022. Update and restart container This issue has been very frustrating for quite a few months so any help is greatly appreciated. Perhaps I should look for a different solution for synchronizing files from my seedbox so I'll take whatever suggestions you have. Thanks! meeseeks-diagnostics-20250801-2247.zip

Okay please verify this action plan Connect a spare hard disk via USB or SATA Use Krusader to copy the contents of disk 5 to the spare disk. Stop array and format disk Copy contents back Start array Run a parity check. Does that sound right?

Thanks Jorge, By reformatting, do you mean remove the disk and re-add or replace? Parity is still valid and should rebuild the data if I understand correctly. Thanks

I noticed my Syncthing docker was not synchronizing files and discovered I/O errors in the logs. This led me to the system log where I found this... Jul 20 21:34:58 MEESEEKS kernel: BTRFS error (device md5p1): bad tree block start, mirror 1 want 5801970647040 have 0 Jul 20 21:34:59 MEESEEKS kernel: BTRFS error (device md5p1: state A): Transaction aborted (error -5) Jul 20 21:34:59 MEESEEKS kernel: BTRFS: error (device md5p1: state A) in __btrfs_update_delayed_inode:1067: errno=-5 IO failure Jul 20 21:35:02 MEESEEKS kernel: BTRFS error (device md5p1: state EA): bad tree block start, mirror 1 want 5801970663424 have 0On the Main tab, Disk #5 is not showing any errors. But when I click on Disk 5 I can see over 8000 corruption errors on the pool device status. Running an extended SMART test resulted in no errors. How can I fix this file system issue? Thanks meeseeks-diagnostics-20250721-1649.zip

A few months ago I installed (3) 14TB Seagate EXOS SAS drives. One became my parity disk and two were for data array. They formatted to 13.9TB strangely. That odd number got me thinking... if one fails and I need to replace it with a 14TB SATA drive, will unraid accept it? As I understand, the replacement disk must be EXACTLY the same size. The replacement disk (14TB) cannot be larger than the 13.9TB parity disk. What are my options in this situation? meeseeks-diagnostics-20230127-1658.zip