The-Kevster
Contributor
Contributor

SATA Support Clear as Mud!?

From the updated I/O sheet this is what's mentioned on supported SATA controllers....

Supported SAS/SATA Dual Controllers

ESX Server 3.5 supports selected SATA devices connected to dual SAS/SATA controllers. This support is limited to ESX Server 3.5. It is not included with ESX Server 3.0.x.

The supported dual SAS/SATA controllers are:

  • mptscsi_2xx (PCIE) ‐ LSI1078*

  • mptscsi_pcie ‐ LSI1068E (LSISAS3442E)*

  • mptscsi_pcix ‐ LSI1068 (SAS 5)*

  • aacraid_esx30 ‐ IBM serveraid 8k SAS controller*

  • cciss ‐ Smart Array P400/256 controller*

So what is the best PCIE card for me to put into my S5000PAL server that will use the above driver, if only someone could make a list :smileygrin:

Thanks,

Kev

0 Kudos
342 Replies
sshd_root
Contributor
Contributor

When start in normal mode I get this error :

Mounting root failed. Dropping into maintenance shell

......

BusyBox v0.60.5 Built-in shell

......

sh: can`t acceess tty; job control turned off

#

In troubleshooting mode:

# mount

/dev/sda2 on / type ext3 (rw)

none on /proc type proc (rw)

none on /dev/pts type devpts (rw,gid=5,mode=620)

usbdevfs on /proc/bus/usb type usbdevfs (rw)

/dev/sda1 on /boot type ext3 (rw)

none on /dev/shm type tmpfs (rw)

/dev/sda6 on /var/log type ext3 (rw)

0 Kudos
wildblue
Contributor
Contributor

Can anyone suggest a working PCIe controller with external connections? All I'm seeing here and on vm-help.com is internal.

0 Kudos
jtkv
Contributor
Contributor

I have 2 additons to the whitebox list:

Tested using VMWare ESX 3.5

Desktop

~~~~~~~~

Compaq Evo D510 CMT

P4 2.4Ghz

2.0 GB RAM

NIC: Intel 82801DB Pro/100

ESX O/S installs off the local IDE CD-ROM unto the local IDE disk

Used iSCSI target (Open-e DSS Lite) to create VMFS datastore and VMs

Motherboard

~~~~~~~~~~~

Intel D865GBF desktop board

P4 2.80Ghz (Hyper-Threading)

1.75 GB RAM

NIC: Intel 82801EB (ICH5) PRO/100 VE

On installation from IDE CD-ROM, the local SATA disk is recognized as /dev/sda

Installer is able to create boot partitions, as well as a VMFS store

ESX O/S reboots off local SATA disk properly, and can create VMs on the local VMFS store

iSCSI

~~~~~

iSCSI works sucessfully using the free DSS Lite target software from Open-E

http://www.open-e.com/

0 Kudos
devzero
Expert
Expert

FYI .... For my Test environment I used the ASUS KFN4-D16SAS.

>There is an LSI 1068 onboard. It worked with 3.0.2 and the noapic

>boot option. I'll try it with 3.5 asap and post if it works.

divintas , any news on this?

i`m interested in this board, but the need for noapic option frightens me.

does 3.5 work well with this?

0 Kudos
divintas
Enthusiast
Enthusiast

I am sorry that it tooks that long since my last entry.

The board works like charm. I run 1 week 3.0.2 on it with no problem and then updatet to 3.5. And with 3.5 its running perfect aswell.

Regards,

divin

0 Kudos
devzero
Expert
Expert

thank you !

one last question - does 3.5 still need "noapic" ?

0 Kudos
mikelane
Expert
Expert

I must admit that even having this thread things are not 100% clear to me ...

I have a motherboard with the NVidia Chipset (6100 / 430) so I have installed ESX 3.5 fine to a old IDE drive (which I thought would simplify the process of installing). I have Intel Pro 1000 MT for networking.

I can't figure out how to get any storage configured in ESX though - I have a SATA drive connected directly to the motherboard and during setup I thought that ESX was formatting both the remainder of the IDE and the entire SATA drive as VMFS.

Do I still have to do the whole Live CD thing mentioned earlier in the thread or is this a question of just mounting my SATA drive somehow is ESX?

Previously I read somewhere that SATA could only be used to install ESX and SATA was not supported for VMFS - yet it appears that people do have VMFS on SATA here ...

0 Kudos

Previously I read somewhere that SATA could only be used to install ESX and SATA was not supported for VMFS - yet it appears that people do have VMFS on SATA here ...

