"ERROR: device 'UUID=...' not found" and "mount: /new_root: can't find UUID=..." errors on HP Laptop

[chillbruh]

As for mkinitcpio.conf, I got the idea from this post:

Boot error: mount: /new_root: can't find UUID=

It could also help to modify /etc/mkinitcpio.conf as follows before rebuilding the initramfs. On the line that reads… HOOKS=(base udev autodetect modconf kms block keyboard keymap filesystems) … or something similar to that, replace the udev hook by systemd and keymap by sd-vconsole. When you then recreate the initcpios, systemd will detect your actual runtime configuration and include all the necessary modules. Also check which compression algorithm is being used — it’s at the…

[Wollie]

@chillbruh

Boot0004* USB Drive (UEFI) - KingstonDataTraveler 3.0PMAP PciRoot(0x0)/Pci(0x14,0x0)/USB(13,0)/CDROM(1,0x7482bc,0x8000)0000424f

At least at the moment your firmware is booting from KingstonDataTraveler.

@chillbruh

Boot0000* Manjaro HD(1,GPT,b24e8f64-8b4c-457e-a4b7-36e1256dc898,0x200,0x12c00)/File(\EFI\Manjaro\grubx64.efi)

This does not seem to be the right partition if I compare the UUID/Partition-ID.

[chillbruh]

I’ve checked the checksum of the latest ISO image. The SHA512 checksum matches with what I have. I am using manjaro-kde-23.1.1-231223-linux66.iso, which is the latest Plasma KDE build offered.

[Wollie]

I would try to restore the boot loader again. So manjaro-chroot and then:

# grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=Manjaro --recheck
# grub-mkconfig -o /boot/grub/grub.cfg
# exit
$ exit

and reboot.

It still could be required to select the Manajro entry as the one to be booted from within your firmware. (This is not the grub menu!)

Also, please provide output of

cat /etc/default/grub

There might be some wrong settings.

[soundofthunder]

@Wollie

It still could be still required to select the Manajro entry as the one to be booted from within your firmware.

This might be true, despite Manjaro previously being indicated as first in the boot order.

Check BIOS and ensure the Manjaro entry is first, disable others.
Is your BIOS otherwise setup as per UEFI requirements?

[chillbruh]

I tried restoring the boot loader again as directed, still got the same error from within the emergency shell.

On the off-chance it didn’t choose the Manjaro entry, I pressed F9 on my laptop, and chose “Manjaro” from the listing. Same error. I then restarted the machine, pressed F9, chose Manjaro, and then immediately hit the escape key. I tried choosing the main option for starting Manjaro, and also choosing the Linux66 kernel, on both the regular kernel and the fallback, still the same issue.

Here is the output of /etc/default/grub:

# GRUB boot loader configuration

GRUB_DEFAULT=saved
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash udev.log_priority=3"
GRUB_CMDLINE_LINUX=""

# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"

# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK=y

# Set to 'countdown' or 'menu' to change timeout behavior,
# press ESC key to display menu.
GRUB_TIMEOUT_STYLE=hidden

# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console

# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command 'videoinfo'
GRUB_GFXMODE=auto

# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep

# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true

# Uncomment and set to the desired menu colors.  Used by normal and wallpaper
# modes only.  Entries specified as foreground/background.
GRUB_COLOR_NORMAL="light-gray/black"
GRUB_COLOR_HIGHLIGHT="green/black"

# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/usr/share/grub/background.png"
GRUB_THEME="/usr/share/grub/themes/manjaro/theme.txt"

# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"

# Uncomment to make GRUB remember the last selection. This requires
# setting 'GRUB_DEFAULT=saved' above.
GRUB_SAVEDEFAULT=true

# Uncomment to disable submenus in boot menu
#GRUB_DISABLE_SUBMENU=y

# Uncomment this option to enable os-prober execution in the grub-mkconfig command
GRUB_DISABLE_OS_PROBER=false

# Uncomment to ensure that the root filesystem is mounted read-only so that
# systemd-fsck can run the check automatically. We use 'fsck' by default, which
# needs 'rw' as boot parameter, to avoid delay in boot-time. 'fsck' needs to be
# removed from 'mkinitcpio.conf' to make 'systemd-fsck' work.
# See also Arch-Wiki: https://wiki.archlinux.org/index.php/Fsck#Boot_time_checking
#GRUB_ROOT_FS_RO=true

[Wollie]

@chillbruh

nouveau.modeset=1 i915.modeset=1 radeon.modeset=1

Where are these set? Is the grub you posted from within manjaro-chroot?

[soundofthunder]

@chillbruh

I pressed F9 on my laptop, and chose “Manjaro” from the listing

That’s not quite what I meant. If you can reach your BIOS, look for the Boot section and make sure Manjaro is first. This is only a longshot, in any case.

[chillbruh]

Correct, the one I posted previously was inside manjaro-chroot. Here is the output from outside manjaro-chroot, in a new terminal window:

GRUB_DEFAULT=saved
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX=""

