Re: linux-image-3.10-3-amd64 unbootable: /dev/disk/by-uuid not created
On Sat, Oct 12, 2013 at 3:30 PM, Jesse Molina <jesse@opendreams.net> wrote:
> On 10/12/13 8:22 AM, Hugo Vanwoerkom wrote:
>> Jesse Molina wrote:
>>>
>>> I have a Debian unstable host which successfully boots from the
>>> linux-image-3.10-1-amd64 kernel package. However, I recently installed the
>>> linux-image-3.10-3-amd64 kernel package, and it is unbootable.
>>>
>>> When I boot from the linux-image-3.10-3-amd64 package kernel, the boot
>>> fails and drops me into the initramfs busybox. The messge "Gave up waiting
>>> for the root device." appears, along with "ALERT!
>>> /dev/disk/by-uuid/bla-bla-bla-my-id-here does not exist.".
>>>
>>> The problem appears to be that udev is not creating /dev/disk/by-uuid/*
>>> and similar objects. The only directory being created in /dev/disk is
>>> "by-id". Note that the mdadm arrays are being successfully assembled and I
>>> can see them if I cat /proc/mdstat.
>>>
>>> the root= argument in grub is a UUID of a mdadm RAID1 array. This host's
>>> boot part is a RAID1, and the root part is a RAID5. This is standard PC
>>> desktop hardware with four disk drives upon which the md RAIDs are built.
>>>
>>> The host has been dist-upgraded as of this time.
>>>
>>> Advice appreciated. Otherwise, I'll file a bug on it.
>>
>> try 'rootdelay=5' (w/o quotes) as bootparam.
>
> That's a good idea, but this system already had a rootdelay=5 configured,
> and I even raised it to 15 during testing with no effect upon the situation.
>
> I have had problems on a different host using md RAID5 as it's boot array,
> which requires a rootdelay on the 3.8 and 3.10 kernels. There are some bugs
> out there with my name on them regarding this.
>
> Reference bugs:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718533
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678696
>
> And this is the long-term solution which needs to be implemented:
> https://wiki.debian.org/InitramfsEventBased
>
> Anyway, the above doesn't seem to be the problem.
>
> As I said before, the md RAIDs are being assembled. udev, or something
> else, is failing to properly create the device nodes.
Since the "by-id" links are being created, I assume that the answer to
the following question will be "yes" but just in case: does
"lib/udev/rules.d/60-persistent-storage.rules" exist in the initramfs?
Can you add a line to "scripts/local" to retrigger the udevadm
creation of the "by-uuid" links? I don't know the <deleted> syntax
offhand, sorry. ("udevadm trigger ...)
Reply to: