Another 2.6.8.1 problem, unknown-block(3,65)
 

I'm trying to get the 2.6.8.1 kernel installed properly on my pc. I have had no problems installing and running it on my laptop but this Dell pc is just giving me one problem after another.

The current issue is that the kernel cannot mount the filesystem at boot. I have two hard-drives, the root target is (and in lilo as such):

root = /dev/hdb1

This is also called by "make" block device (3,65). When the 2.6.8.1 kernel boots it gets as far as mounting the root filesystem and gives the following:

I have an ext3 filesystem, with ext3 support compiled directly into the kernel. I have never had this issue before.

The entire entry in lilo reads as follows:

In fstab
If there is anything I've left out that can help let me know, I appreciate any help as I'm stumped.

hi,

here's an answer to the same Q.: http://www.ussg.iu.edu/hypermail/lin...08.3/0451.html
might help....

egag

I tried fsck on the drive but was warned that data may be damaged so thought better of it. I also compiled a new 2.4.27 kernel which is giving the very same problem as the 2.6.8.1. Thank fully I keep a backup of the default 2.4.26 kernel and modules.

That boots fine thankfully.

I don't see how it could be a lilo problem as the Slack kernel is pointed at /dev/hdb1 like the other two kernels. There must be something wrong with my kernel config. At the moment I am compiling the 2.6.8.1 kernel using the default .config from the slackware mirrors. I'll see if that changes anything.

See if you have enabled correct IDE controler (or SCSI if you have SCSI or SATA)

just rechecked all that and I have the correct controller enabled. I'm using the following these instructions to see if this can work.

Do you use udev ? Have you enabled ext2 fs in config ? Do you use a hard drive originally partitionned with windows ?

My hardrive was partitioned under Linux, with ext3 installed as the filesystem. EXT3 is compiled directly into the kernel with ext2 as a module. I shouldn't need to compile ext2 directly as I have no filesystem (expect for floppy disks) which are ext2. With the 2.6.x kernels I have been using UDEV. There have been no problems until yesterday when it got messed up like this.

I also found this which I'll try.

ext2 is the original linux filesystem, ext3 is a variant with journal feature, to my opinion, it won't hurt to try to enable it as built-in.

ok. should current attempt not work I'll add ext2. Thanks for the help.

I also just added this:

File systems ---> Partition Types --->[*] PC BIOS (MSDOS partition tables) support

Hope something works, although now I'll have no idea what fixed the problem!

[*] PC BIOS (MSDOS partition tables) support

That 's why I asked you if the hard drive was partitionned with windows, I had this problem one time with a PC.

I got thinking bout your question and so added it just in case. Kernel being built at the moment so fingers crossed it'll work...

hi there

intially during the bootup the partition is loaded as EXT2
then it is relaoded as EXT3
so u need ext2 support also in ur kernel

i too have faced this problem and it was rectified after u got ext2 support in my kernel(not as modules)

regards

ext2 support made no difference, nor did the partition table entry for msdos. Getting annoyed now. Building a new kernel using slackware 2.6.8.1 config file.

check and re-check IDE config, here is mine for 2.6.7 kernel (nvforce2 chipset)

cat .config | grep _IDE

CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
# CONFIG_IDEDISK_MULTI_MODE is not set
CONFIG_BLK_DEV_IDECD=m
# CONFIG_BLK_DEV_IDETAPE is not set
CONFIG_BLK_DEV_IDEFLOPPY=m
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_TASKFILE_IO=y
CONFIG_IDE_GENERIC=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_IDE_ARM is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y

this is mine (at the moment)

I change CONFIG_IDE_TASKFILE_IO from n to y to reflect yours. You have a references to CONFIG_IDEDMA_AUTO, whereas I do not, do I have to enable DMA someplace else?