1 hour ago, JorgeB said:

This:

ls -la /mnt/user/NAS/jellyfin

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/

Is NAS a public share?

1 hour ago, trurl said:

Is NAS a public share?

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

See what happens if you make it public

Also post the output from:

getfacl /mnt/user/NAS/jellyfin/movies

getfacl /mnt/user/NAS/jellyfin/tvshows

21 hours ago, trurl said:

See what happens if you make it public

Just tried but it didn't change anything

11 hours ago, JorgeB said:

Also post the output from:

getfacl /mnt/user/NAS/jellyfin/movies

getfacl /mnt/user/NAS/jellyfin/tvshows

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

ACLs look OK; don't see a reason for the issue. This should not be the problem, but to change movies to also be owned by nobody, just in case it helps, type this:

chown -R nobody:users /mnt/user/NAS/jellyfin

Reboot UNuiradi, reboot the client PC, and retest. If it's still the same, try accessing that share from a different client, like your phone or a tablet, to see if it's the same.

On 1/31/2026 at 9:00 AM, JorgeB said:

ACLs look OK; don't see a reason for the issue. This should not be the problem, but to change movies to also be owned by nobody, just in case it helps, type this:

chown -R nobody:users /mnt/user/NAS/jellyfin

Reboot UNuiradi, reboot the client PC, and retest. If it's still the same, try accessing that share from a different client, like your phone or a tablet, to see if it's the same.

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.

Edited February 2Feb 2 by Tyrus

Post new diagnostics.

8 minutes ago, trurl said:

Post new diagnostics.

Here it is :)

unraidnas-diagnostics-20260202-2223.zip

Check filesystem on disk2 from the webUI. Post the output.

15 minutes ago, trurl said:

Check filesystem on disk2 from the webUI. Post the output.

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.

21 hours ago, trurl said:

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.

If you can't repair the filesystem, you would have to go to something like UFS Explorer to try to recover files.

Or reformat and restore from backup.

21 minutes ago, trurl said:

If you can't repair the filesystem, you would have to go to something like UFS Explorer to try to recover files.

Or reformat and restore from backup.

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

Edited February 3Feb 3 by Tyrus

8 minutes ago, Tyrus said:

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

That is what the webUI is doing anyway. We usually insist on using the webUI because there are several ways to get that command wrong, some just waste time, some invalidate parity.

3 minutes ago, trurl said:

That is what the webUI is doing anyway. We usually insist on using the webUI because there are several ways to get that command wrong, some just waste time, some invalidate parity.

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/

Edited February 3Feb 3 by Tyrus

The filesystem is mounted despite the corruption, so you could copy whatever it can somewhere and reformat.

5 minutes ago, Tyrus said:

dentify the corrupted files on the drive with this command?

ls -la /mnt/disk2/NAS/jellyfin/movies/

For example?