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.

User shares suddenly missing

Featured Replies

Solved

There was a permissions problem that was fixed with the following command.

chmod 777 /mnt/user

 

Hello,

I've noticed today that suddenly my user shares don't appear to exist anymore.

 

Now I have just updated unRAID to 6.2.4 last night but it did seem to be working fine immediately afterwards.

Possibly it started after updating the plugins.

 

Removed all plugins now to troubleshoot.

I have rebooted the server a few times

shfs process appears to be running (checked this after reading a similar thread)

If I try to create a new share it just says that it has been deleted.

I'm doing a parity check now but I was wondering if there was anything else I should be checking.

I've attached a diagnostics output because I couldn't find anything with my limited knowledge.

 

Thanks in advance.

unraid-diagnostics-20170122-2045.zip

  • Author

Thanks for the quick reply but unfortunately for me they aren't just missing from the webGUI.

I can't see them when via smb either.

 

Also I have my adblocker disabled for the webGUI and tested it in other browsers just in case.

Post the contents of this command (either from the local console or via SSH/Putty)

ls -al /mnt/user

  • Author

Here you go

 

d-wx-wx-wx 1 nobody users 4096 Jan 22 21:52 ./
drwxr-xr-x 7 root   root   140 Jan 22 20:59 ../
drwxrwxrwx 1 nobody users 4096 Dec 12 11:51 B***/
drwxrwxrwx 1 nobody users 8192 Dec 27 06:16 F***/
drwxrwxrwx 1 nobody users 4096 Dec 27 10:03 M***/
drwxrwxrwx 1 nobody users 4096 Nov  6 18:06 M***/
drwxrwxrwx 1 nobody users   39 May 11  2016 P***/
drwxr-xr-x 1 nobody users 8192 Dec 15 21:59 P***/
drwxrwxrwx 1 nobody users   24 Dec  7 23:00 S***/
drwxrwxrwx 1 nobody users 4096 Dec 25 14:04 T***/
drwxrwxrwx 1 nobody users 4096 Dec  7 23:01 T***/
drwxrwxrwx 1 nobody users    6 Jan 22 21:04 p***/
drwxrwxrwx 1 nobody users    6 Jan 22 21:04 t***/

Here you go

 

d-wx-wx-wx 1 nobody users 4096 Jan 22 21:52 ./
drwxr-xr-x 7 root   root   140 Jan 22 20:59 ../
drwxrwxrwx 1 nobody users 4096 Dec 12 11:51 B***/
drwxrwxrwx 1 nobody users 8192 Dec 27 06:16 F***/
drwxrwxrwx 1 nobody users 4096 Dec 27 10:03 M***/
drwxrwxrwx 1 nobody users 4096 Nov  6 18:06 M***/
drwxrwxrwx 1 nobody users   39 May 11  2016 P***/
drwxr-xr-x 1 nobody users 8192 Dec 15 21:59 P***/
drwxrwxrwx 1 nobody users   24 Dec  7 23:00 S***/
drwxrwxrwx 1 nobody users 4096 Dec 25 14:04 T***/
drwxrwxrwx 1 nobody users 4096 Dec  7 23:01 T***/
drwxrwxrwx 1 nobody users    6 Jan 22 21:04 p***/
drwxrwxrwx 1 nobody users    6 Jan 22 21:04 t***/

Did you sanitize that output?
  • Author

yes sorry meant to say ignore names

Not sure.  Everything looks ok I think.  I'm sure someone else is going to pipe in

 

  • Author

Hah fair enough, thanks for trying.

I've just noticed I can't get access to disk shares via smb even though they're currently enabled, set to public etc. Might be related, looking into it now.

Can access flash drive share.

 

Is the array started?  You do have autostart array set to no

  • Author

Yep

Do you have 9 user shares or 11? The two shares that begin with lowercase letters (p*** and t***) have no matching entries in your configuration. Do they match the names of the P*** and T*** shares, by any chance (eg. "porn" and "Porn")?

 

  • Community Expert

You have a line in your go file to start unMenu. Probably not the cause of your problem but you should probably remove it. This does suggest however that you may have some things hanging around from an old install. Does your flash drive have an extra folder? There is also this in your syslog

