You are not logged in.
Hello,
I have an issue with linux-grsec from community, which does correctly detect my cryptsetup root container but after unlocking will not mount it, and thus not boot.
Here is my setup:
mkinitcpio.conf
MODULES="i915 crc32c-intel"
BINARIES=""
FILES=""
HOOKS="base udev autodetect modconf block encrypt filesystems keyboard fsck"
COMPRESSION="xz"syslinux.cfg (normal + grsec options)
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=/dev/mapper/crypto-root cryptdevice=/dev/sda2:crypto-root rw acpi_osi="!Windows 2012"
INITRD ../initramfs-linux.img
LABEL archgrsec
MENU LABEL Arch Linux (grsecurity)
LINUX ../vmlinuz-linux-grsec
APPEND root=/dev/mapper/crpyto-root cryptdevice=/dev/sda2:crypto-root rw acpi_osi="!Windows 2012" nopcid pax_softmode=1
INITRD ../initramfs-linux-grsec.imgI have two images from the boot process, to clarify where I'm stuck at.
http://i.imgur.com/Ex6HZMj.jpg
http://i.imgur.com/xTCaQj5.jpg
I can mount /dev/mapper/crypto-root and access my rootfs from that console manually.
What to do to fix this?
Last edited by mweinelt (2015-01-04 12:59:11)
Offline
Offline
There does not seem anything meaningful for me in the topic you linked. I'm using syslinux not grub/gummiboot, and I don't use EFI/SecureBoot. I used the search function but it is pretty scarce when it comes to the grsecurity patched kernel.
Everything works fine with the standard kernel. It is just linux-grsec that does not mount my rootfs.
Offline
Hah; there is a typo in your fstab, search for crpyto ![]()
Last edited by Spider.007 (2015-01-04 12:56:07)
Offline
Oh wow, thank you. I did not see that.
It is booting up fine now, marking this as solved.
Offline