Re: Possible generation of damaged initrd / lilo problem
On Saturday 13 March 2004 01:48, Herbert Xu wrote: Make sure that you have dash 0.4.24 and regenerate the initrd image. Please let me know If the problem persists. Thank You! That was it.
Re: Weird problem after kernel/lilo upgrade
On Friday 12 March 2004 09:30, you wrote: Having booted from a CD Run lilocfg to regenerate your lilo config Rerun lilo from the hard drive You should see new entries DEB 0 DEB 1 Rerun lilo again for good luck :) Reboot HTH - it worked for me. Andy Unfortunately, it didn't do the trick in my case .. Furthermore I've tried writing a new partition table, just added a new partition in the unpartitioned space, but that didn't help either .. Thanks for the help ;) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Possible generation of damaged initrd / lilo problem
Hello, I had this[1] problem, and after investigating further, I think it's either lilo fault to write the initrd correctly or the initrd.img is generated badly. Here's my lilo.conf: boot=/dev/hda install=/boot/boot.b map=/boot/map prompt timeout=50 default=425 lba32 image=/vmlinuz label=default root=/dev/hda2 read-only initrd=/initrd.img image=/boot/vmlinuz-2.4.25-1-686 label=425 root=/dev/hda2 read-only initrd=/boot/initrd.img-2.4.25-1-686 I've tried changing the value of DELAY to 10 in /etc/mkinitrd/mkinitrd.conf and did dpkg-reconfigure kernel-image-version which generates the new initrd.img, run lilo afterwards but no delay occurs, and no modules for the ide disk are loaded. I've mounted the newly generated initrd.img-version and all the files seem to be in it. I've also run the lilo with -v 3 and it seems to do everyting correctly. Any ideas ? Cheers, Delian [1] http://lists.debian.org/debian-boot/2004/debian-boot-200403/msg01195.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Weird problem after kernel/lilo upgrade
Hi, I did apt-get upgrade yesterday, and additionaly installed the latest kernel-image(4.25 and 6.3) debs. The system was not updated from about mid February. I've rebooted the system after the upgrade, just to verify everything is ok. Unfortunately now I'm getting the: Kernel panic: VFS: Unable to mount root fs on 03:02 I've tried reverting the kernel-image to the previous one installed, and also noticed that lilo was also upgraded in that apt-get upgrade, so reverted it also. I've also tried specifying different bootparams - specifying the root device, giving the hda=noprobe hda=..., etc. etc. I've also looked at lilo.conf, and ran lilo several times(the new and the reverted version). Unfortunately I'm not able to boot with any of the Debian supplied kernels. I got an slack 8.1 bootable cd, passed the root=/dev/hda2 and it booted ok. The kernel from netinsts cd from mid february also boots ok with default params, but is not able with root=/dev/hda2. Here are the last several lines before the kernel panic msg: RAMDISK: cramfs filesystem found at block 0 RAMDISK: Loading 3948 blocks [1 disk] into ram disk... done. Freeing initrd memory: 3938k freed VFS: Mounted root (cramfs filesystem). VFS: Cannot open root device 302 or 03:02 Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on 03:02 It's debian sid running on HP Vectra P3 500Mhz, 20G ide, 128 mem etc. Any help will be greatly appreciated. Thanks Delian P.S. please cc me since I'm not currently subscibed to the list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
