VMware Cloud Community
adamelg
Contributor
Contributor
Jump to solution

After migration from ESXi 4.1 to 5.0 update 1, ESXi containing datastore missing

I'm planning on upgrading a production ESXi 4.1 host, but I wanted to run through a test upgrade on a separate machine. I set this up through a VM and the upgrade went smoothly. However, now when I load up my vSphere client, I can only see the datastore containing my VM data.

Before migrating to 5, I had 2 disks setup, a 4 GB disk for ESXi and a 40 GB disk for the VM data. I could see and access both stores via the vSphere client in 4.1 but after the upgrade only the VM data store is available. Is there any reason this is the case?

I upgraded but did not modify the datastore partitions. I selected the migrate and preserve VMFS store, which was VMFS-3. I also tried re-adding the datastore of the 4GB disk with the client, but receive an error: "Either the selected disk already has a vmfs datastore or the host cannot perform a partition table conversion.
Select another disk."

I found this article related to the error message: http://kb.vmware.com/kb/2000454, but I never actually deleted the datastore. Using the upgraded ESXi 5.0 I can see the VMFS store on the 4 GB disk, which should have about 3.2 GB of space available (the rest being used by the hypervisor).

Another user recommended trying esxconfig-volume --list and then use the output of that to do a mount (http://communities.vmware.com/message/1666168#1666168), but the list command had no output at all.

I searched through these forums and Google but haven't seen anything.

Reply
0 Kudos
1 Solution

Accepted Solutions
Samcer
Expert
Expert
Jump to solution

ESXi 5 has a different architecture and I think the problem regards the disk size (too small) and the required scratch partition.

Have a look here:

HTH

Sam

samcer| http://about.me/samcer | http://www.vm-support.it/ | @samuelecerutti

View solution in original post

Reply
0 Kudos
2 Replies
Samcer
Expert
Expert
Jump to solution

ESXi 5 has a different architecture and I think the problem regards the disk size (too small) and the required scratch partition.

Have a look here:

HTH

Sam

samcer| http://about.me/samcer | http://www.vm-support.it/ | @samuelecerutti
Reply
0 Kudos
adamelg
Contributor
Contributor
Jump to solution

Grazie Samcer! You were right, the disk was too small. I tried the same upgrade again with a 20 GB disk and both datastores showed up.

I looked over those documents and see that an ESXi 5.0 install would require a larger disk (5.2 GB) than I had provisioned because of the scratch partition. This makes sense because useable space on the 1st datastore from the 1st disk is 15GB, so it seems the installation takes around 5 GB.

Thanks for your help.

Reply
0 Kudos