Also on Debian based systems
Also on Debian based systems
Posted Jul 31, 2020 20:58 UTC (Fri) by kreijack (guest, #43513)In reply to: Also on Debian based systems by leromarinvit
Parent article: Grub2 updates for Red Hat systems are making some unbootable
> What would it do? Treat the GPT partition table as MBR and corrupt it? While definitely not pretty, that should be recoverable as GPT has a backup table hopefully not located in the first few sectors.
Apart the fact that boot device could not be /dev/sda, the GPT table would be not affected. In fact both GPT and MBR partition can co-exist together (and say the same thing or different thing ! more often the latter).
I think that the real risk is that some bios doesn't start in UEFI mode if a MBR partition table is available. My BIOS (which is quite old) didn't show any UEFI related option until I removed all MBR partition table.
Posted Jul 31, 2020 21:23 UTC (Fri)
by anselm (subscriber, #2796)
[Link] (1 responses)
Theoretically, GPT-partitioned disks have a fake MBR with one huge untouchable “partition” that covers all the space within the GPT partitions. (This only gets you so far if your disk is bigger than MBR will support.)
Posted Aug 2, 2020 6:05 UTC (Sun)
by kreijack (guest, #43513)
[Link]
Correct.
To complete the answer, I have to point out that below of the "MBR" label there are two kind if information:
Both are stored in the first sector. Grub-install change only the latter. So in any case grub-installer can't change nor damage the GPT table. However installing a MBR boot loader, could start the bios in legacy mode (and not uefi one).
Also on Debian based systems
In fact both GPT and MBR partition can co-exist together (and say the same thing or different thing ! more often the latter).
Also on Debian based systems
> partitions. (This only gets you so far if your disk is bigger than MBR will support.)
- the partition table
- the boot loader