various mishandlings of corrupt GPT

Jeffrey Bastian jbastian at redhat.com
Thu Oct 24 15:40:23 UTC 2013


On Wed, Oct 23, 2013 at 10:49:35PM -0600, Chris Murphy wrote:
> The bottom line question is, would it be useful to have an fsck_gpt
> run by systemd at either startup or shutdown time? 

I have a system that corrupts the backup GPT on every reboot: the CRC32
in the backup GPT is always 0.  I run parted or gdisk to fix it, verify
that everything is good (even by dd'ing the backup GPT and manually
inspecting it), then reboot and bam, it's corrupt again (i.e., set to
0).  I don't know if it's an OS bug, a firmware bug, or something with
the actual disk.

This was causing some headaches for me with anaconda:
https://bugzilla.redhat.com/show_bug.cgi?id=950145
https://bugzilla.redhat.com/show_bug.cgi?id=951244  <-- especially this

So fsck_gpt would indeed be useful.  (Although it would probably force
me to switch from UEFI back to legacy BIOS emulation and back to MBR
partitioning on this one system.)

Jeff


More information about the devel mailing list