I’ll not ask again after this.
I’m writing on my french phone. It’s sometimes change what i type
There is no change when i type ls -al /home
The chown command doesn’t work because it’s missing an operator, even though I’ve retyped it several times
ok - last time (!)
I don’t want to know whether it changed or not.
I want to see the result.
So I can tell what the situation is and give you the correct command.
Thee lines
drwxr-xr- 3 root root
drwxr-xr-x 17 root root
drwx------ 362 root root Lost+founs
Very confusing.
You did:
and your answer was:
Therefore:
/home is mounted
But it seems to be empty.
It was not empty before:
and your response was:
… and now there is nothing …
I do not know what to make of this anymore
Apparently: your /home is completely empty
However that might have happened …
Ok. I’m going to ask a colleague for help. It’ll be easier with the post in front of him
Thank you for your help and your time
if /home is mounted
should give you a full listing of the first level of the contents of your user account
If the command doesn’t give you more than:
the /home is completely empty
and it is no wonder why you have the problems that you have
With ls -al /home/* i’ve more lines with m’y username instead of root
That doesn’t make sense.
ls /home
or
ls -al /home
should return at least one user account - “pierre” it is (I took that from your picture in your first post)
ls -al /home/* lists that and everything further down
Why would that work, while listing the level above returns nothing?
If your user name is pierre
then the command from above would be:
chown -R pierre:pierre /home/pierre
The lines at the top correspond to the end of ls -al/home/*.
Impossible to Access to /home/pierre: No file with this name
This looks like a listing of the lost+found directory
Something with your first file system check has gone wrong
and now you have only the unnamed rescued files left
That’s what it looks like to me.
Very hard to restore - I know that much.
I hope you do have a backup of /home/pierre
I have. Thanks again
Good!
The problem was very likely this command from the thread that you mentioned:
It assumed “yes” as the answer for every error it found - perhaps you gave it the wrong device name or who knows what happened then …
Normally I had chosen sdb2. I had checked before with lsblk -f
In that case there really was - and probably still is - a problem with the hardware, with the disk.
Normally the fsck can correct errors without half the system ending up as lost+found.
Ok. A tech will look
As an infrequent forum user, please take some time to familiarise yourself with Forum requirements; in particular, the many ways to use the forum to your benefit:
The Update Announcements should be checked frequently for important update related information.
These announcements contain a Known Issues and Solutions section and should generally be checked before posting a request for support.
Output of the following command formatted according to forum requirements (see links above) may be useful for those wishing to help:
inxi --admin --verbosity=8 --filter --no-host --width
Be prepared to provide more information and outputs from other commands when asked.
Regards.