[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Kernel 2.6.10 boots panic



> I don't have much concept about Debian kernel images. I just compiled
> from vanilla source with the correct IDE chipset enabled and used
> mkinitrd introduced in
> http://copper.matsc.kyutech.ac.jp/~yoshi/linux/sata/index_e.html. Now
> kernel 2.6.10 finally boots properly on the no-brand box.
> 
> My next step is trying to boot the kernel on the server having Interl
> 6300ESB and Promise PDC20319 chipsets. I have more confidence of success
> now.

I booted kernel 2.4.25 from the ordinary old IDE disk. From there I did
these:

insmod scsi_mod
insmod ft3xx
mount -t ext3 /dev/sda1 /mnt
chroot /mnt
cd /usr/src/linux

and configured Promise SATA TX2/TX4 support (CONFIG_SCSI_SATA_PROMISE=y)
in the kernel. Compiled and copied bzImage to /boot and did "make
modules_install".

Then I applied RedHat mkinitrd from
http://minus-9.com/stuff/hostraid-debian/ as pointed by
http://copper.matsc.kyutech.ac.jp/~yoshi/linux/sata/index_e.html (under
the root shell, ie. no chroot) by doing:

cd /lib/modules
mv 2.6.10 2.6.10-bak
ln -s /mnt/lib/modules/2.6.10 /lib/modules/2.6.10
/opt/mkinitrd/sbin/mkinitrd /mnt/boot/initrd-img-2.6.10 2.6.10
chroot /mnt
<add entry "initrd=/boot/initrd-img-2.6.10" under 2.6.10>
lilo
exit
rm 2.6.10
mv 2.6.10-bak 2.6.10

When booting from Promise disk array, the new kernel aborts with
messages:

Red Hat nash version 3.4.42
Mounting /proc filesystem
Creating block devices
Creating root device
Mounting root filesystem
EXT3-fs error (device sda1): ext3_check_descriptors: Block bitmap for
group 912 not in group (block 0)!
EXT3-fs: group descriptors corrupted
mount: error 22 mounting ext3
pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2

Seeing this, I rebooted v2.4.25 from the old IDE disk and did "fsck -f
/dev/sda1". Fsck fixed a few filesystem bugs the first time. The second
run of fsck did not find any errors. Then I did the following again:

chroot /mnt
lilo

Rebooting from Promise still fails with the same errors. Please help!

BTW, which Debian package contains mkinitrd? Should I use it rather than
RedHat's mkinitrd? Somehow I have been unable to reach
http://packages.debian.org to search for it.

Regards,
CN



Reply to: