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 share only showing partial contents + getxattr error spam

Featured Replies

Having a strange issue with my PELICAN share. The data is definitely there on the disks - disk1 has 9 folders, disk2 has 11, cache has 4 - but when I look at /mnt/user/PELICAN I only see one folder called "logs". Everything else is just missing from the user share view.

 

Syslog is getting hammered with this error every second:

emhttpd: error: malloc_share_locations, 7200: Operation not supported (95): getxattr: /mnt/user/PELICAN

Running 6.12.14, two data disks on XFS, cache on btrfs, all SMART tests pass, array shows started and healthy.

 

I've tried rebooting, manually clearing /mnt/user and restarting emhttpd, running mdcmd misc scan_shares, checking permissions and extended attributes on the disk folders - nothing works. The shares.ini file either stays empty or shows PELICAN with size="0".

 

When I try to manually run shfs it either exits immediately or mounts but then returns "no such file or directory" when you try to access anything.

 

Feels like some kind of chicken-and-egg thing where emhttpd can't populate shares.ini because shfs isn't mounted, but shfs can't mount because there's nothing in shares.ini. The data's all fine on the raw disk paths, it's just the user share layer that's broken.

 

Anyone run into this before?

Solved by JorgeB

  • Community Expert

Attach Diagnostics ZIP to your NEXT post in this thread.

  • Community Expert

What do you get from command line with this?

ls -lah /mnt
  • Author

root@raptor:~# ls -lah /mnt

total 16K

drwxr-xr-x 6 root root 120 Dec 31 05:30 ./

drwxr-xr-x 20 root root 460 Dec 31 05:31 ../

drwxrwxrwx 1 nobody users 54 Nov 29 2024 cache/

drwxrwxrwx 4 nobody users 33 Dec 5 2024 disk1/

drwxrwxrwx 6 nobody users 105 Oct 6 08:03 disk2/

drwxr-xr-x 3 root root 60 Dec 31 05:24 user/

  • Community Expert

Not thats not right for user/

  • Community Expert

Updating to 7.2.3 should fix that, since it applies the correct permissions at every boot

  • Author

After upgrading to 7.2.3

^Croot@raptor:~# ls -lah /mnt

total 16K

drwxr-xr-x 6 root root 120 Dec 31 06:19 ./

drwxr-xr-x 20 root root 440 Dec 31 06:19 ../

drwxrwxrwx 1 nobody users 54 Nov 29 2024 cache/

drwxrwxrwx 4 nobody users 33 Dec 5 2024 disk1/

drwxrwxrwx 6 nobody users 105 Oct 6 08:03 disk2/

drwxr-xr-x 6 root root 120 Dec 31 06:19 user/

  • Community Expert

Post new diags, please.

  • Community Expert

There appears to be something creating this mount point: /mnt/user/PELICAN

/mnt/user is reserved and cannot be used by anything external. Diags don't show the complete go file contents and it's been modified, to rule that out and also rule out a script or plugin, reboot in safe mode and post new diags.

  • Community Expert

Do you know where that PELICAN folder comes from?

Post the output from

ls -la /mnt/disk1

ls -la /mnt/disk2

ls -la /mnt/cache

  • Author

root@raptor:~# ls -la /mnt/disk1

total 0

drwxrwxrwx 4 nobody users 33 Dec 5 2024 ./

drwxr-xr-x 6 root root 120 Dec 31 06:59 ../

drwxrwxrwx 11 nobody users 183 Dec 31 05:13 PELICAN/

drwxrwxrwx 2 nobody users 6 Dec 5 2024 isos/

root@raptor:~# ls -la /mnt/disk2

total 0

drwxrwxrwx 6 nobody users 105 Oct 6 08:03 ./

drwxr-xr-x 6 root root 120 Dec 31 06:59 ../

drwxrwx--- 3 nobody users 33 Oct 6 08:02 DESKTOP-HVCTNTU/

drwxrwxrwx 11 nobody users 198 Aug 23 06:23 PELICAN/

drwxrwx--- 2 nobody users 6 Oct 6 07:46 clients/

drwxrwx--- 2 nobody users 38 Oct 6 08:03 urbackup_tmp_files/

root@raptor:~# ls -la /mnt/cache

total 16

drwxrwxrwx 1 nobody users 54 Nov 29 2024 ./

drwxr-xr-x 6 root root 120 Dec 31 06:59 ../

drwxrwxrwx 1 nobody users 60 Dec 27 05:09 PELICAN/

drwxrwxrwx 1 nobody users 374 Dec 2 02:21 appdata/

drwxrwxrwx 1 nobody users 32 Nov 11 04:04 domains/

drwxrwxrwx 1 nobody users 26 Nov 28 2024 system/

  • Community Expert

Stop the array, and post the output from ls -l /mnt

  • Author

root@raptor:~# ls -l /mnt

total 0

drwxr-xr-x 3 root root 60 Jan 4 03:51 user/


Is there a way to reinstall and keep all my files?

Edited by bavik

  • Community Expert

/mnt/user should not exist without the array being started. With the array still stopped, post output from ls -l /mnt/user

  • Author

root@raptor:~# ls -l /mnt/user

total 0

root@raptor:~# bash: total: command not found

root@raptor:~# drwxr-xr-x 3 root root 60 Jan 4 03:51 PELICAN/

bash: drwxr-xr-x: command not found

I'm also now getting this

Unraid Parity disk SMART health [199]
Warning [RAPTOR] - udma crc error count is 15

WDC_WUH721414ALE6L1_Y5HBKKGC (sdd)

maybe a hardware issue?

  • Community Expert
  • Solution
1 hour ago, bavik said:

PELICAN/

This is the problem: whatever is creating this folder before the array starts

1 hour ago, bavik said:

udma crc error count is 15

This is typically a bad SATA cable; if the attributes keep increasing, replace it.

  • Author

Figured it out. Thank you for your help!

I guess I had the syslog server configured to write logs to /mnt/user/PELICAN/logs/. That's what was making the folder.

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.