February 10, 20251 yr I am fairly new to Unraid, so forgive me if I missed something basic here. I suddenly am unable to use any of my *arr stack as they all give read-only or invalid permission errors saying they can't write to /config. Steps taken so far: - Ran both Docker Safe New Permissions & New Permissions. - Manually changed the owner from UNKNOWN back to Nobody using the Unraid front end. - Deleted one of the Docker apps (Sonarr) and re-installed it, but this did not fix the issue for Sonarr. - Rebooted the entire Unraid server. Attached is my diagnostic file. Thank you in advance for the help so I can get this thing working again. unraid-diagnostics-20250209-2315.zip
February 10, 20251 yr Community Expert Is /config mapped to the appdata share? Also a lot of spam in the log, try rebooting in safe mode and post new diags.
February 10, 20251 yr Author When I first encountered the issue, /config was mapped to /mnt/user/appdata. I changed them all to /mnt/cache/appdata partly as trying to fix this permissions issue and partly due to some write-up somewhere saying that could improve speed. The share is set to be Cache only, and the Cache drive is a single 512GB NVME m.2 SSD (with 460GB-ish free). Attached is a fresh set of diagnostics after having booted in safe mode, as requested. Thank you for your help. If there is something specific I should look at in the digs to help me self-troubleshoot in the future, please feel free to share. unraid-diagnostics-20250210-1233.zip
February 10, 20251 yr Community Expert It looks like those diagnostics are taken with the array stopped. Likely to be more useful to provide diagnostics taken after starting the array.
February 10, 20251 yr Author My apologies (I did say I was a newb, right?). Attached are an updated set of diags after the array had been started. Not sure if this is because I booted into safe mode, but I did notice the array didn't auto-start even though I do have that enabled in Settings -> Disk Settings. Also, I only now noticed that XFS is the default file system for the array, though the Cache drive is using btrfs. No idea if that is ideal or not. unraid-diagnostics-20250210-1309.zip Edited February 10, 20251 yr by DJFriar
February 10, 20251 yr Author I updated my signature to provide my system information in case that helps with troubleshooting. Edited February 10, 20251 yr by DJFriar wording change
February 11, 20251 yr Community Expert Don't see anything that would prevent writing to appdata, type: touch /mnt/user/appdata/test
February 11, 20251 yr Author Solution I ended up self resolving this by forcing the new permissions on to the cache drive and the appdata share. After running it twice it finally updated both /mnt/user/appdata and /mnt/cache/appdata which were showing different permissions at first. I also balanced and scrubbed the cache drive, and then re-configured the Docker apps from the existing templates. Once I did all the above, they were able to work as expected again.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.