I have seem this problem on non-ia64 system. First, check which root partition the kernel is said to use (root= kernel option).
Then watch the boot process and check how your boot HDD is being recognized. The most common case is when you try to boot from root=/dev/hda1, but your HDD is being recognized as, say, /dev/hde1. On my system I have two IDE controllers and sometimes their recognition order is being changed. I have PATA HDD attached to ICH7 controller and DVD-RW to ITE8211. So, in normal case I have /dev/hde for my HDD and /dev/hda for DVD-RW. But sometimes ICH7 driver is being loaded before ITE8211, and I get them switched: /dev/hda for HDD and /dev/hde for DVD-RW, and I get the same error as you. В Вск, 02/07/2006 в 10:14 -0700, Spundun Bhatt пишет: > Can someone please respond to my question over here? This *is* the right > forum, isn't it? > > > Spundun Bhatt wrote: > > Hi debian-ia64. > > > > I updated the kernel on my debian linux testing from > > linux-image-2.6.12-1-mckinley to linux-image-2.6.15-1-mckinley . > > > > When I rebooted, I got the error saying the following (very early in the > > boot). > > > > RAMDISK: Compressed image found at block 0 > > Kernel panic - not syncing: VFS: Unable to mount root fs on > > unknown-block (0,0) > > > > I suspect that the new kernel bootloader configuration is pointing to a > > non-existing location for root partition... > > > > Can anyone guide me as to how to debug this problem? > > Also is there any literature available that will help me understand how > > linux boot loader works on debian on ia64? I mean what are the packages > > responsible for installing the bootloaders and where can I find the > > configuration so that I can check whether its right or not, etc? > > > > Thanks a lot > > > > Spundun > > > > > > -- Покотиленко Костик <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
