Chris Murphy wrote:
> We'd need to look at LBA 0 on a broken system to do an autopsy. Once
> it's fixed, the evidence of what stepped on it is wiped away.
I have two more systems to upgrade, probably next week. If one of them
fails in the same way, I'll capture the MBR and post here.
--
On Thu, May 30, 2019 at 4:00 PM Chris Murphy wrote:
>
> I'm pretty sure (been a while since I checked) that neither the
> bootloader nor kernel care if the primary GPT header or table fail
> checksum verification, they just use it in the blind anyway. No
> fallback to the backup. And no fail. That
On Thu, May 30, 2019 at 12:36 PM Samuel Sieb wrote:
>
> 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 ta
On Thu, May 30, 2019 at 11:07 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
> >
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 pa
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 bi
On Wed, May 29, 2019 at 7:01 PM CLOSE Dave
wrote:
>
> I have upgraded three VMware images previously running Fedora 29 to
> Fedora 30 using system-upgrade. All the images are running on the same
> ESC hardware and, so far as I know, use the same VMware foundation. The
> first worked flawlessly. Bo
I have upgraded three VMware images previously running Fedora 29 to
Fedora 30 using system-upgrade. All the images are running on the same
ESC hardware and, so far as I know, use the same VMware foundation. The
first worked flawlessly. Both the second and third failed in exactly the
same way: they
