MX Linux Forum

Every time someone recommends Debian or a Debian Stable based distro, a very common complaint against it is that the packages are too old to run and, as they say, are more unstable than more updated repos. Also tied directly to this is the accusation that Debian doesn't support new enough hardware....

Many years ago, systemd would go to emegency shell if the swap was formatted during installation of another distro. UUID of swap changed. Maybe it still does? Final solution. You're right, it wasn't just the swap partition that was the problem, but the EFI partition, whose UUID changed for some mys...

Many years ago, systemd would go to emegency shell if the swap was formatted during installation of another distro. UUID of swap changed. Maybe it still does? Final solution. You're right, it wasn't just the swap partition that was the problem, but the EFI partition, whose UUID changed for some mys...

@DO, yes I thought about that. There is more automation that probably obviates the need to tweak fstab. I think you are correct, the issue is deeper than fstab. I have only ever used systemd for a while when Manjaro went there. My main reason for hopping away from Manjaro. Haven't tried EndeavourOS...

Our efi partition is mounted in fstab as well. Strticlty speaking it’s not required to mount it at all. So you can comment the line out in fstab and see if that helps Bingo! ● mx State: running Jobs: 0 queued Failed: 0 units Since: Thu 2021-12-02 16:24:31 CET; 5min ago CGroup: / ├─user.slice │ └─us...

As root, make a backup of the file, /etc/fstab, of the distro controlling the boot. Compare the UUID of swap partition to the result of blkid from fstab of distro controlling the boot. If different, then change the UUID in /etc/fstab and reboot. Note: blkid gives all the info though not formatted v...

Richard wrote: ↑Sun Nov 28, 2021 10:20 pm use blkid & lsblk to check the actual UUID.

And if I looked at the current UUID, what else to do?

profhawk wrote: ↑Wed Dec 01, 2021 12:50 am I'm surprised sysv is even running at all. From what I read in the logs your efi partition is improperly configured causing time out issues.

I created the EFI partition during the installation of another distribution.

Many years ago, systemd would go to emegency shell if the swap was formatted during installation of another distro. UUID of swap changed. Maybe it still does? You maybe right. I remember seeing a similar error message in the terminal at startup and it was in the log. For me, this is exactly the sit...

I wonder if the systemd-fstab-generator or maybe the systemd-gpt-generator is failing. I tend to think its the second, since a swap file is also referenced. maybe make an empty file sudo touch /etc/systemd/system-generators/systemd-gpt-auto-generator and reboot. can't hurt to try. Thanks, next time...