[SOLVED] Missing All Files in Share

[dukeminster]

Hi All,

 

Hi Guys, pretty new to unraid here. But have purchased Basic and am slowly getting to grips with it, and what a great product it is.

 

I'm having an issue and wondered if i could get some help.

 

Until last night I had 8TB parity, 2x8TB and 1x500GB in the array. I replaced the 500GB with another 8TB so that now there is 4x 8TB. The way i did it was just, turning off, pulling the 500 and replacing with the 8TB and letting it rebuild. Probably not the right way but its done now. Anyway, i seem to have "lost" all my linux distros in one particular share. I can see them when I navigate the individual disks in the unraid GUI, but see nothing when browsing to the share in windows....

 

When I installed the new drive I did physically move one of the other 8TBs up a bay, and connected the sata cable which was previously for the 500gb. But from what I gather in my testing and reading in forums, I could swap all 4 around and unraid wouldnt blink, since it recognises the drives indepentanly of their sata slot.

 

Some extra info: 1TB NVME cache drive. Main array is XFS. Share is public. 

 

Some things i have tried

1. Reboot Unraid
2. Tools - Docker Safe New Perms
3. Reboot Windows Client
4. Connect to share with different windows client.

 

The share is there, but it wont let you create anything nor display all my files....any idea whats up?

 

[Squid]

3 minutes ago, dukeminster said:

The way i did it was just, turning off, pulling the 500 and replacing with the 8TB and letting it rebuild. Probably not the right way but its done now.

That is the right way

 

 

You should post your diagnostics

[dukeminster]

Thanks in advance...

 

Edited November 2, 2021 by dukeminster

[JorgeB]

Check filesystem on disk1.

[dukeminster]

Hi Jorge thanks for that, i have started the array in maintenance mode and ran xfs repair -nv

 

Output is attached. I was expecting it to tell me what command is to fix the errors. is it -d?

 

thanks

 

Edited November 2, 2021 by dukeminster

[JorgeB]

Run it again without -n or nothing will be done, if it asks for -L use it.

[dukeminster]

Perfect, that has sorted it. Thank you for your help.

[KluthR]

So, what was the issue? A bug in unRAID?

[JorgeB]

1 hour ago, KluthR said:

So, what was the issue?

File system corruption, as it should be evident by the post above:

 

3 hours ago, JorgeB said:

Check filesystem on disk1.

 

[KluthR]

This was not detected by unRAID? Is it even possible or is a manually check/repair via console wanted in that case?

[trurl]

Fix Common Problems will detect this I think.