Hello,
I seem to be confused now...
I thought booting starts with MBR or GPT and a tiny little piece of code inside... pointing to loader in /boot to launch kernel and further on mounting /...
In addition I thought in case of UEFI boot the GPT points to a small UEFI disk which then loads a bootmenu and points to loader/kernel....
And yes in a test vmware I found the installer to create a tiny slice with freebsd-boot type beside a bigger /boot and a huge /
=> Ok, I thought:" ok it is UEFi in vmware player! " But no... I got to know that I have to enable uefi in vm config file and after doing this, the OS is not booting anymore.
=> I turned out that I am not booting UEFI style... but what the hell is the tiny 64K slice for? it is of type freebsd-boot and I cannot mount it as FAT16...
What I have missed? Is this slice home of stage 2 code which is not fitting in GPT header?
I seem to be confused now...
I thought booting starts with MBR or GPT and a tiny little piece of code inside... pointing to loader in /boot to launch kernel and further on mounting /...
In addition I thought in case of UEFI boot the GPT points to a small UEFI disk which then loads a bootmenu and points to loader/kernel....
And yes in a test vmware I found the installer to create a tiny slice with freebsd-boot type beside a bigger /boot and a huge /
=> Ok, I thought:" ok it is UEFi in vmware player! " But no... I got to know that I have to enable uefi in vm config file and after doing this, the OS is not booting anymore.
=> I turned out that I am not booting UEFI style... but what the hell is the tiny 64K slice for? it is of type freebsd-boot and I cannot mount it as FAT16...
What I have missed? Is this slice home of stage 2 code which is not fitting in GPT header?
Last edited by a moderator: