You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In speaking with @bgilbert we are going to be taking this issue with a 2 pronged approach
Mitigation reduce risk of data loss when there is an MBR with partitions we should save.
Migrate MBR saved partitions to GPT format so the installer can effectively save them.
Keeping in mind, that a disagreeing MBR/GPT shouldn't happen; however, its possible, and the feature is intended for preserving data from pre-existing disks with an unknown history.
That being said, this issue will become the stage 1.
Stage two will be linked here and no longer considered a part of this issue.
Fixescoreos#816, when running the `install` cmd with the arg `--save-partindex` an
additonal check is done on the disk to ensure that MBR is not present. If MBR is
present the proccess will bail.
prestist
added a commit
to prestist/coreos-installer
that referenced
this issue
Sep 13, 2022
If running `install` with the `----save-partindex` argument on a MBR drive
the listed partitions would be lost durring the install. To prevent the loss
of data the install proccess now checks to see if the drive is MBR, and if it
is it will bail fixescoreos#816
Bug
Host Operating System Version
Any
Target Operating System Version
Any
coreos-installer Version
All releases through 0.13.1
Expected Behavior
coreos-installer install --save-partindex
correctly saves partitions on disks that have an MBR partition table and no GPT.Actual Behavior
coreos-installer install --save-partindex
clobbers such partitions.Reproduction Steps
fdisk
to create a partition on a blank target disk--save-partindex
to save the partitionOther Information
--save-partlabel
isn't affected because MBR doesn't support partition labels.We could support this via mbrman. We'd need to detect and ignore protective MBRs, and to fail if the MBR otherwise doesn't match a valid GPT.
The text was updated successfully, but these errors were encountered: