Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1223251

Bug#1089516: kpartx won't handle boot cryptsetup'ed devices after decryption

Show all headers | View raw

Control: tags -1 + wontfix

* Sergey Aleynikov <sergey.aleynikov+deb@gmail.com> [241208 11:09]:
> While investigating this, I found that kpartx package has two following changes between bullseye and bookworm:
> 
> - dropped /lib/udev/dmsetup_env
> - removed IMPORT{program}="dmsetup_env %M %m" line from /lib/udev/rules.d/60-kpartx.rules
> 
> After reverting those two changes, automatic boot sequence is restored for me. Is it possible to revert this change and restore
> old correct behaviour? Or is some new mechanism suggested (and in this case it'd be great to mention it in Changes,
> as currently there's no mentions of possible breakage and workarounds)?

If dmsetup_env helps with anything, then you found some other
package's udev rules relying on extremely outdated stuff.

dmsetup_env should have exported DM_NAME, DM_UUID, DM_STATE=ACTIVE,
DM_TABLE_STATE=LIVE. DM_NAME and DM_UUID should be exported by the
dmsetup udev helper (from src:lvm2).

Hope that helps.

Chris

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Bug#1089516: kpartx won't handle boot cryptsetup'ed devices after decryption Sergey Aleynikov <sergey.aleynikov+deb@gmail.com> - 2024-12-08 11:10 +0100
  Bug#1089516: kpartx won't handle boot cryptsetup'ed devices after decryption Chris Hofstaedtler <zeha@debian.org> - 2024-12-08 19:20 +0100
  Bug#1089516: kpartx won't handle boot cryptsetup'ed devices after decryption Chris Hofstaedtler <zeha@debian.org> - 2024-12-08 20:50 +0100

csiph-web