Draconis Posted October 20, 2022 Share Posted October 20, 2022 Unraid version 6.9.2 Just using a single unraid share for Plex servers. I had an unexpected power outage. Both Linux via NFS and Windows via SMB report there is no more room on the share. Can't create any files but can read them just fine. I attempted to chmod the files as I've had permission issues before with linux and windows hitting the same share but that didn't work. Help is appreciated. diagnostics-20221019-2021.zip Quote Link to comment
JorgeB Posted October 20, 2022 Share Posted October 20, 2022 There's no cache assigned, was there supposed to be one? Quote Link to comment
Draconis Posted October 21, 2022 Author Share Posted October 21, 2022 (edited) There was a cache drive but another power outage a month ago killed it. Had to go away for a while and everything seemed to work fine when I unassigned the drive. Not what I wanted to do but I was rushed. Edit: I'm not super sure everything was fine as I'm not sure I added anything since that last drive failed. I only tested the read. Maybe no cache drive is related. Edited October 21, 2022 by Draconis Quote Link to comment
itimpi Posted October 21, 2022 Share Posted October 21, 2022 Try changing the Use Cache setting for the share anonymised as ‘r——-s’ to No. it is currently set to Yes which I can see causing problems if you no longer have a cache drive. Quote Link to comment
Draconis Posted October 21, 2022 Author Share Posted October 21, 2022 1 hour ago, itimpi said: Try changing the Use Cache setting for the share anonymised as ‘r——-s’ to No. it is currently set to Yes which I can see causing problems if you no longer have a cache drive. That option is greyed out and I can't change it. Quote Link to comment
Draconis Posted October 21, 2022 Author Share Posted October 21, 2022 Found this else where We can add a fix for this in 6.10, however a workaround for you is to Stop the array and then edit the file: 'config/shares/r------s.cfg' find this line: shareUseCache="yes" and change to: shareUseCache="no" You can edit the file by navigating to it via 'flash' share on your network, or open Terminal window and directly edit on the path: '/boot/config/shares/r--------s.cfg' Set the value exactly to all lower-case "no". The gui reflects the change. Still can not write to the share. Quote Link to comment
Draconis Posted October 21, 2022 Author Share Posted October 21, 2022 "Records" is the share name. It was the only one using a cache and the one my servers are attempting to read and write too. They still are unable to write to the share over NFS or SMB. Quote Link to comment
Solution JorgeB Posted October 21, 2022 Solution Share Posted October 21, 2022 Share floor is set to 4TB, since no disk has more than 4TB free you cannot write to it, just adjust that. Quote Link to comment
Draconis Posted October 21, 2022 Author Share Posted October 21, 2022 wow... That worked. I forgot most of my drives were small. 1 Quote Link to comment
Recommended Posts
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.