VMware Cloud Community
LucasAlbers
Expert
Expert

unable to upgrade from esxi 4 error unsupported boot disk, prereq.sh

So I was continueing my experimentation with upgrading.

I wiped my disk raid volumes in the perc raid management bios.

I installed esxi 4.0 GA.

I attempt to upgrade from 164009 to 171294 using the "Vmware vsphere host update utility."

I point it to the upgrade package.

It fails teh "Host Compatibility Check" with the following error:

ERROR: Unsupported boot disk

The boot device layout on the host does not support upgrade.

I could upload the log, but I decided to run the precheck script and determine why it was failing.

This is the step that is failing:

+ /sbin/partedUtil get /vmfs/devices/disks/naa.60022190b43dcc0011e53b691464be85

+ grep ^2

+ set -- 2 1843200 10229759 6 0

+

So this determines the partitions, startsector, end sector, type, attr.

/sbin/partedUtil get /vmfs/devices/disks/naa.60022190b43dcc0011e53b691464be85

557568 64 32 1141899264

4 32 8191 4 128

1 8192 1843199 5 0

5 8224 520191 6 0

6 520224 1032191 6 0

7 1032224 1257471 252 0

8 1257504 1843199 6 0

2 1843200 10229759 6 0

3 10229760 1141899263 251 0

So matching the partitions with fdisk -lu:

fdisk -lu

Disk /dev/disks/naa.60022190b43dcc0011e53b691464be85: 584.6 GB, 584652423168 bytes

64 heads, 32 sectors/track, 557568 cylinders, total 1141899264 sectors

Units = sectors of 1 * 512 = 512 bytes

Device Boot Start End Blocks Id System

/dev/disks/naa.60022190b43dcc0011e53b691464be85p1 8192 1843199 917504 5 Extended

/dev/disks/naa.60022190b43dcc0011e53b691464be85p2 1843200 10229759 4193280 6 FAT16

/dev/disks/naa.60022190b43dcc0011e53b691464be85p3 10229760 1141899263 565834752 fb VMFS

/dev/disks/naa.60022190b43dcc0011e53b691464be85p4 * 32 8191 4080 4 FAT16 <32M

/dev/disks/naa.60022190b43dcc0011e53b691464be85p5 8224 520191 255984 6 FAT16

/dev/disks/naa.60022190b43dcc0011e53b691464be85p6 520224 1032191 255984 6 FAT16

/dev/disks/naa.60022190b43dcc0011e53b691464be85p7 1032224 1257471 112624 fc VMKcore

/dev/disks/naa.60022190b43dcc0011e53b691464be85p8 1257504 1843199 292848 6 FAT16

It indicates the ending offset (10229759):

/dev/disks/naa.60022190b43dcc0011e53b691464be85p2 1843200 10229759 4193280 6 FAT16

This has to be true:

+

Does that sound right?

So it is comparing the offset against the esx_3i scratch ending partition?

/vmfs/volumes/4a528247-36d54338-78b9-00221927561b/ESXi-4.0.0-0.4.171294-upgrade-release # sh -x ./precheck.sh

+ : /sbin/partedUtil

+ TRUE=0

+ FALSE=1

+ retcode=0

+ ESX_3i_SCRATCH_BEG=1536000

+ ESX_3i_SCRATCH_END=9922559

+ ESX_4i_SCRATCH_BEG=1843200

+ ESX_4i_EXTENDED_END=1843199

+ SCRATCH_PARTITION=2

+ BOOTBANK=/bootbank

+ LOG_FILE=/var/log/vmware/upgrade.log

+ cpu_test_result=ERROR

+ cpu_test_found=False

+ Log Checking compatible CPU...

+ echo Checking compatible CPU...

+ vsish -b -r -e cat /hardware/cpu/cpuList/0

+ sed -n /id81/ {N N N N s/.edx:\(.\)/\1/p }

+ edx81=0xefd3fbff

+ CPU_MASK_LM=0x20000000