Jan 22 20:34:22 unRAID root: plugin: installing: /boot/config/plugins/dynamix.plg
Jan 22 20:34:22 unRAID root: plugin: not installing older version

The syslog isn't very long so doesn't show us much about using the filesystems, which maybe you can't do anyway. But it looks like your disks are all completelly full or nearly full. This makes me wonder if maybe you have some filesystem corruption.

  • Author

Should be 9 but those last two I created just now via the webGUI as a test and thats when it just says they've been deleted. So I guess they didn't get created properly.

 

Do you have 9 user shares or 11? The two shares that begin with lowercase letters (p*** and t***) have no matching entries in your configuration. Do they match the names of the P*** and T*** shares, by any chance (eg. "porn" and "Porn")?

 

  • Author

Good points. I've manually deleted all the plugins from the flash drive and removed that unmenu line and unmenu folder leftovers.

Still the same after a reboot.

Yes the drives are pretty full so maybe waiting out the parity check?

 

You have a line in your go file to start unMenu. Probably not the cause of your problem but you should probably remove it. This does suggest however that you may have some things hanging around from an old install. Does your flash drive have an extra folder? There is also this in your syslog

Jan 22 20:34:22 unRAID root: plugin: installing: /boot/config/plugins/dynamix.plg
Jan 22 20:34:22 unRAID root: plugin: not installing older version

The syslog isn't very long so doesn't show us much about using the filesystems, which maybe you can't do anyway. But it looks like your disks are all completelly full or nearly full. This makes me wonder if maybe you have some filesystem corruption.

  • Author

Fixed it, it was a permissions problem. Some reason it was setup like this with no read permissions

 

d-wx-wx-wx 10 nobody users 4096 Jan 23 03:45 disk1/
d-wx-wx-wx  9 nobody users  139 Jan 23 03:45 disk2/
d-wx-wx-wx 11 nobody users  185 Jan 23 03:45 disk3/
d-wx-wx-wx  9 nobody users  139 Jan 23 03:45 disk4/
d-wx-wx-wx  1 nobody users 4096 Jan 23 03:45 user/

 

ran chmod 777 /mnt/user so now it looks like this. Shares are all back now.

 

drwxrwxrwx 10 nobody users 4096 Jan 23 03:45 disk1/
drwxrwxrwx  9 nobody users  139 Jan 23 03:45 disk2/
drwxrwxrwx 11 nobody users  185 Jan 23 03:45 disk3/
drwxrwxrwx  9 nobody users  139 Jan 23 03:45 disk4/
drwxrwxrwx  1 nobody users 4096 Jan 23 03:45 user/

 

 

  • Community Expert

Fixed it, it was a permissions problem. Some reason it was setup like this with no read permissions

 

d-wx-wx-wx 10 nobody users 4096 Jan 23 03:45 disk1/
d-wx-wx-wx  9 nobody users  139 Jan 23 03:45 disk2/
d-wx-wx-wx 11 nobody users  185 Jan 23 03:45 disk3/
d-wx-wx-wx  9 nobody users  139 Jan 23 03:45 disk4/
d-wx-wx-wx  1 nobody users 4096 Jan 23 03:45 user/

 

ran chmod 777 /mnt/user so now it looks like this. Shares are all back now.

 

drwxrwxrwx 10 nobody users 4096 Jan 23 03:45 disk1/
drwxrwxrwx  9 nobody users  139 Jan 23 03:45 disk2/
drwxrwxrwx 11 nobody users  185 Jan 23 03:45 disk3/
drwxrwxrwx  9 nobody users  139 Jan 23 03:45 disk4/
drwxrwxrwx  1 nobody users 4096 Jan 23 03:45 user/

I don't see any way it could ever get like that unless you or something you installed is making it happen. These particular "folders" don't actually exist until unRAID starts the array and it mounts the disks.
  • Author

Yeah it is kinda strange.

I remember I had to adjust permissions once when experimenting with torrents, but I'm pretty sure it was just to edit a config file and I didn't touch those folders.

I don't think I would have messed up the command because I'm familiar with it and understand what it's doing.

Haven't touched anything like that in about a year either.

I'm guessing updating unRAID and/or the plugins somehow caused it because it's been working perfectly until then.