# If you want to enable the save default function, uncomment the following
# line, and set GRUB_DEFAULT to saved.
GRUB_SAVEDEFAULT=true

# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"

# Uncomment to enable Hidden Menu, and optionally hide the timeout count
#GRUB_HIDDEN_TIMEOUT=5
#GRUB_HIDDEN_TIMEOUT_QUIET=true

# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console

# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=auto

# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep

# Uncomment if you want GRUB to pass to the Linux kernel the old parameter 
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx" 
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true

# Uncomment and set to the desired menu colors.  Used by normal and wallpaper 
# modes only.  Entries specified as foreground/background.
GRUB_COLOR_NORMAL="light-gray/black"
GRUB_COLOR_HIGHLIGHT="green/black"

# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/usr/share/grub/background.png"
#GRUB_THEME="/path/to/gfxtheme"

# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"

[soundofthunder]

# Uncomment this option to enable os-prober execution in the grub-mkconfig command
GRUB_DISABLE_OS_PROBER=false

and other entries seem to be miising.
This line in particular I would tend to re-add (uncommented), even though it would be more relevant in a multiboot system.

[Wollie]

@chillbruh

System:
  Kernel 6.6.8-2-MANJARO arch x86_64 bits 64 compiler gcc v 13.2.1 clocksource tsc
    available acpi_pm parameters BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC
    misobasedir=manjaro misolabel=MANJARO_KDE_2311 quiet systemd.show_status=1 splash driver=free
    nouveau.modeset=1 i915.modeset=1 radeon.modeset=1

I still wonder where this is set in your case:
nouveau.modeset=1 i915.modeset=1 radeon.modeset=1

Usually, I would have assumed it came from your /etc/default/grub… but it isn’t.

[chillbruh]

I’m not entirely too sure, I’ve tried inxi -Fza in both the Live USB and manjaro-chroot environments, both having those three parameters set within the kernel parameters. And yet they don’t seem to appear in /etc/default/grub for either…

[soundofthunder]

I found a similar error in Arch forums. See if Posts #7 and #8 (the apparent solution) might apply to your situation.

And another; which doesn’t necessarily seem related, but you might glean something useful from it. And yet another as vague as the others, and yet all found a solution.

I’m afraid I have not much more to offer. I’ll chime in again, if I think of anything useful. Cheers.

[chillbruh]

I tried booting up without having anything plugged into the laptop, although I had the same issue as before.

Out of curiosity, I went ahead and ran two commands to reinstall and reconfigure the Linux kernel, which outputs as following:

[manjaro /]# pacman -S linux66 linux66-headers
warning: linux66-6.6.8-2 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (3) pahole-1:1.25-4  linux66-6.6.8-2  linux66-headers-6.6.8-2