It used to be the case that SATA controllers were not supported at all. With 3.5, a number of dual SAS/SATA controllers are supported - http://www.vmware.com/pdf/vi35_io_guide.pdf - but ESX is able to recognize a number a SATA controllers which work fine for both the install of ESX and for VMFS.

If you go to Configuration \ Storage I would take it that you don't see your VMFS datastore or the SATA controller? If that's the case, you can take a look at these steps - http://www.vm-help.com/esx/esx3.5/SATA_mounting_root_failed.html. It's likely that the install was able to recognize the SATA controller, but the vmkernel can't. In that case you'll just have to modify the PCI ID database files. You can also do that with the steps listed in this thread. Basically you'll want to want to run lspic at the console and see if the vmkernel has recognized the specific SATA controller that your PC has.

0 Kudos
devzero
Expert
Expert

i dug in the mud a little bit and this is what i found so far:

  • ahci.c - AHCI SATA support

{ PCI_VENDOR_ID_INTEL, 0x2652, PCI_ANY_ID, PCI_ANY_ID, 0, 0,

board_ahci }, /* ICH6 */

{ PCI_VENDOR_ID_INTEL, 0x2653, PCI_ANY_ID, PCI_ANY_ID, 0, 0,

board_ahci }, /* ICH6M */

{ PCI_VENDOR_ID_INTEL, 0x27c1, PCI_ANY_ID, PCI_ANY_ID, 0, 0,

board_ahci }, /* ICH7 */

{ PCI_VENDOR_ID_INTEL, 0x27c5, PCI_ANY_ID, PCI_ANY_ID, 0, 0,

board_ahci }, /* ICH7M */

{ PCI_VENDOR_ID_INTEL, 0x27c3, PCI_ANY_ID, PCI_ANY_ID, 0, 0,

board_ahci }, /* ICH7R */

{ PCI_VENDOR_ID_AL, 0x5288, PCI_ANY_ID, PCI_ANY_ID, 0, 0,

board_ahci }, /* ULi M5288 */

{ PCI_VENDOR_ID_INTEL, 0x2681, PCI_ANY_ID, PCI_ANY_ID, 0, 0,

board_ahci }, /* ESB2 */

{ PCI_VENDOR_ID_INTEL, 0x2682, PCI_ANY_ID, PCI_ANY_ID, 0, 0,

board_ahci }, /* ESB2 */

{ PCI_VENDOR_ID_INTEL, 0x2683, PCI_ANY_ID, PCI_ANY_ID, 0, 0,

board_ahci }, /* ESB2 */

{ PCI_VENDOR_ID_INTEL, 0x27c6, PCI_ANY_ID, PCI_ANY_ID, 0, 0,

board_ahci }, /* ICH7-M DH */

  • ata_piix.c - Intel PATA/SATA controllers

{ 0x8086, 0x7111, PCI_ANY_ID, PCI_ANY_ID, 0, 0, piix4_pata },

{ 0x8086, 0x24db, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich5_pata },

{ 0x8086, 0x25a2, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich5_pata },

#endif

/* NOTE: The following PCI ids must be kept in sync with the

  • list in drivers/pci/quirks.c.

*/

{ 0x8086, 0x24d1, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich5_sata },

{ 0x8086, 0x24df, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich5_sata },

{ 0x8086, 0x25a3, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich5_sata },

{ 0x8086, 0x25b0, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich5_sata },

{ 0x8086, 0x2651, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich6_sata },

{ 0x8086, 0x2652, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich6_sata_rm },

{ 0x8086, 0x2653, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich6_sata_rm },

{ 0x8086, 0x27c0, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich7_sata },

{ 0x8086, 0x27c4, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich7_sata },

{ 0x8086, 0x2680, PCI_ANY_ID, PCI_ANY_ID, 0, 0, esb2_sata },

/* Mobile SATA Controller IDE (ICH8M) */

{ 0x8086, 0x2828, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich8_sata_ahci },

/* SATA Controller IDE (ICH9) */

{ 0x8086, 0x2920, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich8_sata_ahci },

/* SATA Controller IDE (ICH9) */

{ 0x8086, 0x2921, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich8_sata_ahci },

/* SATA Controller IDE (ICH9) */

{ 0x8086, 0x2926, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich8_sata_ahci },

/* SATA Controller IDE (ICH9M) */

{ 0x8086, 0x2928, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich8_sata_ahci },

/* SATA Controller IDE (ICH9M) */

