One of my share subfolders is showing empty in windows and "Structure needs cleaning" on cli

[mbc0]

Hi, 

Just as the title describes I cannot access one of my subfolders in a share but plex and other dockers seem to be able to?

 

I have attached my diags, if someone could take a look I would really appreciate it!  The folder in question is /mnt/user/TV Shows/tv

 

This is a new build, upgraded motherboard & cpu about a week or so ago that has been running fine although yesterday I was unable to access any shares, stopped the array and restarted and all seemed fine but I suspect it was the start of this problem.

 

 

Many thanks, 

[mbc0]

Just this moment thought of something!

 

Last week, I lost all my appdata on my cache drive, the physical drive is a Samsung 970 Evo Plus NVME, one morning I woke up and it was empty!

 

I have now added 2 Rocket NVME drives to create a cache pool and the Samsung I moved to a secondary cache to handle caching for my shares including the TV Shows folder I am having an issue with.  

 

It maybe nothing to do with it but it does seem a coincidence?

[JorgeB]

Please post the diagnostics.

[mbc0]

So sorry, I forgot to add the Diags! 

unraid1-diagnostics-20230210-1450.zip

[mbc0]

4 minutes ago, JorgeB said:

Please post the diagnostics.

Done! Sorry!

[trurl]

Check filesystem on disk10

[mbc0]

49 minutes ago, trurl said:

Check filesystem on disk10

Found some problems! Should I do a standard repair?

 

Phase 1 - find and verify superblock... - block cache size set to 1481960 entries Phase 2 - using internal log - zero log... zero_log: head block 443485 tail block 443485 - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 illegal attribute format -36, ino 8589934725 bad attribute fork in inode 8589934725, would clear attr fork would have cleared inode 8589934725 - agno = 5 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 2 - agno = 5 - agno = 1 - agno = 3 - agno = 0 - agno = 4 illegal attribute format -36, ino 8589934725 bad attribute fork in inode 8589934725, would clear attr fork would have cleared inode 8589934725 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 Metadata corruption detected at 0x46e19c, inode 0x200000085 dinode couldn't map inode 8589934725, err = 117 - agno = 5 - traversal finished ... - moving disconnected inodes to lost+found ... disconnected dir inode 10841621675, would move to lost+found Phase 7 - verify link counts... Metadata corruption detected at 0x46e19c, inode 0x200000085 dinode couldn't map inode 8589934725, err = 117, can't compare link counts No modify flag set, skipping filesystem flush and exiting.

[mbc0]

OK, so I carried out a repair and everything is now back looking like it should do but there is no lost+found folder on disk 10 so does that mean I have not lost any files? 

[JorgeB]

3 minutes ago, mbc0 said:

but there is no lost+found folder

That's good news.

[mbc0]

Thank you for all your help @JorgeB @trurl