Control: tag -1 pending Control: retitle -1 cryptsetup-initramfs: "ERROR: Couldn't find sysfs hierarchy for <unencrypted partition>"
Hi Chris, On Sat, 23 Jun 2018 at 08:45:54 +0100, Chris Lamb wrote: > cryptsetup: ERROR: Couldn't find sysfs hierarchy for /dev/sda1 > cryptsetup: ERROR: Couldn't find sysfs hierarchy for > UUID=2efdbd50-bc29-4134-9519-5a007c41c12a My commit from yesterday to make cryptsetup ≥2:2.0.3-2 work with d-i is also fixing this :-) https://salsa.debian.org/cryptsetup-team/cryptsetup/commit/8ea400db2e146ee9e4a0f475f9353bf87201d1f3 The problem is that while you have you have a sysfs(5) entry ‘block/sda’ corresponding to ‘/dev/sda’, there is no entry ‘block/sda1’ corresponding to its first partition. It's not a problem for mapped devices (dm) as there are entries ‘block/dm-$index’, so finding slaves of an encrypted devices should always succeed and never spew this error. According to our tests, at least :-). My bad for not reading the docs carefully. sysfs(5) mentions ‘/sys/dev/block/$maj:$min’ not ‘/sys/block/$blk’ as the reliable way to access the sysfs directory corresponding to a device. This is what the hook is using now. > So, I didn't look into the sysfs error at all — as I do not use > cryptsetup on this machine, I thought I would just remove the > cryptsetup-initramfs package and get on with my morning (NB. typo bug > already filed in #901971!). > […] > Anything I should be concerned with? Nope, removing 'cryptsetup-initramfs' was the right thing to do since you don't need to unlock anything at initramfs stage. Cheers, -- Guilhem.
signature.asc
Description: PGP signature