applications/manjaro-architect
3
0
Fork 0
Code Issues 1 Pull requests Projects Releases 39 Packages Wiki Activity Actions

Installing systemd-boot using the architect menu doesn't work #292

New issue
Open
opened 2021-03-16 19:29:30 +00:00 by fiechr · 9 comments
fiechr commented 2021-03-16 19:29:30 +00:00 (Migrated from gitlab2.manjaro.org)
Copy link

v0.9.34 (manjaro-architect 0.9.34-5)

I'm installing into a VirtualBox VM using different ISOs (i3 and KDE), the issue is the same for both.

When I select the menu option to install systemd-boot as boot manager, I get a message, that it has been installed, but it actually hasn't, at least not completely. Of course, at this point, /boot is already mounted and the kernel images are present.

Later, when chrooting into the new installation, I can confirm this:

# ls -l /boot
total 47560
-rwxr-xr-x 1 root root    40960 Feb 11 16:27 amd-ucode.img
-rwxr-xr-x 1 root root 30314187 Mar 16 17:21 initramfs-5.4-x86_64-fallback.img
-rwxr-xr-x 1 root root  8203205 Mar 16 17:21 initramfs-5.4-x86_64.img
-rwxr-xr-x 1 root root  3624960 Feb 17 08:15 intel-ucode.img
-rwxr-xr-x 1 root root       22 Feb 26 11:18 linux54-x86_64.kver
drwxr-xr-x 2 root root     4096 Mar 16 17:21 memtest86+
-rwxr-xr-x 1 root root  6506816 Mar 16 17:21 vmlinuz-5.4-x86_64

# bootctl
systemd-boot not installed in ESP.
No default/fallback boot loader installed in ESP.
System:
     Firmware: n/a (n/a)
  Secure Boot: disabled
   Setup Mode: user
 Boot into FW: supported

Current Boot Loader:
      Product: n/a
     Features: - Boot counting
               - Menu timeout control
               - One-shot menu timeout control
               - Default entry control
               - One-shot entry control
               - Support for XBOOTLDR partition
               - Support for passing random seed to OS
               - Boot loader sets ESP partition information
          ESP: n/a
         File: `-n/a

Random Seed:
 Passed to OS: no
 System Token: not set
       Exists: no

Available Boot Loaders on ESP:
          ESP: /boot (/dev/disk/by-partuuid/8e0b3250-e787-429f-97c5-ad49bb2bf06e)

Boot Loaders Listed in EFI Variables:
        Title: Linux Boot Manager
           ID: 0x0004

I need to call bootctl install to actually install it:

# bootctl install
Created "/boot/EFI".
Created "/boot/EFI/systemd".
Created "/boot/EFI/BOOT".
Created "/boot/loader".
Created "/boot/loader/entries".
Created "/boot/EFI/Linux".
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/boot/EFI/systemd/systemd-bootx64.efi".
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/boot/EFI/BOOT/BOOTX64.EFI".
Random seed file /boot/loader/random-seed successfully written (512 bytes).
Not installing system token, since we are running in a virtualized environment.
Created EFI boot entry "Linux Boot Manager".
# sdboot-manage gen

# bootctl
System:
     Firmware: n/a (n/a)
  Secure Boot: disabled
   Setup Mode: user
 Boot into FW: supported

Current Boot Loader:
      Product: n/a
     Features: - Boot counting
               - Menu timeout control
               - One-shot menu timeout control
               - Default entry control
               - One-shot entry control
               - Support for XBOOTLDR partition
               - Support for passing random seed to OS
               - Boot loader sets ESP partition information
          ESP: n/a
         File: `-n/a

Random Seed:
 Passed to OS: no
 System Token: not set
       Exists: yes

Available Boot Loaders on ESP:
          ESP: /boot (/dev/disk/by-partuuid/8e0b3250-e787-429f-97c5-ad49bb2bf06e)
         File: `-/EFI/systemd/systemd-bootx64.efi (systemd-boot 247.3-1-manjaro)
         File: `-/EFI/BOOT/BOOTX64.EFI (systemd-boot 247.3-1-manjaro)

