On Mon, Feb 21, 2005 at 11:20:21AM -0500, Smith, Albert wrote: > > -----Original Message----- > > From: redhat-list-bounces@xxxxxxxxxx > > [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Dean Landry > > Sent: Monday, February 21, 2005 10:38 AM > > To: redhat-list@xxxxxxxxxx > > Subject: Kernel Panic with Latest AS v.4 update > > > > The RHN just released an update to my kernel > > (2.6.9-5.03.ELsmp). I installed it using up2date and then > > restarted the machine. I got a Kernel Panic when I restarted > > so I've rebooted into the old kernel (2.6.9-5.ELsmp). > > > > The lines leading up to the error were: > > > > Red Hat mash version 4.1.18 starting > > Mounted /proc filessystem > > Mounting sysfs > > Creating /dev > > starting udev > > Loading jbd.ko module > > Loading ext3.ko module > > Creating root device > > mkrootdev: label / not found This means that the volume isn't labeled or doesn't match what's in grub.conf. > > Mounting root filesystem > > mount: error 2 mounting ext3 > > mount: error 2 mounting none > > Switching to new root > > switchroot: mount failed: 22 > > umount /initrd/dev failed: 2 > > Kernel panic - not syncing: Attempted to kill init! > > > > How do I start to troubleshoot this? > > > > When you put the new kernel in did you create a new ramdisk? That's done automatically by the post-install scripts for the kernel. You can see this with: $ rpm -q kernel --scripts As for the original poster, let's have a look at /etc/grub.conf. Please don't tell us you're still running lilo. -- Ed Wilts, RHCE Mounds View, MN, USA mailto:ewilts@xxxxxxxxxx Member #1, Red Hat Community Ambassador Program -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
