Hi, > Bahadir Balban wrote: > > > Hi, > > > > I am trying to mount /dev/hda0 (the first partition on /dev/hda) as my > > ext3 root filesystem during boot. Even though I can mount this > > partition after boot and successfully see the files on it, (using > > "mount -text3 /dev/hda1 /mnt/disk1" and hda1 with major 3, minor 1) > > the same partition cannot be mounted as the root filesystem during > > boot. I get the error: > > > > VFS: Cannot open root device "0x301" or unknown-block(3,1) > > VFS: Cannot open root device "0x301" or unknown-block(3,1) > > Please append a correct "root=" boot option > > Please append a correct "root=" boot option > > <0>Kernel panic - not syncing: VFS: Unable to mount root fs on > > unknown-block(3,1) > > Kernel panic - not syncing: VFS: Unable to mount root fs on > > unknown-block(3,1) > > > > In kernel bootargs, I tried root=/dev/hda0, /dev/hda1 and also > > root=0x301 (major 3, minor 1) to mount it. It should have just worked. > > Any idea why it doesn't? > > It cannot load the ext3 unless it has driver for it, check if ext3 > driver is inbuilt... Hmmm... I'm able to boot my kernel when ext3 is compiled as a module. But this is because I use initrd. What distribution are you running? I use Fedora 6, and it correctly builds the ext3.ko module into the initrd so that the above module vs. built-in isn't an issue. However, I think it determines that it needs to include ext3 in the initrd via the /etc/fstab file's including an entry for the boot device as ext3. What kernel version are you running? Don't quote me on this, but I believe 2.6.21.x changed how drives are referred in that drives formerly referenced as /dev/hd* are now /dev/sd*. My guess is that since it works once the system is up, this isn't the issue. Kirk -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
