Gentoo Archives: gentoo-user

From: Grant Edwards <grant.b.edwards@×××××.com>
To: gentoo-user@l.g.o
Subject: [gentoo-user] Re: Can't find init due to inconsistent drive order
Date: Tue, 02 Jul 2013 17:00:02
Message-Id: kqv0pm$ccf$1@ger.gmane.org
In Reply to: Re: [gentoo-user] Re: Can't find init due to inconsistent drive order by "Randolph Maaßen"
1 On 2013-07-02, Randolph Maa?en <r.maassen60@×××××.com> wrote:
2 > 2013/7/2 Grant Edwards <grant.b.edwards@×××××.com>
3
4 >> I still haven't figured out why my drives suddenly started getting
5 >> discovered in varying orders. [...]
6 >>
7 >> It looks like my options are:
8
9 [...]
10 >
11 >> 5) For the drive with the root parition on it switch from a DOS
12 >> parition table to a GPT partition table and use the
13 >> root=PARTUUID=<whatever> kernel option.
14 >
15 > You don't need to switch to GPT for that.
16
17
18 All the references Google can find for me say that you have to use a
19 GPT partition table if you want to specify a boot partition using
20 root=PARTUUID=<partition-uuid>.
21
22 Does the root=PARTUUID option work for you?
23
24 Can you point to some documentation on how you can use
25 root=PARTUID=<partition-uuid> with an DOS/MBR partition table?
26
27 > I have a DOS partitioned disk and "blkid" prints the LABEL and UUID
28 > for each partition.
29
30 Anybody can write a program to gnerate and print a UUID for a
31 partition. What matters is what the _kernel_ thinks the partition
32 UUID is.
33
34 I added some printk() calls to the kernel mount code to print out the
35 parition UUIDs. They don't match the UUIDs printed by blkid:
36
37 kernel blkid
38 sector UUID UUID
39
40 sda1 64 0004c99d-01 66E1C3CF7C012A2E
41 sda2 209715264 0004c99d-02 e9a3eb9e-10d0-4075-aacf-018219cf77a3
42 sda3 211812416 <null> n/a
43 sda4 <n/a> <n/a> n/a
44 sda5 211812480 0004c99d-05 ab4724ab-9030-4217-8582-00f0abe1a48e
45 sda6 421527744 0004c99d-06 n/a
46 sda7 429916416 0004c99d-07 13c0fbde-db8a-4784-861a-b3f4e4cdd8f5
47 sda8 639631680 0004c99d-08 d0f87d87-002c-4d12-b5f3-193d9b0bebee
48 sda9 849346944 0004c99d-09 03c479f0-ecf8-4060-885b-b350368deee8
49 sda10 1059062208 0004c99d-0a 60acb3d3-ce8e-48ce-b197-858bc51a74ea
50 sda11 1268777472 0004c99d-0b n/a
51 sda12 1478492736 0004c99d-0c n/a
52 sda13 1688208000 0004c99d-0d n/a
53 sda14 1897923264 0004c99d-0e n/a
54
55 IOW, it appears that the "blkid" program is either just making stuff
56 up or its the filesystem UUID rather than the partition UUID. I
57 suspect the latter, since I notice that blkid doesn't print a UUID for
58 paritions that don't have filesystems.
59
60 One might think that one could use root=PARTUUID=0004c99d-06 instead
61 of root=/dev/sda5, but the kernel will reject any partition UUID
62 strings shorter than 36 characters.
63
64 --
65 Grant Edwards grant.b.edwards Yow! ... I see TOILET
66 at SEATS ...
67 gmail.com

Replies

Subject Author
Re: [gentoo-user] Re: Can't find init due to inconsistent drive order Neil Bothwick <neil@××××××××××.uk>
Re: [gentoo-user] Re: Can't find init due to inconsistent drive order Paul Hartman <paul.hartman+gentoo@×××××.com>