Your message dated Mon, 17 Mar 2025 10:37:18 +0000
with message-id <[email protected]>
and subject line Re: Bug#669686: checkfs.sh causes boot failure due to crypt /
lvm
has caused the Debian Bug report #669686,
regarding checkfs.sh causes boot failure due to crypt / lvm
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
669686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669686
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: initscripts
Version: 2.88dsf-13.1
Hi,
I just had a tough upgrade to squeeze. checkfs is failing and bombing
out on boot.
The reason appears to be related to the ordering of the initscripts
related to cryptdisks, lvm2, and mount.
In my configuration, root is an encrypted disk broken up into lvm2
volumes. This raid volume is unlocked by user password entry on boot.
This machine has several other encrypted disks; the keys to each of
these is found on the filesystem of one of the root array's disks.
In short, whereas the current init setup fires:
checkroot > cryptdisks-early > lvm2 > cryptdisks > checkfs > mount
My configuration would require
cryptdisks-early > lvm2 > checkroot > mountroot > cryptdisks > lvm2 >
checkfs > mount
In Etch and Lenny I didn't have any issues which is partly why I'm a
little confused. Is there anything that can be done to make this part of
boot less brittle?
Has a special runlevel for block devices should be created that runs
commands like these (and mdadm) in a loop, collecting the results of
each run, until nothing has changed before continuing and running a
checkfs that fails been discussed?
-BK
--- End Message ---
--- Begin Message ---
On Mon, Mar 17, 2025 at 10:27:05AM +0000, Mark Hindley wrote:
> Is this still an issue for you?
Submitter email bouncing.
Closing.
Mark
--- End Message ---
