You are not logged in.
Pages: 1
After more than a year, I need to boot into windows, and find the windows entry is missing in the boot menu.
bootctl sees the windows installation, but "bootctl install" does not add an entry for it. I must be missing something silly.
# bootctl
Using EFI System Partition at /boot.
System:
Firmware: UEFI 2.40 (American Megatrends 5.11)
Secure Boot: disabled
Setup Mode: user
Current Loader:
Product: systemd-boot 234
ESP: /dev/disk/by-partuuid/39129565-4fc7-4572-852a-80b2b9275441
File: └─/EFI/systemd/systemd-bootx64.efi
Boot Loader Binaries:
ESP: /boot (/dev/disk/by-partuuid/39129565-4fc7-4572-852a-80b2b9275441)
File: └─/EFI/systemd/systemd-bootx64.efi (systemd-boot 234)
File: └─/EFI/BOOT/BOOTX64.EFI (systemd-boot 234)
Boot Loader Entries in EFI Variables:
Title: Linux Boot Manager
ID: 0x0001
Status: active, boot-order
Partition: /dev/disk/by-partuuid/39129565-4fc7-4572-852a-80b2b9275441
File: └─/EFI/systemd/systemd-bootx64.efi
Title: UEFI: PM951 NVMe SAMSUNG 256GB, Partition 1
ID: 0x0002
Status: active, boot-order
Partition: /dev/disk/by-partuuid/39129565-4fc7-4572-852a-80b2b9275441
File: └─EFI/boot/bootx64.efi
Title: Windows Boot Manager
ID: 0x0000
Status: active, boot-order
Partition: /dev/disk/by-partuuid/39129565-4fc7-4572-852a-80b2b9275441
File: └─/EFI/Microsoft/Boot/bootmgfw.efipartitions:
# lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
nvme0n1
├─nvme0n1p1 vfat 20CD-969F /boot
├─nvme0n1p2
├─nvme0n1p3 ntfs OS B6E0703CE07004C1
├─nvme0n1p4 ntfs WINRETOOLS 66F2DA53F2DA2759
├─nvme0n1p5 ntfs Image 8884DAA884DA9850
├─nvme0n1p6 btrfs 62e1dfaf-436d-4ae5-ac92-6e5b2eec7383 /
└─nvme0n1p7 btrfs 42b5b750-4541-40d0-8364-e012d27e3df4 /homeOffline
Paste full log dmesg
Offline
What use would a dmesg be? This is happening before the system boots.
Angelo, do you have a Windows entry in your systemd-boot config (/boot/loader/entries/*.conf)?
If so then post it, if not then that's your problem.
Offline
There are only linux entries in /boot/loader/entries.
I looked at the seemingly related thread https://bbs.archlinux.org/viewtopic.php?id=214239 .
It seems the issue there was no timeout, hence boot into arch automatically, and the windows entry was there all along.
However, comment from ewaller there suggests that bootmgr should create the entry automatically. Do I need to create one manually?
Not sure if this is relevant, but windows appears in efibootmgr as well:
# efibootmgr
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001,0002,0000
Boot0000* Windows Boot Manager
Boot0001* Linux Boot Manager
Boot0002* UEFI: PM951 NVMe SAMSUNG 256GB, Partition 1Last edited by angelo (2017-10-12 19:28:40)
Offline
Ruling out the obvious: Did you run "bootctl update" to actually update the config?
Offline
Paste full log dmesg
slithery's reply makes sense to me - the issue is before booting. Is there something I might look for in dmesg output?
Offline
Ignore him, he is clueless.
Offline
Ruling out the obvious: Did you run "bootctl update" to actually update the config?
Running "bootctl update" and "bootctl install" does not generate an entry in /boot/loader/entries .
I will see later if there is nonetheless an entry in the boot menu.
Offline
Are you ever actually booting into systemd-boot? You shouldn't have to generate anything explicitly, given the standard paths systemd-boot should detect and create a Windows entry (dynamically, you are not going to have a file in your entries directory for that). What's the output of
tree /boot #Requires the tree packageLast edited by V1del (2017-10-12 22:15:09)
Offline
% tree /boot
/boot
├── EFI
│ ├── BOOT
│ │ └── BOOTX64.EFI
│ ├── Dell
│ │ └── logs
│ │ └── diags_current.xml
│ └── systemd
│ └── systemd-bootx64.efi
├── initramfs-linux-fallback.img
├── initramfs-linux.img
├── intel-ucode.img
├── loader
│ ├── entries
│ │ ├── arch.conf
│ │ ├── arch-fallback.conf
│ │ └── arch-label.conf
│ └── loader.conf
└── vmlinuz-linux7 directories, 11 files
Offline
There is no Windows UEFI binary. Have you formatted the partition during initial Arch setup? You will have to repair that. Get the Windows installation media and google for a guide on how to restore your Windows UEFI bootloader
Offline
I have definitely used Windows after the arch install (a few months ago, though). I did not touch the partitions since then.
I see instructions for this at
http://www.dell.com/support/article/us/ … pc?lang=en
Will this interfere with the arch installation? Is this a risky procedure?
Last edited by angelo (2017-10-15 06:53:47)
Offline
The only thing that should possibly happen (although there's no sane reason for why this would happen) is that the ESP partition gets cleared and you'd have to reinstall systemd-boot and maybe the linux package from a chroot.
Offline
Pages: 1