packages
packages copied to clipboard
getsolus
Reinstall of linux-current failed with clr-boot-manager error: FATAL: Cannot mount boot device
Please confirm there isn't an existing open bug report
- [X] I have searched open bugs for this issue
Summary
Reinstall of linux-current failed with an error from clr-boot-manager
After doing a check for broken packages, the following were listed as broken
Reordering install order so system.base packages come first.
Following packages will be installed:
font-droid-ttf golang linux-current linux-lts
The attempted reinstall of linux-current failed with an error (linux-lts worked)
Installing 4 / 4
linux-current-6.10.6-300-1-x86_64.eopkg [cached]
Installing linux-current, version 6.10.6, release 300
Extracting the files of linux-current
Installed linux-current
[✓] Syncing filesystems success
[✗] Updating clr-boot-manager failed
A copy of the command output follows:
[FATAL] cbm (../src/bootman/bootman.c:L562): FATAL: Cannot mount boot device /dev/nvme0n1p1 on /boot: No such device
[✗] Updating clr-boot-manager failed
A copy of the command output follows:
[FATAL] cbm (../src/bootman/bootman.c:L562): FATAL: Cannot mount boot device /dev/nvme0n1p1 on /boot: No such device
[✓] Running depmod on kernel 6.10.6-300.current success
[✓] Running depmod on kernel 6.6.47-252.lts success
[✓] Compiling and Reloading AppArmor profiles success
[✓] Rebuilding font cache success
[✓] Updating mimetype database success
This was the command used to find and fix broken packages (from the Help Center)
sudo eopkg check | grep Broken | awk '{print $4}' | xargs -r sudo eopkg it --reinstall
Steps to reproduce
- Run
sudo eopkg check | grep Broken | awk '{print $4}' | xargs -r sudo eopkg it --reinstall
I don't know if simply trying to reinstall linux-current will trigger the error
Expected result
linux-current is reinstalled if necessary
Actual result
Error
[FATAL] cbm (../src/bootman/bootman.c:L562): FATAL: Cannot mount boot device /dev/nvme0n1p1 on /boot: No such device
Environment
- [X] Is system up to date?
Repo
Unstable
Desktop Environment
Plasma
System details
Operating System: Solus 4.5 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.6-300.current (64-bit) Graphics Platform: Wayland Processors: 16 × 11th Gen Intel® Core™ i7-11800H @ 2.30GHz Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: Dell Inc. Product Name: XPS 17 9710
Other comments
This has affected at least one other user on stable. forum post
Running this was successful:
sudo eopkg it --reinstall linux-current
Can you (or anyone with the same issue) provide the output of the following command if it fails?
sudo env CBM_DEBUG=1 clr-boot-manager update
Additionally, the output of sudo journalctl -k around the time that the failure occurs would probably be helpful to determine where the issue is.
got the same problem, fresh installation + sudo eopkg up
sudo env CBM_DEBUG=1 clr-boot-manager update
[DEBUG] cbm (../src/cli/cli.c:L142): No such file: //etc/kernel/update_efi_vars [INFO] cbm (../src/bootman/bootman.c:L787): Current running kernel: 6.6.9-269.current [DEBUG] cbm (../src/bootman/bootman.c:L141): shim-systemd caps: 0x26, wanted: 0x02 [DEBUG] cbm (../src/bootman/bootman.c:L156): UEFI boot now selected (shim-systemd) [INFO] cbm (../src/bootman/bootman.c:L807): path ///etc/kernel/initrd.d does not exist [INFO] cbm (../src/bootman/bootman.c:L807): path ///usr/lib64/kernel/initrd.d does not exist [INFO] cbm (../src/bootman/bootman.c:L503): Checking for mounted boot dir [FATAL] cbm (../src/bootman/bootman.c:L520): Cannot determine boot device
@Prichman: that looks like a different error to me. Could you create a new issue? Include the output of the following commands:
sudo bootctl --no-pager
sudo efibootmgr
sudo blkid
Can you (or anyone with the same issue) provide the output of the following command if it fails?
sudo env CBM_DEBUG=1 clr-boot-manager update
[DEBUG] cbm (../src/cli/cli.c:L142): No such file: //etc/kernel/update_efi_vars [INFO] cbm (../src/bootman/bootman.c:L787): Current running kernel: 6.6.49-253.lts [INFO] cbm (../src/bootman/sysconfig.c:L179): Discovered UEFI ESP: /dev/disk/by-partuuid/e0ee4067-2145-498e-90d4-b6c9499d1607 [INFO] cbm (../src/bootman/sysconfig.c:L256): Fully resolved boot device: /dev/nvme0n1p1 [DEBUG] cbm (../src/lib/probe.c:L290): Root device exists on device-mapper configuration [DEBUG] cbm (../src/bootman/bootman.c:L141): shim-systemd caps: 0x26, wanted: 0x26 [DEBUG] cbm (../src/bootman/bootman.c:L156): UEFI boot now selected (shim-systemd) [INFO] cbm (../src/bootman/bootman.c:L807): path ///etc/kernel/initrd.d does not exist [INFO] cbm (../src/bootman/bootman.c:L807): path ///usr/lib64/kernel/initrd.d does not exist [INFO] cbm (../src/bootman/bootman.c:L503): Checking for mounted boot dir [INFO] cbm (../src/bootman/bootman.c:L555): Mounting boot device /dev/nvme0n1p1 at /boot [SUCCESS] cbm (../src/bootman/bootman.c:L568): /dev/nvme0n1p1 successfully mounted at /boot [DEBUG] cbm (../src/bootman/update.c:L164): Now beginning update_native [DEBUG] cbm (../src/bootman/update.c:L173): update_native: 1 available kernels [DEBUG] cbm (../src/bootman/update.c:L191): update_native: Running kernel is (lts) ///usr/lib/kernel/com.solus-project.lts.6.6.49-253 [ERROR] cbm (../src/lib/bootvar.c:L372): efi_set_variable() failed: No space left on device [ERROR] cbm (../src/bootloaders/shim-systemd.c:L365): Cannot create EFI variable (boot entry) [ERROR] cbm (../src/bootloaders/shim-systemd.c:L366): Please manually update your bios to add a boot entry for Solus [SUCCESS] cbm (../src/bootman/update.c:L205): update_native: Bootloader updated [SUCCESS] cbm (../src/bootman/update.c:L220): update_native: Repaired running kernel ///usr/lib/kernel/com.solus-project.lts.6.6.49-253 [DEBUG] cbm (../src/bootman/update.c:L230): update_native: Checking kernels for type lts [INFO] cbm (../src/bootman/update.c:L243): update_native: Default kernel for type lts is ///usr/lib/kernel/com.solus-project.lts.6.6.49-253 [SUCCESS] cbm (../src/bootman/update.c:L255): update_native: Installed tip for lts: ///usr/lib/kernel/com.solus-project.lts.6.6.49-253 [SUCCESS] cbm (../src/bootman/update.c:L269): update_native: Installed last_good kernel (lts) (///usr/lib/kernel/com.solus-project.lts.6.6.49-253) [DEBUG] cbm (../src/bootman/update.c:L280): update_native: Analyzing for type lts: ///usr/lib/kernel/com.solus-project.lts.6.6.49-253 [DEBUG] cbm (../src/bootman/update.c:L285): update_native: Skipping running kernel [INFO] cbm (../src/bootman/bootman.c:L503): Checking for mounted boot dir [INFO] cbm (../src/bootman/bootman.c:L510): boot_dir is already mounted: /boot [SUCCESS] cbm (../src/bootman/update.c:L338): update_native: Default kernel for lts is ///usr/lib/kernel/com.solus-project.lts.6.6.49-253 [DEBUG] cbm (../src/bootman/update.c:L353): No kernel removals found [INFO] cbm (../src/bootman/bootman.c:L469): Attempting umount of /boot [SUCCESS] cbm (../src/bootman/bootman.c:L473): Unmounted boot directory
Additionally, the output of
sudo journalctl -karound the time that the failure occurs would probably be helpful to determine where the issue is.
Sep 12 20:16:40 solus kernel: Linux version 6.6.49-253.lts ([email protected]) (gcc (Solus) 14.2.0, GNU ld (GNU Binu> Sep 12 20:16:40 solus kernel: Command line: initrd=\EFI\com.solus-project\initrd-com.solus-project.lts.6.6.49-253 root=> Sep 12 20:16:40 solus kernel: BIOS-provided physical RAM map: Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009cfffff] usable Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x0000000009d00000-0x0000000009ffffff] reserved Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a209fff] ACPI NVS Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x000000000a20a000-0x000000000affffff] usable Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x000000000b000000-0x000000000b01ffff] reserved Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x000000000b020000-0x00000000eac2bfff] usable Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x00000000eac2c000-0x00000000ec104fff] reserved Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x00000000ec105000-0x00000000ec119fff] ACPI data Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x00000000ec11a000-0x00000000ec5c2fff] ACPI NVS Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x00000000ec5c3000-0x00000000ed313fff] reserved Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x00000000ed314000-0x00000000eeffffff] usable Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x00000000ef000000-0x00000000efffffff] reserved Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x00000000fd100000-0x00000000fdffffff] reserved Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x00000000fea00000-0x00000000fea0ffff] reserved Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x00000000feb80000-0x00000000fec01fff] reserved Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x00000000fec30000-0x00000000fec30fff] reserved Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x00000000fed40000-0x00000000fed44fff] reserved Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x00000000fedc2000-0x00000000fedcffff] reserved Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x00000000fedd4000-0x00000000fedd5fff] reserved Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000feefffff] reserved Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved Sep 12 20:16:40 solus kernel: BIOS-e820: [mem 0x0000000100000000-0x000000040f33ffff] usable Sep 12 20:16:40 solus kernel: NX (Execute Disable) protection: active Sep 12 20:16:40 solus kernel: APIC: Static calls initialized Sep 12 20:16:40 solus kernel: extended physical RAM map: Sep 12 20:16:40 solus kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009ffff] usable Sep 12 20:16:40 solus kernel: reserve setup_data: [mem 0x00000000000a0000-0x00000000000fffff] reserved Sep 12 20:16:40 solus kernel: reserve setup_data: [mem 0x0000000000100000-0x0000000009cfffff] usable Sep 12 20:16:40 solus kernel: reserve setup_data: [mem 0x0000000009d00000-0x0000000009ffffff] reserved Sep 12 20:16:40 solus kernel: reserve setup_data: [mem 0x000000000a000000-0x000000000a1fffff] usable Sep 12 20:16:40 solus kernel: reserve setup_data: [mem 0x000000000a200000-0x000000000a209fff] ACPI NVS Sep 12 20:16:40 solus kernel: reserve setup_data: [mem 0x000000000a20a000-0x000000000affffff] usable
@hdansin72 your output shows a different error than the one this ticket is about:
[ERROR] cbm (../src/lib/bootvar.c:L372): efi_set_variable() failed: No space left on device
[ERROR] cbm (../src/bootloaders/shim-systemd.c:L365): Cannot create EFI variable (boot entry)
[ERROR] cbm (../src/bootloaders/shim-systemd.c:L366): Please manually update your bios to add a boot entry for Solus
Feel free to submit a different issue, but I recommend you join the Matrix support chat for interactive debugging.
@TraceyC77: What happens if you execute sudo modprobe vfat before reinstalling? So:
sudo modprobe vfat
sudo env CBM_DEBUG=1 eopkg it --reinstall linux-current
(Don't ask how badly I had to mess up my system to get the same error)
Another update must have fixed the problem. I can now reinstall linux-current
❯ sudo eopkg it --reinstall linux-current
[sudo] password for tracey:
Total size of package(s): 192.37 MB
Downloading 1 / 1
Package linux-current found in repository Solus-Dev
linux-current-6.10.11-303-1-x86_64.eopkg [cached]
Installing 1 / 1
linux-current-6.10.11-303-1-x86_64.eopkg [cached]
Installing linux-current, version 6.10.11, release 303
Extracting the files of linux-current
Installed linux-current
[✓] Syncing filesystems success
[✓] Updating clr-boot-manager success
[✓] Running depmod on kernel 6.10.11-303.current success
[✓] Updating mimetype database success
░▒▓ ~ ──
I'll close this out for now. If someone else has this specific error:
[FATAL] cbm (../src/bootman/bootman.c:L562): FATAL: Cannot mount boot device {/dev/drive_name}
then feel free to re-open this issue.
@uni-dos: does running sudo modprobe vfat before updating resolve the issue for you? So:
sudo modprobe vfat
sudo env CBM_DEBUG=1 eopkg it --reinstall linux-current
@uni-dos: does running
sudo modprobe vfatbefore updating resolve the issue for you? So:sudo modprobe vfat sudo env CBM_DEBUG=1 eopkg it --reinstall linux-current
I ran it under chroot and got module vfat not found in directory
@uni-dos: you didn't say, but if you're doing this from boot rescue you have a different issue. This issue is about getting this error from a normal working installation.
Hi there I have the same issue in a newly installation of Solus.
sudo eopkg install gopass
Following packages will be installed:
gopass xdotool xsel
Total size of package(s): 10.61 MB
There are extra packages due to dependencies. Do you want to continue? (yes/no)y
Downloading 1 / 3
Package xsel found in repository Solus
xsel-1.2.1-2-1-x86_64.eopkg (15.0 KB)100% 0.00 --/- [--:--:--] [complete]
Downloading 2 / 3
Package xdotool found in repository Solus
xdotool-3.20210903.1-5-1-x86_64.eopkg (54.0 KB)100% 0.00 --/- [--:--:--] [complete]
Downloading 3 / 3
Package gopass found in repository Solus
gopass-1.15.16-40-1-x86_64.eopkg (10.5 MB)100% 6.20 MB/s [00:00:00] [complete]
Installing 1 / 3
xsel-1.2.1-2-1-x86_64.eopkg [cached]
Installing xsel, version 1.2.1, release 2
Extracting the files of xsel
Installed xsel
Installing 2 / 3
xdotool-3.20210903.1-5-1-x86_64.eopkg [cached]
Installing xdotool, version 3.20210903.1, release 5
Extracting the files of xdotool
Installed xdotool
Installing 3 / 3
gopass-1.15.16-40-1-x86_64.eopkg [cached]
Installing gopass, version 1.15.16, release 40
Extracting the files of gopass
Installed gopass
[✓] Syncing filesystems success
[✓] Updating dynamic library cache success
[✗] Updating clr-boot-manager failed
A copy of the command output follows:
[FATAL] cbm (../src/bootman/bootman.c:L548): Cannot determine boot device
[✗] Updating clr-boot-manager failed
A copy of the command output follows:
[FATAL] cbm (../src/bootman/bootman.c:L548): Cannot determine boot device
[✗] Updating clr-boot-manager failed
A copy of the command output follows:
[FATAL] cbm (../src/bootman/bootman.c:L548): Cannot determine boot device
[✗] Updating clr-boot-manager failed
A copy of the command output follows:
[FATAL] cbm (../src/bootman/bootman.c:L548): Cannot determine boot device
[✓] Updating manpages database success
1- at first I tried reinstalling linux-current running
sudo eopkg it --reinstall linux-current...
and worked correctly, but every time I install a new software (I am setting my pc from start) I have the same error.
2- then tried
sudo modprobe vfat
sudo env CBM_DEBUG=1 eopkg it --reinstall linux-current
but in the next sofware installation the same thing happend (it's the message at top of my post)
I have installed Solus 4.7 Endurance and in case it helps... the partitioning of my disk is like :
GNU Parted 3.6
Using /dev/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
Model: ATA WD Green 2.5 240 (scsi)
Disk /dev/sda: 240GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 1075MB 1074MB primary fat32 boot, esp
2 1075MB 41,9GB 40,8GB primary linux-swap(v1) swap
3 41,9GB 107GB 65,2GB primary ext4
4 107GB 240GB 133GB primary ext4
