Sysvinit works, Systemd doesn't [Solved]

[dolphin_oracle]

I know, you meant "sudo touch" :)

you know me too well

[Huckleberry Finn]

[zoli62]

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

Code: Select all

sudo touch /etc/systemd/system-generators/systemd-gpt-auto-generator

and reboot. can't hurt to try.

Thanks, next time I'm at the machine, I'll try this too.

[Richard]

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?

[asqwerth]

Nah, it would just have a 90s countdown, then still boot up if swap uuid has changed.

[zoli62]

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 situation above that the installation of another distribution has formatted the. swap partition. What to do in such cases? Maybe temporarily turn off the swap partition?

[Richard]

use blkid & lsblk to check the actual UUID.

[profhawk]

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.

[profhawk]

@zoli62 That's why I always recommend swap to file instead of a swap partition. It's not as catastrophic then a swap partition. It works much better with things like snapshots or cloning software like clonezilla.

[zoli62]

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.