Tyrus

I see, thanks :) Does it help us in any way, that I could identify the corrupted files on the drive with this command? ls -la /mnt/disk2/NAS/jellyfin/movies/

What about "xfs_repair -L /dev/sdb" that was suggested by AI? Is it a viable solution without high riscs?

The problems surfaced after the last system update, so I am a bit hesitant to do an other one. I was hoping to fix the problem before modifying the system, if not absolutely necessary.

Phase 1 - find and verify superblock... couldn't verify primary superblock - not enough secondary superblocks with matching geometry !!! attempting to find secondary superblock... ......................................................................................... could not find valid secondary superblock Exiting now.

Here it is :) unraidnas-diagnostics-20260202-2223.zip

So, when I try to do this, I get following error: chown: cannot read directory '/mnt/user/NAS/jellyfin/movies': Structure needs cleaning With further help from AI I could identify some files, that are corrupt on drive2 in the movies folder. I tried an other fix fileysystem via the UI on disk 2 but I don't think it did anything again. It was running for a long time, I pressed fix, it ran again for a long time and then turned to fix again. I tried it 3 consecutive times. AI suggested "xfs_repair -L /dev/md2" but with a warning of file loss on the corrupted files. It would be ok for me, I can redo them, it's just time. But is it a viable solution? Don't trust the AI with something so important. Since I have also stuff on the drive like old photos that can't be recovered.

Just tried but it didn't change anything root@UnRaidNAS:~# getfacl /mnt/user/NAS/jellyfin/movies getfacl: Removing leading '/' from absolute path names # file: mnt/user/NAS/jellyfin/movies # owner: dimi # group: users user::rwx group::rwx other::rwx root@UnRaidNAS:~# getfacl /mnt/user/NAS/jellyfin/tvshows getfacl: Removing leading '/' from absolute path names # file: mnt/user/NAS/jellyfin/tvshows # owner: nobody # group: users user::rwx group::rwx other::rwx

Hi, no it is a private share and only for one user (and a test user I created, but the test user had the same empty "movies" folder problem).

root@UnRaidNAS:~# ls -la /mnt/user/NAS/jellyfin total 20 drwxrwxrwx 1 nobody users 47 Aug 3 17:12 ./ drwxrwxrwx 1 nobody users 4096 Jan 17 20:59 ../ drwxrwxrwx 1 dimi users 8192 Dec 12 23:24 movies/ drwxrwxrwx 1 nobody users 4096 Nov 29 21:36 tvshows/

Sorry, I messed up the hierarchy a bit. So it is : - NAS (the share) - jellyfin, which child folder is the problematic one but there are many other folders here too - movies and tvshows (2 folders only, children of jellyfin) - movies is shown empty, tvshows is normal So do I have to do ls -la /mnt/user/NAS/jellyfin/movies instead?

The structure is a following: Share(called NAS) This share has two folders. Both of the folders have files but only the files of one of the folders are visible in the share. But the files are visible in the unraid file manager and are accessible. It is one of the problems that appeared after the initial problem that started this thread was fixed by rebuilding from parity. It used to work before and I haven't changed anything about this folders. I fixed the permissions on the problematic "empty" folder with the help of @trurl but unfortunately it didn't help :( We also checked naming conflicts but everything is fine there too.

Sorry for the late reply. So there is still this problem, that no files are shown in one particular folder, when I access it over the network. The Unraid file manager can see the files though. All other folders and files work without any problems. unraidnas-diagnostics-20260126-1635.zip

Hmmm, I am not sure what else I could do, to fix the file problem...😞

I understand what you mean. SMB doesn't care about uppercase letters so "Folder" and "folder" would be the same folder for it and depending on how it is accessed, it could happen that it would access the wrong folder and that's why my problematic folder could appear empty. I checked in the file browser. The folder hierarchy is NAS/parent/child(our empty folder) So for this problem to be true the parent folder would need to have an other folder inside that would have same name, but written with different upper/lower cases, right? But there is only one other folder in the "parent" folder and it has a completely different name. So I am not sure it is this problem :/

Nope, we didn't talk about SMB before. I checked but I can't see any folders with same names but different cases. I also didn't create much on the NAS, since the file system error happened and it was working fine before. First I want to know it's back to normal.