steveblackburn
Contributor
Contributor

URGENT!! GRUB _ STUCK PROBLEM

Hi

hoping someone can help me here. We have two ESX 3.5 servers running on identical DELL Poweredge 2900 servers.

I attempted to upgrade one of these to ESX 4 using the upgrade client from vSphere. All went well until the server reboot and then I got a: root (hd 0,1) ERROR 22, no such partition. Now I beleive this was down to the RAID arrays in the server (2 RAID Arrays) where it boots off the second array but then couldnt see the upgrade partition on the datastore. I then edited the ESX 4 upgrade option at the boot loader prompt to tell set the upgrade partition to hd 1,1, selected upgrade from the boot loader again and it loaded it found the upgrade partition and did the upgrade sucessfully. I then rebooted and selected ESX 4 and got a similar error about the partition not being found. It then dropped be back to the boot loader menu and I selected the old ESX 3.5 and it booted and ran 3.5 fine. I then shut down the server again and restarted it (all vm's still powered off) and when it rebooted this time it got to: GRUB _ (with a flashing _) and I am unable to do anything except CRTLALTDEL to reboot the server!!!!!! I have tried booting of the 3.5 CD and choosing upgrade and it finds existing 3.5 and upgrades fine but again when I reboot it gets stuck at GRUB _

I've tried to ring support but it looks like my boss only bought gold support (grrrrr) so I cannot get any support until monday morning!!!

Can anyone help please??!! (dont know if it might help but as the servers are identical h/w is there a way to get working grub from the working server and replace it on the broken one? just an idea Smiley Happy

Thanks

0 Kudos
4 Replies
AntonVZhbankov
Immortal
Immortal

Just make clean install of 4.0 on failed server. It would be much faster.


---

VMware vExpert '2009

http://blog.vadmin.ru

EMCCAe, MCITP: SA+VA, VCP 3/4/5, VMware vExpert http://blog.vadmin.ru
0 Kudos
steveblackburn
Contributor
Contributor

Hi

I had just tried that a few minutes ago (preserving the existing datastore) and same result.

some more info: I beleive ESX 3.5 was on vmhba1:1:0 and DATASTORE was on vmhba1:0:0:1 (as per working server) as I seem to recall that was how we had to install it to get it to boot from the correct RAID array

during the ESX 4 install I can select vmhba1:1:0 for ESX but am only given the option of vmhba1:0:0:1 for the console files. I have tried ticking and unticking the option of whether to put GRUB on MBR or disk

Thanks

0 Kudos
steveblackburn
Contributor
Contributor

Hi

ok, I think I have resolved it. I went into the LSI RAID config and changed the bootable disk (VD0 = Datastore was set to bootable, changed it to VD1 = ESX and it booted)

going to do the other server now but fingers crossed its all sorted.

0 Kudos
AntonVZhbankov
Immortal
Immortal

Glad to hear it.


---

VMware vExpert '2009

http://blog.vadmin.ru

EMCCAe, MCITP: SA+VA, VCP 3/4/5, VMware vExpert http://blog.vadmin.ru
0 Kudos