VMware Cloud Community
Cyrille63
Contributor
Contributor

ESX 3.5 U4 upgrade -> PSOD

Hi to all,

I just upgrade ESX 3.5 U2 to U4 with the cdrom (upgrade) , installation was great but when I reboot I have the PSOD. I cannot see the grub.

My server is HP Proliant ML570 G3 whith 2 logical RAID drives.

Channel 1 /dev/cciss/c0d0 is for VMs

Channel 2 /dev/cciss/c0d1 is for ESX

  • /dev/cciss/c0d1p1 is /boot

  • /dev/cciss/c0d1p2 is swap

  • /dev/cciss/c0d1p3 is /

  • /dev/cciss/c0d1p4 is vmkcore

  • /dev/cciss/c0d1p5 is /var/log

I think MBR is not installed on the right disk. I think GRUB is on /dev/cciss/c0d1 and it's searched on /dev/cciss/c0d0

Thanks in advance,

Cyrille

Reply
0 Kudos
10 Replies
marcelo_soares
Champion
Champion

If is a PSOD, I think your host is booting. Can you post a (legible please) picture of it?

Marcelo Soares

VMWare Certified Professional 310

Technical Support Engineer

Linux Server Senior Administrator

Marcelo Soares
Reply
0 Kudos
Cyrille63
Contributor
Contributor

This is my PSOD

Reply
0 Kudos
marcelo_soares
Champion
Champion

wow... this definitely is not a PSOD... they are a bit more "purple" that this red one and have more information.

Are you sure you are looking at the right place?

Marcelo Soares

VMWare Certified Professional 310

Technical Support Engineer

Linux Server Senior Administrator

Marcelo Soares
Reply
0 Kudos
Cyrille63
Contributor
Contributor

Can you explain, I don't understand, this is not a psod ?

What do you mean by "Are you sure you are looking at the right place?" ?

Thanks

Reply
0 Kudos
marcelo_soares
Champion
Champion

The PSOD is something like this: http://www.amikkelsen.com/images/ESX305-PSOD.jpg

It appears on your physical console when you boot the host. This red message I think is from your bios, not from the ESX.

Marcelo Soares

VMWare Certified Professional 310

Technical Support Engineer

Linux Server Senior Administrator

Marcelo Soares
Reply
0 Kudos
Cyrille63
Contributor
Contributor

Sorry I think it was a PSOD, in fact it's a red sod like http://communities.vmware.com/thread/218427

My server is in the compatibility list, I don't understand, my bios is up to date

Reply
0 Kudos
bulletprooffool
Champion
Champion

If your server IS on the HCL, I'd suggest booting the latest HP Smart Start and updating all your firmware etc.

Next remove any additional attached storage / USB / Serial etc devices.

Next run the ESX upgrade AGAIN.

Now close your eyes, hit the power on button and say a little prayer

Please post back on your resolution as it seems this problem has appeared for a few people.

One day I will virtualise myself . . .
Reply
0 Kudos
Cyrille63
Contributor
Contributor

BIOS is the lastest

RAID Controler firmware is the lastest

I have done a test, I take back all the disks from channel 1 (so no vms) and I boot aonly with channel 2, and It's OK ESX starts but without vms (it's normal)

I think my problem is because MBR is on hte fisrt disk (channel 1) and /boot is on second disk (channel). I think grub is not correct.

Any idea about boot options to install MBR ?

Reply
0 Kudos
Silverchenau
Enthusiast
Enthusiast

As far as I know (correct me if I am wrong), the boot must be seeing by ESX when it boots. Put boots into second HD channel is bad idea(can I ask why?).

It's the same thing as booting from SAN(when you use blade server), u must make sure ESX(well, SC more accruate) must see that partition.

Following partition should be on first primary partition.

/boot

/

/swap

- Silver My Vmware blog: http://geeksilverblog.com
Reply
0 Kudos
Cyrille63
Contributor
Contributor

You are right Silvercheneau, /boot and grub must be on the same partition and on the primary partition.

In my case I cannot put grub and /boot on the first HD channel (because there are vms) so I found the solution "add a storage controler and put esx on this controler". ESX and grub are now on first primary partition.

Now it works, the firs installation was not correct and the upgrade shows it.

Thanks to Gus, , and

Reply
0 Kudos