Issue after drive rebuild. I think it's a folder permission issue.

[Hostile89]

Hello folks,

Unraid 6.9.2

I recently had a drive fail and replaced and rebuilt it but now I'm having an issue with a folder inside one my Shares. I have a video share that has two folders (TV Shows and Movies). The TV Shows folder seems to be working fine but I can't write to the Movies folder. When using the GUI to navigate to the folder it will often say "No listing: Too many files".

 

I have attached diagnostics.

Any help is greatly appreciated.

 

Thanks

tower-diagnostics-20220727-1417.zip

[JorgeB]

Check filesystem on disk2.

[Hostile89]

I have a wall of text from that. Is there something to look for or should I post it?

[trurl]

4 minutes ago, Hostile89 said:

post it

 

[Hostile89]

pastebin

[trurl]

Don't want to go to external site. Zip and attach 

[Hostile89]

Attached

drive check.rtf

drive check.zip

Edited July 27, 2022 by Hostile89

[trurl]

Plain text please 

[Hostile89]

drive check 2.zip

[trurl]

That's a lot to repair.

No modify flag set

You would have to run it without -n to get it to actually do the repair.

 

Seems unusual that it would need that much repair and yet still be mountable. And encryption might make that even more complicated.

 

Wait for another opinion @JorgeB before you do anything.

 

[trurl]

Do you have backups of anything important and irreplaceable?

[trurl]

Did you do this check from the webUI? It is easy to get the command wrong if you try to do it from the command line.

[Hostile89]

I ran it -nv just to check. I have backups so I'm not overly worried about losing it all but it would be nice to keep most of it. So at this point its basically run "xfs_repair -v /dev/md2" and hope it still works?

 

Thanks again for your help.

 

 

[trurl]

22 minutes ago, trurl said:

Did you do this check from the webUI? It is easy to get the command wrong if you try to do it from the command line.

 

15 minutes ago, Hostile89 said:

xfs_repair -v /dev/md2

That is the wrong command for encrypted disks.

 

Do it again with -n (nomodify) from the webUI and it will use the correct command. Then we can see what it thinks needs repairing.

[Hostile89]

webui -n.zip

[trurl]

That looks just as bad, I would wait on another opinion

[JorgeB]

Basically the only option is to fix the filesystem, this corruption after a rebuild suggests parity wasn't 100% in sync, do you still have the old disk intact or it failed/died?

[Hostile89]

It had a ton of read errors when I pulled it but I haven't hooked it back up to anything to see.

[JorgeB]

Repair the filesystem and then depending on the result you can see if the old disk can still be used to recover data if needed.

[Hostile89]

Appreciate the help. Repair seemed to work. I'll keep the old drive in case I find anything missing/corrupted.

 

Thanks again.

[JorgeB]

Look for a lost+found folder and any files there.

[trurl]

14 minutes ago, JorgeB said:

Look for a lost+found folder and any files there.

It would show up as a new user share named 'lost+found'

[Hostile89]

Thanks. Just a bunch of numbered folders. Some are empty some have an empty Thumbs folder. 

[trurl]

lost+found is where repair puts things it can't figure out, folder and files without names, files with no idea what folder they belonged to.

 

How large is the lost+found user share?

 

You can see how much of each disk is used by each user share by clicking Compute... for it on the User Shares page.