+

+

+ cpu_test_found=True

+ cpu_test_result=SUCCESS

+ Log Passed CPU test

+ echo Passed CPU test

+ EXPECTED_MEM=2047

+ mem_test_result=ERROR

+ mem_test_found=

+ Log Checking available memory...

+ echo Checking available memory...

+ vsish -b -r -e cat /memory/comprehensive

+ grep physmem

+ physmem= physmem:0x0000000001ffde74

+ total_mem=0x0000000001ffde74

+

+ mem_test_found=32768

+

+ mem_test_result=SUCCESS

+ Log Passed memory test.

+ echo Passed memory test.

+ Log Checking supported boot disk...

+ echo Checking supported boot disk...

+ bootdisk_test_result=ERROR

+ bootdisk_test_found=False

+ vmkfstools -P /bootbank

+ sed -n $s/^.\(.\+\):[0-9]$/\1/p

+ BootHBA=naa.60022190b43dcc0011e53b691464be85

+ vmware -v

+ BootDisk=/vmfs/devices/disks/naa.60022190b43dcc0011e53b691464be85

+ http:// -n naa.60022190b43dcc0011e53b691464be85 -a -n /vmfs/devices/disks/naa.60022190b43dcc0011e53b...

+ /sbin/partedUtil get /vmfs/devices/disks/naa.60022190b43dcc0011e53b691464be85

+ head -1

+ set -- 557568 64 32 1141899264

+

+ esxcfg-info -e

+ wrapped=1

+

+

+ /sbin/partedUtil get /vmfs/devices/disks/naa.60022190b43dcc0011e53b691464be85

+ grep ^2

+ set -- 2 1843200 10229759 6 0

+

+ Log Failed boot disk test, ThinESX

+ echo Failed boot disk test, ThinESX

+

+ cat

<?xml version="1.0" ?>

<precheck>

<tests>

<test>

<name>SUPPORTED_CPU</name>

<expected>

<value>True</value>

</expected>

<found>

<value>True</value>

</found>

<result>SUCCESS</result>

</test>

<test>

<name>MEMORY_SIZE</name>

<expected>

<value>2047</value>

</expected>

<found>

<value>32768</value>

</found>

<result>SUCCESS</result>

</test>

<test>

<name>SUPPORTED_BOOT_DISK</name>

<expected>

<value>True</value>

</expected>

<found>

<value>False</value>

</found>

<result>ERROR</result>

</test>

</tests>

</precheck>

+ exit 0

0 Kudos
5 Replies
AlbertWT
Virtuoso
Virtuoso

Hi Lucas Albers,

Firstly, your name is almost the same as my full name and the funny thing is taht i also experienced the same problem in upgrading the ESXi 3.5u4 into ESXi 4, eventhough i did extract the files and execute the .SH as well as following the upgrade steps from: http://technodrone.blogspot.com/2009/05/esx3i-to-esx4i-update.html

still no avail. Smiley Sad oh well i ended up with clean reinstall of my servers and then install it from the beginning.

Kind Regards,

AWT

/* Please feel free to provide any comments or input you may have. */
0 Kudos
LucasAlbers
Expert
Expert

i think i'll have another go at determining why it is failing.

The other system i upgraded from esxi 3.5 u4, upgrades perfectly to 4.0 using the host update utility.

0 Kudos
ceemour
Enthusiast
Enthusiast

I gave up on this method and used the cd to "repair' the install

0 Kudos
LucasAlbers
Expert
Expert

it appears you are able to patch a system, but not upgrade.

So the upgrade zip file I was referring to earlier is to upgrade from esxi 3.5 to 4.

It appears I was able to successfully patch up to build 175625.

You need to select PATCH not upgrade.

One big fat caveat, a patch will reboot the system immediately.

0 Kudos
dwang
Contributor
Contributor

Yes, the package you referred is for upgrade from ESXi 3.5 to 4.0 only.

0 Kudos