>
<where> don't I need default=x86_64-efi in grub?
<stalebrim> where: no, with EFI Solus uses systemd-boot, not grub
<where> how can I restore the boot?
<stalebrim> https://getsol.us/articles/troubleshooting/boot-rescue/en/
<NarwhalBot> [ Boot Rescue | Solus Help Center ]
<where> read it already
<where> executed without errors, no broken packages
<abdulocracy> Are you sure you did boot rescue, not checking for broken packages
<where> maybe skipped [ ] Updating clr-boot-manager skipped
<abdulocracy> When running usysconf?
<where> broken packages belongs to the boot rescue article and yes, when running usysconf
<abdulocracy> My bad
<abdulocracy> If you're running with -f and it's still skipping the step, then I don't think you've mounted the boot partition properly
<abdulocracy> Please paste the output of lsblk
<where> I dont have any boot partition in fstab
<where> I think I used a separate one and deleted it !
<abdulocracy> Then you're not running an EFI installation
<abdulocracy> Unless you are, and you manually deleted it, in which case you have to recreate it
<where> Solus is EFI-installed, when it went, now I am in ubuntu and chroot and I think ubuntu uses BIOS?
* Saijin_Naib hat die Verbindung getrennt (Ping timeout: 258 seconds).
<abdulocracy> You're dual booting with Ubuntu?
<where> yes, and win10
<where> its a long output
<where> just paste here?
* Getrennt ().
Kein Channel betreten. Versuchen Sie /join #<channel>
Kein Channel betreten. Versuchen Sie /join #<channel>
* Sie sprechen jetzt in #Solus-Chat
* Das Thema für #Solus-Chat ist: Solus Off-Topic Channel || Support Channel: #Solus || Dev Channel: #Solus-Dev || Livestream Channel: #Solus-LiveStream || Solus 4.2 Released: https://getsol.us/2021/02/03/solus-4-2-released
* Das Thema für #Solus-Chat wurde von JoshStrobl!~joshua@joshuastrobl.com (Wed Feb 3 15:14:16 2021) gesetzt.
<where> rejoining?
<ermo> who? what?
<where> how can I recreate the boot partition?
<where> I have an empty /boot
<where> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
<where> loop0 7:0 0 9,1M 1 loop
<where> loop1 7:1 0 138,8M 1 loop
<where> loop2 7:2 0 55,5M 1 loop
<where> loop3 7:3 0 32,3M 1 loop
<where> loop4 7:4 0 162,9M 1 loop
<where> loop5 7:5 0 51M 1 loop
<where> loop6 7:6 0 64,8M 1 loop
<where> loop7 7:7 0 179,6M 1 loop
<where> loop8 7:8 0 138,8M 1 loop
<where> loop9 7:9 0 55,5M 1 loop
<where> loop10 7:10 0 32,3M 1 loop
<where> loop11 7:11 0 99,2M 1 loop
<where> loop12 7:12 0 219M 1 loop
<where> loop13 7:13 0 179,5M 1 loop
<where> loop14 7:14 0 99,2M 1 loop
<where> sda 8:0 0 238,5G 0 disk
<where> ├─sda1 8:1 0 300M 0 part
<where> ├─sda2 8:2 0 128M 0 part
<where> ├─sda3 8:3 0 199,9G 0 part
<where> ├─sda4 8:4 0 578M 0 part
<where> ├─sda5 8:5 0 128M 0 part
<where> └─sda9 8:9 0 29,5G 0 part
<where> sdb 8:16 1 2,7T 0 disk
<where> ├─sdb1 8:17 1 1,4T 0 part
<where> └─sdb2 8:18 1 1,3T 0 part /
<where> sr0 11:0 1 1024M 0 rom
<where> sr1 11:1 1 1,7G 0 rom
<where> recreatign boot partition?
<abdulocracy> How were you booting previously
<abdulocracy> Did you use the Windows boot ESP?
<where> EFI
<where> yes
<where> now ubuntu
<abdulocracy> Well, don't do that
<abdulocracy> It gets filled up since it's tiny and you won't be able to update your kernel anymore
<where> ok
<abdulocracy> Can Ubuntu boot? And is it booting with EFI?
<abdulocracy> You can check if it's booted in EFI by running `ls /sys/firmware/efi/efivars`
<where> yes, I am in ub and in chroot of Solus now and I can execute efibootmgr successfully in ub
<abdulocracy> Is Ubuntu also using the Windows ESP?
<where> I get a lot of output there, what variable?
<abdulocracy> If it lists anything then you're booted in EFI
<where> I dont know (esp), yes the list is there
<abdulocracy> ESP is the boot partition, when booted into Ubuntu, run lsblk and see what's mounted at /boot, /efi, or /boot/efi
<abdulocracy> That partition is your ESP
<abdulocracy> If it's using the Windows-created 200MB one, then don't bother with it, you're best off making a new boot partition
<where> yes, it is
* AlienTrooper (~Alien@81-224-101-181-no2201.tbcn.telia.com) ist beigetreten.
<abdulocracy> Then please make space for a 512MB or so partition, and format it as FAT32, this will be your Solus ESP
<where> 300 MB
* Getrennt ().
* Sie sprechen jetzt in #Solus
* Das Thema für #Solus ist: Solus Support || Off-Topic Channel: #Solus-Chat || Development Channel: #Solus-Dev || Development Tracker: https://dev.getsol.us || Forums: https://discuss.getsol.us || Community Guidelines: https://getsol.us/articles/contributing/community-guidelines/en/ || Solus 4.2 Released: https://getsol.us/2021/02/03/solus-4-2-released
* Das Thema für #Solus wurde von JoshStrobl (Wed Feb 3 15:14:10 2021) gesetzt.
<where_> check
<where_> 249 MB free
<stalebrim> you need 512mb ESP partition minimum for Solus
<abdulocracy> where_: 249 free in what, the Windows one?
* zyga hat die Verbindung getrennt (Quit: zyga).
<where_> the common esp partition
<abdulocracy> You have to understand that storing multiple kernels in that is going to be a pain in the ass
<where_> I think I already enlarged it
<abdulocracy> Fine, then boot into chroot, mount your root and ESP, and rerun usysconf
<abdulocracy> The chroot and mount should be the other way around
<where_> before, and I am in
<where_> so again the part with the possible skipping ?
<abdulocracy> Does it do the bootloader step this time?
<abdulocracy> Yes, please execute the usysconf command in chroot, but make sure you have ESP mounted
<abdulocracy> You need to mount it at /boot
* zyga (~zyga@unaffiliated/zyga) ist beigetreten.
<where_> https://bpa.st/RMJA
<NarwhalBot> [ View paste RMJA ]
<where_> do u see tha paste?
<where_> It doesnt
<abdulocracy> You should be able to use clr-boot-manager manually then
<where_> it shows errors
<stalebrim> where's the paste for the errors?
<where_> https://bpa.st/EBDQ
<NarwhalBot> [ View paste EBDQ ]
<abdulocracy> Try -p /boot
<stalebrim> .. where did you mount your efi partition?
<where_> Unknown command: -p
<where_> at /boot
<where_> although -p is in the help options
<abdulocracy> Try putting it at the end of the command
<where_> I did
<where_> clr-boot-manager -p
<abdulocracy> `sudo clr-boot-manager update`
<where_> same errors as list!
<stalebrim> I don't think that's a solus kernel
<abdulocracy> Perhaps try installing the kernel once again, with `sudo eopkg it --reinstall linux-current`
<where_> at least it is the as the ubuntu one
<stalebrim> are you trying to boot rescue ubuntu or Solus?
<where_> same as
<where_> I am in ubuntu
<where_> I am in chroot, no sudo
<stalebrim> I don't think that boot partition is mounted where it should be
<stalebrim> because clr-boot-manager sees some other kernels, not Solus kernels
<where_> installiert (cached), skipped clr-
<where_> test
<abdulocracy> You're here
<where_> dev/sda1 on /boot type vfat
<stalebrim> is it on /boot or on the /boot of your chroot?
<where_> of course, I use the ubuntu kernel for this chroot
<where_> second
<stalebrim> wtf
* AlienTrooper (~Alien@81-224-101-181-no2201.tbcn.telia.com) ist beigetreten.
<where_> that is the external system
<stalebrim> if you are chrooting into your solus system why are you trying to use an ubuntu kernel?
<where_> I am not doing it un purpose
<where_> don't we have to?
<abdulocracy> Can you please run and paste the output of lsblk inside your Solus chroot
* VicKelson[m] (vkelsonmat@gateway/shell/matrix.org/x-pnnixsvkdljzhute) ist gegangen ("User left").
<where_> https://bpa.st/6KZA
<NarwhalBot> [ View paste 6KZA ]
* ultr4_l4s3r (~ultr4_l4s@cpe90-146-85-156.liwest.at) ist beigetreten.
<where_> you know it is detected in ub by grub, but not in the grub.cfg
<abdulocracy> Solus doesn't use GRUB for EFI boot, it uses systemd-boot
<where_> I accept
<abdulocracy> So in this current chroot, reinstalling kernel doesn't work?
<where_> it does
<abdulocracy> Does it update clr-boot-manager
<where_> https://bpa.st/75OA
<NarwhalBot> [ View paste 75OA ]
<where_> no
* AlienTrooper hat die Verbindung getrennt (Ping timeout: 240 seconds).
* Flabb hat die Verbindung getrennt (Remote host closed the connection).
<abdulocracy> Please try with a separate Solus ESP
<where_> systemd and chroot?
* resistite|laptop (resistite@gateway/vpn/mullvad/resistite) ist beigetreten.
* ultr4_l4s3r hat die Verbindung getrennt (Quit: Goodbye, everyone! (Probably forgot to say that)).
<where_> I created it, mounted it at /boot in chroot and ran clr-
<where_> same
``
EDIT:
can also grub shell using ub kernel, but systemctl tracking doesnt work
live@solus ~ $ cd /mnt/
live@solus /mnt $ ls
live@solus /mnt $ sudo mkdir mount1
live@solus /mnt $ sudo mount ^C
live@solus /mnt $ sudo su
root@solus /mnt # mount /dev/sdb
sdb sdb1 sdb2 sdb3
root@solus /mnt # mount /dev/sdb2 mount1/
root@solus /mnt # mount --bind /proc mount1/proc
root@solus /mnt # cd mount1/
root@solus /mnt/mount1 # mount --bind /sys sys
root@solus /mnt/mount1 # ls
bin boot dev etc home lib lib64 lost+found media mnt opt proc root run sbin srv sys tmp usr var
root@solus /mnt/mount1 # mount --bind /dev dev
root@solus /mnt/mount1 # chroot .
root@solus / # clr-
clr-boot-manager clr-update-wrapper
root@solus / # clr-
clr-boot-manager clr-update-wrapper
root@solus / # clr-boot-manager
Usage: clr-boot-manager [command]
Re-run with -h for a list of supported commands
root@solus / # clr-boot-manager -h
Usage: clr-boot-manager
version - Print the version and quit
report-booted - Report the current kernel as successfully booted
help - Show help message
update - Perform post-update configuration of the system
set-timeout - Set the timeout to be used by the bootloader
get-timeout - Get the timeout to be used by the bootloader
set-kernel - Configure kernel to be used at next boot
list-kernels - Display currently selectable kernels to boot
Options:
-p, --path Set the base path for boot management operations.
-i, --image Force clr-boot-manager to run in image mode.
-n, --no-efi-update Don't update efi vars when using shim-systemd backend.
root@solus / # clr-boot-manager list-kernels
[FATAL] cbm (../src/bootman/bootman.c:L477): Cannot determine boot device
com.solus-project.current.5.11.12-177
com.solus-project.current.5.11.6-174
com.solus-project.current.5.10.15-172
com.solus-project.current.5.10.12-171
root@solus / # mount /dev/sdb
sdb sdb1 sdb2 sdb3
root@solus / # mount /dev/sdb5 /boot/
mount: /boot: Spezialgerät /dev/sdb5 ist nicht vorhanden.
root@solus / # mount /dev/sda5 /boot/
root@solus / # mount /dev/sda1 /boot/efi
root@solus / # clr-boot-manager list-kernels
[FATAL] cbm (../src/bootloaders/systemd-class.c:L507): sd_class_get_default_kernel Unable to parse loader config
com.solus-project.current.5.11.12-177
com.solus-project.current.5.11.6-174
com.solus-project.current.5.10.15-172
com.solus-project.current.5.10.12-171
root@solus / # clr-boot-manager update
[ERROR] cbm (../src/bootman/update.c:L189): Cannot determine the currently running kernel
[FATAL] cbm (../src/bootman/kernel.c:L668): Failed to install initrd /boot/efi/com.solus-project/initrd-com.solus-project.current.5.11.12-177: No space left on device
[FATAL] cbm (../src/bootman/update.c:L250): Failed to install default-current kernel: ///usr/lib/kernel/com.solus-project.current.5.11.12-177
root@solus / # clr-boot-manager
get-timeout help list-kernels report-booted set-kernel set-timeout update version
root@solus / # clr-boot-manager
get-timeout help list-kernels report-booted set-kernel set-timeout update version
root@solus / # clr-boot-manager
get-timeout help list-kernels report-booted set-kernel set-timeout update version
root@solus / # clr-
clr-boot-manager clr-update-wrapper
root@solus / # clr-update-wrapper
[ERROR] cbm (../src/bootman/update.c:L189): Cannot determine the currently running kernel
[FATAL] cbm (../src/bootman/kernel.c:L668): Failed to install initrd /boot/efi/com.solus-project/initrd-com.solus-project.current.5.11.12-177: No space left on device
[FATAL] cbm (../src/bootman/update.c:L250): Failed to install default-current kernel: ///usr/lib/kernel/com.solus-project.current.5.11.12-177
root@solus / # usysconf run -f
[✓] Syncing filesystems success
[✓] Updating dynamic library cache success
[ ] Updating clr-boot-manager skipped
[ ] Updating clr-boot-manager skipped
[ ] Registering QoL migration on next boot skipped
[✓] Running depmod on kernel 5.11.12-177.current success
[✓] Running depmod on kernel 5.10.12-171.current success
[✓] Running depmod on kernel 5.11.6-174.current success
[✓] Running depmod on kernel 5.10.15-172.current success
[✓] Updating hwdb success
[✓] Updating graphical driver configuration success
[✓] Updating system users success
[✓] Updating systemd tmpfiles success
[ ] Reloading systemd configuration skipped
[ ] Re-starting vendor-enabled .socket units skipped
[ ] Re-executing systemd skipped
[ ] Compiling and Reloading AppArmor profiles skipped
[ ] Compiling and Reloading AppArmor profiles skipped
[✓] Compiling glib-schemas success
[✓] Rebuilding font cache success
[✓] Updating mimetype database success
[✓] Updating icon theme cache: hicolor success
[✓] Updating icon theme cache: solus-sc success
[✓] Updating icon theme cache: Papirus-Adapta-Nokto success
[✓] Updating icon theme cache: default success
[✓] Updating icon theme cache: HighContrast success
[✓] Updating icon theme cache: Papirus-Light success
[✓] Updating icon theme cache: breeze_cursors success
[✓] Updating icon theme cache: Papirus-Adapta success
[✓] Updating icon theme cache: Papirus-Dark success
[✓] Updating icon theme cache: Papirus success
[✓] Updating icon theme cache: Adwaita success
[✓] Updating desktop database success
[✓] Rebuilding dconf database success
[✓] Updating GTK2 input module cache success
[✓] Updating GTK3 input module cache success
[✓] Updating manpages database success
[✓] Updating SSL certificates success
[ ] Populating Mono certificates skipped
[ ] Reloading udev rules skipped
[ ] Reloading udev rules skipped
root@solus / # clr-boot-manager update
[ERROR] cbm (../src/bootman/update.c:L189): Cannot determine the currently running kernel
[FATAL] cbm (../src/bootman/kernel.c:L668): Failed to install initrd /boot/efi/com.solus-project/initrd-com.solus-project.current.5.11.12-177: No space left on device
[FATAL] cbm (../src/bootman/update.c:L250): Failed to install default-current kernel: ///usr/lib/kernel/com.solus-project.current.5.11.12-177
root@solus / # cd /boot/efi/
root@solus /boot/efi # df . -h
Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf
/dev/sda1 300M 253M 48M 85% /boot/efi
root@solus /boot/efi # ls -lah
insgesamt 9,2M
drwxr-xr-x 9 root root 16K 1. Jan 1970 .
drwxr-xr-x 6 root root 1,0K 11. Apr 23:17 ..
drwxr-xr-x 2 root root 8,0K 17. Mär 16:54 b75e4fae4d2c4c1bbd0cc18462864426
drwxr-xr-x 2 root root 8,0K 11. Apr 23:17 Boot
drwxr-xr-x 2 root root 8,0K 11. Apr 23:19 com.solus-project
-rwxr-xr-x 1 root root 97K 11. Nov 2015 config-4.1.12-gentoo
drwxr-xr-x 11 root root 8,0K 17. Mär 16:54 EFI
drwxr-xr-x 7 root root 8,0K 4. Jun 2020 grub
drwxr-xr-x 3 root root 8,0K 17. Mär 16:54 loader
drwxr-xr-x 2 root root 8,0K 11. Apr 23:17 systemd
-rwxr-xr-x 1 root root 3,2M 11. Nov 2015 System.map-4.1.12-gentoo
-rwxr-xr-x 1 root root 5,9M 11. Nov 2015 vmlinuz-4.1.12-gentoo
root@solus /boot/efi # ls -lah^C
root@solus /boot/efi # du -hs *
8,0K b75e4fae4d2c4c1bbd0cc18462864426
104K Boot
7,9M com.solus-project
104K config-4.1.12-gentoo
217M EFI
19M grub
56K loader
104K systemd
3,2M System.map-4.1.12-gentoo
5,9M vmlinuz-4.1.12-gentoo
root@solus /boot/efi # cd com.solus-project/
root@solus /boot/efi/com.solus-project # ls
kernel-com.solus-project.current.5.11.12-177
root@solus /boot/efi/com.solus-project # du -hs *
7,9M kernel-com.solus-project.current.5.11.12-177
root@solus /boot/efi/com.solus-project # cd ..
root@solus /boot/efi # ls
b75e4fae4d2c4c1bbd0cc18462864426 Boot com.solus-project config-4.1.12-gentoo EFI grub loader systemd System.map-4.1.12-gentoo vmlinuz-4.1.12-gentoo
root@solus /boot/efi # cd EFI/
root@solus /boot/efi/EFI # ls
Boot com.solus-project debian EFI gentoo Linux Microsoft systemd ubuntu
root@solus /boot/efi/EFI #
how about copying a kernel and maybe an intiram onto the boot partition? it has to be located somewhere.
root@solus /boot/efi/EFI # systemctl
Running in chroot, ignoring command 'list-units'
root@solus /boot/efi/EFI # systemctl
add-requires condrestart disable force-reload hybrid-sleep isolate list-dependencies list-unit-files poweroff reload revert show suspend unmask
add-wants condstop edit get-default import-environment is-system-running list-jobs list-units preset reload-or-restart service-watchdogs show-environment suspend-then-hibernate unset-environment
cancel daemon-reexec emergency halt is-active kexec list-machines log-level preset-all rescue set-default start switch-root
cat daemon-reload enable help is-enabled kill list-sockets log-target reboot reset-failed set-environment status try-reload-or-restart
condreload default exit hibernate is-failed link list-timers mask reenable restart set-property stop try-restart
root@solus /boot/efi/EFI # systemctl rescue
Running in chroot, ignoring command 'rescue'
root@solus /boot/efi/EFI # cd /lib
lib/ lib64/
root@solus /boot/efi/EFI # cd /lib
lib/ lib64/
root@solus /boot/efi/EFI # cd /lib64/
apparmor/ firmware/ modules/ security/ udev/ xtables/
root@solus /boot/efi/EFI # cd /lib64/
apparmor/ firmware/ modules/ security/ udev/ xtables/
root@solus /boot/efi/EFI # cd /lib64/
apparmor/ firmware/ modules/ security/ udev/ xtables/
root@solus /boot/efi/EFI # cd /lib64/
apparmor/ firmware/ modules/ security/ udev/ xtables/
root@solus /boot/efi/EFI # cd ..
root@solus /boot/efi # ls
b75e4fae4d2c4c1bbd0cc18462864426 Boot com.solus-project config-4.1.12-gentoo EFI grub loader systemd System.map-4.1.12-gentoo vmlinuz-4.1.12-gentoo
root@solus /boot/efi # cd com.solus-project/
root@solus /boot/efi/com.solus-project # ls
kernel-com.solus-project.current.5.11.12-177
root@solus /boot/efi/com.solus-project # ls -la
insgesamt 8088
drwxr-xr-x 2 root root 8192 11. Apr 23:19 .
drwxr-xr-x 9 root root 16384 1. Jan 1970 ..
-rwxr-xr-x 1 root root 8255296 11. Apr 23:17 kernel-com.solus-project.current.5.11.12-177
root@solus /boot/efi/com.solus-project # file kernel-com.solus-project.current.5.11.12-177
kernel-com.solus-project.current.5.11.12-177: Linux kernel x86 boot executable bzImage, version 5.11.12-177.current (root@paddedroom) #1 SMP PREEMPT Thu Apr 8 15:46:08 UTC 2021, RO-rootFS, swap_dev 0x7, Normal VGA
found the UEFI OS again and can access the boot manager, also change kernel parameters, now it waits endlessly for one device
