I’m having an issue with a few folders in Unraid. One folder, for example, mnt/user/Media, shows no files even though it contains them. However, mnt/drive1/Media does show files allocated to that drive.

I’ve checked permissions but that doesn’t seem to be the problem. Does anybody know how I ca fix this?

Note. I have replaced my USB drive recently

tower-diagnostics-20260125-1342.zip

Edited January 25Jan 25 by Phill360
Added Diagnostics

Attach Diagnostics ZIP to your NEXT post in this thread.

16 minutes ago, trurl said:

Attach Diagnostics ZIP to your NEXT post in this thread.

Sorry. I added diagnostic to original post.

1 minute ago, Phill360 said:

Sorry. I added diagnostic to original post.

Good thing you made that new post or anyone who had already read your first post would not know there was anything new to see in this thread. I may not have visited this thread again. That is why I always say

20 minutes ago, trurl said:

Attach Diagnostics ZIP to your NEXT post in this thread.

Why is your cache drive NTFS?

1 minute ago, trurl said:

Why is your cache drive NTFS?

I replaced the cache a few month back and I must not have reformatted the drive. I will correct this soon.

Looks like it isn't using the full capacity. If this was originally a windows system drive, it probably has multiple partitions.

What do you get from command line with this?

lsblk

And it has some entries in syslog that make me suspect corruption, though we haven't seen much of this since NTFS support for assigned disks is a new feature.

Jan 25 12:43:22 Tower kernel: ntfs3(sdc1): MFT: r=a3278, expect seq=178 instead of 157!
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Jan 25 12:43:24 Tower kernel: ntfs3(sdc1): MFT: r=25cbd, expect seq=7c instead of 78!

8 minutes ago, trurl said:

Looks like it isn't using the full capacity. If this was original a windows system drive, it probably has multiple partitions.

What do you get from command line with this?

lsblk

root@Tower:~# lsblk

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS

loop0 7:0 0 651.6M 1 loop /usr

loop1 7:1 0 173.4M 1 loop /lib

sda 8:0 1 28.6G 0 disk

└─sda1 8:1 1 28.6G 0 part /boot

sdb 8:16 0 3.6T 0 disk

└─sdb1 8:17 0 3.6T 0 part

sdc 8:32 0 894.3G 0 disk

└─sdc1 8:33 0 894.3G 0 part /mnt/cache

sdd 8:48 0 5.5T 0 disk

└─sdd1 8:49 0 5.5T 0 part

sde 8:64 0 447.1G 0 disk

└─sde1 8:65 0 447.1G 0 part /mnt/disks/Plex_Data

sdf 8:80 0 7.3T 0 disk

└─sdf1 8:81 0 7.3T 0 part

sdg 8:96 0 9.1T 0 disk

└─sdg1 8:97 0 2T 0 part

sdh 8:112 0 3.6T 0 disk

└─sdh1 8:113 0 3.6T 0 part

sdi 8:128 0 3.6T 0 disk

└─sdi1 8:129 0 3.6T 0 part

sdj 8:144 0 5.5T 0 disk

└─sdj1 8:145 0 5.5T 0 part

sdk 8:160 0 7.3T 0 disk

└─sdk1 8:161 0 7.3T 0 part

sdl 8:176 0 9.1T 0 disk

└─sdl1 8:177 0 9.1T 0 part

md1p1 9:1 0 7.3T 0 md /mnt/disk1

md2p1 9:2 0 7.3T 0 md /mnt/disk2

md3p1 9:3 0 5.5T 0 md /mnt/disk3

md4p1 9:4 0 3.6T 0 md /mnt/disk4

md5p1 9:5 0 3.6T 0 md /mnt/disk5

md6p1 9:6 0 3.6T 0 md /mnt/disk6

md7p1 9:7 0 5.5T 0 md /mnt/disk7

zram0 252:0 0 0B 0 disk

7 minutes ago, Phill360 said:

I replaced the cache a few month back and I must not have reformatted the drive. I will correct this soon.

Maybe correct this now and see if that fixes your problem. Looks like there is only 50G on there currently. Copy it to the array.

You will have to stop the array, click on the drive to get to its settings, and Erase the partitions. Set it to btrfs or ZFS. Start the array and format it. Make sure it is the only drive listed for formatting.

Just now, trurl said:

Maybe correct this now and see if that fixes your problem. Looks like there is only 50G on there currently. Copy it to the array.

You will have to stop the array, click on the drive to get to its settings, and Erase the partitions. Set it to btrfs or ZFS. Start the array and format it. Make sure it is the only drive listed for formatting.

In the process of doing it. I only have Appdata on it currently. I have stopped docker and I'm using Unbalanced to move it to the array

2 minutes ago, Phill360 said:

I only have Appdata on it currently.

Looks like appdata also has files on the array. Ideally, your docker/VM related shares - appdata, domains, system - would have all files on cache or other pool, with nothing on the array, so docker/VM will perform better, and so array disks can spin down since these files are always open.

Why do you have 200G docker.img? Have you had problems filling it? The usual cause of growing docker.img usage is an application writing to a path that isn't mapped.

3 minutes ago, trurl said:

Why do you have 200G docker.img? Have you had problems filling it? The usual cause of growing docker.img usage is an application writing to a path that isn't mapped.

I did notice it was filling up and I think it is due to JellyFin metadata. I another issue I need to fix