Total Download Size:    32.54 MiB
Total Installed Size:  255.11 MiB
Net Upgrade Size:      120.01 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
 pahole-1:1.25-4-x86_64                294.6 KiB   737 KiB/s 00:00 [####################################] 100%
 linux66-headers-6.6.8-2-x86_64         32.2 MiB  20.0 MiB/s 00:02 [####################################] 100%
 Total (2/2)                            32.5 MiB  16.2 MiB/s 00:02 [####################################] 100%
(3/3) checking keys in keyring                                     [####################################] 100%
(3/3) checking package integrity                                   [####################################] 100%
(3/3) loading package files                                        [####################################] 100%
(3/3) checking for file conflicts                                  [####################################] 100%
(3/3) checking available disk space                                [####################################] 100%
:: Running pre-transaction hooks...
(1/1) Creating Timeshift snapshot before upgrade...
==> skipping timeshift-autosnap due skipRsyncAutosnap in /etc/timeshift-autosnap.conf set to TRUE.
:: Processing package changes...
(1/3) reinstalling linux66                                         [####################################] 100%
(2/3) installing pahole                                            [####################################] 100%
Optional dependencies for pahole
    ostra-cg: Generate call graphs from encoded traces
(3/3) installing linux66-headers                                   [####################################] 100%
:: Running post-transaction hooks...
(1/5) Arming ConditionNeedsUpdate...
(2/5) Updating module dependencies...
(3/5) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux66.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.6-x86_64 -g /boot/initramfs-6.6-x86_64.img --microcode /boot/intel-ucode.img
==> Starting build: '6.6.8-2-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [kms]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [plymouth]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.6-x86_64.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux66.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.6-x86_64 -g /boot/initramfs-6.6-x86_64-fallback.img -S autodetect --microcode /boot/intel-ucode.img
==> Starting build: '6.6.8-2-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [plymouth]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.6-x86_64-fallback.img'
==> Image generation successful
(4/5) Refreshing PackageKit...
Error connecting: Could not connect: No such file or directory
error: command failed to execute correctly
(5/5) Updating Grub-Bootmenu
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-6.6-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.6-x86_64.img
Found initrd fallback image: /boot/initramfs-6.6-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
ERROR: unsupported sector size 4096 on /dev/sdb.
grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your device.map.
Adding boot menu entry for UEFI Firmware Settings ...
Root filesystem isn't btrfs
If you think an error has occurred, please file a bug report at "https://github.com/Antynea/grub-btrfs"
Found memtest86+ image: /boot/memtest86+/memtest.bin
Found memtest86+ EFI image: /boot/memtest86+/memtest.efi
done
[manjaro /]# mkinitcpio -P
==> Building image from preset: /etc/mkinitcpio.d/linux66.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.6-x86_64 -g /boot/initramfs-6.6-x86_64.img --microcode /boot/intel-ucode.img
==> Starting build: '6.6.8-2-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [kms]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [plymouth]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.6-x86_64.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux66.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.6-x86_64 -g /boot/initramfs-6.6-x86_64-fallback.img -S autodetect --microcode /boot/intel-ucode.img
==> Starting build: '6.6.8-2-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [plymouth]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.6-x86_64-fallback.img'
==> Image generation successful

I’ll try to reboot my laptop now, and see if I get the emergency shell again.

[chillbruh]

Nope, same issue after reboot.

The only thing I can think of that may help is a different kernel version. As I previously stated, when I installed Linux Mint, it was able to boot on Kernel 5.15, albeit without working Wi-Fi or a touchpad. However as soon as I updated to kernel 6.5 to fix this issue, I got the same device error on bootup.

So unless the installation process for Linux Mint went perfectly and it wasn’t just the kernel, it could be a kernel issue.

Going ahead with installing a new kernel, I went ahead and installed linux515, and removed linux66 from the system. Once I ran mkinitcpio -P, I got some warnings, but went ahead and rebooted afterwards.

Now, when I start the system, it no longer shows the Manjaro loading symbol, and all I see is this:

[ OK ] Started CUPS Scheduler
[ OK ] Finished Hold until boot process finishes up
[ OK ] Finished Terminate Plymouth Boot Screen
-

Not sure what to make of this.

[cscs]

Remove plymouth … because it can cause problems … and its only eye-candy booting animation.

Plymouth errors, Could not start Display server on vt 1

Remove plymouth then? Well… you can test with some boot parameters: plymouth.enable=0 disablehooks=plymouth You can add this to options during boot from grub if you hit ‘e’ at selection. You can also apply it persistently by editing /etc/default/grub and adding to the GRUB_CMDLINE_LINUX line. ex: GRUB_CMDLINE_LINUX="plymouth.enable=0 disablehooks=plymouth" Then run: sudo update-grub And reboot. To remove it completely: Uninstall: sudo pacman -Rns plymouth plymouth-theme-manjaro (im…

(for whatever reason I didnt mention the actual plymouth option in grub. splash.)

More of the same

Failed to start Terminate Plymouth Boot Screen

Plymouth is the boot splash things before KDE/SDDM 's own splash screen. You can remove and disable it if you like … its nothing but bloat. (that would entail uninstalling the package[s], removing the plymouth entries in /etc/mkinitcpio.conf and then running sudo mkinitcpio -P && sudo update-grub) EDIT. Oh yeah, I forgot there would also be splash in /etc/default/grub … this should similarly be removed before running sudo update-grub. Note: this can be replaced with quiet if you are aiming …

[chillbruh]

I was bouncing around with other Linux versions, and eventually tried other solutions for Manjaro, when it occurred to me where those three parameters were coming from.

When I booted into the Live USB, I am given the two options to boot Boot with open source drivers and Boot with proprietary drivers. If I don’t enter either one, and hit “e” to edit the boot options, I can see that those three parameters are within the boot options for both environments.

[chillbruh]

I tried disabling Plymouth, however the boot still got hung up.

[chillbruh]

One other thing I should note, whenever I install Manjaro either with “Erase Disk” or “Manual Partitioning”, there is always a small amount of unallocated space before and after all partitions. I’m not sure if this would cause issues with booting, or if the UUID’s would change somehow after installation.

Also, when I wipe the drive with GParted, and I go to boot up the Live USB, I noticed that it only shows the USB drive as being something I can boot. Then, after installing Manjaro, I notice that I now have two more options, “Manjaro” and “Windows Boot Manager”, even though I never installed Windows after the wipe.

[soundofthunder]

@chillbruh

there is always a small amount of unallocated space before and after all partitions

Would that unallocated space between partitions equal 128MB?

The only time I’ve encountered this was with early MacOS drives (GPT formatted with HFS+); I mention this only to illustrate the timeframe. These gaps were by design, to workaround common MacOS issues of the time; with partition alignment, from memory; however, this should have no place in modern architecture.

GDisk is a tool I frequently use to pre-condition a disk ready for installing Linux; creating the partition layout I want, manually; and naturally, separating the / and /home partitions. Then I progress to install Linux to the pre-defined partitions, using the manual partitioning method; only without actually partitioning; only formatting and adding the mount points as needed.

I mention this mainly because there have been; albeit few; recent posts mentioning malaligned partitions and other issues seemingly as a result of partitioning via Calamares.

While this adds nothing to the immediate issue, it’s an option for any subsequent reinstall, thereby avoiding partitioning with Calamares. This might also serve to rule out partitioning via Calamares being a possible culprit.