Systemd boot - Cannot open access to console, the root account is locked [Solved]

[Catalin-]

Done:
1.

Code: Select all

sudo passwd root

2.

dumb question, if you remove the job scheduler, (which uses cron) does the the boot improve?

Now I get it like this https://i.imgur.com/ROwtrpd.jpg

I don't like the ACPI errors neither but a developer from this forum told me this it's something normal.. https://forum.mxlinux.org/viewtopic.php ... 72#p683072
They are not as bad as PCIE flooding errors that I used to have on the laptop which i tried with Huckleberry Finn to make work but.. but this is another story.

[dolphin_oracle]

my new guess is that something in your fstab has the wrong UUID.

Code: Select all

cat /etc/fstab

and

Code: Select all

sudo blkid

may shed some light.

[Catalin-]

cat /etc/fstab

Code: Select all

$ cat /etc/fstab
# Pluggable devices are handled by uDev, they are not in fstab
UUID=7b80403e-f1bb-40a2-bfb7-ca024d1884ec   /               ext4   discard,noatime                 1 1 
UUID=9e4bf024-388d-4bac-b39d-110dda8c3713   /home           ext4   noatime                         1 2 
UUID=d0c4bf5d-b443-4e1e-940b-7b382b067dbf   swap            swap   discard                         0 2 
UUID=957D-A008                              /boot/efi       vfat   noatime,dmask=0002,fmask=0113   0 0 
UUID=100b0c34-ade9-4d04-a12c-898db9ca2a3d   /mnt/HDD/HDD1   ext4   defaults                        0 0 
UUID=227b998a-4bf3-4da2-aee1-c1a1ea480b64   /mnt/HDD/HDD2   ext4   defaults                        0 0 

sudo blkid

Code: Select all

$ sudo blkid
/dev/sdb1: LABEL="homeMX" UUID="9e4bf024-388d-4bac-b39d-110dda8c3713" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="897a042f-9dc8-5b4d-af12-1b9c52f9007d"
/dev/sdb2: UUID="100b0c34-ade9-4d04-a12c-898db9ca2a3d" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="22dceee0-f34f-f64c-99c9-499fde1ce521"
/dev/sdb3: UUID="227b998a-4bf3-4da2-aee1-c1a1ea480b64" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="3e9b8b18-6e80-4842-bc65-da029a0f4db6"
/dev/sdb4: UUID="a2702f41-04c1-452b-9818-568de968e0a7" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="8221f8fe-535a-9b4f-9e44-0ff20b4676e1"
/dev/sda1: LABEL_FATBOOT="BOOT_EFI" LABEL="BOOT_EFI" UUID="B22B-87AE" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="f419b698-17ac-0c40-932f-4641be02c85f"
/dev/sda2: LABEL="rootMX21" UUID="7b80403e-f1bb-40a2-bfb7-ca024d1884ec" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="98c7ef40-48b2-8e4a-810a-9f952939f7a0"
/dev/sda4: LABEL="swapMX" UUID="d0c4bf5d-b443-4e1e-940b-7b382b067dbf" TYPE="swap" PARTUUID="45008913-fe0d-7941-9902-d785e80665d9"

So.. I have to replace UUID=957D-A008 with UUID="B22B-87AE" right?

[Huckleberry Finn]

Good catch . Just, the question is: Why doesn't it cause any issues with the default (SysV)init ?

[Catalin-]

Good catch . Just, the question is: Why doesn't it cause any issues with the default (SysV)init ?

Because (SysV)init is superior

You guys are the Linux experts here, I've been only using Linux for like 4-5 months now but usually from what I've read on the internet, with systemd, if one thing goes wrong then the whole system goes down, pretty much like a domino game.
Now I've also heard for example that Clear Linux can mount your drives even without having an fstab directory? Like okay that's crazy.

I thought to use systemd as it might make it easier with making software run automatically in the background. Also lately I've seen Timeshift acting weird like making snapshots at odd hours, missing a day sometimes or not making as many as I want to.

Edit- I have to go now but I will come back with a reply after this!

[dolphin_oracle]

Good catch . Just, the question is: Why doesn't it cause any issues with the default (SysV)init ?

because sysVInit doesn't do any mounting, unlike systemd.

Code: Select all

# Pluggable devices are handled by uDev, they are not in fstab
UUID=7b80403e-f1bb-40a2-bfb7-ca024d1884ec   /               ext4   discard,noatime                 1 1 
UUID=9e4bf024-388d-4bac-b39d-110dda8c3713   /home           ext4   noatime                         1 2 
UUID=d0c4bf5d-b443-4e1e-940b-7b382b067dbf   swap            swap   discard                         0 2 
UUID=957D-A008                              /boot/efi       vfat   noatime,dmask=0002,fmask=0113   0 0 
UUID=100b0c34-ade9-4d04-a12c-898db9ca2a3d   /mnt/HDD/HDD1   ext4   defaults                        0 0 
UUID=227b998a-4bf3-4da2-aee1-c1a1ea480b64   /mnt/HDD/HDD2   ext4   defaults                        0 0 

OK, I think that UUID=957D-A008 should be UUID=B22B-87AE for the efi partition. Just edit your fstab and you should be good.

fun part is that even though systemd tries to mount it, and times out, its not actually harmful to not mount an efi partition. its a convenience thing.

[Catalin-]

Thanks guys. This was the issue, now it works!

About the other topic https://forum.mxlinux.org/viewtopic.php ... 28#p684628
Regarding this issue I will have come back as I tried to make my laptop run again on Manjaro but it started freezing. At the moment it's running and "accepting" Garuda Xfce.
God knows why and I tried like all distros out there (Ubuntu and its flavours, Linux Mint, Fedora, Modicia, Linux Lite, Clear Linux, Ultramarine, Zorin, Debian OG, Pop_OS! etc) and they all have some issue. Mostly all distros freeze during the installation, I suspect some PCIE continous error happening in the background.. not sure how a Linux installation could be started in a way that it's not freezing by hardware incompatibility. And one that doesn't eat free space afterwards.

I can't keep it on Garuda as my family members don't know how to use it. The same issue that I had on MX with it running out of space also happened on PC Linux distro. But i'll get back on that thread.

[Huckleberry Finn]

Posted there about that issue.