[SOLVED]System doesn't boot

Morta · 2022-01-23 21:30:07

I fucked up the system. I rebooted and ends up in a kernel panic I have to reinstall the system. Shit!

Last edited by Morta (2022-01-25 16:21:22)

seth · 2022-01-23 21:36:15

After editing the exports you need to run "exportfs -r"

What kernel panic? Mount failure? Because of the bind mount to the encrypted (?) partition?
Just comment that line in the fstab.

Morta · 2022-01-23 21:44:01

seth wrote:

After editing the exports you need to run "exportfs -r"
What kernel panic? Mount failure? Because of the bind mount to the encrypted (?) partition?
Just comment that line in the fstab.

I don’t know. It’s doesn’t come up anymore nor even a password prompt. I have to Chroot the system and reinstall the hole basic system.

It doesn’t write anything of failed mount but yes it’s is encrypted. Do you think it’s because of encrypted drive?

Last edited by Morta (2022-01-23 21:46:30)

seth · 2022-01-23 21:50:36

I think it's because of the bind mount that's not tagged "noauto"
Do you see some output if you remove the "quiet" parameter?

Morta · 2022-01-23 22:00:06

seth wrote:

I think it's because of the bind mount that's not tagged "noauto"
Do you see some output if you remove the "quiet" parameter?

I chrooted. Now I have to commentout the bind mount to /etc/fstab

Where I have to put nouauto options?

I also removed quiet from arch.conf in /boot/loaders/entries

Morta · 2022-01-23 22:09:51

No I'm see nothing with not quiet.

Can't even boot in emergency shell.

It's written Kernel panic not snycing no working init found Try pasing init= option to kernel.

What that means?

seth · 2022-01-23 22:09:55

Where I have to put nouauto options?

In the options field… "man fstab"
However, since you commented the line, that's irrelevant for now.

seth · 2022-01-23 22:12:12