If anything I'd say it was a plugin because it seemed ok after the initial unRAID update .

  • Community Expert

What plugins and dockers are you running? If you have given any of them access to /mnt then maybe they did something.

 

If you have a docker volume mapping /mnt to /mnt, that may be the easy way to get past not understanding volume mappings, but it isn't really a good way to do things.

  • Author

I didn't have many because I use it almost as fileserver only. Docker was actually switched off.

 

I've since removed everything but I believe it was just the following plugins:

 

  • IPMI
  • Dynamix Active Streams
  • Dynamix File Integrity
  • Dynamix System Buttons
  • Transmission

 

I did play around with some other things like that unmenu entry we found. But maybe it wasn't fully removed and maybe a script was leftover in that.

 

I noticed there was left over 32bit packages which I was notified of via the Fix Common Problems plugin that I installed to help troubleshoot this problem.

 

Those were:

  • curl-7.21.4-i486-1
  • libevent-2.0.11-i486-1sl
  • libidn-1.19-i486-1
  • openldap-client-2.4.21-i486-1

They've since been removed.

 

The only time I can recall ever changing permissions was before I settled for using Transmission I was trying something else and found myself changing permissions to its config file so I can edit it. I cant remember exactly what it was but it was a long time ago and it didn't cause trouble at the time.

 

Probably will never know now because I haven't documented everything I've done with the server. Just odd that it was fine until I did those updates. I had been using it daily for the last year prior to that. It had been off for couple weeks because I've moved and just got it setup again the other night.

  • Community Expert

Fixed it, it was a permissions problem. Some reason it was setup like this with no read permissions

 

d-wx-wx-wx 10 nobody users 4096 Jan 23 03:45 disk1/
d-wx-wx-wx  9 nobody users  139 Jan 23 03:45 disk2/
d-wx-wx-wx 11 nobody users  185 Jan 23 03:45 disk3/
d-wx-wx-wx  9 nobody users  139 Jan 23 03:45 disk4/
d-wx-wx-wx  1 nobody users 4096 Jan 23 03:45 user/

 

ran chmod 777 /mnt/user so now it looks like this. Shares are all back now.

 

drwxrwxrwx 10 nobody users 4096 Jan 23 03:45 disk1/
drwxrwxrwx  9 nobody users  139 Jan 23 03:45 disk2/
drwxrwxrwx 11 nobody users  185 Jan 23 03:45 disk3/
drwxrwxrwx  9 nobody users  139 Jan 23 03:45 disk4/
drwxrwxrwx  1 nobody users 4096 Jan 23 03:45 user/

I don't see any way it could ever get like that unless you or something you installed is making it happen. These particular "folders" don't actually exist until unRAID starts the array and it mounts the disks.

I assumed this was a directory listing of /mnt, but you seem to be saying it is a directory listing of /mnt/user. That would imply that you have user shares named disk1,disk2,disk3,disk4,user. Is that what's going on here? If so, no wonder things are confused.

 

  • Author

No it is /mnt but somehow changing /mnt/user permissions affected the /mnt/disk permissions. I admittedly don't know why.

I assumed the disk folders were just where the actual disks mount, but after this I thought it's all part of the unRAID magic and they are somehow inheriting the permissions from /mnt/user

 

I definitely did not do anything else.

Yes, that works. Probably a consequence of the FUSE filesystem:

 

