Centos4 & VMWare ESX server - kernel panic

If it doesn't fit in another category, ask it here.
User avatar
toracat
Forum Moderator
Posts: 7230
Joined: 2006/09/03 16:37:24
Location: California, US
Contact:

Re: Centos4 & VMWare ESX server - kernel panic

Postby toracat » 2010/04/07 16:22:07

freethinker wrote:

I think it needs "mptsas, mptspi & mptscsi" for the VMWare ESX "LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI" controller.
It is not loading the module so it cannot mount the root volume and then I get a Kernel Panic.
Just my working theory.

I'll try to get an outage for Monday evening and then post a screen shot.
Maybe that will give everyone some ideas.

Any new development on this?

As far as kernel modules are concerned, CentOS is supposed to be identical to RHEL. So, what you are experiencing is puzzling.

freethinker
Posts: 29
Joined: 2010/03/24 16:24:15
Location: St. Louis, MO
Contact:

Re: Centos4 & VMWare ESX server - kernel panic

Postby freethinker » 2010/04/07 16:45:23

I lost a few days because of the holiday over the weekend but I am hoping to get an outage tonight so I can get you a screen shot.

Thanks,
Dave

freethinker
Posts: 29
Joined: 2010/03/24 16:24:15
Location: St. Louis, MO
Contact:

Re: Centos4 & VMWare ESX server - kernel panic

Postby freethinker » 2010/04/07 23:25:53

Screen shot attached.

Hopefully it is legible and helps.

Thanks,
Dave

User avatar
toracat
Forum Moderator
Posts: 7230
Joined: 2006/09/03 16:37:24
Location: California, US
Contact:

Re: Centos4 & VMWare ESX server - kernel panic

Postby toracat » 2010/04/07 23:27:04

