-
Notifications
You must be signed in to change notification settings - Fork 246
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
GPT table creation does not recover old disk and partition GUIDs #2548
Comments
@DEvil0000 No interest in writing a PR for your proposal? |
@DEvil0000 PR has been merged, if you could recheck if all goes well? |
The vfat ID now gets set for the UEFI partition but the GPT partition GUID (not type id) is still newly generated and was not addressed by #2546 |
@DEvil0000 Sorry for the delay in answer - please show us what is really missing here - it seems we misunderstood |
A efi boot entry contains
The When using a msdos So when using a GPT partition table and UEFI you should definitely save the GPT UUIDs (disk and partition) and also insert those when creating the partition on recover. This way you restore the system "as it was". Edit: |
@DEvil0000 Not all system are equal it seems - my UEFI knowledge became a bit rusty...
Not sure where to start? @gozora Do you have some more insights on these matters? |
Let us not forget that there are also users that are migrating to different HW. For this group of people recreating all the UEFI boot configuration entries make little sense. Of course if anybody is willing to cover this complex topic with a pull request, I have no objections. Hope it helps. V. |
After a recover a new UEFI boot entry gets created for the recovered efi since the GPT partition GUID changed.
Of course this is more a minor issue only affecting people making use of multiple boot options tried to boot in order.
This however has two side effects:
There are at least two possible workarounds/fixes possible for this:
The complete fix for rear would be also writing GPT GUIDs to the layout file and then setting them e.g. with sgdisk.
The text was updated successfully, but these errors were encountered: