Something went wrong...

[Nils Kassube]

On 18.07.24 Bas G. Roufs wrote:
> Op do 18 jul. 2024 09:07 schreef Nils Kassube <kassube at gmx.net>:
> > On 18.07.24 Bas G. Roufs wrote:
> > > I could not find anymore home-new. However. I DID copy bas and all
> > > subfolders from sda3 to sda5/bas.
> >
> > Was that before replacing /etc/fstab with the new version?
>
> Yes!
>
> > Maybe sda5 was not mounted to the expected place.
>
>
> I could see sda5, Camino-casa via Midnight Commander. This is only possible
> when mounted.

Well, how did you know that the partition was mounted? I think with mc you only see the folder where it should be mounted which is named Camino-casa. If the partition was mounted at this folder you should see the home-new folder.

> You can check it with the command
> >
> > mount | grep /dev/sda
> >
>
> Can I do this via:
>
> Kubuntu 24.04 in recovery mode?

Yes, in recovery mode the partitions should be mounted to the right places according to /etc/fstab.

> or via the same OS at a Ventoy live usb?

No, if you use a live system the fstab of the internal disk are ignored and the output should be blank.

> How can I copy command line output in such situations?

That's a bit tricky. There are two options:

You could append " 2>&1 |tee -a /root/logfile.txt" to the command which would write a file logfile.txt in the /root folder. For the mount command above it would be

mount | grep /dev/sda 2>&1 |tee -a /root/logfile.txt

the "2>&1" will combine standard out and standard error so you logfile includes error messages and "tee -a" is used to append the output to the logfile and also show it on the terminal.

Or as an alternative you could install the program gpm which provides mouse support to the terminal. Then you would run a command, mark the relevant output with the mouse, open a logfile with a text editor like nano and then paste the marked text by pressing the middle mouse button (wheel).

> > > However, whenever I try to access the system, I do not manage. I get
> > stuck
> > > after. the password. Changing the password in emergency mofe does not
> > help.
> >
> > That was after replacing /etc/fstab with the new version?
>
>
> Yes.
>
> The password shouldn't be the problem because it was working before.
>
>
> I agree.
>
> I'd rather think it is a problem of permissions or missing /home/bas
> > folder. When you are in emergency mode you should first check that the
> > partitions are mounted correctly with the mount command above, i.e. sda3
> > mounted at / and sda5 mounted at /home.
>
>
> I'll try this later today.
>
> If that isn't OK, you could check the file /var/log/syslog for mounting
> > errors.
> >
>
> Accessible via the emergency or recovery mode?

Yes, you can access it in recovery mode.

> > Then you can check that /home/bas exists and the permissions are OK with
> > the command
> >
> > ls -la /home
> >
> > and the output should look like this:
> >
> > drwxr-xr-x  4 root root 4096 Dec 26  2023 .
> > drwxr-xr-x 26 root root 4096 Jul 14 08:43 ..
> > drwxr-x--- 56 bas  bas  4096 Jul 18 08:03 bas
> > ^^^^^^^^^^    ^^^^^^^^^                   ^^^  only these parts are
> > important here.
> >
> > With the command
> >
> > ls -lA /home/bas
> >
>
>
> All possible in the recovery mode?

Yes, all the commands were meant to be used in recovery mode.

> > you could check that the files and folders in your $HOME are owned by bas.
> > If the permissions are wrong you could change it with the command
> >
> > chown -R bas:bas /home/bas
> >
>
> I get this.
>
> Possible in the recovery mode?

Yes.

> > but I suppose your /home/bas is missing.
> >
>
> What can I do if it is like that?
>
> Is there a way to recover it?

Yes, please see my other mail from today.

> Or is better to reformat the whole 1 TB  SSD, after which I take recourse
> to the Floxclone  iso backup and the Backintime user data backups at the
> big external SSD?

That's another option - but I don't know if it is easier.


Nils