forcemerge 752591 752605
severity 752591 critical
thanks
Am 25.06.2014 09:21, schrieb Michael Biebl:
> Am 25.06.2014 07:56, schrieb Ben Caradoc-Davies:
>> Package: udev
>> Version: 204-11
>> Severity: critical
>> Justification: breaks the whole system
>>
>> Dear Maintainer,
>>
>> after the following dist-upgrade to udev 204-11, there was no offer to unlock
>> luks on /dev/sda2, rendering the system unbootable. May be the same as 
>> #752591
>> (/dev/sda* not created) but with different symptoms as /root is on a luks/lvm
>> volume.
> 
> FYI, I've just setup a test-VM with luks/lvm and was not able to
> reproduce the problem, so I'm a bit stuck with debugging this further.

Some progress: Could reproduce the issue on another system, physical
hardware. It's not using luks/lvm, so this is a general issue.

I was dropped into the rescue shell and same as Russel, I had no
/dev/sda devices. I noticed that the sd_mod module, the SCSI disk driver
module, was not loaded.
Manually loading that allowed me to successfully boot.

So it looks like manually loading the sg module from within the
80-drivers.rules udev rule under certain circumstances prevents sd_mod
from being loaded.

As no /dev/sd* devices then show up, that would also explain why you
never see the luks unlock prompt.

I'm pretty sure it's the same bug, so I'm going the merge the two.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to