Add PARTUUID to DOS MBR

Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I have an MBR style formatted SD card where I need a PARTUUID in order to mount a partition there as the rootfs (via linux kernel parameter root=PARTUUID=...). Using an fs UUID does not work.
However, blkid does not show any PARTUUIDs, only UUIDs.
I understand that PARTUUID is not a historical feature of MBRs, but that they can still be used. I have looked around for a way to add or change a PARTUUID, but all I can find is stuff where a GPT is being used.
I've read this answer to a related question, but the identifier pulled that way is just four null bytes (i.e., all zeros). This is also what fdisk gives as the "Disk Identifier", 0x00000000.
partition fdisk uuid partition-table
add a comment |Â
up vote
0
down vote
favorite
I have an MBR style formatted SD card where I need a PARTUUID in order to mount a partition there as the rootfs (via linux kernel parameter root=PARTUUID=...). Using an fs UUID does not work.
However, blkid does not show any PARTUUIDs, only UUIDs.
I understand that PARTUUID is not a historical feature of MBRs, but that they can still be used. I have looked around for a way to add or change a PARTUUID, but all I can find is stuff where a GPT is being used.
I've read this answer to a related question, but the identifier pulled that way is just four null bytes (i.e., all zeros). This is also what fdisk gives as the "Disk Identifier", 0x00000000.
partition fdisk uuid partition-table
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have an MBR style formatted SD card where I need a PARTUUID in order to mount a partition there as the rootfs (via linux kernel parameter root=PARTUUID=...). Using an fs UUID does not work.
However, blkid does not show any PARTUUIDs, only UUIDs.
I understand that PARTUUID is not a historical feature of MBRs, but that they can still be used. I have looked around for a way to add or change a PARTUUID, but all I can find is stuff where a GPT is being used.
I've read this answer to a related question, but the identifier pulled that way is just four null bytes (i.e., all zeros). This is also what fdisk gives as the "Disk Identifier", 0x00000000.
partition fdisk uuid partition-table
I have an MBR style formatted SD card where I need a PARTUUID in order to mount a partition there as the rootfs (via linux kernel parameter root=PARTUUID=...). Using an fs UUID does not work.
However, blkid does not show any PARTUUIDs, only UUIDs.
I understand that PARTUUID is not a historical feature of MBRs, but that they can still be used. I have looked around for a way to add or change a PARTUUID, but all I can find is stuff where a GPT is being used.
I've read this answer to a related question, but the identifier pulled that way is just four null bytes (i.e., all zeros). This is also what fdisk gives as the "Disk Identifier", 0x00000000.
partition fdisk uuid partition-table
partition fdisk uuid partition-table
asked 10 hours ago
goldilocks
60.3k13142197
60.3k13142197
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
The PARTUUIDs used with MBR's are based on the "disk identifier", which evidently is not mandatory -- you can end up without one and the partition table is still functional.
I've read this answer to a related question, but the identifier pulled that way is just four null bytes (i.e., all zeros). This is also what
fdiskgives as the "Disk Identifier",0x00000000.
If you use fdisk to change the identifier to a non-zero value, you will magically have PARTUUIDs reported afterwards.
This is an "expert" option; from the main menu choose
x.From the expert menu, choose
i.Enter any eight random hex digits, prefaced with
0x, e.g.,Oxd3b587f.Go back to the main menu,
r, and write the table,w.
blkid should now report PARTUUIDs for the partitions.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
The PARTUUIDs used with MBR's are based on the "disk identifier", which evidently is not mandatory -- you can end up without one and the partition table is still functional.
I've read this answer to a related question, but the identifier pulled that way is just four null bytes (i.e., all zeros). This is also what
fdiskgives as the "Disk Identifier",0x00000000.
If you use fdisk to change the identifier to a non-zero value, you will magically have PARTUUIDs reported afterwards.
This is an "expert" option; from the main menu choose
x.From the expert menu, choose
i.Enter any eight random hex digits, prefaced with
0x, e.g.,Oxd3b587f.Go back to the main menu,
r, and write the table,w.
blkid should now report PARTUUIDs for the partitions.
add a comment |Â
up vote
0
down vote
The PARTUUIDs used with MBR's are based on the "disk identifier", which evidently is not mandatory -- you can end up without one and the partition table is still functional.
I've read this answer to a related question, but the identifier pulled that way is just four null bytes (i.e., all zeros). This is also what
fdiskgives as the "Disk Identifier",0x00000000.
If you use fdisk to change the identifier to a non-zero value, you will magically have PARTUUIDs reported afterwards.
This is an "expert" option; from the main menu choose
x.From the expert menu, choose
i.Enter any eight random hex digits, prefaced with
0x, e.g.,Oxd3b587f.Go back to the main menu,
r, and write the table,w.
blkid should now report PARTUUIDs for the partitions.
add a comment |Â
up vote
0
down vote
up vote
0
down vote
The PARTUUIDs used with MBR's are based on the "disk identifier", which evidently is not mandatory -- you can end up without one and the partition table is still functional.
I've read this answer to a related question, but the identifier pulled that way is just four null bytes (i.e., all zeros). This is also what
fdiskgives as the "Disk Identifier",0x00000000.
If you use fdisk to change the identifier to a non-zero value, you will magically have PARTUUIDs reported afterwards.
This is an "expert" option; from the main menu choose
x.From the expert menu, choose
i.Enter any eight random hex digits, prefaced with
0x, e.g.,Oxd3b587f.Go back to the main menu,
r, and write the table,w.
blkid should now report PARTUUIDs for the partitions.
The PARTUUIDs used with MBR's are based on the "disk identifier", which evidently is not mandatory -- you can end up without one and the partition table is still functional.
I've read this answer to a related question, but the identifier pulled that way is just four null bytes (i.e., all zeros). This is also what
fdiskgives as the "Disk Identifier",0x00000000.
If you use fdisk to change the identifier to a non-zero value, you will magically have PARTUUIDs reported afterwards.
This is an "expert" option; from the main menu choose
x.From the expert menu, choose
i.Enter any eight random hex digits, prefaced with
0x, e.g.,Oxd3b587f.Go back to the main menu,
r, and write the table,w.
blkid should now report PARTUUIDs for the partitions.
answered 10 hours ago
goldilocks
60.3k13142197
60.3k13142197
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f474258%2fadd-partuuid-to-dos-mbr%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password