| 1 |
On Sunday, 11 October 2020 23:21:49 -00 peter@××××××××××××.uk wrote: |
| 2 |
|
| 3 |
> Can anyone please tell me precisely where 'efibootmgr -c ...' writes a boot |
| 4 |
> record, or whatever it's called? My machine seems unable to store what I |
| 5 |
> give it, and I suspect that the BIOS ROM has failed. Big expense if so. |
| 6 |
|
| 7 |
I have a bootable system again. |
| 8 |
|
| 9 |
In one line: I need Windows as part of my system maintenance. |
| 10 |
|
| 11 |
Yes, I did mean to write that. Let me explain. |
| 12 |
|
| 13 |
Every attempt of mine to write bootable images failed. I still don't know why, |
| 14 |
but while I was trying everything I could think of, I ran Windows (on /dev/ |
| 15 |
sdb) to restore a system image (from /dev/sda; /root is on /dev/nvme0n1). On |
| 16 |
rebooting, lo! and behold! there was a boot menu! It was an old one, dating |
| 17 |
from when I created the system image in Windows, but after booting from USB |
| 18 |
and adding the right kernels and /boot/loader/ structure, and running 'bootclt |
| 19 |
update', a reboot showed me the proper boot menu. |
| 20 |
|
| 21 |
A kernel upgrade arrived today, so after installing it and updating the /boot/ |
| 22 |
loader config, I ran Windows again to create a new system image. |
| 23 |
|
| 24 |
So on my machine, efibootmgr is no use. I have to use bootctl from systemd-boot |
| 25 |
to manage my bootable images. And Windows to preserve them. |
| 26 |
|
| 27 |
I've attached a shot of the boot menu I've been referring to in this thread. |
| 28 |
It's not pretty, but there's only so much I can do with a curved screen and a |
| 29 |
hand-held phone. |
| 30 |
|
| 31 |
-- |
| 32 |
Regards, |
| 33 |
Peter. |
Archives