On Monday, February 1, 2021 at 8:20:07 AM UTC-6, Mike wrote:
> In article ,
> Martin Gregorie  wrote: 
> 
> >/lost+found is normally empty on a clean partition with no disk errors
> Correct.
> >So, why do you think there are no files or directories on your NAS disk 
> >since you apparently haven't run "sudo ls /"
> Because "ls /" would show the root filesystem of the machine (irrelevant) 
> and the OP did mount the affected disk on /mnt/NAS, and then did 
> 
> ls /mnt/NAS 
> 
> which showed an empty disk has been mounted, save for lost+found (which I 
> suggested they look *inside*, not just squint *at* as they've done so far!)
> >How many files were you expecting to see?
> 22591. As per fsck's claim that there are 22591 files in the fscked-up 
> filesystem (hiding!) 
> 
> Tips about restoring /home etc. may be a red-herring here, as there is 
> no indication there is anything *wrong* with /home, or the / filesystem,
proceed 
> with caution. 
> 
> Make very sure you know WHICH filesystem you are
mounting/fscking/wiping/restoring 
> before doing it. 
> 
> The best time to shoot yourself in the *other* foot, is when you are just 
> recovering from shooting yourself in the first one!
> -- 
> --------------------------------------+------------------------------------ 
> Mike Brown: mjb[-at-]signal11.org.uk | http://www.signal11.org.uk


Thanks to all.  I found all the missing folders in lost+found with
#inode-numbers.  It was easy to move those folders into the main directory and
rename to original names as best as I remember.  All seems well now.  I just
got this 8TB drive for 
christmas and am hoping it is not dying already.  I learned about lost+found in
this adventure.  I always wondered what it was used for.  I found that fsck did
a better job than gparted for resurrecting drive.

  --Steven

--- SoupGate-Win32 v1.05