Attachment does not work with the current forum software. :-( Any other way you can show?

freethinker
Posts: 29
Joined: 2010/03/24 16:24:15
Location: St. Louis, MO
Contact:

Re: Centos4 & VMWare ESX server - kernel panic

Postby freethinker » 2010/04/07 23:32:24

I noticed that...
I tried several times and a few different extensions.

How about here?

http://docs.google.com/leaf?id=0B39fjQE ... MTll&hl=en

freethinker
Posts: 29
Joined: 2010/03/24 16:24:15
Location: St. Louis, MO
Contact:

Re: Centos4 & VMWare ESX server - kernel panic

Postby freethinker » 2010/04/07 23:48:35

Now that I am staring at it, /proc is mounted...
Does /proc mount before or after / & /boot on RHEL4?

Maybe it is reading something it does not like after all...

My thinking is that / & /boot are not mounted because the SCSI modules try to load after udev

User avatar
toracat
Forum Moderator
Posts: 7230
Joined: 2006/09/03 16:37:24
Location: California, US
Contact:

Re: Centos4 & VMWare ESX server - kernel panic

Postby toracat » 2010/04/08 00:58:18

My impression is /proc is mounted first, but I'm not quite certain about it. May need some investigation ...

pschaff
Retired Moderator
Posts: 18276
Joined: 2006/12/13 20:15:34
Location: Tidewater, Virginia, North America
Contact:

Re: Centos4 & VMWare ESX server - kernel panic

Postby pschaff » 2010/04/08 12:03:43

Looks to me to be a normal boot up to the point of trying to mount the new root filesystem. Earlier in the thread you said you weren't sure about the mkinitrd, although I don't know why it would not have been done right automatically in the first place, it might be worth revisiting that. If you can boot to the old kernel, you should be able to make a new initrd. Should go something like

Code: Select all

cd /boot
mv initrd-2.6.9-89.0.23.EL.img initrd-2.6.9-89.0.23.EL_bad.img
mkinitrd initrd-2.6.9-89.0.23.EL.img 2.6.9-89.0.23.EL
for the latest standard kernel.

IIRC substitute "ELsmp" for "EL" above for the smp kernel - haven't been on 4.x for a while.

freethinker
Posts: 29
Joined: 2010/03/24 16:24:15
Location: St. Louis, MO
Contact:

Re: Centos4 & VMWare ESX server - kernel panic

Postby freethinker » 2010/04/12 20:26:25

OK, I think I am narrowing it down.

Instead of making a new initrd, I thought I would just re-install the vmware tools since that makes a new image anyway.

During the install, this message scrolls quickly past:
"No module mptsspi found for kernel 2.6.9-89.0.11.ELsmp, aborting."

The fun part is that the vmware tools actually starts up anyway, which is what hides the problem.

Here is the modprobe.conf:

alias bond0 bonding
options bond0 mode=5 miimon=100 use_carrier=0
alias scsi_hostadapter cciss
alias scsi_hostadapter1 mptsspi
alias usb-controller ohci-hcd
alias eth1 tg3
alias eth0 tg3
# Added by VMware Tools
install pciehp /sbin/modprobe -q --ignore-install acpiphp; /bin/true
install pcnet32 /sbin/modprobe -q --ignore-install vmxnet;/sbin/modprobe -q --ignore-install pcnet32 $CMDLINE_OPTS;/bin/true
alias char-major-14 sb
options sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330


I have these modules:
/lib/modules/2.6.9-89.0.23.ELsmp/kernel/drivers/message/fusion/mptscsih.ko
/lib/modules/2.6.9-89.0.23.ELsmp/kernel/drivers/message/fusion/mptctl.ko
/lib/modules/2.6.9-89.0.23.ELsmp/kernel/drivers/message/fusion/mptlan.ko
/lib/modules/2.6.9-89.0.23.ELsmp/kernel/drivers/message/fusion/mptscsi.ko
/lib/modules/2.6.9-89.0.23.ELsmp/kernel/drivers/message/fusion/mptsas.ko
/lib/modules/2.6.9-89.0.23.ELsmp/kernel/drivers/message/fusion/mptspi.ko
/lib/modules/2.6.9-89.0.23.ELsmp/kernel/drivers/message/fusion/mptfc.ko
/lib/modules/2.6.9-89.0.23.ELsmp/kernel/drivers/message/fusion/mptbase.ko
/lib/modules/2.6.9-89.0.18.ELsmp/kernel/drivers/message/fusion/mptscsih.ko
/lib/modules/2.6.9-89.0.18.ELsmp/kernel/drivers/message/fusion/mptctl.ko
/lib/modules/2.6.9-89.0.18.ELsmp/kernel/drivers/message/fusion/mptlan.ko
/lib/modules/2.6.9-89.0.18.ELsmp/kernel/drivers/message/fusion/mptscsi.ko
/lib/modules/2.6.9-89.0.18.ELsmp/kernel/drivers/message/fusion/mptsas.ko
/lib/modules/2.6.9-89.0.18.ELsmp/kernel/drivers/message/fusion/mptspi.ko
/lib/modules/2.6.9-89.0.18.ELsmp/kernel/drivers/message/fusion/mptfc.ko
/lib/modules/2.6.9-89.0.18.ELsmp/kernel/drivers/message/fusion/mptbase.ko
/lib/modules/2.6.9-89.0.11.ELsmp/kernel/drivers/message/fusion/mptscsih.ko
/lib/modules/2.6.9-89.0.11.ELsmp/kernel/drivers/message/fusion/mptctl.ko
/lib/modules/2.6.9-89.0.11.ELsmp/kernel/drivers/message/fusion/mptlan.ko
/lib/modules/2.6.9-89.0.11.ELsmp/kernel/drivers/message/fusion/mptscsi.ko
/lib/modules/2.6.9-89.0.11.ELsmp/kernel/drivers/message/fusion/mptsas.ko
/lib/modules/2.6.9-89.0.11.ELsmp/kernel/drivers/message/fusion/mptspi.ko
/lib/modules/2.6.9-89.0.11.ELsmp/kernel/drivers/message/fusion/mptfc.ko
/lib/modules/2.6.9-89.0.11.ELsmp/kernel/drivers/message/fusion/mptbase.ko

Problem is, as soon as I edit the modprobe.conf (replacing mptsspi with mptscsi, mptspi, or mptbase, for example) and make a new image, the conf file is over-written with this one again and I'm back where I started.

Is there something from a GUI overriding my changes somewhere?

freethinker
Posts: 29
Joined: 2010/03/24 16:24:15
Location: St. Louis, MO
Contact:

Re: Centos4 & VMWare ESX server - kernel panic

Postby freethinker » 2010/04/12 20:44:50

In the meantime I've made a few symlnks (ln -s /lib/modules/2.6.9-89.0.23.ELsmp/kernel/drivers/message/fusion/mptspi.ko /lib/modules/2.6.9-89.0.23.ELsmp/kernel/drivers/message/fusion/mptsspi.ko) and I'm hoping to get an outage to reboot