Thanks. I had already checked, and ext2 was compiled in. Just to be sure, I went ahead and started from scratch - recompiled the kernel, modules, etc. I also re-checked my .config settings, and ide support, along with ext2 were both included. Upon reboot, I encountered the same error.
Is it possible that, due to changes in the kernel, that /dev/hda5 is no longer pointing to the same place? Maybe my root partition has moved somehow? I can't imagine how, but could ext2 have changed? Thanks again. Mikkel L. Ellertson wrote: >On Fri, 19 Oct 2001, Michael Stack wrote: > >>All, >> >>I've been running the stock RH7.1 kernel for about 6 months. I recently >>decided to upgrade, so I grabbed the source to 2.4.12, and did the >>following: >> >>make mrproper >>make xconfig >>(selected options) >>make dep >>make bzImage >>make modules >>make modules_install >> >>Since I use a boot disk, I grabbed a new disk, and issued the "mkbootdisk >>2.4.12" command. The boot disk seemed to build fine. >> >>However, when I boot with the new boot disk, I get an error: >> >>"VFS: cannot mount /dev/hda5, please specify root= option" >> >>or something very similar. When I boot with the old boot disk (kernel >>2.4.2-2), everything works fine. >> >>I checked: >> >>(1) /etc/lilo.conf - entries seem correct for both 2.4.2-2 and 2.4.12. I >>also ran lilo, so the changes were committed. >> >>(2) ext2fs is compiled into the kernel. >> >> >>/dev/hda5 *is* an ext2fs partition, and it works fine with 2.4.2-2. >> >>Does anyone know why the new kernel refuses to mount /dev/hda5? FYI, that's >>my root partition. >> >>Thanks. >> >Double check that you have compiled in the IDE hard drive drivers. Also >make sure you have support compiled in for your root file system. >(Probably ext2 support.) > >Mikkel > _______________________________________________ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
