Unable to mount ext3 on laptop: kernel panic
 

I have a laptop which doesn’t have a brandname. It is a ‘china make’ and I think is assembled laptop. This laptop uses a promise SATA card, to which a harddisk is connected. So, during booting it requires a promise SATA card driver, otherwise Harddisk is not detected properly. I faced this problem with Windows and Linux installation. I could install linux in 3rd attempt. Anyways now the problem is that when i recompiled kernel 2.6.15.4 on the same machine it gives the following kernel panic message:

****************************************************************

Booting ‘Fedora Core 4 (2.16.15.4)’

Root (hd0,4)

Filesystem type is ext2fs, partition type 0x83

Kernel /boot/vmlinuz-2.6.15.4 ro root=LABEL=/1 rootfstype=ext3 enforcing=0 rhgb quiet

[Linux-bzImage, setup=0x1e00, size=0x19f457]

Initrd /boot/initrd-2.6.15.4.img

[Linux-initrd @ 0x1fd67000, 0x128da7 bytes ]



Uncompressing Linux . . . Ok, booting kernel.

PCI: Failed to allocate mem resource #6:20000@d0000000 for 0000:01:00.0

Red Hat nash version 4.2.15 starting

Mkrootdev: label / not found

Mount: error 2 mounting ext3

ERROR opening /dev/console!!!!: 2

Error dup2’ing fd of 0 to 0

Error dup2’ing fd of 0 to 1

Error dup2’ing fd of 0 to 2

Switchroot: mount failed: 22

Kernel Panic – not syncing: Attempted to kill init!

**************************************************************************************************** **************************

My grub.conf looks this way:



#boot=/dev/sda5

default=3

timeout=5

splashimage=(hd0,4)/boot/grub/splash.xpm.gz

hiddenmenu

title Fedora Core (2.6.11-1.1369_FC4smp)

root (hd0,4)

kernel /boot/vmlinuz-2.6.11-1.1369_FC4smp ro root=LABEL=/ rhgb quiet

initrd /boot/initrd-2.6.11-1.1369_FC4smp.img

title Fedora Core-up (2.6.11-1.1369_FC4)

root (hd0,4)

kernel /boot/vmlinuz-2.6.11-1.1369_FC4 ro root=LABEL=/ rhgb quiet

initrd /boot/initrd-2.6.11-1.1369_FC4.img

title Fedora Core 4 (2.6.15.4)

root (hd0,4)

kernel /boot/vmlinuz-2.6.15.4 ro root=/dev/sda5 rhgb quiet

initrd /boot/initrd-2.6.15.4.img

title Other

rootnoverify (hd0,0)

chainloader +1

**************************************************************************

My fdisk -l looks like this:

Disk /dev/sda: 60.0 GB, 60011642880 bytes

255 heads, 63 sectors/track, 7296 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sda1 * 1 3824 30716248+ c W95 FAT32 (LBA)

/dev/sda2 3825 7295 27880807+ f W95 Ext'd (LBA)

/dev/sda5 3825 7167 26852616 83 Linux

/dev/sda6 7168 7294 1020096 82 Linux swap / Solaris

And the fstab entry looks like this :

# This file is edited by fstab-sync - see 'man fstab-sync' for details

LABEL=/ / ext3 defaults 1 1

/dev/devpts /dev/pts devpts gid=5,mode=620 0 0

/dev/shm /dev/shm tmpfs defaults 0 0

/dev/proc /proc proc defaults 0 0

/dev/sys /sys sysfs defaults 0 0

LABEL=SWAP-sda6 swap swap defaults 0 0

/dev/hdb /media/cdrecorder auto pamconsole,exec,noauto,managed 0 0

**************************************************************************************************** ************************

What could be the reason for this??

in your fstab file and menu.lst, replace
LABEL=/ with /dev/hda4

(or whatever partiition your root is, i think hd(0,4) is first ide - master, partition 4,
that is device /dev/hda4 in linux)

FYI:
/dev/hda primary ide - master
/dev/hdb primary ide - slave
/dev/hdc secondary ide - master
/dev/hdd secondary ide - slave

and the numbers 1-4 for primary partitions and 5 or greater for logical ones.


hth,
Flo

and btw: one posting is normally enough,
you'll get more answers without spamming the forum ;)

Hi there


hd(0,4) is first ide - master, partition 4,

is not correcnt

hd(0,4) stands for 5th partition not for 4th

also since he is not having any issues while booting with older kernels,then i do not think he need to replace the entry in /etc/fstab.
Now there can be a problem with the kernel that he has compiled.

regards

you're right, and of course with a sata disk he has to use /dev/sda* instead /dev/hda*

seems that the sata modules are not compiled in or not correctly loaded by initrd...

but I never used initrd and don't hava a SATA system, so I'm out...

good luck anyway,
Flo