Jump to content

Files inaccessible after unclean shutdown


Recommended Posts

We just had a power outage so the server shutdown immediately. After bringing it back online I'm starting the array with a parity check. Strangely, many of the TV shows stored on Disk 1 are not showing under file explorer in Windows (and plex won't play them or other files that are visible). The shows and files do appear under the disk explorer in Unraid though. Shown this in the attached screenshot.

 

Are there certain steps I should take to fix this?

Appreciate any advice :)

Capture.png

fatal1ty3-diagnostics-20240205-2038.zip

Link to comment
9 hours ago, JorgeB said:

No filesystem issues that I can see, but check filesystem on disk1, run it without -n

Hi JorgeB! Thank you for replying.

 

I want to mention that my TV and Movie shares were symbolically linked under my Media share using:
ln -s /mnt/user/Movies Movies
ln -s /mnt/user/TV TV

 

I'm not sure if that has anything to do with it. I did try deleting and recreating the symbolic link to no effect. I also tried mapping the TV share directly but the files are still not there.

 

Anyway, I ran the check as you asked, and here is the output:

Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
        - 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
        - agno = 8
        - agno = 9
        - agno = 10
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
Phase 5 - rebuild AG headers and trees...
        - reset superblock...
Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - traversing filesystem ...
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...
done

 

I have then downloaded the diagnostics and attached them here.
As the drive was xfs I started in maintenance mode. Should I stop the array, start it in normal (non-maintenance mode) and see if the files are there?
 

Thanks for your help

fatal1ty3-diagnostics-20240206-1855.zip

Link to comment
36 minutes ago, JorgeB said:

Yes, though it looks like no file system issues were found.

Started the array and the files are still not showing, unfortunately.

 

Like I said, the folders and files are visible when viewing in Unraid. In fact, I've just downloaded a file via the webui and it works perfectly fine. It's just that they've disappeared in file explorer.

 

Do you reckon it's a permission issue?

Owner and permission are quite different to other folders on the same disk

 

Did some further logic checking and it seems that any sub-folder with the owner of nobody doesn't show, whilst the owner of admin does. See this in the second screenshot. So I'm thinking batch change the owner and permission, but this comment here suggests just using the new permissions tool within unraid: 

Capture.png

Screenshot 2024-02-06 at 19-44-10 FATAL1TY3_Browse.png

Edited by TekWarfare
Further insight
Link to comment

The permissions on Directories should be 777  and on Files 666.  

 

For access from Unraid shares, (From my experience on recent releases) is that the owner of a resource is not the key, it is the Group (which Unraid expects to be users and that any user who wants to have access to a resource must also be either the owner or a member of users.  The easiest way to become a member is to added as a 'Share Access' user under the USERS tab of the GUI. 

 

Futhermore, all Dockers apps (and, I assume, VM's) that write to Unraid Shares should have these parameters as follows:

 

image.png.f67a6545aab57544437123b23b0aa40d.png

 

This information comes from this posting:

 

        https://forums.unraid.net/topic/131730-update-from-69-to-6115-and-got-permission-denied/#comment-1219731

 

EDIT:  Actually in a secure environment, much of the access to a share will be through being a member of the Group.  That is way why it is necessary for the members of the Group to have full access to any resource. 

Edited by Frank1940
Link to comment

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

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...