{ 0x8086, 0x292d, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich8_sata_ahci },

/* SATA Controller IDE (ICH9M) */

{ 0x8086, 0x292e, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich8_sata_ahci },

  • sata_nv.c - NVIDIA nForce SATA

{ PCI_VENDOR_ID_NVIDIA, PCI_DEVICE_ID_NVIDIA_NFORCE2S_SATA,

PCI_ANY_ID, PCI_ANY_ID, 0, 0, NFORCE2 },

{ PCI_VENDOR_ID_NVIDIA, PCI_DEVICE_ID_NVIDIA_NFORCE3S_SATA,

PCI_ANY_ID, PCI_ANY_ID, 0, 0, NFORCE3 },

{ PCI_VENDOR_ID_NVIDIA, PCI_DEVICE_ID_NVIDIA_NFORCE3S_SATA2,

PCI_ANY_ID, PCI_ANY_ID, 0, 0, NFORCE3 },

{ PCI_VENDOR_ID_NVIDIA, PCI_DEVICE_ID_NVIDIA_NFORCE_CK804_SATA,

PCI_ANY_ID, PCI_ANY_ID, 0, 0, CK804 },

{ PCI_VENDOR_ID_NVIDIA, PCI_DEVICE_ID_NVIDIA_NFORCE_CK804_SATA2,

PCI_ANY_ID, PCI_ANY_ID, 0, 0, CK804 },

{ PCI_VENDOR_ID_NVIDIA, PCI_DEVICE_ID_NVIDIA_NFORCE_MCP04_SATA,

PCI_ANY_ID, PCI_ANY_ID, 0, 0, CK804 },

{ PCI_VENDOR_ID_NVIDIA, PCI_DEVICE_ID_NVIDIA_NFORCE_MCP04_SATA2,

PCI_ANY_ID, PCI_ANY_ID, 0, 0, CK804 },

{ PCI_VENDOR_ID_NVIDIA, PCI_DEVICE_ID_NVIDIA_NFORCE_MCP51_SATA,

PCI_ANY_ID, PCI_ANY_ID, 0, 0, GENERIC },

{ PCI_VENDOR_ID_NVIDIA, PCI_DEVICE_ID_NVIDIA_NFORCE_MCP51_SATA2,

PCI_ANY_ID, PCI_ANY_ID, 0, 0, GENERIC },

{ PCI_VENDOR_ID_NVIDIA, PCI_DEVICE_ID_NVIDIA_NFORCE_MCP55_SATA,

PCI_ANY_ID, PCI_ANY_ID, 0, 0, GENERIC },

{ PCI_VENDOR_ID_NVIDIA, PCI_DEVICE_ID_NVIDIA_NFORCE_MCP55_SATA2,

PCI_ANY_ID, PCI_ANY_ID, 0, 0, GENERIC },

{ PCI_VENDOR_ID_NVIDIA, PCI_ANY_ID,

PCI_ANY_ID, PCI_ANY_ID,

PCI_CLASS_STORAGE_IDE<<8, 0xffff00, GENERIC },

{ PCI_VENDOR_ID_NVIDIA, PCI_ANY_ID,

PCI_ANY_ID, PCI_ANY_ID,

PCI_CLASS_STORAGE_RAID<<8, 0xffff00, GENERIC },

  • sata_promise.c - Promise SATA

{ PCI_VENDOR_ID_PROMISE, 0x3371, PCI_ANY_ID, PCI_ANY_ID, 0, 0,

board_2037x },

{ PCI_VENDOR_ID_PROMISE, 0x3570, PCI_ANY_ID, PCI_ANY_ID, 0, 0,

board_2037x },

{ PCI_VENDOR_ID_PROMISE, 0x3571, PCI_ANY_ID, PCI_ANY_ID, 0, 0,

board_2037x },

{ PCI_VENDOR_ID_PROMISE, 0x3373, PCI_ANY_ID, PCI_ANY_ID, 0, 0,

board_2037x },

{ PCI_VENDOR_ID_PROMISE, 0x3375, PCI_ANY_ID, PCI_ANY_ID, 0, 0,

board_2037x },

{ PCI_VENDOR_ID_PROMISE, 0x3376, PCI_ANY_ID, PCI_ANY_ID, 0, 0,

board_2037x },

{ PCI_VENDOR_ID_PROMISE, 0x3574, PCI_ANY_ID, PCI_ANY_ID, 0, 0,

board_2037x },

{ PCI_VENDOR_ID_PROMISE, 0x3d75, PCI_ANY_ID, PCI_ANY_ID, 0, 0,

board_2037x },

