MSGID: 2:240/12 6251c1b2
TZUTC: 0200
REPLY: 2:240/77 6289852e
CHRS: LATIN-1 2
TID: hpt/fbsd 1.9 2021-12-02
Hello Kai!

22 May 22 02:24, Kai Richter wrote to Gerrit Kuehn:

 GK>> If there is no bootloader on the EFI partition as you wrote above,
 GK>> there is nothing the BIOS could find.

 KR> I does find the disk.

Does it just find "the disk", or does it present it as EFI-bootable option?

 KR> new disk to re-attach the old one. Then no boot anymore. The old disk 
 KR> on the same port in place of the new disk did not boot. I think 
 KR> that's because the bios does use some ID flags to identify the disk 
 KR> to boot of. I never noticed that kind of behavior on legacy systems.

For being EFI-bootable, the installation will need an EFI-partition with boot
loader. Your description said your EFI partition was empty (no bootlader).
This will not be recognised as bootable by the BIOS (of course).Maybe it was
booting legacy before, and you changed the BIOS setting to EFI only?


Regards,
Gerrit

...  7:21AM  up 61 days, 12:27, 8 users, load averages: 0.17, 0.37, 0.48

--- msged/fbsd 6.3 2021-12-02
 * Origin: And the pastiche we've invented (2:240/12)
SEEN-BY: 1/123 3/50 15/0 90/1 92/1 103/705 105/81 106/201 114/709
SEEN-BY: 120/340 123/131 129/305 330 331 153/7715 154/10 218/700 221/1
SEEN-BY: 221/6 226/30 227/114 229/110 111 112 113 206 317 400 424
SEEN-BY: 229/426 428 452 470 550 616 664 700 240/12 1120 1634 1895
SEEN-BY: 240/8001 8002 8005 266/512 280/464 5003 282/1038 291/111
SEEN-BY: 292/854 301/1 113 812 303/0 313/41 317/3 320/219 322/757
SEEN-BY: 335/364 341/66 342/200 371/0 382/147 396/45 460/58 633/267
SEEN-BY: 633/280 712/620 848 770/1 2432/390 2452/250 3634/12 5020/1042
SEEN-BY: 5058/104
PATH: 240/12 1120 301/1 712/848 229/426