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.

(SOLVED) Files not shown in user share

Featured Replies

Let me start out by saying I'm a newb to UnRaid and much appreciate any help.

For some reason when navigate to a user share Unraid => Videos =>Movies => Hollywood Movies, it shows that the folder is empty. Altho it showed up before.

However, in Main tab, click on individual disk, let say Disk 1 (using the Browse folder on the right column), and navigate to Videos =>Movies => Hollywood Movies, there would be individual movies folders shown.

Thank you for any suggestion, this problem is driving me mad :(

unraid-diagnostics-20170727-2331.zip

Edited by abn001

  • Author

I tried to xfs repair but get

root@UNRAID:~# xfs_repair-v/dev/md5
-bash: xfs_repair-v/dev/md5: No such file or directory
 

What should I do next?  Thanks in advance.

unraid-diagnostics-20170728-1915.zip

You're missing the spaces, it should be:

 

xfs_repair -v /dev/md5

 

  • Author

Thank you for the correction.  Ran repair but still unable to see files on user share :(

unraid-diagnostics-20170728-1925.zip

 

root@UNRAID:~# xfs_repair -v /dev/md5
Phase 1 - find and verify superblock...
        - block cache size set to 1406632 entries
Phase 2 - using internal log
        - zero log...
zero_log: head block 220144 tail block 220144
        - scan filesystem freespace and inode maps...
        - found root inode chunk
Phase 3 - for each AG...
        - scan and clear agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 3
        - agno = 7
        - agno = 1
        - agno = 2
        - agno = 4
        - agno = 6
        - agno = 5
Phase 5 - rebuild AG headers and trees...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - reset superblock...
Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - traversing filesystem ...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...

        XFS_REPAIR Summary    Fri Jul 28 20:35:27 2017

Phase           Start           End             Duration
Phase 1:        07/28 20:35:24  07/28 20:35:24
Phase 2:        07/28 20:35:24  07/28 20:35:24
Phase 3:        07/28 20:35:24  07/28 20:35:25  1 second
Phase 4:        07/28 20:35:25  07/28 20:35:25
Phase 5:        07/28 20:35:25  07/28 20:35:25
Phase 6:        07/28 20:35:25  07/28 20:35:26  1 second
Phase 7:        07/28 20:35:26  07/28 20:35:26

Total run time: 2 seconds
done
 

Edited by abn001

Disk 6 has corruption

 

ul 28 19:25:10 UNRAID kernel: XFS (md6): Metadata corruption detected at xfs_inode_buf_verify+0x92/0xb8, xfs_inode block 0x18ea90f88
Jul 28 19:25:10 UNRAID kernel: XFS (md6): Unmount and run xfs_repair
Jul 28 19:25:10 UNRAID kernel: XFS (md6): First 64 bytes of corrupted metadata buffer:

And, if I'm reading the logs correctly, both 5 & 6 are on a Marvel Controller (SASLP?)  This *may* be the cause of this as some users / combinations of hardware exhibit this behaviour with Marvel based controllers.

  • Author

Thank you all.  That fixed my problem.  Much appreciated. :)

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.