{ PCI_VENDOR_ID_PROMISE, 0x3d73, PCI_ANY_ID, PCI_ANY_ID, 0, 0,

board_2037x },

{ PCI_VENDOR_ID_PROMISE, 0x3318, PCI_ANY_ID, PCI_ANY_ID, 0, 0,

board_20319 },

{ PCI_VENDOR_ID_PROMISE, 0x3319, PCI_ANY_ID, PCI_ANY_ID, 0, 0,

board_20319 },

{ PCI_VENDOR_ID_PROMISE, 0x3519, PCI_ANY_ID, PCI_ANY_ID, 0, 0,

board_20319 },

{ PCI_VENDOR_ID_PROMISE, 0x3d17, PCI_ANY_ID, PCI_ANY_ID, 0, 0,

board_20319 },

{ PCI_VENDOR_ID_PROMISE, 0x3d18, PCI_ANY_ID, PCI_ANY_ID, 0, 0,

board_20319 },

{ PCI_VENDOR_ID_PROMISE, 0x6629, PCI_ANY_ID, PCI_ANY_ID, 0, 0,

board_20619 },

  • sata_sil.c - Silicon Image SATA

{ 0x1095, 0x3112, PCI_ANY_ID, PCI_ANY_ID, 0, 0, sil_3112_m15w },

{ 0x1095, 0x0240, PCI_ANY_ID, PCI_ANY_ID, 0, 0, sil_3112_m15w },

{ 0x1095, 0x3512, PCI_ANY_ID, PCI_ANY_ID, 0, 0, sil_3112 },

{ 0x1095, 0x3114, PCI_ANY_ID, PCI_ANY_ID, 0, 0, sil_3114 },

{ 0x1002, 0x436e, PCI_ANY_ID, PCI_ANY_ID, 0, 0, sil_3112_m15w },

{ 0x1002, 0x4379, PCI_ANY_ID, PCI_ANY_ID, 0, 0, sil_3112_m15w },

{ 0x1002, 0x437a, PCI_ANY_ID, PCI_ANY_ID, 0, 0, sil_3112_m15w },

  • sata_svw.c - ServerWorks / Apple K2 SATA

/* 0x240 is device ID for Apple K2 device

  • 0x241 is device ID for Serverworks Frodo4

  • 0x242 is device ID for Serverworks Frodo8

  • 0x24a is device ID for BCM5785 (aka HT1000) HT southbridge

  • integrated SATA controller

  • 0x24b is device ID for BCM5785 (aka HT1000) HT southbridge

  • integrated PATA/IDE controller

  • */

static const struct pci_device_id k2_sata_pci_tbl[] = {

{ 0x1166, 0x0240, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 4 },

{ 0x1166, 0x0241, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 4 },

{ 0x1166, 0x0242, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 8 },

{ 0x1166, 0x024a, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 4 },

{ 0x1166, 0x024b, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 4 },

{ }

};

  • sata_vsc.c - Vitesse VSC7174 4 port DPA SATA

/*

  • 0x1725/0x7174 is the Vitesse VSC-7174

  • 0x8086/0x3200 is the Intel 31244, which is supposed to be identical

  • compatibility is untested as of yet

*/

static const struct pci_device_id vsc_sata_pci_tbl[] = {

{ 0x1725, 0x7174, PCI_ANY_ID, PCI_ANY_ID, 0x10600, 0xFFFFFF, 0 },

{ 0x8086, 0x3200, PCI_ANY_ID, PCI_ANY_ID, 0x10600, 0xFFFFFF, 0 },

{ }

};

