Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Errors of no more space

Featured Replies

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

Solved by JorgeB

  • Community Expert

There's no cache assigned, was there supposed to be one?

  • Author

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 by Draconis

  • Community Expert

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.

  • Author
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.

  • Author

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.

  • Community Expert

Which share?

  • Author

"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.

  • Community Expert
  • Solution

Share floor is set to 4TB, since no disk has more than 4TB free you cannot write to it, just adjust that.

  • Author

wow...
That worked. I forgot most of my drives were small.

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.