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
Am 25.06.2014 08: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
On 25/06/14 14:21, Michael Biebl wrote:
If you downgrade again to 204-10 and rebuild the initrd, does the system
boot successfully?
Success! After downgrading to 204-10 with the following command (which
triggers update-initramfs), the system became bootable again:
dpkg -i
On 25/06/14 14:38, Ben Caradoc-Davies wrote:
The only changes that were made to udev in 204-11 are [1] and [2]
If so, could you both try to revert those two patches one by one,
rebuild the initrd and see if that makes a change
I will try this next.
Michael, manually reverting your [1] and
Martin, could you have a look at this?
This was one of the patches you merged over from Ubuntu and it seems
that loading the sg module does break luks+crypt.
Do you remember why that patch was needed in the first place?
Am 25.06.2014 08:54, schrieb Ben Caradoc-Davies:
On 25/06/14 14:38, Ben
Russel, can you confirm that that reverting the kmod load sg patch
also fixes your problem?
Am 25.06.2014 08:54, schrieb Ben Caradoc-Davies:
On 25/06/14 14:38, Ben Caradoc-Davies wrote:
The only changes that were made to udev in 204-11 are [1] and [2]
If so, could you both try to revert
I restored /lib/udev/rules.d/80-drivers.rules to that shipped with
204-11 and tried rootdelay=30 on the command line; this had no effect
other than introducing a delay in the boot process. There was still no
passphrase prompt.
On 25/06/14 14:39, Michael Biebl wrote:
Since Russel expects a
Russell, for your convenience I have attached the patch as a file to
prevent line wrapping (or patch may reject it). You can apply it with:
cd /
patch -p0 /path/to/where/you/save/80-drivers.rules.patch
update-initramfs -u
Kind regards,
Ben.
On 25/06/14 15:02, Michael Biebl wrote:
Russel,
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
On 25/06/14 15:21, Michael Biebl wrote:
Ben, could you include your/etc/{fstab,crypttab}
Attached.
It is also worth noting that I am running sysvinit with systemd-shim.
Note sure how this changes the contents of initrd.
Kind regards,
--
Ben Caradoc-Davies ben.caradoc-dav...@csiro.au
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
Processing commands for cont...@bugs.debian.org:
forcemerge 752591 752605
Bug #752591 [udev] udev: initrd fails to create /dev/sda* after udev upgrade
Bug #752605 [udev] udev: luks/lvm not detected rendering system unbootable
Severity set to 'important' from 'critical'
Merged 752591 752605
Some updates after more debugging.
The original rule was
SUBSYSTEM==scsi, ENV{DEVTYPE}==scsi_device, TEST!=[module/sg], \
RUN+=/sbin/modprobe -b sg
and was added to fix [1].
Apparently this didn't cause any issues so far.
This was then modified to use
Hello all,
Michael Biebl [2014-06-25 9:01 +0200]:
This was one of the patches you merged over from Ubuntu and it seems
that loading the sg module does break luks+crypt.
Do you remember why that patch was needed in the first place?
No, it didn't come from Ubuntu, but this has been a Debian
On Wed, 25 Jun 2014 09:02:59 Michael Biebl wrote:
Russel, can you confirm that that reverting the kmod load sg patch
also fixes your problem?
It seems to. Booted once since applying it and it worked.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog
Am 25.06.2014 10:20, schrieb Martin Pitt:
E. g. in wheezy the rule looked like
SUBSYSTEM==scsi, ENV{DEVTYPE}==scsi_device, TEST!=[module/sg],
RUN+=/sbin/modprobe -b sg
So the main change was that we now use the kmod builtin instead of
calling modprobe. The latter is much slower, and
On 25/06/14 17:00, Michael Biebl wrote:
Ben, Russel: I'm about to make the upload with the change Martin
mentioned, but it would be great if you can confirm that using
SUBSYSTEM==scsi, ENV{DEVTYPE}==scsi_device, TEST!=[module/sg],
RUN+=/sbin/modprobe -b sg
actually works for you as well.
Can you
17 matches
Mail list logo
