You are not logged in.
So,after the latest kernel upgrade, Arch won't boot.
What have I done so far;
First I ran this commands;
cryptsetup luksOpen /dev/sda ar ro
modprobe dm-mod
vgscan
vgchange -ay
Then I try to mount them, and chroot into my install.
mkdir /mnt/arch
mount /dev/ch/ro /mnt/arch
mount /dev/sda1 /mnt/arch/boot
mount /dev/ch/ho /mnt/arch/home
mount /dev/ch/va /mnt/arch/var
mount /dev/ch/tp /mnt/arch/tmp
arch-chroot /mnt/arch
This brings me into chroot, checking home dir, everything is oke, so far!
I try updating with pacman -Syyu, but no updates.
Reinstalled mkinitcpio and Linux,
Ran mkinitcpio -p linux, unchroot,unmount and reboot didn't solve it.
I was running grub legacy, installed Grub2 in chroot, but this leads me to the same problem.
What should happen normaly,
I boot and it should ask for the password to decrypt volume 'ch'.
It doesn't and comes with an error not being able to find the root device on /dev/mapper.
If it's not asking for the crypt-password in the first place, of course it won't be able to find the root-device;)
Perhaps boot is going to fast and it just runs over decrypting the LVM.
Maybe there is something wrong with my kernel line, but I don't see it,(
/vmlinuz-linux root=/dev/mapper/ch-ro ro cryptevice=/dev/sda2:ar ro
My mkinitcpio.conf
MODULES="i915"
HOOKS="base udev autodetect modconf block filesystems usbinput fsck"
If I need to provide more info...)
Legenda: ar=cryptdevice ch=LVM
edit:typo & mkinitcpio.conf
Last edited by qinohe (2013-01-04 14:08:40)
Offline
/etc/mkinitcpio.conf is relevant.
Thanks falconindy, added mkinitcpio.conf to FP.
Offline
To boot, like it has always done;)
So, I miss somethings in my mkinitcpio.conf, I will investigate , but it strikes me a little bit since I never changed anything.
Ah, I remember having a upgrade for mkinitcpio.conf a few days or more back, will look into it.
----------------
Update: after falconindy's hint') added lvm2 and encrypt to the hooks.
After that I ran; grub-mkconfig -o /boot/grub/grub.cfg && mkinitcpio -p linux
The system boots, but I have to add; cryptdevice=/dev/sda2:ar ro in grub by hand!
Last edited by qinohe (2013-01-04 12:31:24)
Offline
You're right, I did , after checking a backup this was evidently proven,)
I'm always careful when it comes to merging pacnew files, but you see...
I leave it partially solved, as I still have to add the line: cryptdevice=/dev/sda2:ar ro in grub by hand!
I know I can edit grub.cfg, by why isn't it automatically created?
Offline
I guess you're right I'll add the line to grub.cfg.
Problem solved!
Thanks for your time falconindy')
Offline