I have a share called "music" and it had about 2TB of music files.  When I go to the "SHARES" tab, and click on view to see the files in that share, I get a message that says "No listing: Too many files."  I also can't see the files in Windows Explorer, or by using Krusader.  I know the files are there though, because when I view the files by looking at the Disks, either on the "MAIN" tab or in Krusader, I can see them.  

 

I cannot see nor play the music with my music players .   Please help.  Diagnostics attached.  Thanks. 

tower-diagnostics-20210810-1735.zip

Edited August 11, 20213 yr by xrqp

Reboot.

Tried reboot, but it did not help.  I think I even did power cycle (shutdown, then power back up) prior to posting.  

Edited August 11, 20213 yr by xrqp

The syslog in the diagnostics is full of messages of the form:

Aug  9 22:18:32 Tower kernel: XFS (md5): Metadata corruption detected at xfs_buf_ioend+0x51/0x284 [xfs], xfs_inode block 0x11fe6e050 xfs_inode_buf_verify
Aug  9 22:18:32 Tower kernel: XFS (md5): Unmount and run xfs_repair
Aug  9 22:18:32 Tower kernel: XFS (md5): First 128 bytes of corrupted metadata buffer:
Aug  9 22:18:32 Tower kernel: 00000000: 24 1a 9c 92 6d 85 ce 6d 6f 93 4c d2 44 fc dc 3b  $...m..mo.L.D..;
Aug  9 22:18:32 Tower kernel: 00000010: 98 25 67 cf 3f 77 ea c1 c5 b7 19 f8 16 ee f9 6f  .%g.?w.........o
Aug  9 22:18:32 Tower kernel: 00000020: 76 48 30 f5 c9 61 87 35 a3 da 2a ee a0 d8 92 c3  vH0..a.5..*.....
Aug  9 22:18:32 Tower kernel: 00000030: cc 6c cd 9b 9b 53 a0 69 79 01 e4 94 72 d5 4f 37  .l...S.iy...r.O7
Aug  9 22:18:32 Tower kernel: 00000040: aa 93 9e 81 25 4c 5d dd d7 25 b1 ba 1c c7 68 6b  ....%L]..%....hk
Aug  9 22:18:32 Tower kernel: 00000050: 00 b6 ab b7 f7 3e 76 31 ad 48 42 a3 ae b1 05 df  .....>v1.HB.....
Aug  9 22:18:32 Tower kernel: 00000060: de da 64 5c 81 28 13 65 0b 6f 1f 49 78 a2 3e 33  ..d\.(.e.o.Ix.>3
Aug  9 22:18:32 Tower kernel: 00000070: b4 01 36 42 53 25 cc d8 e1 93 28 7f 0a 9c db 66  ..6BS%....(....f
Aug  9 22:18:32 Tower kernel: XFS (md5): metadata I/O error in "xfs_imap_to_bp+0x5c/0xa2 [xfs]" at daddr 0x11fe6e050 len 32 error 117

which shows that you have file system level corruption on disk5.   This is probably the cause of your symptoms.

The procedure for checking and repairing file system issues is covered here in the online documentation that can be accessed via the ‘Manual’ link at the bottom of the Unraid GUI.

 

I will try what you suggested.  Thanks.  How did you know which disk it is (disk 5)?  Does "md5" mean 'media disk 5'?

1 hour ago, xrqp said:

I will try what you suggested.  Thanks.  How did you know which disk it is (disk 5)?  Does "md5" mean 'media disk 5'?

Yes - the mdX numbers correspond to the diskX numbers that show in the Unraid GUI.

The xfs repair appears to have worked, it appears I got my music back.  I will separately post a general question about lost+found.  Thanks for checking my diagnostics and helping me.

9 hours ago, xrqp said:

The xfs repair appears to have worked, it appears I got my music back.  I will separately post a general question about lost+found.  Thanks for checking my diagnostics and helping me.

Glad to hear you got the music back.

 

have you even got a lost+found folder (which would show up as a User Share of that name?     You normally only get one if any corruption was such that a file can be recovered but it’s name cannot be retrieved.    If you DO have a lost+found folder then sorting it out is a labour intensive manual process, and in such a case the Linux ‘file’ command can be useful to at least determine the content type (and thus file extension) for files that have lost their name.

Yes.  I had a lost+found folder from doing xfs repair about 8 months ago.   It seemed too laborious to go thru.  Also, since it has so many files and folders, it took time just to open the folder and subfolders, in windows Explorer.   I assume the xfs repair yesterday may have added more to the old lost+found folder. 

 

I guess when it creates files there, they keep their old creation date, so I could not separate the ones from the 2 repairs.  My guess is that it is not worth it to save them, but I need to search for info and read more about it.  

 

I don't know Linux, but I may try the file command.  Thanks.

12 minutes ago, xrqp said:

 I assume the xfs repair yesterday may have added more to the old lost+found folder. 

The user shares are just the top folders on pools and array, so lost+found share is the combined contents of the lost+found for each repaired disk. Each repaired disk will have its own lost+found folder if that will help you sort things out.

Both repairs were on the same disk #5.