I had this same error for months with my Pentium II machine, and it drove me absolutely nuts. Everytime I asked for help, I was told to compile in fs, other basic things, which I already did. So my P2 machine never switched to 2.6 for along time because I got this error and the kernels would never boot.
Once I was watching the boot messages scroll by on a working 2.4. I think it was a config from way back, a distro one back when I used Slackware that had everything but the kitchen sink compiled into it. To make a long story short(er), there's another IDE bus in there. Why I don't know, I didn't build this machine. I had supported the PIIX3 IDE, but there was still a PDC20246 in there that attached the actual disks. I have this as my root, which is not standard: /dev/hde1 Usually you'd expect /dev/hda1 or similar. Once I added another hard disk to the machine I got to see what they did when it was built, looks like this:
PIIX3: ide0, ide1, a ATAPI CD and Tape drive
hdc, hdd
20246: ide2, ide3, a 80gig HD, and a 3gig HD,
hde, hdf
So, the bus my actual disks were sitting was not supported: no wonder "can't find root" Can't see disk
If you've made sure you've compiled in your filesystem and any obvious hardware, make absolutely sure you're supporting anything not-so-obvious, like this IDE bus in my example. Try to compare a working boot messages log to one that doesn't, line by line, real carefully. There must be something in there that's not getting supported (failing you're having actual hardware failure, but I think what you've said is not about broken hardware.)
Here's my 2.6.16.16 off my Pentium4's config:
Code:
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDE_SATA=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDEFLOPPY=y
CONFIG_IDE_GENERIC=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_IDEDMA_PCI_AUTO=y
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDEDMA_AUTO=y
CONFIG_VIDEO_SELECT=y
and the P2 at same version:
Code:
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDE_SATA=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDETAPE=m
CONFIG_BLK_DEV_IDEFLOPPY=y
CONFIG_IDE_GENERIC=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_IDEDMA_PCI_AUTO=y
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDEDMA_AUTO=y
CONFIG_VIDEO_SELECT=y
The option that alone caused the kernel not to boot with the VFS errors was this one not being set:
Code:
CONFIG_BLK_DEV_PDC202XX_NEW=y
Have a look at "lsdev", "lspci", and compare the two boot sequences. "Unknown block 3-2" sure sounds alot like my PDC problem. Have a look at the other CONFIG_BLK_DEV stuff as well. From devices.txt:
Quote:
3 block First MFM, RLL and IDE hard disk/CD-ROM interface
0 = /dev/hda Master: whole disk (or CD-ROM)
64 = /dev/hdb Slave: whole disk (or CD-ROM)
For partitions, add to the whole disk device number:
0 = /dev/hd? Whole disk
1 = /dev/hd?1 First partition
2 = /dev/hd?2 Second partition
|