Martin T wrote:
> for some reason, I do not see those partitions with gdisk:
> http://i.imgur.com/4BlDQx7.jpg On the other hand, I'm also using older
> version(0.8.5 vs 0.8.8) of gdisk than you.. Or is there some other
> reason?
No. If gdisk does not show any special boot partition then there is
Sven,
for some reason, I do not see those partitions with gdisk:
http://i.imgur.com/4BlDQx7.jpg On the other hand, I'm also using older
version(0.8.5 vs 0.8.8) of gdisk than you.. Or is there some other
reason?
In addition, while your gdisk output says that you have 0B of free
space, then I have 1
Martin T wrote:
> I see. Thanks! Are those "bios_grub" or "EFI system" partitions
> located inside the GPT scheme, i.e. inside the first ~16KiB of the
> disk and it is not seen with gdisk? In addition, if this small area
> after the last partition is also for alignment purposes, then where is
> t
Sven,
I see. Thanks! Are those "bios_grub" or "EFI system" partitions
located inside the GPT scheme, i.e. inside the first ~16KiB of the
disk and it is not seen with gdisk? In addition, if this small area
after the last partition is also for alignment purposes, then where is
the backup GPT stored?
Martin T wrote:
> 2) Am I correct that boot loaders use their code on this area after
> the primary GPT and before the first partition?
No.
Bootloaders store their code in a special "bios_grub" partition (type
EF02) when using the CSM/BIOS boot mode or inside a EFI System
partion when using EFI
Hi,
DebianInstaller shows "FREE SPACE" before the first partition and
after the last partition if GPT scheme is used:
http://i.imgur.com/qjNrdAx.jpg While there is nothing wrong with that
as there is indeed some free space before the first partition and
after the last partition(http://i.imgur.com/
6 matches
Mail list logo