Description of Problem: After bug #60134, I booted the system with a rescue cd I made. I moved the boot directory to '/blah', symlinked boot to boot0, mounted sda1 & sdb1 as boot0 and boot1, copied all files from /blah (cp -a blah boot0). I ran "lilo -r ." and rebooted. The system recognised lilo but fails with the above kernel panic. I did not change the lilo.conf from the created one. I tried changing the lilo.conf file to boot=/dev/sda (i have 11 other systems like that) and ran lilo with 'lilo -r ." again. Rebooted, same error -- No init found. Version-Release number of selected component (if applicable): How Reproducible: Every time I reboot it fails. Steps to Reproduce: 1. 2. 3. Actual Results: Expected Results: Additional Information:
Do
Er... bugzilla ate that. Do you have an initrd line in your lilo.conf?
Yes, I deleted the message line. prompt boot=/dev/md0 map=/boot/map install=/boot/boot.b vga=ext image=/boot/vmlinuz-2.4.7-10 label=linux initrd=/boot/initrd-2.4.7-10.img read-only root=/dev/md0
Is the SCSI driver getting properly loaded from the initrd?
Closing due to inactivity, please reopen if you contine to have problems.
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.