[SOLVED] Re: Boot issue

[Hans <hans.ullrich@loop.de>]

I am answering myself. It must be the opened UUID. Looks like this problem is 
solved. 

Thank you all for the fast response! I hope, my question was not too annoying.

But I am very very happy, to get this little issue so easily solved - and 
learned something, too.

Thank you all, you made a man happy!

Best regards

Hans

Am Sonntag, 27. August 2023, 21:12:30 CEST schrieb Hans:
> So, now I added all UUIDs. But I am not quite sure for the enrcypted /home
> partition. The UUID changes when the device is luks-opened.
> 
> Which one must be in the fstab? The one from "lsblk -f /dev/sda4" or
> "lsblk -f /dev/mapper/home"?
> 
> Am Sonntag, 27. August 2023, 20:26:46 CEST schrieb Greg Wooledge:
> > On Sun, Aug 27, 2023 at 08:19:35PM +0200, Hans wrote:
> > > When I boot the system, then the drives are not mounted as set in
> > > /etc/fstab. For example, the SDD should mounted to /space, and the
> > > unencrypted HDD shall be mounted to /daten.
> > > 
> > > But it seems, sometimes the mountpoints are not correct, so the SDD is
> > > not
> > > mounted to /space, but to /daten.
> > 
> > This sounds like you used the dynamically assigned device names (e.g.
> > /dev/sda1 and so on) in fstab.  If that's what you did, stop doing that.
> > 
> > Use UUIDs or Labels instead.  These won't change, while the device names
> > *will* change.