On 2013-07-02, Randolph Maa?en <[email protected]> wrote:
> 2013/7/2 Grant Edwards <[email protected]>

>> I still haven't figured out why my drives suddenly started getting
>> discovered in varying orders. [...]
>>
>> It looks like my options are:

[...]
>
>>  5) For the drive with the root parition on it switch from a DOS
>>     parition table to a GPT partition table and use the
>>     root=PARTUUID=<whatever> kernel option.
>
> You don't need to switch to GPT for that.


All the references Google can find for me say that you have to use a
GPT partition table if you want to specify a boot partition using
root=PARTUUID=<partition-uuid>.

Does the root=PARTUUID option work for you?

Can you point to some documentation on how you can use
root=PARTUID=<partition-uuid> with an DOS/MBR partition table?

> I have a DOS partitioned disk and "blkid" prints the LABEL and UUID
> for each partition.

Anybody can write a program to gnerate and print a UUID for a
partition.  What matters is what the _kernel_ thinks the partition
UUID is.

I added some printk() calls to the kernel mount code to print out the
parition UUIDs.  They don't match the UUIDs printed by blkid:

                      kernel           blkid
           sector      UUID             UUID

sda1          64  0004c99d-01    66E1C3CF7C012A2E
sda2   209715264  0004c99d-02    e9a3eb9e-10d0-4075-aacf-018219cf77a3
sda3   211812416  <null>         n/a
sda4   <n/a>      <n/a>          n/a
sda5   211812480  0004c99d-05    ab4724ab-9030-4217-8582-00f0abe1a48e
sda6   421527744  0004c99d-06    n/a
sda7   429916416  0004c99d-07    13c0fbde-db8a-4784-861a-b3f4e4cdd8f5
sda8   639631680  0004c99d-08    d0f87d87-002c-4d12-b5f3-193d9b0bebee
sda9   849346944  0004c99d-09    03c479f0-ecf8-4060-885b-b350368deee8
sda10 1059062208  0004c99d-0a    60acb3d3-ce8e-48ce-b197-858bc51a74ea
sda11 1268777472  0004c99d-0b    n/a
sda12 1478492736  0004c99d-0c    n/a
sda13 1688208000  0004c99d-0d    n/a
sda14 1897923264  0004c99d-0e    n/a

IOW, it appears that the "blkid" program is either just making stuff
up or its the filesystem UUID rather than the partition UUID. I
suspect the latter, since I notice that blkid doesn't print a UUID for
paritions that don't have filesystems.

One might think that one could use root=PARTUUID=0004c99d-06 instead
of root=/dev/sda5, but the kernel will reject any partition UUID
strings shorter than 36 characters.

-- 
Grant Edwards               grant.b.edwards        Yow! ... I see TOILET
                                  at               SEATS ...
                              gmail.com            


Reply via email to