<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Gretech.be &#187; ESXi 3.5</title>
	<atom:link href="http://gretech.be/blog/index.php/tag/esxi-3-5/feed/" rel="self" type="application/rss+xml" />
	<link>http://gretech.be/blog</link>
	<description>Just another WordPress weblog...</description>
	<lastBuildDate>Sat, 20 Nov 2010 16:58:03 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Updating ESX 3.5 to 4.0: PANIC: Failed to find HD boot partition</title>
		<link>http://gretech.be/blog/index.php/2010/04/06/updating-esx-3-5-to-4-0-panic-failed-to-find-hd-boot-partition/</link>
		<comments>http://gretech.be/blog/index.php/2010/04/06/updating-esx-3-5-to-4-0-panic-failed-to-find-hd-boot-partition/#comments</comments>
		<pubDate>Tue, 06 Apr 2010 22:08:27 +0000</pubDate>
		<dc:creator>GregoryBE</dc:creator>
				<category><![CDATA[Network]]></category>
		<category><![CDATA[ESXi 3.5]]></category>
		<category><![CDATA[Failed to find HD boot partition]]></category>
		<category><![CDATA[upgrade esx]]></category>

		<guid isPermaLink="false">http://gretech.be/blog/?p=54</guid>
		<description><![CDATA[In September I successfully updated a ESXi 3.5 host to ESXi 4.0. A week ago I needed to upgrade another server, so I thought no need backing up de VM's this time before doing the upgrade. Of course, with no backup the upgrade failed, the ESXi server rebooted after performing the upgrade with vSphere and [...]]]></description>
			<content:encoded><![CDATA[<p>In September I successfully updated a ESXi 3.5 host to ESXi 4.0.<br />
A week ago I needed to upgrade another server,<br />
so I thought no need backing up de VM's this time before doing the upgrade.<br />
Of course, with no backup the upgrade failed, the ESXi server rebooted after performing the upgrade with vSphere and came up with the following message:</p>
<p><strong>PANIC: Failed to find HD boot partition.</strong></p>
<p>Before trying the repair wizard on the ESXi 3.5 CD, I backup-ed all VM's to another machine over the network using an <strong>Ubuntu Live CD</strong>, how to mount the VMFS store:</p>
<ul>
<li>In the software sources, enable the Universe library and reload the packages</li>
<li>Open a terminal: <em>su</em></li>
<li><em>apt-get install vmfs-tools</em></li>
<li><em>mkdir /vmdir/</em></li>
<li><em>vmfs-fuse /vmdir/ /dev/sda3</em> (look up your sda, in gparted f.e.)</li>
</ul>
<p>Also useful to know to fasten the backup:<br />
- Mounting a Samba share to a dir:<br />
<em>apt-get install smbfs<br />
sudo mount -t smbfs -o username=usernamePC,password=ShareAccessPassword,workgroup=MSHOME,gid=smb,uid=$USER,fmask=770,dmask=770,rw "//DEVMACHINE/Share with Spaces" /createdDir</em></p>
<p>So, after creating a backup, I tried the ESX 3.5 repair wizard, wich is useless, it re-installs ESX and leaves the VMFS store unallocated.</p>
<p>I then just installed ESXi 4 (that formats the full disk)</p>
<p><span style="text-decoration: underline;">Second problem</span>: I started VSphere update client, when scanning for updates I get:</p>
<p><strong>The scan operation has failed... Check the logs</strong>.</p>
<p>The problem wasn't very known on the internet, so I just reinstalled a second time. Surprisingly the problem disappeared and updates where installed correctly.</p>
<p>Then I just installed VMware converter on the backup PC to re-import the VM's to the ESXi  server in the new VMware 7 format.</p>
]]></content:encoded>
			<wfw:commentRss>http://gretech.be/blog/index.php/2010/04/06/updating-esx-3-5-to-4-0-panic-failed-to-find-hd-boot-partition/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->