> kernel's internal name for the device otherwise known as /dev/hda2. The 3
> uniquely identifies the IDE disk block driver. This is known as the ``major
> number''. And the 2 is interpreted by the driver as a designator of the second
> partition on the primary drive. This is known as the ``minor number''.
> When the kernel is in its early booting stages, there is no mounted filesystem
> yet, which means that the ability to refer to devices by handy names like
> /dev/hda2 isn't yet available. Thus the kernel uses the low-level means to
> locate the ``root FS''---the filesystem that will provide the essential root
> The question is, why is your kernel not finding a filesystem at the second
> partition of your primary drive?
> One possibility is that the kernel is mistaken. Perhaps there is no filesystem
> at 03:02; the root filesystem is in some other partition. Luckily, if you are
> using LILO, you can pass a command line parameter to the kernel to tell it to
> look for the root partition elsewhere. The command line parameter looks like
> "root=/dev/hda1". After you boot successfully, you can use the "rdev"
> utility to deposit correct the information in the kernel image so that it will
> look in the right place by itself the next time you boot it.
> Another possibility is that the IDE device driver known by the major number
> 3 simply isn't in the kernel.
> Have you done anything to the floppy disk lately, like put a new kernel on it?
> We can rule out the above causes if you haven't tampered with the floppy.
> Secondly, has your system crashed or exhibited erratic behavior? Did you ever
> see, on the console, panics or error messages related to your hard disk?
> It could be that your /dev/hda2 is toast and you need to recover from backups.
> Or worse; the drive may have failed. But let's not jump to conclusions until we
> know that it's not something silly, like the kernel looking at the wrong