[ppc64el] LVM+crypto on ppc64el points to an invalid crypto_source
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
multipath-tools (Ubuntu) |
Expired
|
Medium
|
Unassigned | ||
partman-crypto (Ubuntu) |
Fix Committed
|
Medium
|
Mathieu Trudel-Lapierre |
Bug Description
4.582154] 8regs : 17120.000 MB/sec
[ 4.622155] 8regs_prefetch: 15152.000 MB/sec
[ 4.662154] 32regs : 17968.000 MB/sec
[ 4.702155] 32regs_prefetch: 16512.000 MB/sec
[ 4.742155] altivec : 26000.000 MB/sec
[ 4.742202] xor: using function: altivec (26000.000 MB/sec)
[ 4.743182] async_tx: api initialized (async)
done.
Spawning shell within the initramfs
BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu4) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) grep -r mpatha3 *
cryptroot/
Boot reproducibly fails because it can't find /dev/mapper/
We really need to standardize on the naming...
Filed in partman-crypto for now, I'm guessing that's what writes crypttab, and it might not be aware of multipath's special way of addressing devices?
This might well not be ppc64el-specific, given the symptoms, I'm pretty sure it will fail the same way everywhere. I will check on that.