Error: The partition table on /vmfs/devices/disks/vmhba1:0:0:0 is inconsistent

[aboland]

Hello, I have a problem with my ESX 3.5, I'm using ServeRAID 8k, with 6 disks on RAID 5, the log file shows:

2008-01-14 09:53:22.391 'Partitionsvc' 3076445088 info InvokePartedUtil /sbin/partedUtil

2008-01-14 09:53:22.518 'Partitionsvc' 3076445088 warning Unable to get partition information for /vmfs/devices/disks/vmhba1:0:0:0

2008-01-14 09:53:22.518 'Partitionsvc' 3076445088 warning Status : 255

Output:

Error : Error: The partition table on /vmfs/devices/disks/vmhba1:0:0:0 is inconsistent. There are many reasons why this might be the ca

se. However, the most likely reason is that Linux detected the BIOS geometry for /vmfs/devices/disks/vmhba1:0:0:0 incorrectly. GNU Part

ed suspects the real geometry should be 283638/64/32 (not 36158/255/63). You should check with your BIOS first, as this may not be corre

ct. You can inform Linux by adding the parameter /devices/disks/vmhba1:0:0:0=283638,64,32 to the command line. See the LILO or GRUB doc

umentation for more information. If you think Parted's suggested geometry is correct, you may select Ignore to continue (and fix Linux l

ater). Otherwise, select Cancel (and fix Linux and/or the BIOS now).

Error: Can't have a partition outside the disk!

Unable to read partition table for device /vmfs/devices/disks/vmhba1:0:0:0

the partitions are :

/vmfs/devices/disks> vdf -h

Filesystem Size Used Avail Use% Mounted on

/dev/sda2 4.9G 2.9G 1.7G 63% /

/dev/sda1 97M 26M 67M 28% /boot

none 132M 0 132M 0% /dev/shm

/dev/sda6 2.0G 37M 1.8G 2% /var/log

/vmfs/devices 4.3T 0 4.3T 0% /vmfs/devices

/vmfs/volumes/47629ba9-f8e410a6-1ac3-001a64635138

2.0T 1.2T 782G 61% /vmfs/volumes/storage1

the problem is that in some few hours the following error appears:

cpu0:1024)VMNIX: <0>scsi: device set offline - command error recovery failed: host 1 channel 0 id 0 lun 0

cpu0:1024)VMNIX: <0>journal commit I/O error

and I lose the control of vmware (but the VM continue running)

see this: http://communities.vmware.com/message/839524

[cforger]

I'm having the same problems. I'm just begining to research what it is.

I'm using an Adaptec 1210SA SATA RAID controller to run SATA drives as the main device. I haven' had it up long enough to get a datastore created, so it's nothing to do with that.

Interestingly, the same machine ran ESX 3.0 fine, using a PERC Raid controller for the datastore (but the same Adaptec card for boot/console).

I don't have any bad sectors or drive problems. New drives, and every sector was tested.

If anyone has any hints, let me know, or I'll post back later with what I've found.

[cforger]

Well, for further testing, I loaded up ESX 3i 3.5, and I've had no problems at all. It looks to be the service console that is causing the faults in ESX 3.5 for me. I'll have to dig a bit deeper.

[dufflepod]

I'm running 3i 3.5 and I just noticed the same problem. It happened when I brought the server back out of maintanence mode. It seems to be running fine. I was trying to fix an HA problem. I'm not sure how to diagnose it any further without a service console. I am using HP Blade Servers with 2 mirrored local disks.

2008-04-11 09:11:55 Local4.Info 192.168.1.1 Hostd:

2008-04-11 09:11:55 Local4.Info 192.168.1.1 Hostd: InvokePartedUtil /sbin/partedUtil

2008-04-11 09:11:56 Local4.Info 192.168.1.1 Hostd: Error Stream from partedUtil while getting partitions: Error: The partition table on /dev/disks/vmhba0:0:0:0 is inconsistent. There are many reasons why this might be the case. However, the most likely reason is that Linux detected the BIOS geometry for /dev/disks/vmhba0:0:0:0 incorrectly. GNU Parted suspects the real geometry should be 139979/64/32 (not 17844/255/63). You should check with your BIOS first, as this may not be correct. You can inform Linux by adding the parameter disks/vmhba0:0:0:0=139979,64,3

2008-04-11 09:11:56 User.Notice 192.168.1.1 2 to the command line. See the LILO or GRUB documentation for more information. If you think Parted's suggested geometry is correct, you may select Ignore to continue (and fix Linux later). Otherwise, select Cancel (and fix Linux and/or the BIOS now). Geometry Known: 0

[hb]

Anyone have a solution to this problem?

I have talked with VMWare support, and the only solution they pointed out is that I have a problem with my hard drives.

My setup is a IBM HS21 blade with 2 local SAS discs.

The problem only occurs in ESXi 3.5

/henrik

[s1m0nb]

dont know if this helps at all (probably not) but here is my similar experience..

Had 3.5 running - no issues --

decided to blow it away and play with esx3i -- no issues --

decided to go back to 3.5 U2 - and got the same error as you during the initial installation (on the local disks). Luckily I had the ability to just blow away the raid array and restart the install - no problems since then.

for info -- its a HP dl585 with the p400 raid controller

[ScottChapman]

So, I am seeing this same problem with ESXi 3.5 U3.

Has anyone figured out what the fix is? I know the disk is OK, I have scanned it with several tools and believe that is not the problem.

[smcclos]

I found a solution to this one: My problem is that I Upgraded my ESX 3i from U3 to U4 last night and I lost 1 out of my 3 datastores. I am running 1 73GB SCSI for boot, and 2 400GB stat for datastore. One of the 400 GB sata drives did not come back up with the same error

KB article 9453805 Fixed the problem:

I had to re-add all of my VMs, and answer the GUID question, but it was fine.

[Texiwill]

Hello,

Is vmhba1:0:0:0 a VMFS or an ext3 partition. If it is the later you can run fsck on it . If it is a VMFS... You may need to rebuild the partition table, if so check out http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1347841,00.html?track=sy840

Best regards,
Edward L. Haletky
VMware Communities User Moderator, VMware vExpert 2009
====
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.
Blue Gears and SearchVMware Pro Blogs -- Top Virtualization Security Links -- Virtualization Security Round Table Podcast

[smcclos]

I didn't think those types of commands would work with ESX 3i since it is so much of the OS is locked down?

[Texiwill]

Hello,

They will not on ESX3i but the OP was concerned about ESX v3.5.

Best regards,
Edward L. Haletky
VMware Communities User Moderator, VMware vExpert 2009
====
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.
Blue Gears and SearchVMware Pro Blogs -- Top Virtualization Security Links -- Virtualization Security Round Table Podcast