VMware Communities: Message List - ESX 3.0 extend issue

Re: ESX 3.0 extend issue

KidE — Fri, 12 May 2006 05:13:05 GMT

ehh nope because this ha snothing todo with my problem

Re: ESX 3.0 extend issue

kertofer — Wed, 10 May 2006 18:05:08 GMT

ESX3.0 uses RHEL 3.0 for the Service Console OS. Remember that there are basically 2 operating systems running at the same time. There is RHEL 3 for the Service Console and then there is the ESX kernel, which is a proprietary OS kernel that is running to support the VM's. The Service Console is there to support and manage the ESX kernel so that you do not directly access it.

Hope this helps!

Re: ESX 3.0 extend issue

KidE — Wed, 10 May 2006 07:28:09 GMT

The filesystem/disk cannot be in use because i fresh installed it and there is nothing running on it.
i'm not trying to extend a vmfs but create a new one.

@SV: are you sure about the linux thing? since i red that 3.0 is completely base on RHEL 3

Re: ESX 3.0 extend issue

SV — Mon, 08 May 2006 15:16:53 GMT

Since ESX is not Linux, Linux fundamentals do not apply directly to this OS. CHogan is most probably right - the partition you are trying to extend your VMFS with, seems to be in use by the Service Console or by a VM. If you are using vmkfstools, make sure you are not supplying vmhbaX:Y:Z:0 as the device to be extended with. "0" corresponds to the entire disk, and the Service Console might have the disk open in case you have Service Console partitions on it.

Re: ESX 3.0 extend issue

KidE — Mon, 08 May 2006 07:27:16 GMT

Nope because then i would get a different kind of error as i know from my linux background. The strange thing is if i try to kickstart this machine with 2.5.x it also has a problem with creating filesystems so it could be that the driver is the problem. Today i gonnan rebuild the raid config and gonna see if that helps out

Re: ESX 3.0 extend issue

CHogan — Sun, 07 May 2006 22:59:11 GMT

The message suggests that something else has the disk open. You didn't happen to have an fdisk session running on the disk at the same time that you were trying to create the VMFS volume?

Re: ESX 3.0 extend issue

KidE — Fri, 05 May 2006 08:32:01 GMT

Well i cant find it anymore in the logfiles but it looks familiair.

i do get some errors like :
May 4 15:18:57 pinky vmkernel: 0:01:16:28.168 cpu2:1033)WARNING: SCSI: 5647: Can't write through read-only handle 0x533
May 4 15:18:57 pinky vmkernel: 0:01:16:28.168 cpu2:1033)WARNING: SCSI: 5524: status 0xbad0021, rstatus 0xc0de00 for vmhba2:0:0. residual R 999, CR 81, ER 3

I'm thinking we're having a driver compatibility issue here.

Re: ESX 3.0 extend issue

CHogan — Thu, 04 May 2006 13:52:02 GMT

Ernst,

I'm not sure you can do this. Do you observe the following message in the vmkernel log file?

"Modification of active partition vmhbaX:X:X:X is not supported"

Re: ESX 3.0 extend issue

jgswinkels — Thu, 04 May 2006 13:47:41 GMT

Local disks

Re: ESX 3.0 extend issue

boydd — Thu, 04 May 2006 13:45:16 GMT

Local or SAN Disk?

DB

Re: ESX 3.0 extend issue

KidE — Thu, 04 May 2006 13:36:28 GMT

ehh oops. sorry for that. but problem is still here

Re: ESX 3.0 extend issue

Paul.B — Thu, 04 May 2006 12:42:11 GMT

You'd probably be better off asking in the Beta forum.. Just an FYI.

ESX 3.0 extend issue

KidE — Thu, 04 May 2006 12:40:21 GMT

Hi,

We're installing esx 3.0 and want to add a new local vmfs3 extend. If we do that we get the error "cant read partition table". After that i see that a new partition is been created but that no vmfs3 filesystem is created and also no vmhba2.0.0.x instance is made.

Anybody any suggestions?

P.S. we're runnign on a Dell Poweredge 6450

Gr,

Ernst