Hello mpxipix,

unfortunatly your workarround to get the script working doens't work with me.

The workarrund for itself works. But when i execute the script for the ml115 (which i have) the same errors like "command not found" or "directory not found" come up again.

Its strange because other people with the same hardware say that it works.

I hope that somebody knows what I can try anymore...

Regards

Hm, I'm not positive, but I was looking through the script and it seems that "umount $BOOT_PREFIX" and "umount $ROOT_PREFIX" are commented out. So I was hesitant to run it because as written, the script may wipe your ESX install ... I'll leave it to someone else to verify

Hi,

many thanks for the hint!

Tried it and yes you were right. Cleaned up my / and /boot.

Commented out these two lines (rm -r -f ...) so you have to delete these subdirs manually, leave them or change the script.
Fortunately i have kickstart in place for my devel server, so if it crashes it does no harm...

thanks again,
Reinhard.

ps: Award points if you find answers helpful. Thanks.

I have the ASUS P5BV-E / SAS motherboard, which as anyone who has read up on SAS/SATA support knows, works great with VMware ESX v3.5. But, what has me scratching my head is that 3.5 installs, allows me to create a VMFS and deploy VMs even though I only have 1 SATA drive connected to the ICH7R controller (I'm not even using the SAS controller!). In the dmesg output below, you can see that the SAS controller is scsi5 and has no devices attached. While scsi4 is my AHCI Intel controller with a lone disk attached. Am I the only one that did not expect this to work? Does this mean that any ICH7R board w/ a support NIC will run ESX? That would let you pick up $80 motherboards and run ESX.

scsi4 : ahci
Vendor: ATA Model: ST380013AS Rev: 3.43
Type: Direct-Access ANSI SCSI revision: 05
VMWARE SCSI Id: Supported VPD pages for sda : 0x0 0x80 0x83
VMWARE SCSI Id: Device id info for sda: 0x2 0x0 0x0 0x18 0x4c 0x69 0x6e 0x75 0x7
8 0x20 0x41 0x54 0x41 0x2d 0x53 0x43 0x53 0x49 0x20 0x73 0x69 0x6d 0x75 0x6c 0x6
1 0x74 0x6f 0x72
VMWARE SCSI Id: Id for sda 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x2
0 0x20 0x34 0x4d 0x52 0x31 0x5a 0x41 0x37 0x42 0x53 0x54 0x33 0x38 0x30 0x30
VMWARE: Unique Device attached as scsi disk sda at scsi4, channel 0, id 0, lun 0
Attached scsi disk sda at scsi4, channel 0, id 0, lun 0
SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 >
scsi5 : mptscsi_2xx

Jaap,

I am running a Sun Ultra 40 M2, but I was not able to get it working with the onboard sata controllers. I also have a LSI1068E as my SAS/SATA controller which is a VMware supported controller. I have tried it with both SAS and SATA disks and it works fine. The LSI1068E also works in raid mode, although only supports raid 0,1 and 10.

Two things to keep in mind with the Ultra 40, one there is a multimedia timer setting in the bios that must be disabled for VMware to work. Secondly if you are running with multi processors using both sockets, you will either need to have the same amount of memory on both sockets, or turn on memory interleaving to disable NUMA. If you are only using one socket then it won't matter, but with both sockets you will need that set.

Dave

Hi Dave,

Thanks for the reply. I gave up on the U40M2 and indeed ordered the SAS controller (which did not arrive yet). I will keep your other suggestions in mind.

I also tried Ultra20M2 and it had the same "mount of root failed" problem. On this box the fix worked: boot in service console mode, changed sata_nv.xml and run esxcfg-pciid.

Thanks,

Jaap

Hi blackforce,
use v0.61. (bug fixed)

hth Reinhard.

ps: Award points if you find answers helpful. Thanks.