|
Boot problem with logical volume on encrypted container
I have a sidux with liquorix and smxi on a system with an encrypted container created basically according the instructions on the sidux wiki. All the relevant filesystems [EDIT: i.e. /, /tmp, /var, /home] are ext4 (there is a second disk with one big unencrypted ext3 partition manually mountable under /home/pub; it only contains data files).
Today I have upgraded in one go both the system and the liquorix kernel. After the restart I am sent to a maintenance shell with the following messages: :: Quote :: Loading, please wait...
Volume group “cryptVG” not found Skipping volume group cryptVG Unable to find LVM volume cryptVG/root Unlocking the disk /dev/disk-by-uuid/<long-number-here> (sda2_crypt) Enter passphrase: _ Internal error: Maps lock 13766656 < unlock 13770752 Internal error: Maps lock 13770752 < unlock 13774848 Internal error: Maps lock 13774848 < unlock 13778944 Internal error: Maps lock 13778944 < unlock 13783040 Internal error: Maps lock 13783040 < unlock 13787136 5 logical volume(s) in volume group “cryptVG” now active cryptsetup: sda2_crypt set up successfully kinit: No resume image, doing normal boot... INIT: version 2.88 booting Using make-file style concurrent boot in runlevel S. Starting the hotplug events dispatcher: udevdudevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:4 udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:6 udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:8 udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:10 udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:12 udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:14 udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:16 udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:18 udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:20 udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:22 udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:24 udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:26 udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:28 udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:30 udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:32 . Synthesizing the initial hotplug events... done. udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:4Waiting for /dev to be fully populated...udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:6 udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:8 udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:10 udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:12 udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:14 udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:16 udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:18 udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:20 udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:22 udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:24 udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:26 udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:28 udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:30 udevd[990]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match a parent device, in /etc/udev/rules.d/libnjb.rules:32 done. Setting parameters of disk (none) Setting preliminary keymap...done Activating swap...done Checking root file system...fsck from util-linux-ng 2.17.2 fsck.ext4:No such file or directory while trying to open /dev/mapper/cryptVG-root /dev/mapper/cryptVG-root: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> fsck died with exit status 8 failed (code 8) An automatic file system check (fsck) of the root filesystem failed. A manual fsck must be performed, then the system restarted. The fsck should be performed in maintenance mode with the root filesystem mounted in read-only mode. ... failed! The root system is currently mounted in read-only mode. A maintenance shell will now be started. After performing system maintenance, press CONTROL-D to terminate the maintenance shell and restart the system (warning). Give root password for maintenance (or type Control-D to continue): I can see all the files in the root partition when I log into the console. Also, if I use the original sidux moros live disk I can open and mount all the filesystems. It's just that the boot process always leaves me at the maintenance console. What can be the problem and where should I look for a solution? Back to top |
|
If you choose such a complex setup expect problems.
I can't help you, if someone else who tries to run such things knows about solutions, feel free to post, but this is not an smxi issue in any way, shape, or form. Back to top |
|
All times are GMT - 8 Hours |