#14839: DriveSetup doesn't modify GPT UUID Partition code when formating Haiku
partition
-------------------------------------+------------------------------
Reporter: smallstepforman | Owner: stippi
Type: enhancement | Status: new
Priority: normal | Milestone: Unscheduled
Component: Applications/DriveSetup | Version: R1/Development
Keywords: GPT UUID Partition Code | Blocked By:
Blocking: | Has a Patch: 0
Platform: All |
-------------------------------------+------------------------------
Using DriveSetup, when formating an existing partition as a BeFS partition
(ie. without creating new paritions first), DriveSetup doesnt modify the
GPT UUID partition code. The GPT table will still maintain the previous OS
partition code, and the EFI loader would struggle to identify a Haiku
partition (I have to manually scan for bootable devices every boot, and
play with safe mode settings to get 2 in 3 chances of booting. Once I
discovered this issue, I used gdisk (a GPT version of fdisk) to modify the
GPT UUID partition code to Haiku (42465331-3BA3-10F1-802A-4861696B7521,
from https://en.wikipedia.org/wiki/GUID_Partition_Table 1). Once I fixed
the GPT UUID parition code, Haiku's EFI loader would boot perfectly 100%
of the time.
The Drive Setup tool would need to be updated so that it writes the GPT
UUID partition code of Haiku (42465331-3BA3-10F1-802A-4861696B7521) when
formatting a Haiku disk.
--
Ticket URL: <https://dev.haiku-os.org/ticket/14839>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.
