Solved: Re: Host Upgrade to 6.0.0U1 using update manager r...

Joris85 · ‎12-08-2015

Dear,

I am stuck when upgrading one of my production servers to 6.0.0U1 using Dell customized VMware images and Update Manager.

vCenter and Update manager are version 6.0.0U1, the ESXi hosts do not have U1 but have the image A00 of Dell (initial release).

After we tried to upgrade from dell image A00 to image A01 of vmware ESXi 6.0 (upgrade to U1), using the update manager, we got this error on the idrac:

When pressing enter:

After pressing enter again, the server reboots and has the same issue.

The upgrade is done using the official DEll images and the latest vsphere update manager (U1) vcenter (U1):

I can find some articles on VMware knowledgebase but since I cannot type in anything, I don't know what to do:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=201582...

SSH is not working at this stage.

We are stuck on this, anyone can help?

Joris

EDIT: I was able to restore the previous image doing Shift + R, but I do not know why the upgrade fails. I have no local datastores. The hypervisor is installed on internal flash.

Disk /dev/disks/mpx.vmhba32:C0:T0:L0: 7969 MB, 7969177600 bytes

64 heads, 32 sectors/track, 7600 cylinders

Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System

/dev/disks/mpx.vmhba32:C0:T0:L0p1 5 900 917504 5 Extended

/dev/disks/mpx.vmhba32:C0:T0:L0p2 901 3460 2621440 fc VMKcore

/dev/disks/mpx.vmhba32:C0:T0:L0p4 * 1 4 4080 ef EFI (FAT-12/16/32)

/dev/disks/mpx.vmhba32:C0:T0:L0p5 5 254 255984 6 FAT16

/dev/disks/mpx.vmhba32:C0:T0:L0p6 255 504 255984 6 FAT16

/dev/disks/mpx.vmhba32:C0:T0:L0p7 505 614 112624 fc VMKcore

/dev/disks/mpx.vmhba32:C0:T0:L0p8 615 900 292848 6 FAT16

Partition table entries are not in disk order

Found valid GPT with protective MBR; using GPT

Joris85 · ‎12-08-2015

OK I got Dell Prosupport 24/7 on this (OEM vSphere License) and boy I keep getting impressed by these guys.

It seems ALL MY SERVERS (4) are effected by this issue. Dell claims it is a bug in the ESXi image used by Dell but provided by VMware to Dell.

We identified this to a common problem with vmware for upgrade.

In the upgrade phase vmware update manager looks for vmhba32.C0:T0:L0:7 if that is not the active parttion it will fail

esxcli system coredump partition list

will list something like this:

mpx.vmhba32:C0:T0:L0:7 /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0:7   false       false

mpx.vmhba32:C0:T0:L0:2 /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0:2    true        true

we are going to activate the partition 7

#esxcli system coredump partition set -–partition=mpx.vmhba32:C0:T0:L0:7

After this we enable it:

#esxcli system coredump partition set –-enable true

Then we delete the partition 2:

partedUtil delete “/vmfs/devices/disks/mpx.vmhba32:C0:T0:L0” 2

Now we check it:

Esxcli system coredump partition list

Expected output:

[root@FG-ESX-3:~] esxcli system coredump partition list

Name                                 Path                                                                   Active Configured

---------------------- ------------------------------------------ ------ ----------

mpx.vmhba32:C0:T0:L0:7 /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0:7   True       True

After this, setup using the Update Manager was run and continued correctly but I had an issue on:

"Running 003.firstboot_ad_migration" during boot of the U1 version, that hang.

So I used these guidelines: Upgrade to 6 from 5.5 hangs at "Running 003.firstboot_ad_migration"

And reverted to the previous version, removed the ESXi Host from Active Directory, Upgraded to U1 again and it worked.

Then I readded the ESXi to Active Directory.

That was quite some struggle just to update 1 ESXi host to 6.0.0U1 (Dell A00 2494585 to A01 Build 3073146).

View solution in original post

Joris85 · ‎12-08-2015