From: Geoffrey <li...@se...> - 2010-04-21 14:04:00
|
Geoffrey wrote: > So I rebuilt my kernel, insuring that I had ext3 support and I still get > a panic, although it is a different message: > > Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(0,0) > > Here are my grub entries. The first is the new kernel, the second is my > current working kernel. > > title Red Hat Enterprise Linux Client (2.6.33.2) > root (hd0,2) > kernel /vmlinuz-2.6.33.2 ro root=LABEL=/ irqpoll rhgb > initrd /initrd-2.6.33.2.img > title Red Hat Enterprise Linux Client (2.6.18-194.el5) > root (hd0,2) > kernel /vmlinuz-2.6.18-194.el5 ro root=LABEL=/ irqpoll rhgb quiet > initrd /initrd-2.6.18-194.el5.img > > I still wonder if the fact that file returns different info about my > current working kernel and this new kernel has anything to do with this > issue? > > boot> file vmlinuz-2.6.33.2 vmlinuz-2.6.1 > vmlinuz-2.6.33.2: Linux kernel x86 boot executable RO-rootFS, > root_dev 0x808, swap_dev 0x3, Normal VGA > vmlinuz-2.6.18-194.el5: ELF 64-bit LSB shared object, AMD x86-64, > version 1, stripped Googling this keeps pointing to the lack of file system support, but I've got it in my config: CONFIG_EXT3_FS=y # CONFIG_EXT3_DEFAULTS_TO_ORDERED is not set CONFIG_EXT3_FS_XATTR=y # CONFIG_EXT3_FS_POSIX_ACL is not set # CONFIG_EXT3_FS_SECURITY is not set -- Until later, Geoffrey "I predict future happiness for America if they can prevent the government from wasting the labors of the people under the pretense of taking care of them." - Thomas Jefferson |