Fails to boot after full system upgrade

larsb · 17 June 2022 21:16

Hello everyone!

After updating Manjaro on my pinebook pro the boot process shows the manjaro logo but eventually this shows up:

Give root password for maintenance
(or press Control-D to continue):

Login with root password does not work: It won’t accept my password.

From pacman.log:

[2022-06-16T11:02:07+0200] [ALPM] upgraded manjaro-system (20220404-1 → 20220528-1)

I am wondering if the boot issue is related to:

[2022-06-16T11:56:27+0200] [ALPM] running ‘90-linux-pinebookpro.hook’…
[2022-06-16T11:56:27+0200] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-pinebookpro.preset: ‘default’
[2022-06-16T11:56:27+0200] [ALPM-SCRIPTLET] → -k 5.7.19-1-MANJARO-ARM -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2022-06-16T11:56:27+0200] [ALPM-SCRIPTLET] ==> Starting build: 5.7.19-1-MANJARO-ARM
[2022-06-16T11:56:27+0200] [ALPM-SCRIPTLET] → Running build hook: [base]
[2022-06-16T11:56:29+0200] [ALPM-SCRIPTLET] → Running build hook: [udev]
[2022-06-16T11:56:30+0200] [ALPM-SCRIPTLET] ==> ERROR: Hook ‘plymouth’ cannot be found
[2022-06-16T11:56:30+0200] [ALPM-SCRIPTLET] → Running build hook: [autodetect]
[2022-06-16T11:56:31+0200] [ALPM-SCRIPTLET] → Running build hook: [modconf]
[2022-06-16T11:56:31+0200] [ALPM-SCRIPTLET] → Running build hook: [block]
[2022-06-16T11:56:36+0200] [ALPM-SCRIPTLET] → Running build hook: [filesystems]
[2022-06-16T11:56:36+0200] [ALPM-SCRIPTLET] → Running build hook: [keyboard]
[2022-06-16T11:56:37+0200] [ALPM-SCRIPTLET] → Running build hook: [fsck]
[2022-06-16T11:56:37+0200] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2022-06-16T11:56:38+0200] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
[2022-06-16T11:56:40+0200] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete.
[2022-06-16T11:56:41+0200] [ALPM] running ‘90-mkinitcpio-install.hook’…
[2022-06-16T11:56:41+0200] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-pinebookpro.preset: ‘default’
[2022-06-16T11:56:41+0200] [ALPM-SCRIPTLET] → -k 5.7.19-1-MANJARO-ARM -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2022-06-16T11:56:41+0200] [ALPM-SCRIPTLET] ==> Starting build: 5.7.19-1-MANJARO-ARM
[2022-06-16T11:56:41+0200] [ALPM-SCRIPTLET] → Running build hook: [base]
[2022-06-16T11:56:42+0200] [ALPM-SCRIPTLET] → Running build hook: [udev]
[2022-06-16T11:56:44+0200] [ALPM-SCRIPTLET] ==> ERROR: Hook ‘plymouth’ cannot be found
[2022-06-16T11:56:44+0200] [ALPM-SCRIPTLET] → Running build hook: [autodetect]
[2022-06-16T11:56:44+0200] [ALPM-SCRIPTLET] → Running build hook: [modconf]
[2022-06-16T11:56:44+0200] [ALPM-SCRIPTLET] → Running build hook: [block]
[2022-06-16T11:56:46+0200] [ALPM-SCRIPTLET] → Running build hook: [filesystems]
[2022-06-16T11:56:47+0200] [ALPM-SCRIPTLET] → Running build hook: [keyboard]
[2022-06-16T11:56:47+0200] [ALPM-SCRIPTLET] → Running build hook: [fsck]
[2022-06-16T11:56:48+0200] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2022-06-16T11:56:48+0200] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
[2022-06-16T11:56:51+0200] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete.

Can I fix my boot problems by creating a Manjaro-KDE live-usbstick, update Manjaro on it and replace the initramfs-linux.img on my SD-Card with the one from the live-usbstick? Or are the troubles during booting unrelated to that ERROR from pacman.log?

Thank you =)

spikerguy · 4 July 2022 08:43

Boot from live sdcard and share the following.

lsblk -o Name, partuuid, Label

This data from emmc rootfs
cat /etc/fstab

Keruskerfuerst · 4 July 2022 10:18

From the log above, I can see, that the initrd is not completly build.
You must croot into the system ans run mkinitcpio -P.

larsb · 5 July 2022 19:21

I should mention my harddrive setup:

emmc (mmcblk1): Linux distro that I do not use (the one the pinebook was shipped with originally - some ubuntu or debian).
nvme (nvme0n1): Data
Micro-SD (mmcblk0): Manjaro

Here is output of lsblk -o NAME,PARTUUID,LABEL:

NAME         PARTUUID                             LABEL
mmcblk1                                           
|-mmcblk1p1  0666f440-01                          BOOT
`-mmcblk1p2  0666f440-02                          
mmcblk1boot0                                      
mmcblk1boot1                                      
mmcblk1rpmb                                       
mmcblk0                                           
`-mmcblk0p1  32c0149c-01                          ROOT
nvme0n1                                           
`-nvme0n1p1  07b3e47f-3b0d-544b-bf4c-6a0afdd7b072 Data

And here cat /etc/fstab from the Manjaro rootfs (on the SD-card):

# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
LABEL=BOOT_MNJRO  /boot   vfat    defaults,noexec,nodev,showexec     0   0

@Keruskerfuerst: chrooting into the system and running mkinitcpio -P is an option that I also thought about when I saw that the kernel on my system differs from the one that is installed on a live-usb-stick. Is there any tutorial on how to accomplish that? I.e. can I follow these instructions: [HowTo] Chroot from or into any Linux distribution

Cheers
Lars

Strit · 5 July 2022 19:31

Your mmcblk0 (sd card?) only has one partition? that either means that this install is well over 2 years old or you have a special setup.

And the fstab is wrong, as your install is so old. Our current packages have an issue where very old installs, like yours, gets a /boot partition added, but it does not exist on your system. So my best advise, is to edit /etc/fstab and remove the last line, save the file and try booting again after that.
We are working on fixing the package that caused this, so hopefully it will not happen anymore after this.

larsb · 5 July 2022 19:34

It could be that the install is over 2 years old. I will try to find this one out. But yes, I also recognized that on newer installs there 2 partitions.

However, I did post the wrong fstab originally (the one from the system on the emmc). I edited my post some time ago and corrected that. Sorry for that.

EDIT: I think you read the correct fstab though … I will try your advise to remove that line, so rebooting now.

EDIT2: Now that worked like a charm - Manjaro is back and working. Thanks a lot Strit!

EDIT3: And yes, I can confirm, the install is from end of March 2020.

system · 8 July 2022 09:35

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.