Boot Loaders Listed in EFI Variables:
        Title: Linux Boot Manager
           ID: 0x0005`

# ls -l /boot
total 47568
drwxr-xr-x 5 root root     4096 Mar 16 17:27 EFI
-rwxr-xr-x 1 root root    40960 Feb 11 16:27 amd-ucode.img
-rwxr-xr-x 1 root root 30314187 Mar 16 17:21 initramfs-5.4-x86_64-fallback.img
-rwxr-xr-x 1 root root  8203205 Mar 16 17:21 initramfs-5.4-x86_64.img
-rwxr-xr-x 1 root root  3624960 Feb 17 08:15 intel-ucode.img
-rwxr-xr-x 1 root root       22 Feb 26 11:18 linux54-x86_64.kver
drwxr-xr-x 3 root root     4096 Mar 16 17:27 loader
drwxr-xr-x 2 root root     4096 Mar 16 17:21 memtest86+
-rwxr-xr-x 1 root root  6506816 Mar 16 17:21 vmlinuz-5.4-x86_64

After that, it works fine (it's successfully booting into the new system).

`v0.9.34 (manjaro-architect 0.9.34-5)` I'm installing into a VirtualBox VM using different ISOs (i3 and KDE), the issue is the same for both. When I select the menu option to install systemd-boot as boot manager, I get a message, that it has been installed, but it actually hasn't, at least not completely. Of course, at this point, /boot is already mounted and the kernel images are present. Later, when chrooting into the new installation, I can confirm this: ``` # ls -l /boot total 47560 -rwxr-xr-x 1 root root 40960 Feb 11 16:27 amd-ucode.img -rwxr-xr-x 1 root root 30314187 Mar 16 17:21 initramfs-5.4-x86_64-fallback.img -rwxr-xr-x 1 root root 8203205 Mar 16 17:21 initramfs-5.4-x86_64.img -rwxr-xr-x 1 root root 3624960 Feb 17 08:15 intel-ucode.img -rwxr-xr-x 1 root root 22 Feb 26 11:18 linux54-x86_64.kver drwxr-xr-x 2 root root 4096 Mar 16 17:21 memtest86+ -rwxr-xr-x 1 root root 6506816 Mar 16 17:21 vmlinuz-5.4-x86_64 ``` ``` # bootctl systemd-boot not installed in ESP. No default/fallback boot loader installed in ESP. System: Firmware: n/a (n/a) Secure Boot: disabled Setup Mode: user Boot into FW: supported Current Boot Loader: Product: n/a Features: - Boot counting - Menu timeout control - One-shot menu timeout control - Default entry control - One-shot entry control - Support for XBOOTLDR partition - Support for passing random seed to OS - Boot loader sets ESP partition information ESP: n/a File: `-n/a Random Seed: Passed to OS: no System Token: not set Exists: no Available Boot Loaders on ESP: ESP: /boot (/dev/disk/by-partuuid/8e0b3250-e787-429f-97c5-ad49bb2bf06e) Boot Loaders Listed in EFI Variables: Title: Linux Boot Manager ID: 0x0004 ``` I need to call `bootctl install` to actually install it: ``` # bootctl install Created "/boot/EFI". Created "/boot/EFI/systemd". Created "/boot/EFI/BOOT". Created "/boot/loader". Created "/boot/loader/entries". Created "/boot/EFI/Linux". Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/boot/EFI/systemd/systemd-bootx64.efi". Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/boot/EFI/BOOT/BOOTX64.EFI". Random seed file /boot/loader/random-seed successfully written (512 bytes). Not installing system token, since we are running in a virtualized environment. Created EFI boot entry "Linux Boot Manager". # sdboot-manage gen ``` ``` # bootctl System: Firmware: n/a (n/a) Secure Boot: disabled Setup Mode: user Boot into FW: supported Current Boot Loader: Product: n/a Features: - Boot counting - Menu timeout control - One-shot menu timeout control - Default entry control - One-shot entry control - Support for XBOOTLDR partition - Support for passing random seed to OS - Boot loader sets ESP partition information ESP: n/a File: `-n/a Random Seed: Passed to OS: no System Token: not set Exists: yes Available Boot Loaders on ESP: ESP: /boot (/dev/disk/by-partuuid/8e0b3250-e787-429f-97c5-ad49bb2bf06e) File: `-/EFI/systemd/systemd-bootx64.efi (systemd-boot 247.3-1-manjaro) File: `-/EFI/BOOT/BOOTX64.EFI (systemd-boot 247.3-1-manjaro) Boot Loaders Listed in EFI Variables: Title: Linux Boot Manager ID: 0x0005` ``` ``` # ls -l /boot total 47568 drwxr-xr-x 5 root root 4096 Mar 16 17:27 EFI -rwxr-xr-x 1 root root 40960 Feb 11 16:27 amd-ucode.img -rwxr-xr-x 1 root root 30314187 Mar 16 17:21 initramfs-5.4-x86_64-fallback.img -rwxr-xr-x 1 root root 8203205 Mar 16 17:21 initramfs-5.4-x86_64.img -rwxr-xr-x 1 root root 3624960 Feb 17 08:15 intel-ucode.img -rwxr-xr-x 1 root root 22 Feb 26 11:18 linux54-x86_64.kver drwxr-xr-x 3 root root 4096 Mar 16 17:27 loader drwxr-xr-x 2 root root 4096 Mar 16 17:21 memtest86+ -rwxr-xr-x 1 root root 6506816 Mar 16 17:21 vmlinuz-5.4-x86_64 ``` After that, it works fine (it's successfully booting into the new system).
pheiduck commented 2023-06-19 17:58:38 +00:00 (Migrated from gitlab2.manjaro.org)
Copy link

assigned to @pheiduck

assigned to @pheiduck
pheiduck commented 2023-06-19 18:01:42 +00:00 (Migrated from gitlab2.manjaro.org)
Copy link

I can confirm that the systemd-boot installation does not work as expected.
I will work on it and hope to find a solution for this problem.

I can confirm that the **systemd-boot** installation does not work as expected. I will work on it and hope to find a solution for this problem.
pheiduck commented 2023-06-19 18:18:25 +00:00 (Migrated from gitlab2.manjaro.org)
Copy link

mentioned in merge request !581

mentioned in merge request !581
pheiduck commented 2023-06-25 18:50:44 +00:00 (Migrated from gitlab2.manjaro.org)
Copy link

mentioned in commit f23d2f9b24

mentioned in commit f23d2f9b2402e76921765c9120369716db80bbb4
pheiduck (Migrated from gitlab2.manjaro.org) closed this issue 2023-06-25 18:50:44 +00:00
pheiduck (Migrated from gitlab2.manjaro.org) reopened this issue 2024-10-12 14:28:59 +00:00
pheiduck commented 2024-10-12 14:29:14 +00:00 (Migrated from gitlab2.manjaro.org)
Copy link

Issue is still present.

Issue is still present.
pheiduck commented 2024-10-12 17:07:44 +00:00 (Migrated from gitlab2.manjaro.org)
Copy link

mentioned in merge request !584

mentioned in merge request !584
pheiduck commented 2024-10-18 15:35:31 +00:00 (Migrated from gitlab2.manjaro.org)
Copy link

mentioned in commit 09235a3e9e

mentioned in commit 09235a3e9eade75b11c889f6c7c235a678f8f266
pheiduck (Migrated from gitlab2.manjaro.org) closed this issue 2024-10-18 15:35:31 +00:00
pheiduck commented 2024-10-19 12:43:30 +00:00 (Migrated from gitlab2.manjaro.org)
Copy link

Okay... I may not able to fix this issue, after another round of testing.
I try to install systemd-boot via menu on /boot -> failed -> chroot into system install systemd-boot ->

bootctl install
sdboot-manage gen

no errors

Installer prompt there is no bootloader installed. -> install via menu -> no prompt no error

Workaround which works for me:
(1) Install systemd-boot on /boot via installer it fails now, so (2) go to chroot and execute
bootctl install and sdboot-manage gen. (3) Go back to bootloader installer menu and install systemd-boot as in (1. step), (4) proceed other installation parts. Installer closed as normal.

Okay... I may not able to fix this issue, after another round of testing. I try to install systemd-boot via menu on /boot -> failed -> chroot into system install systemd-boot -> ``` bootctl install sdboot-manage gen ``` no errors Installer prompt there is no bootloader installed. -> install via menu -> no prompt no error > Workaround which works for me: > (1) Install systemd-boot on /boot via installer it fails now, so (2) go to chroot and execute > bootctl install and sdboot-manage gen. (3) Go back to bootloader installer menu and install systemd-boot as in (1. step), (4) proceed other installation parts. Installer closed as normal.
pheiduck (Migrated from gitlab2.manjaro.org) reopened this issue 2024-10-19 12:43:33 +00:00
pheiduck commented 2024-10-21 11:02:16 +00:00 (Migrated from gitlab2.manjaro.org)
Copy link

Maybe reordering the commands will help, will test again, if I have enough time...

Maybe reordering the commands will help, will test again, if I have enough time...
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
0.9.39
0.9.38
0.9.37
0.9.36
0.9.35
0.9.34
0.9.33
0.9.32
0.9.31
0.9.30
0.9.29
0.9.28
0.9.27
0.9.26
0.9.25
0.9.24
0.9.23
0.9.22
0.9.21
0.9.20
0.9.19
0.9.18
0.9.17
0.9.16
0.9.15
0.9.14
0.9.12
0.9.11
0.9.10
0.9.9
0.9.8
0.9.7
0.9.6
0.9.5
0.9.4
0.9.3
0.9.2
0.9.1
0.9
0.8.18
0.8.17
0.8.16
0.8.15
0.8.14
0.8.13
0.8.12
0.8.11
0.8.10
0.8.9
0.8.8
0.8.7
0.8.6
0.8.5
0.8.4
0.8.3
0.8.2
0.8.1
0.8.0
0.7.4
0.7.3
Labels
Clear labels   
bug

   
duplicate

   
enhancement

   
help wanted

   
invalid

   
question

   
wontfix
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
applications/manjaro-architect#292
No description provided.