Kernel init failed with Maxtor Ultra ATA 133 adapter

[sundanceloki]

Ok, after a couple of days of searching google, usenet, etc. I am offically stuck.

A little background info first:
I have 5 ide devices. hda, hdb, hdc, and hdd are on the motherboard's IDE controler. The fifth device, hde, was a Maxtor drive hung off of an Adaptec 1200A IDE card. Since there is only on disk connected to this card, ther is no raid involved. This is a dual boot system where hda is XXXindows, hdb is Fedora Core, hdc and hdd are CD-ROMS, and hde is a shared drive between the 2 OS's.

Now everything was just peachy until the Adaptec card Bombed on me. I had a spare Maxtor Ultra 133 card that I replaced it with. If the maxtor card is installed, regardless of whether I have a disk attatched or not. Fedora fails to boot. It gives a Kernel Panic: no init found. Remove the card, Fedora Boots fine.

Help please :)

SDL

[mhelios]

This could be a number of things:
Borked grub config -
run "linux rescue" off the CD and then:
chroot /mnt/sysimage
grub-install /dev/hda (whatever drive has your /boot)
exit

A stuffed /sbin/init -
reinstall SysVinit from rescue mode

Corrupt root fs -
run e2fsck from rescue mode with all partitions unmounted

Other hings to try:
at text grub prompt:
"linux init=/sbin/init"
"single"

Or a boot disk....

[sundanceloki]

Thanks for the reply,

:)

Running lilo not grub. I triple checked the options in /etc/lilo.conf and nothin gseems out of order.

Also since the machine boots as normal without the card. I dont think there is any file corruption.

Its a very strage problem, I'm about at my wits end.:confused:

Either way, thanks again for your suggestion.

[Bana]

It appears that your lilo config file needs to be updated, you need to make sure that lilo is looking on the correct drive (and partition) for your initrd file. The maxtor card is possibly changing the arrangement of your drives around and hence the problem. I forget how to work lilo but there are many good howtos if you search. HTH