Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Partition saving should handle converting MBR partitions to GPT #957

Open
prestist opened this issue Aug 16, 2022 · 2 comments · May be fixed by #1047
Open

Partition saving should handle converting MBR partitions to GPT #957

prestist opened this issue Aug 16, 2022 · 2 comments · May be fixed by #1047
Assignees
Labels

Comments

@prestist
Copy link
Contributor

Feature Request

Desired Feature

Now that partition saving bails when its not able to save partitions that are found on a MBR device, we need to have a way to convert the listed save partitions that are MBR partitions to GPT partitions and save them.

Other Information

This request is expecting issue 816 to be resolved first.

@prestist prestist changed the title Parititon Saving should handel converting MBR partitions to GPT Parititon Saving should handle converting MBR partitions to GPT Aug 16, 2022
@bgilbert bgilbert changed the title Parititon Saving should handle converting MBR partitions to GPT Partition saving should handle converting MBR partitions to GPT Aug 16, 2022
@prestist prestist added the jira label Oct 6, 2022
@prestist prestist self-assigned this Oct 11, 2022
@prestist
Copy link
Contributor Author

Ok, I am currently in the midst of looking into how to convert MBR partition entries into GPT entries, though I have already ran into a question. It looks like GPT has a field called Partition type GUIDs which you can read about here. To my eyes I dont see anything that would indicate a similar concept in MBR.

What should I do about these special GUIDS?
Should I set it as "00000000-0000-0000-0000-000000000000" and let the OS or another app interrogate the saved partitions?
OR should I try for a best effort and handle a few common cases?(I say this with less understanding that I would need to do this atm)

@bgilbert
Copy link
Contributor

MBR has partition type codes, which are a single byte. Most of the possible codes aren't relevant to us, and all of the relevant ones should have corresponding GPT type GUIDs. If we see a type code we don't recognize, I think we should just convert it to a suitable fallback GPT type GUID. AFAIK Linux ignores the type codes/GUIDs anyway, and CoreOS doesn't support dual-booting, so it should be fine to treat the type code conversion as best-effort.

prestist added a commit to prestist/coreos-installer that referenced this issue Nov 16, 2022
Fixes coreos#957. If a MBR partition is marked to be saved, it will be translated
using best effort to GPT. To elaberate on "best effort"; there is metadata
which is present in GPT but not MBR, so it might not translate 1:1.
prestist added a commit to prestist/coreos-installer that referenced this issue Nov 16, 2022
Fixes coreos#957. If a MBR partition is marked to be saved, it will be translated
using best effort to GPT. To elaberate on "best effort"; there is metadata
which is present in GPT but not MBR, so it might not translate 1:1.
prestist added a commit to prestist/coreos-installer that referenced this issue Nov 16, 2022
Fixes coreos#957. If a MBR partition is marked to be saved, it will be translated
using best effort to GPT. To elaberate on "best effort"; there is metadata
which is present in GPT but not MBR, so it might not translate 1:1.
@prestist prestist linked a pull request Nov 16, 2022 that will close this issue
prestist added a commit to prestist/coreos-installer that referenced this issue Nov 16, 2022
Fixes coreos#957. If a MBR partition is marked to be saved, it will be translated
using best effort to GPT. To elaborate on "best effort"; there is metadata
which is present in GPT but not MBR, so it might not translate 1:1.
prestist added a commit to prestist/coreos-installer that referenced this issue Nov 16, 2022
Fixes coreos#957. If a MBR partition is marked to be saved, it will be translated
using best effort to GPT. To elaborate on "best effort"; there is metadata
which is present in GPT but not MBR, so it might not translate 1:1.
prestist added a commit to prestist/coreos-installer that referenced this issue Nov 18, 2022
Fixes coreos#957. If a MBR partition is marked to be saved, it will be translated
using best effort to GPT. To elaborate on "best effort"; there is metadata
which is present in GPT but not MBR, so it might not translate 1:1.
prestist added a commit to prestist/coreos-installer that referenced this issue Nov 18, 2022
Fixes coreos#957. If a MBR partition is marked to be saved, it will be translated
using best effort to GPT. To elaborate on "best effort"; there is metadata
which is present in GPT but not MBR, so it might not translate 1:1.
prestist added a commit to prestist/coreos-installer that referenced this issue Nov 29, 2022
Fixes coreos#957. If a MBR partition is marked to be saved, it will be translated
using best effort to GPT. To elaborate on "best effort"; there is metadata
which is present in GPT but not MBR, so it might not translate 1:1.
prestist added a commit to prestist/coreos-installer that referenced this issue Aug 4, 2023
Fixes coreos#957. If a non extended MBR partition is marked to be saved,
it will be translated to a gpt partition.
prestist added a commit to prestist/coreos-installer that referenced this issue Aug 4, 2023
Fixes coreos#957. If a non extended MBR partition is marked to be saved,
it will be translated to a gpt partition.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants