kernel failed to execute /init. Not booting.

ranurag · 2023-07-23 15:34:43

This is newly installed distro.
I barely altered/touch files.

seth · 2023-07-23 15:35:15

This doesn't look overly suspicous, and still:

file reports

/usr/lib/systemd/systemd: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=c9c4121a7937fd9df375572a970ca3d19bea222b, for GNU/Linux 4.4.0, stripped

but ldd errors

 not a dynamic executable

and curl apparently segfaults.

Since the curl version on the iso doesn't:

cat /mnt/usr/lib/systemd/systemd | curl -F 'file=@-' 0x0.st

Edit:

This is newly installed distro.
I barely altered/touch files.

Is this blackarch, btw?

Last edited by seth (2023-07-23 15:36:04)

ranurag · 2023-07-23 15:39:49

Yes blackarch

seth · 2023-07-23 15:47:37

https://bbs.archlinux.org/misc.php?action=rules

My best guess is that there's something fundamentally broken with the dynamic linker
https://man.archlinux.org/man/core/man- … n#LD_DEBUG

But I've no idea whether and how BA broke anything there.
Did you try to update the system from iso (w/ mounting the /mnt/boot partition, but w/o chrooting; https://wiki.archlinux.org/title/Pacman … n_upgrade)?
However, the iso should™ be the blackacrch one for that as well.

ranurag · 2023-07-23 15:56:47

seth wrote:

Did you try to update the system from iso (w/ mounting the /mnt/boot partition, but w/o chrooting; https://wiki.archlinux.org/title/Pacman … n_upgrade)?
However, the iso should™ be the blackacrch one for that as well.

Yes I have tried it . Thank you for the support (appreciated).

seth · 2023-07-23 15:59:36

You can also brute-force re-install all packages (the pacman wiki describes how to)
And check how much free space is left on your /boot (did you regenerate the initramfs after cleaning up and pay attention it doesn't abort for lack of space?)

ranurag · 2023-07-23 16:06:15

Yes I can, if somehow i get to know how this happens then it will be good. So i will continue my search on it. And till then use the another one.

Onto82 · 2023-08-20 23:55:27

I get the same Error type (-2) & Kernel panic, since July 27th 2023.
Verbose failed boot :

https://ibb.co/pLchRs6 (upper part)
https://ibb.co/jWGyp2W (the display of each line is not tidy. Check the middle part of this photo, where HOME=/ is)
https://ibb.co/VLvKKYf (lower part)

On that day, I did the following:
1) pacman -Syu
2) installed snapd, according to the following link:
(I could follow until Step 2 where I had to reboot, and could not continue. The last command executed before that reboot was "sudo systemctl enable --now snapd.socket") https://www.makeuseof.com/install-set-u … rch-linux/

+Also, on some reboots, UEFI/BIOS only offers 1 booting option (from live flash ISO).
On other reboots, it offers a second option called "grub" (or empty string).

====================================================================
====================================================================
My system: ArchLinux, on an Acer Swift 3 [Intel Core 5, 10th gen]

I chrooted using my flash ISO, and
my output is similar to user ranurag's, except for:

># ls /boot
EFI, grub, initramfs-linux-fallback.img, initramfs-linux.img, vmlinuz-linux
># ls /run
systemd

># lsinitcpio /boot/initramfs-linux.img |& grep -E '(init|systemd)'
(all the same but I lack the last one: usr/lib/udev/rules.d/11-dm-initramfs.rules )

># ls -l /usr/lib/systemd/libsystemd-*
(all the same but I have version 254.1-1.so in both files)

># cat /etc/mkinitcpio.conf:
HOOKS=(all the same but I have one hook called "kms", and have no hook called "encrypt")

(outside chroot, within the Linux installation media)
># sudo LC_ALL=C pacman --sysroot /mnt -Qkk | grep -v ', 0 altered files' > touch.txt
># cat touch.txt | curl -F 'f:1=<-' ix.io
http://ix.io/4E7w

Just as user ranurag, I get
># file /bin/init
/bin/init: symbolic link to ../lib/systemd/systemd

># ldd usr/lib/systemd/systemd
not a dynamic executable

More info (chrooted):
># lsblk -f
http://ix.io/4E8z

># cat /boot/grub/grub.cfg
http://ix.io/4E8A
(it stops inside menuentry 'Arch Linux'. Last echo shown, being 'Loading initial ramdisk ...')

># cat /etc/default/grub
http://ix.io/4E8D

More info (out of chroot):
># lsblk -f
http://ix.io/4E8F

># lsblk
http://ix.io/4E8E

-------------------
Ever since that reboot, I've been following purposed solutions, in different fori, to no success
(I reverted each of these minor changes after not succeding).

Namely:
a) donwgrading/upgrading the kernel,
I have tried:
i) linux-6.4.6.arch1-1-x86_64
i) linux-6.4.9.arch1-1-x86_64 (I was using this one when I upgraded and installed snap)
i) linux-6.4.10.arch1-1-x86_64
i) linux-6.4.11.arch1-1-x86_64 (released in August 19th 2023)

b) re-installing grub

c) extracting initramfs.img & manual modification of /etc/mkinitcpio.conf (by writing the file paths in the FILES section of /etc/mkinitcpio.conf)

d) checking BIOS/UEFI upgrade

e) Memtest86+ are Ok (caption during Memtest process https://ibb.co/Z2qMz6Z)

f) and others related to grub files configuration/update.

Last edited by Onto82 (2023-08-21 06:14:42)

seth · 2023-08-21 06:48:42

># sudo LC_ALL=C pacman --sysroot /mnt -Qkk | grep -v ', 0 altered files' > touch.txt
># cat touch.txt | curl -F 'f:1=<-' ix.io
http://ix.io/4E7w

Did you look at that? The installation is obviously masively corrupted, in particular

systemd: 1360 total files, 571 altered files

seth wrote:

You can also brute-force re-install all packages (the pacman wiki describes how to)

Onto82 · 2023-08-21 09:56:02

Seth, thank you for replying,
I still haven't analyzed that output,
I'll do that rightaway.

Ok, then re-install will be necessary,
I'll go with that, thank you again

seth · 2023-08-21 13:00:01

To be clear, it is not necessary to re-install the system from scratch, just re-install all packages to restore their integrity.

Onto82 · 2023-08-22 01:56:58

Well.. I finally could boot again, I'm back again in Arch!
I just had to try a couple more updates.

However the problem of altered files persists.. (vide infra)
-----------------------------------------------------------------------------

What I did was:

update pacman's mirrors (w reflector)
re-install all packages, by following the pacman wiki section that seth linked in post #36.
I tried both
```
pacman -Qnq | pacman -S - 
```
and
```
 pacman -S $(pacman -Qnq) 
```
just in case...
But there were, still, lots of altered files (specially systemd)
```
sudo LC_ALL=C pacman --sysroot /mnt -Qkk | grep -v ', 0 altered files'
```
http://ix.io/4Ecp
which, when diffcompared to the one in post #34, referenced by seth (my initial situation), only reduced 4 lines to '0 altered files'. The rest is still there, albeit with a lesser amount of altered files on most lines.
Anyway, I rebooted and, as sometimes happened, BIOS/UEFI would not offer booting Arch, only offering the ISO flash drive.
NOTE: I, later, looked for these 4 packages (which had gained '0 altered files' in this step) and were:
mkinitcpio
mkinitcpio-busybox
mod_dnssd
mongo-c-driver

Hence, I looked for more info and tried a couple of commands before going to sleep:

First:

 pacman -Qk 2>/dev/null | grep -v ' 0 missing files' | cut -d: -f1 |
    while read -r package; do
        pacman -S "$package" --overwrite "*" --noconfirm
    done

 pacman -Qkk 1>/dev/null 2>&1 | grep checksum 
      (returned nothing)

[both, taken from https://unix.stackexchange.com/question … em-upgrade ]

Second:

 mkinitcpio -P
grub-mkconfig -o /boot/grub/grub.cfg
pacman -S grub

rebooted to no success.

Finally, I tried
```
 pacman -Syu
pacman -S $(pacman -Qnq) 
```
and that reboot worked fine.

However, when executing
```
 sudo LC_ALL=C pacman --sysroot /mnt -Qkk | grep -v ', 0 altered files' 
```
it returned http://ix.io/4EcB
which, upon diffcomparison to the one in the present post (item 2.), only differs in one python package and one ruby package. So I still have 991 packages with altered files (generally 1 to 10 altered files per package) .

Last edited by Onto82 (2023-08-22 05:04:52)

seth · 2023-08-22 06:09:56

- systemd: 1360 total files, 571 altered files
+ systemd: 1360 total files, 56 altered files

So far less files are affected, but I'd say that your disk is dying.

Arch Linux

#26 2023-07-23 15:34:43

Re: kernel failed to execute /init. Not booting.

#27 2023-07-23 15:35:15

Re: kernel failed to execute /init. Not booting.

#28 2023-07-23 15:39:49

Re: kernel failed to execute /init. Not booting.

#29 2023-07-23 15:47:37

Re: kernel failed to execute /init. Not booting.

#30 2023-07-23 15:56:47

Re: kernel failed to execute /init. Not booting.

#31 2023-07-23 15:59:36

Re: kernel failed to execute /init. Not booting.

#32 2023-07-23 16:06:15

Re: kernel failed to execute /init. Not booting.

#33 2023-08-20 23:55:27

Re: kernel failed to execute /init. Not booting.

#34 2023-08-21 06:48:42

Re: kernel failed to execute /init. Not booting.

#35 2023-08-21 09:56:02

Re: kernel failed to execute /init. Not booting.

#36 2023-08-21 13:00:01

Re: kernel failed to execute /init. Not booting.

#37 2023-08-22 01:56:58

Re: kernel failed to execute /init. Not booting.

#38 2023-08-22 06:09:56

Re: kernel failed to execute /init. Not booting.

Board footer