| 1 |
On 01/07/2013 23:52, Grant Edwards wrote: |
| 2 |
> I've just recently run into a problem where sometimes when a machine |
| 3 |
> boots, the kernel can't find init. This appears to be because my grub |
| 4 |
> configuration line says "root=/dev/sda5" and _sometimes_ the drive |
| 5 |
> that contains my root partition is sdb instead of sda. AFAICT, for the |
| 6 |
> past 30 years the linux kernel was 100% consistent in the order that |
| 7 |
> hard drives were labelled -- but recently that has seems to have |
| 8 |
> changed. |
| 9 |
> |
| 10 |
> I use partition labels in my fstab, so that's not a problem, but after |
| 11 |
> all these years, the kernel still doesn't know how to grok parition |
| 12 |
> labels. |
| 13 |
> |
| 14 |
> Are we really expected now to set up an initrd just so that the kernel |
| 15 |
> can find the root partition?? |
| 16 |
> |
| 17 |
|
| 18 |
|
| 19 |
Where have you been for the past 6 months? |
| 20 |
|
| 21 |
Did you miss the entire clusterfuck debate about latest udev tricks? |
| 22 |
|
| 23 |
Those names depend only on the order in which devices are discovered, |
| 24 |
and that process has always been indeterminate. udev used to get in the |
| 25 |
middle and rename things in an arbitrary but defined order, it no longer |
| 26 |
does this. |
| 27 |
|
| 28 |
We discussed this whole subject *to death* over the last many months |
| 29 |
|
| 30 |
|
| 31 |
|
| 32 |
-- |
| 33 |
Alan McKinnon |
| 34 |
alan.mckinnon@×××××.com |
Archives