so you can see that`s a lot of sata controllers esx vmKernel has drivers for, now. Smiley Happy

users will be happy now - some linux kernel develepors are probably not so amused.

you can read about that quite interesting controversy at:

opinions may differ here - but rip out all the modified linux drivers and we have - a hypervisor which just pines away like poor johnny from that famous metallica video from the eighties.

0 Kudos
mikelane
Expert
Expert

If you go to Configuration \ Storage I would take it that you don't see your VMFS datastore or the SATA controller? If that's the case, you can take a look at these steps -

I have followed this as best i can and I thought I had it figured out - I still cannot get this to work though:

/$ lspci

00:00.0 RAM memory: nVidia Corporation: Unknown device 03ea (rev a1)

00:01.0 ISA bridge: nVidia Corporation: Unknown device 03e0 (rev a2)

00:01.1 SMBus: nVidia Corporation: Unknown device 03eb (rev a2)

00:01.2 RAM memory: nVidia Corporation: Unknown device 03f5 (rev a2)

00:02.0 USB Controller: nVidia Corporation: Unknown device 03f1 (rev a2)

00:02.1 USB Controller: nVidia Corporation: Unknown device 03f2 (rev a2)

00:04.0 PCI bridge: nVidia Corporation: Unknown device 03f3 (rev a1)

00:06.0 IDE interface: nVidia Corporation: Unknown device 03ec (rev a2)

00:08.0 IDE interface: nVidia Corporation: Unknown device 03f6 (rev a2)

00:08.1 IDE interface: nVidia Corporation: Unknown device 03f6 (rev a2)

00:09.0 PCI bridge: nVidia Corporation: Unknown device 03e8 (rev a2)

00:0b.0 PCI bridge: nVidia Corporation: Unknown device 03e9 (rev a2)

00:0c.0 PCI bridge: nVidia Corporation: Unknown device 03e9 (rev a2)

00:0d.0 VGA compatible controller: nVidia Corporation: Unknown device 03d0 (rev a2)

00:18.0 Host bridge: Advanced Micro Devices K8 Athlon64/Opteron HyperTransport Technology Configuration

00:18.1 Host bridge: Advanced Micro Devices K8 Athlon64/Opteron Address MapK8 NorthBridge

00:18.2 Host bridge: Advanced Micro Devices K8 Athlon64/Opteron DRAM Controller

00:18.3 Host bridge: Advanced Micro Devices K8 Athlon64/Opteron Miscellaneous Control

01:08.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)

01:0a.0 Ethernet controller: Intel Corporation 8254NXX Gigabit Ethernet Controller (rev 04)

Initially I picked the following device ID: IDE interface: nVidia Corporation: Unknown device 03f6 (rev a2)

Thinking about this now I assume that 03f6 must be my IDE channel which had my IDE drive and my CD-ROM drive (hence why 03f6 is mentioned twice)?

So I went back and used this instead: 00:06.0 IDE interface: nVidia Corporation: Unknown device 03ec (rev a2)

This is what the end of my sata_nv.xml looks like:

<name>MCP55 SATA Controller</name>

</device>

<device id="03ec">

<vmware label="scsi">

<driver>sata_nv</driver>

</vmware>

The only difference that I see when I go to storage in ESX is that when I go to storage is says "Loading" now but there is still nothing to select.

Am i doing something obviously wrong here?

0 Kudos
rpartmann
Hot Shot
Hot Shot

hi,

did you execute <esxcfg-pciid> after editing the xml file?

The end of you xml file file does not look very valid.

I think it should look like this:

>8-

>8-

hth,

Reinhard






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

ps: Award points if you find answers helpful. Thanks.
0 Kudos
mikelane
Expert
Expert

hi,

did you execute &lt;esxcfg-pciid&gt; after editing the xml file?

The end of you xml file file does not look very valid.

I think it should look like this:

&gt;8-

&lt;device id="03ec"&gt;

&lt;vmware label="scsi"&gt;

&lt;driver&gt;sata_nv&lt;/driver&gt;

&lt;/vmware&gt;

&lt;name&gt;MCP55 SATA Controller&lt;/name&gt;

&lt;/device&gt;

&lt;/vendor&gt;

&lt;/pcitable&gt;

&gt;8-

hth,

Reinhard

Hi Reinhard,

Yes i did execute esxcfg-pciid after editing the xml file.

I edited the xml file again as per the above, executed esxcfg-pciid again and rebooted and now I seem to have multiple errors when I boot esx:

VMKernal module vmfs3 already loaded

Loading VMKernal module deltadisk

WARNING: couldn't read uui from /dev/sda1

WARNING: /devsda1 is not a valid Queued-VMFS3 partition. Searching for renumered partition

WARNING: Could not find partition for UUID 8e7fffe05-6080-4776-8417-76a50687bd14.

Skipping initialization...

Starting ipmi drivers: ipmi_si: Trying "kcs" at I/O port 0xca2

impi_si: Trying "smic" at I/O port 0xca2

impi_si: Trying "bt" at I/O port 0xe4

impi_si: Unable to find any system interface(s)

If any of you can help with this I would be most grateful,

0 Kudos

The 03ec device is the IDE controllor (http://hcl.xensource.com/?showall=yes&subtab=drivers&database=). You'll want to be changing the 03f6 device. In the BIOS you may also want to change the emulation mode that the SATA controller is using.

With the changes you have now, if you go to Configuration \ Storage Adapters, do you see your SATA controllers there? You will see one device for each SATA port (hence the duplicate entry for 03f6).

0 Kudos
mikelane
Expert
Expert

The 03ec device is the IDE controllor (). You'll want to be changing the 03f6 device. In the BIOS you may also want to change the emulation mode that the SATA controller is using.

With the changes you have now, if you go to Configuration \ Storage Adapters, do you see your SATA controllers there? You will see one device for each SATA port (hence the duplicate entry for 03f6).

I changed it to 03f6, esxcfg-pciid and rebooted and I still don't see anything under Configuration / Storage Adapters. I only have on SATA drive connected btw - ESX is installed on IDE drive.

0 Kudos

What are you seeing with lspci now?

0 Kudos
mikelane
Expert
Expert

What are you seeing with lspci now?

I think just the same as before:

/root$ lspci

00:00.0 RAM memory: nVidia Corporation: Unknown device 03ea (rev a1)

00:01.0 ISA bridge: nVidia Corporation: Unknown device 03e0 (rev a2)

00:01.1 SMBus: nVidia Corporation: Unknown device 03eb (rev a2)

00:01.2 RAM memory: nVidia Corporation: Unknown device 03f5 (rev a2)

00:02.0 USB Controller: nVidia Corporation: Unknown device 03f1 (rev a2)

00:02.1 USB Controller: nVidia Corporation: Unknown device 03f2 (rev a2)

00:04.0 PCI bridge: nVidia Corporation: Unknown device 03f3 (rev a1)

00:06.0 IDE interface: nVidia Corporation: Unknown device 03ec (rev a2)

00:08.0 IDE interface: nVidia Corporation: Unknown device 03f6 (rev a2)

00:08.1 IDE interface: nVidia Corporation: Unknown device 03f6 (rev a2)

00:09.0 PCI bridge: nVidia Corporation: Unknown device 03e8 (rev a2)

00:0b.0 PCI bridge: nVidia Corporation: Unknown device 03e9 (rev a2)

00:0c.0 PCI bridge: nVidia Corporation: Unknown device 03e9 (rev a2)

00:0d.0 VGA compatible controller: nVidia Corporation: Unknown device 03d0 (rev a2)

00:18.0 Host bridge: Advanced Micro Devices K8 HyperTransport Technology Configuration

00:18.1 Host bridge: Advanced Micro Devices K8 Address MapK8 NorthBridge

00:18.2 Host bridge: Advanced Micro Devices K8 DRAM Controller

00:18.3 Host bridge: Advanced Micro Devices K8 Miscellaneous Control

01:08.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)

01:0a.0 Ethernet controller: Intel Corporation 8254NXX Gigabit Ethernet Controller (rev 04)

0 Kudos
a18041967
Contributor
Contributor

Very interesting thread, now that we have a number of new ID's that appear to work has anyone tried updating the ESX ISO image with the entires so that the SATA controllers are recognised during installation. Using a tool similar to WinISO allows files to be added edited etc. Do we now have a master XML file with all the new entires in?

0 Kudos
JanPekman
Contributor
Contributor

So what about performance like a copy job from VMFS Volume to another VMFS volume?

I have a HP SATA SA2610 in a HP ML115. That has been great with support out of the box. I'm very happy with it untill I measured 9MB/s transfer rate when copying an ISO from VMFS to VMFs volume.

Job with VeeAM FastSCP. Which seems rather slow. (7 VM's running a the same time though.)

What tranfer rate could I expect from the omboard SATA controller?

Can anyone measure it and post transfer rate?

BTW I measured it with a ML350G5 with a HP SCSI RAID controller and that was still a "lousy' 25MB/s..

0 Kudos
rpartmann
Hot Shot
Hot Shot

Hi,

using "linux" commands like cp,mv to access VMFS are very slow.

This is because of the META data updates.

As a matter of fact this WILL not get very fast.

if you find a tool which creates a big file at once, like vmkfstools with vmdk files, and then copies the contetent you have won. btw: if you find let me know....

hth,

Reinhard.






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

ps: Award points if you find answers helpful. Thanks.
0 Kudos
JanPekman
Contributor
Contributor

You got ML115 with onboard SATA running.

When you use Veeam FastSCP

And copy &gt;1 GB ISO from one VMFS volume to another, what transfer rate do you get?

I'd very welcome if you want to do that for me. Then I know if it's worth the steps to switch from HP SA2610 to onboard SATA Smiley Wink

Thx in advance

0 Kudos