VMware Cloud Community
pkolmann
Contributor
Contributor

Upgrade ESXi4.0 to 4.0.1 fails with: ERROR Unsupported boot disk

I wanted to upgrade my ESXi Server to 4.0U1 and failed using the ESXi-4.0.0-1.9.208167-upgrade-release.zip with the error in the xShphere Host Update Utility:

ERROR: Unsupported boot disk

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

I reinstalled the server with ESXi 4.0 so I don't really understand why the boot layout isn't supported.

Hardware is Sun X4440

Thanks for any help

Philipp

0 Kudos
5 Replies
pkolmann
Contributor
Contributor

Also patching the host fails Smiley Sad

Patching 192.168.61.48

Start uploading files to host

Metadata and binaries have been successfully uploaded

Scanning the host completed

Start installing patches

Installing patches on 192.168.61.48 , deb_vmware-esx-firmware_4.0.0-1.9.208167, deb_vmware-esx-tools-light_4.0.0-1.9.208167, deb_vmware-esx-viclient_4.0.0-1.9.208167\n\r

Start uploading files to host

Metadata and binaries have been successfully uploaded

Tring to exit maintenace mode.

Exit maintenace mode succeeded

There was an error during installing patches on 192.168.61.48

The patch operation has failed with this error: There is an error during the operation, please refer to the logs for investigation.

0 Kudos
DSTAVERT
Immortal
Immortal

Any problems during the original install? How is ESXi installed -- separate partition on HD? USB?

Use the Unsupported Console and do a

fdisk -l

and

mount

and

ls -la

-- David -- VMware Communities Moderator
0 Kudos
pkolmann
Contributor
Contributor

I have never so far seen any issues with the hosts (I got 4 boxes). Install went without issues.

fdisk -l is quite long. I have attached as file.

~ # mount

none on /dev type devfs (defaults,rw,suid,dev,exec,async,atime,diratime,loud)

none on /proc type procfs (defaults)

none on /vmfs/volumes type vcfs (defaults)

none on /tmp type visorfs (2,192,01777,tmp)

visorfs on /var/lib/vmware/hostd/stats type visorfs (253,253,0755,hostdstats)

~ # ls -la

drwxr-xr-x 1 root root 512 Dec 17 13:42 .

drwxr-xr-x 1 root root 512 Dec 17 13:42 ..

-rw-rr 1 root root 0 May 1 2009 .emptytgz

drwxr-xr-x 1 root root 512 Dec 16 15:33 .vmware

l----


0 root root 1984 Jan 1 1970 altbootbank -> /vmfs/volumes/bd26157f-b9ffb834-220d-c6fdb50a9941

drwxr-xr-x 1 root root 512 Dec 16 14:48 bin

l----


0 root root 1984 Jan 1 1970 bootbank -> /vmfs/volumes/4ead1778-4ed1256b-5fe8-d324249b633b

drwxr-xr-x 1 root root 512 Dec 17 13:43 dev

drwxr-xr-x 1 root root 512 Dec 16 15:31 esx4-upgrade

drwxr-xr-x 1 root root 512 Dec 17 12:53 etc

-rw-rr 1 root root 6579 Dec 17 13:42 fdisk.txt

drwxr-xr-x 1 root root 512 Dec 16 14:48 lib

-rw-rr 1 root root 12832 Dec 16 13:53 local.tgz

l----


0 root root 1984 Jan 1 1970 locker -> /store

drwxr-xr-x 1 root root 512 Nov 8 08:51 opt

drwxr-xr-x 1 root root 131072 Dec 17 13:43 proc

l----


0 root root 1984 Jan 1 1970 productLocker -> /locker/packages/4.0.0/

drwxr-xr-x 1 root root 512 Dec 16 14:48 sbin

l----


0 root root 1984 Jan 1 1970 scratch -> /vmfs/volumes/4a544c52-21f19795-1af3-00144fede9e9

l----


0 root root 1984 Jan 1 1970 store -> /vmfs/volumes/efd8efe3-03bc1cbf-15e0-080efd9e7379

drwxrwxrwt 1 root root 512 Dec 17 13:34 tmp

drwxr-xr-x 1 root root 512 Dec 16 14:48 usr

drwxr-xr-x 1 root root 512 Dec 16 14:48 var

drwxr-xr-x 1 root root 512 Dec 16 14:48 vmfs

drwxr-xr-x 1 root root 512 Dec 16 14:48 vmimages

l----


0 root root 1984 Jan 1 1970 vmupgrade -> /locker/vmupgrade/

~ #

Hope you can help me solve this issue.If nothing helps, I need to reinstall the boxes with U1 Smiley Sad

0 Kudos
pkolmann
Contributor
Contributor

We upgraded the vSphere Client to the one released with ESi 4.0.0 Update 1 (rev. 208167) and now the update works.

Don't ask me why, very strange.

Philipp

0 Kudos
DSTAVERT
Immortal
Immortal

Glad all is well. Sorry I didn't see your updated post. If no one responds to your post just give it a bump to bring it back to the front.

-- David -- VMware Communities Moderator
0 Kudos