You are not logged in.

#1 2022-05-04 11:35:33

Borshow
Member
Registered: 2022-05-03
Posts: 5

Failure to boot after adding new fstab entry

Hi guys,

I have issue with this bug too but actually my system does not boot, only in emergency mode.
journactl -xb showing these issues:
MDS CPU bug present and SMT on, data leak possible.
ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PROO._CPC] AE_NOT_FOUND (20211217/psparse-330)

Can you help me to resolve this issue and boot my system again to default?

Thanks

Offline

#2 2022-05-04 13:52:13

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,667

Re: Failure to boot after adding new fstab entry

It's highly unlikely that this is the cause of your failing boot.
The error will be more around unloadable modules or unresolvable devices/fstab entries?

Offline

#3 2022-05-04 17:04:04

Borshow
Member
Registered: 2022-05-03
Posts: 5

Re: Failure to boot after adding new fstab entry

I had this issue (boot stack) few days ago but I disabled secure boot and was alright but now it's not working.
I have made a HDD to automount earlier but I restarted my OS couple of times since with no issue.
In journactl show this too (what you mentioned):
systemd(1): Dependency failed for File System Check on /dev/disk/by-uuid/17106cec.....
A start job for unit systemd-fsck@dev-disk-by/.... service has failed.
systemd(1): Dependency failed for /mnt/sdc1
A start job for unit mnt-sdc1.mount has failed

The last line where I made to automount my HDD.
So you think this can be the problem?

What shall I do?

Thanks

Offline

#4 2022-05-04 17:06:02

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,285

Re: Failure to boot after adding new fstab entry

Make a new thread it's highly unlikely your issue is related to the plain error spam from the OP (or rather I'll do).

FWIW using /dev/sd* as device identifiers on your kernel command line or your fstab is highly discouraged, use persistend identifiers like the UUID: https://wiki.archlinux.org/title/Persis … ng#by-uuid

Last edited by V1del (2022-05-04 17:07:25)

Offline

#5 2022-05-04 17:29:17

Borshow
Member
Registered: 2022-05-03
Posts: 5

Re: Failure to boot after adding new fstab entry

This is the link what I followed to automount my HDD.

https://www.linuxbabe.com/desktop-linux … s-on-linux

I've just deleted in fstab the automount line for my HDD and the system booted perfect. THANKS FOR YOUR HELP!

So you meant just change the sd× to the UUID?

Thanks

Offline

#6 2022-05-04 19:52:59

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,667

Re: Failure to boot after adding new fstab entry

Borshow wrote:

So you meant just change the sd× to the UUID? Thanks

Yes. You can find it in "lsblk -f"

Offline

#7 2022-05-04 20:01:27

Borshow
Member
Registered: 2022-05-03
Posts: 5

Re: Failure to boot after adding new fstab entry

Great. Thanks one more time!

Offline

Board footer

Powered by FluxBB