That either means the initramfs is broken or you edited the kernel commandline a bit too much.
Re-installing the kernel from the chroot (don't forget to mount the /boot partition) should™ fix the former.

Morta · 2022-01-23 22:16:10

seth wrote:

That either means the initramfs is broken or you edited the kernel commandline a bit too much.
Re-installing the kernel from the chroot (don't forget to mount the /boot partition) should™ fix the former.

Ok. I mounted all partitions include /boot

and did

pacman -Sy base base-devel linux linux-lts linux-firmware but doesn't fix it. Have I forgotten something?

Have I to do also bootctl update and mkinticpio -P ?

Last edited by Morta (2022-01-23 22:21:28)

seth · 2022-01-23 22:27:40

Were there any errors?

seth wrote:

That either … or you edited the kernel commandline a bit too much.

lsinitcpio /boot/initramfs-linux.img | grep init
lsinitcpio /boot/initramfs-linux-lts.img | grep init

Morta · 2022-01-23 22:32:45

seth wrote:

Were there any errors?
seth wrote:
That either … or you edited the kernel commandline a bit too much.
lsinitcpio /boot/initramfs-linux.img | grep init
lsinitcpio /boot/initramfs-linux-lts.img | grep init

https://termbin.com/1liq
https://termbin.com/bdzt

No errors by rebuild initramfs.

How I can fix that without new setup?

Last edited by Morta (2022-01-23 22:35:30)

Morta · 2022-01-23 22:44:27

I got a error when I do

bootctl --esp-path=/efi --boot-path=/boot

Failed to check file system type of /efi: No such file or directory

ls -la /boot

https://termbin.com/xy4t

lsblk | nc termbin.com 9999

https://termbin.com/yrmo

Last edited by Morta (2022-01-23 22:47:47)

seth · 2022-01-23 22:44:48

The init binaries are there - what is the exact error you're getting atm? (In doubt link a photo)

Edit: there's no path "/efi" (where you would have been supposed to mount the ESP) - if you omit that parameter, bootctl might find the ESP in /boot/EFI

Last edited by seth (2022-01-23 22:47:59)

Morta · 2022-01-23 22:54:18

https://abload.de/img/cea43c37-7068-4474-bg7kz7.jpeg

moderator edit -- replaced oversized image with link.
Pasting pictures and code

Last edited by 2ManyDogs (2022-01-24 00:03:59)

Morta · 2022-01-24 04:22:34

seth wrote:

The init binaries are there - what is the exact error you're getting atm? (In doubt link a photo)
Edit: there's no path "/efi" (where you would have been supposed to mount the ESP) - if you omit that parameter, bootctl might find the ESP in /boot/EFI

bootctl --esp-path=/boot/efi --boot-path=/boot install

failed in /boot/efi is not the root of the filesystem

What I have to do?

Have I to format /dev/nvme0n1p1 then remount and after it bootctl --esp-path=/boot --boot-path=/boot install ?

I got every time "/dev/block/259:1" has wrong type for extended boot loader partition?

I found this issue

https://github.com/systemd/systemd/issues/16151

How to fix it?

Last edited by Morta (2022-01-24 05:25:57)

seth · 2022-01-24 07:46:31

The systemd issue seems to be around a failure to decrypt the boot device but it seemed to have been a one-off and from your fstab, your boot partition is also not encrypted.
Regarding "what to do", how did you install the bootloader originally, wheres your ESP and esp.: why do you think you have to do this anyway?
The last error you reported was about a failure "no working init found" but not only have you re-installed the kernel and regenerated the initramfs, it's also there according to lsinitcpio.

=>
1. What is the error you currently face and (no paraphrase, link a photo of your monitor)
2. What's the output of "lsblk -f"
3. Aside what's in this thread: what else did you do before the reboot that might have caused any of this?

V1del · 2022-01-24 08:22:03

Splitting this off of the NFS thread as suggested so this can be looked at seperately.

Morta · 2022-01-24 11:51:09

seth wrote:

The systemd issue seems to be around a failure to decrypt the boot device but it seemed to have been a one-off and from your fstab, your boot partition is also not encrypted.
Regarding "what to do", how did you install the bootloader originally, wheres your ESP and esp.: why do you think you have to do this anyway?
The last error you reported was about a failure "no working init found" but not only have you re-installed the kernel and regenerated the initramfs, it's also there according to lsinitcpio.

I installed the Bootloader with bootctl

bootctl --esp-path=/boot --boot-path=/boot install

But after every automatically rebuild of initramfs it’s kills the bootloader

1. What is the error you currently face and (no paraphrase, link a photo of your monitor)

Same error

https://abload.de/img/cea43c37-7068-4474-bg7kz7.jpeg

2. What's the output of "lsblk -f"

https://termbin.com/9q60

3. Aside what's in this thread: what else did you do before the reboot that might have caused any of this?

I installed nextcloud and Nginx that broke the nfs-server and samba but samba does worked again.

efibootmgr -v

https://termbin.com/s06j

shows me three Linux Boot Manager entries

Have I to downgrade systemd that bootctl works again?

Last edited by Morta (2022-01-24 12:58:19)

seth · 2022-01-24 14:28:57

I installed nextcloud and Nginx that broke the nfs-server and samba

Did you maybe, possibly, potentially, in this pursuit - conduct a partial update (ran "pacman -Sy" and then re/installed a bunch of packages)?

From the chroot:

sudo pacman -Syu

Also install and try to boot the lts kernel (5.16 is giving several people boot headaches and 5.16.2 is from last Friday)

Edit: please don't bump by DM either…

Last edited by seth (2022-01-24 14:29:57)

Morta · 2022-01-24 14:45:13

seth wrote:

I installed nextcloud and Nginx that broke the nfs-server and samba
Did you maybe, possibly, potentially, in this pursuit - conduct a partial update (ran "pacman -Sy" and then re/installed a bunch of packages)?
From the chroot:
sudo pacman -Syu
Also install and try to boot the lts kernel (5.16 is giving several people boot headaches and 5.16.2 is from last Friday)
Edit: please don't bump by DM either…

Yes. I did pacman -Sy and install a bunch of packages.

The error message was exactly the same on both kernel mainline and lts

I will try chroot and pacman -Syu

And give a try

Sorry for DM

Morta · 2022-01-24 14:52:09

bootctl | nc termbin.com 9999

https://termbin.com/qvlw

Shows me that boot loader sets ESP information are wrong

I can't even choose between LTS and MAINLINE Kernel.

EDIT: I fixed with the loader.conf but same error on both possibility.

It's directly coming the Kernel offset panic

Last edited by Morta (2022-01-24 15:14:51)

seth · 2022-01-24 15:26:08

Did you shred /bin/init or /lib/systemd/systemd on the installed system?

pacman -Qkk systemd systemd-sysvcompat
pacman -Syu systemd

Morta · 2022-01-24 15:57:26

seth wrote:

Did you shred /bin/init or /lib/systemd/systemd on the installed system?
pacman -Qkk systemd systemd-sysvcompat
pacman -Syu systemd

pacman -Qkk systemd systemd-sysvcompat

https://termbin.com/apmh

/bin/init exists and /lib/systemd/system exists too. I can't remember to shred it.

I did

pacman -Syu systemd

cat /var/log/pacman.log | nc termbin.com 9999

https://termbin.com/wlkv

Last edited by Morta (2022-01-24 16:02:51)

Morta · 2022-01-24 19:25:41

What is happend when /bin/init or /lib/systemd/systemd is shred?

I dosen’t help reinstall systemd

Anyone can help me?

Last edited by Morta (2022-01-24 19:58:04)

seth · 2022-01-24 20:04:09

"shred" means "torn to pieces" (it's just to say that the file got damaged) - and according to pacman -Qkk systemd, that's not the case either.
Are you being asked to decrypt the root partition before the error shows up?
Can you boot if you edit the kernel parameters and add "init=/bin/bash"?

Arch Linux

#1 2022-01-23 21:30:07

[SOLVED]System doesn't boot

#2 2022-01-23 21:36:15

Re: [SOLVED]System doesn't boot

#3 2022-01-23 21:44:01

Re: [SOLVED]System doesn't boot

#4 2022-01-23 21:50:36

Re: [SOLVED]System doesn't boot

#5 2022-01-23 22:00:06

Re: [SOLVED]System doesn't boot

#6 2022-01-23 22:09:51

Re: [SOLVED]System doesn't boot

#7 2022-01-23 22:09:55

Re: [SOLVED]System doesn't boot

#8 2022-01-23 22:12:12

Re: [SOLVED]System doesn't boot

#9 2022-01-23 22:16:10

Re: [SOLVED]System doesn't boot

#10 2022-01-23 22:27:40

Re: [SOLVED]System doesn't boot

#11 2022-01-23 22:32:45

Re: [SOLVED]System doesn't boot

#12 2022-01-23 22:44:27

Re: [SOLVED]System doesn't boot

#13 2022-01-23 22:44:48

Re: [SOLVED]System doesn't boot

#14 2022-01-23 22:54:18

Re: [SOLVED]System doesn't boot

#15 2022-01-24 04:22:34

Re: [SOLVED]System doesn't boot

#16 2022-01-24 07:46:31

Re: [SOLVED]System doesn't boot

#17 2022-01-24 08:22:03

Re: [SOLVED]System doesn't boot

#18 2022-01-24 11:51:09

Re: [SOLVED]System doesn't boot

#19 2022-01-24 14:28:57

Re: [SOLVED]System doesn't boot

#20 2022-01-24 14:45:13

Re: [SOLVED]System doesn't boot

#21 2022-01-24 14:52:09

Re: [SOLVED]System doesn't boot

#22 2022-01-24 15:26:08

Re: [SOLVED]System doesn't boot

#23 2022-01-24 15:57:26

Re: [SOLVED]System doesn't boot

#24 2022-01-24 19:25:41

Re: [SOLVED]System doesn't boot

#25 2022-01-24 20:04:09

Re: [SOLVED]System doesn't boot

Board footer