root@Mandaue:~# cd /mnt
root@Mandaue:/mnt# ls -la
total 32
drwxr-xr-x 14 root   root  280 Jan  5 21:59 ./
drwxr-xr-x 18 root   root  400 Jan 22 02:15 ../
drwxrwxrwx  1 nobody users  52 Jan  5 22:00 cache/
drwxrwxrwx  5 nobody users  51 Jan 10 20:00 disk1/
drwxrwxrwx  4 nobody users  51 Jan 10 20:01 disk2/
drwxrwxrwx  4 nobody users  39 Jan  5 22:00 disk3/
drwxrwxrwx  4 nobody users  51 Jan  5 22:00 disk4/
drwxrwxrwx  4 nobody users  51 Jan 10 20:11 disk5/
drwxrwxrwx  5 nobody users  70 Jan 15 14:56 disk6/
drwxrwxrwx  2 nobody users   6 Jan  5 22:00 disk7/
drwxrwxrwx  2 nobody users   6 Jan  5 22:00 disk8/
drwxrwxrwx  2 nobody users  40 Jan  5 22:29 disks/
drwxrwxrwx  1 nobody users  52 Jan 15 14:56 user/
drwxrwxrwx  1 nobody users  51 Jan 15 14:56 user0/
root@Mandaue:/mnt# chmod 776 user
root@Mandaue:/mnt# ls -la        
total 32
drwxr-xr-x 14 root   root  280 Jan  5 21:59 ./
drwxr-xr-x 18 root   root  400 Jan 22 02:15 ../
drwxrwxrw-  1 nobody users  52 Jan  5 22:00 cache/
drwxrwxrw-  5 nobody users  51 Jan 10 20:00 disk1/
drwxrwxrw-  4 nobody users  51 Jan 10 20:01 disk2/
drwxrwxrw-  4 nobody users  39 Jan  5 22:00 disk3/
drwxrwxrw-  4 nobody users  51 Jan  5 22:00 disk4/
drwxrwxrw-  4 nobody users  51 Jan 10 20:11 disk5/
drwxrwxrw-  5 nobody users  70 Jan 15 14:56 disk6/
drwxrwxrw-  2 nobody users   6 Jan  5 22:00 disk7/
drwxrwxrw-  2 nobody users   6 Jan  5 22:00 disk8/
drwxrwxrwx  2 nobody users  40 Jan  5 22:29 disks/
drwxrwxrw-  1 nobody users  52 Jan 15 14:56 user/
drwxrwxrw-  1 nobody users  51 Jan 15 14:56 user0/
root@Mandaue:/mnt# chmod 777 user
root@Mandaue:/mnt# ls -la        
total 32
drwxr-xr-x 14 root   root  280 Jan  5 21:59 ./
drwxr-xr-x 18 root   root  400 Jan 22 02:15 ../
drwxrwxrwx  1 nobody users  52 Jan  5 22:00 cache/
drwxrwxrwx  5 nobody users  51 Jan 10 20:00 disk1/
drwxrwxrwx  4 nobody users  51 Jan 10 20:01 disk2/
drwxrwxrwx  4 nobody users  39 Jan  5 22:00 disk3/
drwxrwxrwx  4 nobody users  51 Jan  5 22:00 disk4/
drwxrwxrwx  4 nobody users  51 Jan 10 20:11 disk5/
drwxrwxrwx  5 nobody users  70 Jan 15 14:56 disk6/
drwxrwxrwx  2 nobody users   6 Jan  5 22:00 disk7/
drwxrwxrwx  2 nobody users   6 Jan  5 22:00 disk8/
drwxrwxrwx  2 nobody users  40 Jan  5 22:29 disks/
drwxrwxrwx  1 nobody users  52 Jan 15 14:56 user/
drwxrwxrwx  1 nobody users  51 Jan 15 14:56 user0/
root@Mandaue:/mnt#

  • Community Expert

Stop the array, and then go to /mnt. None of those folders should exist.

 

Start the array, and then go to /mnt. unRAID creates them when the array starts. They are simply the mount points for the disks and the user shares.

 

It also creates the user shares under /mnt/user when the array starts, by taking the names of all top level folders on cache or array disks, and looking in /boot/config/shares for each shares settings. If a share doesn't have settings there it will be given default settings.

 

But note that it is not even necessary to use the webUI to create a user share. A user share will exist if it has a top level folder on cache or array disks.

 

Conversely, if you do use the webUI to create a user share, unRAID will create a top level folder as needed on cache or array disks according to the shares settings.

  • Author

I have since rebooted the server twice after changing the /mnt/user permissions and they have stuck.

Is the user folder somewhere on the drives themselves when the array is stopped or is this all virtual stuff in memory once the array is started?

When you start the array is it looking at the drives and applying the permissions it finds, or is it pulling out of a config file or some such store on the flash drive?

Just asking because I'm curious as to how its now remembering the permissions the way they are now and the way they were before, between reboots.

Archived

This topic is now archived and is closed to further replies.

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.