Lilo not finding ramdisk with lvm+luks setup "image starting at 0"
Bought a new ssd drive thought I finally setup encryption on it. I followed the readme at http://slackware.osuosl.org/slackwar...ADME_CRYPT.TXT and everything seemed straight forward, except when finally booting the system. I keep getting RAMDISK: Couldn't find valid RAM disk image starting at 0. , which ofcourse leads to "Please append a correct 'root=' boot option" kernel panic.
My partition setup is as follows: /dev/sda1 /boot partition 100mbs ext2fs /dev/sda2 encrypted lvm partition with two lvs (root ext4/swap) I did a complete install and followed through all the steps in the readme, I even made the initrd with alien bobs script, same result. Lilo is pointing to /boot/initrd.gz and I re ran lilo after running mkinitrd. Lilo is installed on mbr /dev/sda , aside from that I am stumped as to why this isnt working. A normal non encrypted setup on this drive works fine. As always thanks for the help! |
I do not have your set-up so I cannot really help. Anyway:
Try this in /etc/lilo.conf append "rootdelay=10 root=/dev/sda2" Chris |
Quote:
Nope didnt work , delaying root wouldnt help since its not finding a valid ramdisk image in the first place. |
You didn't really provide much detail to help us identify the issue, but the error suggests that the initrd is at fault.
If you mount sda1 somewhere like /mnt you can check it with zcat /mnt/initrd.gz | cpio --list If that looks ok (you should get a file listing displayed), then the error is possibly in your lilo.conf. For reference, I use a similar setup to yours, though not on SSD: /boot on sda1 and an encrypted lvm pv on sda5. I build my mkinitrd using the following little script: Code:
#!/bin/sh I've not tried Eric's mkinitrd generator, so I can't offer any advice on that. I prefer to built the initrd myself. |
File listing in initrd.gz looks fine. Here is my lilo setup:
boot=/dev/sda compact lba32 bitmap=/boot/slack.bmp bmp-colors = 255,0,255,0,255,0 bmp-table = 60,6,1,16 bmp-timer = 65,27,0,255 append="raid=noautodetect vt.default_utf8=1" prompt timeout=300 vga = 791 image = /boot/vmlinuz initrd = /boot/initrd.gz root = /dev/cryptvg/root label = Linux read-only Additional info: Slackware 13.37 64 bit , using stock 2.6.37.6 huge kernel . |
All looks reasonable there..
Were you building your initrd and running lilo from within a chroot environment? One other thing that can catch people out is that they forget to have sda1 mounted on /boot in the chroot when they build the initrd and run lilo, and the initrd and lilo end up referring to a file that is on the encrypted partition rather than sda1, and as such not available at boot time. |
I doubt lilo would run if /boot was empty , since the kernel and additional files
are based in that partition. Not much left to say, is it some weird ssd and luks+lvm issue but I am sure someone else would have run into it by now. |
Quote:
I'm pretty much out of suggestions at this point. :( |
Quote:
Might be worth trying the 'generic' kernel rather than 'huge', when you're using an initrd. |
That was it!, I assumed using the huge kernel was ok since the README uses smp and mentions lilo complaining about the initrd.gz size. Only thing now, I think I am missing my usb drivers for my keyboard as it freezes on password input but thanks for your help!
|
Adding "ehci-hcd:uhci-hcd:usbhid" to your list of modules on the mkinitrd should sort that out. I have to do that too.
Glad you got it sorted. :) |
All times are GMT -5. The time now is 01:43 AM. |