On 5/30/19 10:06 AM, CLOSE Dave wrote:
Chris Murphy wrote:
Not sure what would corrupt it but there is competition for LBA 0,
the MBR, in that there's a bootloader portion in the first ~440 bytes
and then a partition table from that point until the 512th byte. So
whenever something changes a partition or a boot flag (active bit)
or bootloader jump code, there's a risk. This was such a well known
problem it directly affected GPT. For one, don't use LBA 0. Two,
make two copies in two totally different locations. Three, checksum
everything. Four, give the bootloader its own home, no sharing.
Interesting advice but it leaves me without a course of action. How does
one avoid using LBA 0? Doesn't the boot loader already have its own
location?
You could switch to using EFI if vmware supports that. Otherwise you
can't. The BIOS loads the initial boot code from sector 0. That
initial code loads the rest of the boot loader from elsewhere. Updating
that initial boot loader code always has some amount of risk since the
partition table is also stored in that sector.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
