In ESXi 5.5 VMware removed driver support, but also for lots of SATA controllers that have never been on the HCL, but worked fine with the generic ahci driver of ESXi 5.0 and 5.1 (provided that they support and are configured for AHCI mode). For the NICs the problem could easily be solved, but - until recently - I had no idea how to fix the issue for the SATA controllers. I always thought that whenever an ESXi driver is loaded then it would detect and configure any PCI devices that it supports, but the ahci driver of ESXi 5.5 behaves differently: Even if manually loaded (with vmkloadmod ahci) it will only configure the devices that are explicitly listed with their PCI IDs in its map file ( /etc/vmware/driver.map.d/ahci.map). But once you realize this it is easy to add support for other SATA AHCI controllers that are not listed there. You just need to create another map file with the PCI IDs of these devices and a reference to the ahci driver. I was able to verify this method with the help of someone who tried to get his ASMedia ASM1062 Controller (PCI ID 1b21:0612) working with ESXi 5.5.
If you have the same controller then you can add support for it by running the following commands in an ESXi shell: esxcli software acceptance set -level=CommunitySupported esxcli network firewall ruleset set -e true -r httpClient esxcli software vib install -d -n sata-xahci Then reboot the host to make the change effective. I am providing this package ( sata-xahci) in both VIB file and Offline Bundle format. If you need the support at installation time then you can build an ESXi installation ISO that already includes the package using either or the script.
Do you have a different unsupported SATA AHCI Controller? Comment on this post and tell me its brand and its PCI ID, and I will add support for it in a new version of the sata-xahci package. A nice way to find this information is by running the following command in an ESXi shell: lspci -v grep 'Class 0106' -B 1 Just post the output of this command, thanks! Update (2014-12-03): Unfortunately, I had to disable commenting on this post, because new comments will no longer be displayed (although they can still be added).
It looks like we hit a Blogger limit or bug here?! Please send an e-mail to sata-xahci @v-front.de instead, but please read through the FAQ below first. I will just ignore any questions that are already answered there! It is also mandatory to include the output of the lspci command above! Update (2015-04-18): My sata-xahci package still works and is also necessary with ESXi 6.0 if your SATA AHCI controller is not detected out-of-the-box. So I changed the title of this post accordingly. FAQ In the meantime a lot of recurring questions and issues have been posted in the comments of this blog post.
Before posting the same questions over and over again please read the following information and FAQ before posting. PLEASE read before asking questions! A lot of modern SATA controllers also have RAID functionality, but they are no real hardware RAID controllers, but need software/driver support to implement RAID functionality. Please note: This driver support is not available in ESXi, so these controllers can only be used in AHCI, but not in RAID mode!
If configured for RAID mode the device will be shown as ' Class 0104' by ' lspci -v', and they might also expose a different PCI device ID when being in RAID mode. The same applies if your controller is shown as 'Class 0100' (SCSI Controller), 'Class 0101' (IDE Controller), Class '0105' (ATA Controller) or Class '0107' (SAS Controller). I can really only help you with SATA Controllers ( Class '0106') configured for AHCI mode! Be sure to configure the controller for AHCI (not RAID or anything else) mode in your computer's BIOS before you try to use my package and the ahci driver! If you have multiple SATA controllers on your computer's motherboard and/or as add-on cards then you might get confused about what SATA (and eSATA) ports belong to what controller.
So if the controller shows up in ESXi, but not the attached disks, then make sure that the disks are connected to the right ports. I am not able to provide you with a driver for non-AHCI controllers. In fact I'm not able to write an ESXi device driver on my own at all. So please don't ask for it, thanks! If your controller is already shown in the vSphere Client (in Host Configuration / Storage Adapters), but you do not see any disks attached to it then.
make sure that the disks are really attached to this and not to another controller (see 2.). be sure to look at Host Configuration / Storage / Devices (not Datastores). You will see the attached disks as Datastores only after you have created Datastores on the devices (via Add Storage in the Datastores view)!.
There is a bug in the firmware of some Marvell adapters (at least 88SE91xx) that prevents it from properly detecting attached devices if you have VT-D enabled in your computer's BIOS. As a workaround disable VT-D! Many thanks to!). From the comments on this post it looks like ESXi 5.5 introduces issues with Passthrough not working (whereas it worked before in ESXi 5.1 or 5.0).
Sorry, I cannot help with that, because I personally do not use Passthrough on any of my machines. If the command lspci -v grep 'Class 0106' -B 1 lists your controller with a name like vmhba0 (or vmhba1 etc.) in square brackets then that means that it is supposed to be supported out-of-the-box and was configured with the mentioned vmhbaX name. There is no need to add its PCI ID through sata-xahci, because it is already included in the standard mappings of the sata-ahci driver. Example output: # lspci -v grep 'Class 0106' -B 1 0000:00:1f.2 SATA controller Mass storage controller: Intel Corporation Lynx Point AHCI Controller vmhba0 Class 0106: 8086:8c02 If your controller is detected in this way, but does not work correctly then I'm sorry there is nothing I can do about this! Latest Update on 2016-11-07, Version 1.38 Please note: With version 1.10 I moved the download locations of the sata-xahci package from my GoogleCode page to the new.
For download links see the. Version History Device Vendor Device Name PCI ID added in ASMedia Technology Inc. ASM1062 Serial ATA Controller 1b21:0612 1.0 ASMedia Technology Inc. ASM1061 SATA IDE Controller 1b21:0611 1.1 Marvell Technology Group Ltd. 88SE9123 PCIe SATA 6.0 Gb/s controller 2) 1b4b:9123 1.1 Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller 2) 1b4b:9172 1.2 Marvell Technology Group Ltd.
88SE9120 SATA 6Gb/s Controller 2) 1b4b:9120 1.3 Marvell Technology Group Ltd. 88SE9230 PCIe SATA 6Gb/S Controller 2) 1b4b:9230 1.3 AMD SB6xx 1002:4380 1.4 JMicron Technology Corp. JMB363 SATA/IDE Controller 197b:2363 1.4 Intel Corporation Lynx Point-LP SATA Controller 1 8086:9c03 1.4 VMware Inc. Virtual SATA Controller 1) 15ad:07e0 1.4 ATI Technologies Inc. SB700 SATA Controller AHCI Mode 1002:4391 1.5 Marvell Technology Group Ltd. 88SE9128 PCIe SATA 6 Gb/s RAID controller with HyperDuo 2) 1b4b:9130 1.5 Marvell Technology Group Ltd.
Jmicron Linux Driver For Mac Mac
88SE9128 PCIe SATA 6 Gb/s RAID controller 2) 1b4b:9128 1.6 NVIDIA Corporation Unknown SATA controller 10de:0584 1.7 Marvell Technology Group Ltd. 88SE9182 SATA 6 Gb/s RAID controller 2) 1b4b:9182 1.8 Marvell Technology Group Ltd.
88SE9215 SATA 6 Gb/s RAID controller 2) 1b4b:9215 1.9 Marvell Technology Group Ltd. 88SE9125 SATA 6 Gb/s RAID controller 2) 1b4b:9125 1.10 nVidia Corporation MCP79 AHCI Controller 10de:0ab8 1.11 nVidia Corporation GeForce 7100/nForce 630i SATA 10de:07f4 1.12 nVidia Corporation MCP67 AHCI Controller 10de:0554 1.13 nVidia Corporation Apple iMac 9,1 10de:0ab9 1.14 AMD FCH SATA Controller AHCI mode 1022:7801 1.15 Marvell Technology Group Ltd. 9183 88SS9183 PCIe SSD Controller 2) 1b4b:9183 1.16 JMicron Technology Corp. JMB360 AHCI Controller 197b:2360 1.16 Marvell Technology Group Ltd.
88SE9220 SATA 6 Gb/s RAID controller 2) 1b4b:9220 1.17 JMicron Technology Corp. JMB362 AHCI Controller 197b:2362 1.17 Plextor PX-AG256M6e 1c28:0122 1.18 Intel 9 Series Chipset Family SATA AHCI Controller 8086:8c82 1.19 Intel 9 Series Chipset Family SATA AHCI Controller 8086:8c83 1.20 Intel Lynx Point-LP SATA Controller 1 AHCI mode 8086:9c02 1.20 Marvell Technology Group Ltd. 88SE9235 PCIe SATA 6 Gb/s RAID controller 2) 1b4b:9235 1.21 nVidia Corporation MCP65 AHCI Controller 10de:044c 1.22 nVidia Corporation MCP65 AHCI Controller 10de:044d 1.22 nVidia Corporation MCP65 AHCI Controller 10de:044e 1.22 nVidia Corporation MCP65 AHCI Controller 10de:044f 1.22 Marvell Technologies, Inc. 88SE6145 SATA II PCI-E controller 2) 11ab:6145 1.23 Samsung Electronics Co Ltd XP941 PCIe SSD 144d:a800 1.24 JMicron Technology Corp.
JMB361 AHCI/IDE 197b:2361 1.24 Marvell Technology Group Ltd. 88SE9480 SAS/SATA 6Gb/s RAID controller 2) 1b4b:9480 1.25 Marvell Technology Group Ltd. 88SE9485 SAS/SATA 6Gb/s controller 2) 1b4b:9485 1.25 Marvell Technology Group Ltd. 88SX7042 PCI-e 4-port SATA-II 2) 11ab:7042 1.26 ASMedia Technology Inc. SATA3 PCI Express x2 controller 1b21:0625 1.27 Intel Corporation Wildcat Point-LP SATA Controller AHCI Mode 8086:9c83 1.28 Kingston Technologies SATA Controller AHCI Mode 2646:0010 1.29 Samsung Electronics Co Ltd SM951 SSD M.2 Controller 144d:a801 1.30 Kingston Technologies Predator PCIe SSD 2646:0010 1.31 VIA Technologies, Inc. VT8251 AHCI/SATA 4-Port Controller 1106:3349 1.31 ASMedia Technology Inc.
SATA Controller (dev0622) 1b21:0622 1.32 Intel Corporation SATA AHCI Controller (dev22a3) 8086:22a3 1.33 Intel Corporation Atom Processor E3800 Series SATA AHCI Controller 8086:0f22 1.34 Intel Corporation Atom Processor E3800 Series SATA AHCI Controller 8086:0f23 1.34 Marvell Technology Group Ltd. 88SE9170 PCIe SATA 6Gb/s Controller 2) 1b4b:9170 1.35 Silicon Integrated Systems (SIS) AHCI IDE Controller (0106) 1039:1185 1.35 Marvell Technology Group Ltd. 88SE6440 SAS/SATA PCIe controller 2) 11ab:6440 1.36 Marvell Technology Group Ltd. MV1/64462 System Controller, Revision B 2) 11ab:6485 1.37 Samsung Electronics Co Ltd SM951 SSD M.2 Controller 144d:a802 1.37 Intel Corporation Atom/Celeron/Pentium Processor N4200/N3350/E3900 Series SATA AHCI Controller 8086:5ae3 1.38 1) VMware's vSATA controller was introduced in VM hardware version 10 in Workstation 10 and ESXi 5.5. So you can now add a vSATA Controller to your nested ESXi 5 hosts and use it with sata-xahci! 2) See bug info above in 'Read before commenting / 4.' I wanted to express my sincere thanks and appreciation for your help!
Your updates worked wonderfully on my system, and I coupled this package with the PowerCLI instructions to add support for my on-board network adapter, and everything is working wonderfully! I wanted to say thank you and you're doing a great service to the VMware community making ESX accessible on a wide range of hardware. One followup question: Is it possible to add multiple customizations thru ESXi-Customizer, or do they need to be added one at a time and a new ISO rebuilt after each one, if more than one item needs to be added?
Again, my most sincere thanks! Hi Dmitry, yes, see my post here: If you want to add the Realtek driver to a system that was already installed then run the following three commands in an ESXi shell: 1.
Esxcli network firewall ruleset set -e true -r httpClient 2. Esxcli software vib install -d -n net-r8168 3. Reboot Beware of unwanted line breaks. Each command is exactly one line! Hi Alex, this one is already supported out-of-the-box, and your output shows that the controller was already configured as vmhba0. It was detected as RAID controller (class 0104) though, not as a pure SATA controller (class 0106).
This is probably a RAID controller that needs software support to implement RAID functionality, but this is not available in ESXi, so you will most likely see only the individual disks rather than the logical RAID volume(s) that you configured. Sorry, there is nothing you can do about that. Anonymous Hello Andreas Thanks for all your Posts, your blog is great! I'm struggling with a Gigabyte Board that worked fine with ESXi5.0, but 5.5 can no longer find the internal SATA SSD during setup. Here's my output, I'd be really happy if you could assist me!
# lspci -v grep 'Class 0106' -B 1 000:000:31.2 SATA controller Mass storage controller: Intel Corporation Patsburg 6 Port SATA AHCI Controller vmhba0 Class 0106: 8086:1d02 - 000:005:00.0 SATA controller Mass storage controller: Marvell Technology Group Ltd. vmhba32 Class 0106: 1b4b:9172 - 000:006:00.0 SATA controller Mass storage controller: Marvell Technology Group Ltd. vmhba34 Class 0106: 1b4b:9172 - 000:011:00.0 SATA controller Mass storage controller: Marvell Technology Group Ltd. vmhba36 Class 0106: 1b4b:9172 Greetings, Tom.
Anonymous Hello Andreas Thanks for your reply. The SSD is attached directly to the Mainboard (so the Marvell Controller). I just see that you have added this model 'Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller 1b4b:9172' in version 1.2, I have no idea why it's not showing up during the ESX 5.5 installation.:/ I'm not so familiar with that VOB stuff, but I have used ESXCustomizer 2.7.1 to add your VOB File to the ESXi Image ESXi-5.5.0-1331820-standard-customized.iso which I created with help of your other blog post.:) Do you have any idea? Thanks again for your help! I already have thoughts moving to Hyper-V (uhh.
Did I just say that out loud?) Tom. Anonymous Hi Andreas, great initiative! I have issues with my GA-X58A-UD5 MB with 2 extra SATA controllers no longer supported in VMware 5.5. The following output is from 5.1 for the datastores not detected after an initial upgrade to 5.5.
# lspci -v grep 'Class 0106' -B 1 00:01:00.0 SATA controller Mass storage controller: Marvell Technology Group Ltd. 88SE9128 PCIe SATA 6 Gb/s RAID controller vmhba33 Class 0106: 1b4b:9128 - 00:05:00.0 SATA controller Mass storage controller: JMicron Technology Corp. GA-EP45-DS5 Motherboard vmhba41 Class 0106: 197b:2363 Could zou please provide support for these in a next release? Thanks, Koen.
Hi Andreas, I had been using esxi v5.1 update 1 and I'm passing through my 6 port AHCI SATA controller to a FreeNAS VM. (onboard a Tyan S5512 series XEON server mobo) It has Working fine. I have recently installed esxi v5.5 and passed the sata controller back to the same FreeNAS VM. The VM could not see the zfs volume or any connected disks at all. I did a google search to resolve this and found your blog.
I've followed your instructions and have SSH into my host and installed your VIB. After rebooting the host my FreeNAS VM still cannot see the disks.
I'm now back to using esxi v5.1. It's a Class 0106: 8086:1c02 please. I wouldn't be here if it worked out of the box. Can you please add it for you next update Thanks Glenn.
Hi Andreas This one is in your list, but not recognized: # esxcli software vib install -d -n sata-xahci Installation Result Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective. Reboot Required: true VIBs Installed: VFrontDebootbanksata-xahci1.10-1 VIBs Removed: VFrontDebootbanksata-xahci1.9-1 VIBs Skipped: 0000:01:00.0 RAID bus controller Mass storage controller: Marvell Technology Group Ltd. 88SE9230 PCIe SATA 6Gb/s Controller vmhba2 Class 0104: 1b4b:9230 # dmesg grep ahci 2013-12-16T16:10:25.603Z cpu1:33325)Loading module ahci.
2013-12-16T16:10:25.604Z cpu1:33325)Elf: 1861: module ahci has license GPL 2013-12-16T16:10:25.604Z cpu1:33325)module heap vmklnxahci: creation succeeded. Id = 0x41094d36b000 2013-12-16T16:10:25.604Z cpu1:33325)PCI: driver ahci is looking for devices 2013-12-16T16:10:25.604Z cpu1:33325)PCI: driver ahci claimed 0 device 2013-12-16T16:10:25.604Z cpu1:33325)Mod: 4780: Initialization of ahci succeeded with module ID 4146. 2013-12-16T16:10:25.604Z cpu1:33325)ahci loaded successfully.
Regards Roland. It's a MSI Star-SATA6 card There is a flashable firmware that can change the card from IDE to AHCI mode, but I can't find it nowhere. Info about that on this site: I tried contacting the person that uploaded it but he is not answering to my PM.
The uploaded file has been deleted from servers so I can't download it. I found couple of firmwares on other sites like this one I tried also incorporating them in the firmware of the card itself but no luck, the firmware updates but the card is still in IDE mode. I have not made it to change to AHCI mode yet. I have a programmer device so it's not a problem to experiment, but I don't know what exactly I have to change in the bios file itself to make it work in AHCI mode. I have successfully changed the card PCI ID to 1b4b:9128 because it uses the Marvel 88SE9128 chip and the card works but still in IDE mode. I can upload the firmware if someone knows how to modify it so the card will work in AHCI mode.
Do I only have to change the Class of the card from 0101 to 0106 or there is more to it? Thank you for the answer. Hi Andreas, I have the same issue of Jay on my ESXi 5.5: # esxcli software acceptance set -level=CommunitySupported Host acceptance level changed to 'CommunitySupported'. # esxcli network firewall ruleset set -e true -r httpClient # esxcli software vib install -d -n sata-xahci Installation Result Message: Host is not changed. Reboot Required: false VIBs Installed: VIBs Removed: VIBs Skipped: VFrontDebootbanksata-xahci1.12-2 # lspci -v grep ASMedia 0000:04:00.0 SATA controller Mass storage controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller 0000:05:00.0 PCI bridge Bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge The device is not in pass trough and I don't have older drivers: # esxcli software vib list grep xahci # Any other suggestion?:) Thank you!
Hi Andreas, I took your vib and un-vibed and unzipped it on mu Ubuntu Linux host ar vx file.vib tar -tzvf sata-xah Then I added a line concerning my controller (Marvell) at the end of the xahci.map file. This was found within the etc map somewhere.
Regtype=linux,bus=pci,id=1b4b:9123 0000:0000,driver=ahci,class=storage Then i rezipped it like explained somewhere else on the internet (corrected filesize en deleted the checksums in the descriptor.xml file and so on ar -r sata.vib sata-xai descriptor.xml sig.pkcs7 Afterwards i revibed it to sata.vib and used the customizer mentioned here to create an new iso. I can see the sata-sah file becomes loaded but no response from the (tested) harddisk connected to to 1 of the (6gb) sata interface My marvell shows: 0000:00:1f.2 SATA controller Mass storage controller: Intel Corporation ICH10 6 port SATA AHCI Controller vmhba0 Class 0106: 8086:3a22 - 0000:01:00.0 SATA controller Mass storage controller: Marvell Technology Group Ltd. 88SE9123 PCIe SATA 6.0 Gb/s controller vmhba2 Class 0106: 1b4b:9123 1 Did i missed something 2 Can jou add my controller to te list Kind Regards Rene. Anonymous HI Andreas, I upgraded my ESIxi-5.1.u (worked without issues) via shell cmd: # esxcli network firewall ruleset set -e true -r httpClient # esxcli software profile update -d -p ESXi-5.5.0-1331820-standard.now the disks that are attached to the AHCI controller aren't available/not listed via format cmd. These disks (5) are part of a ZFS zpool. Do I need to get a SATA controller? My motherboard has 2 PCI-E slots (x8 & x4) the (x8) is used as raid-0 for the storage OS.
Since there are limitations, what kind of SATA controller do I get? Your help is greatly appreciated. Anonymous I am reading people having problem with the MARVELL tech 88SE9123 driver not showing any disks. I do have this same problem. I am using a PEXSAT32 2-port PCI Express 6Gbit/s SATA 3.0 Controllercard. The thing is that the manul says that it needs to use the chipset Marvell - '88SE9128'.
But Esxi is instead ( i am currently still using 5.1) using Marvell - 88SE9123. Could this be the problem that there are no disks detected? In the vsphere client the storage adapter is showing the controller as it should be: Marvell - 88SE9123 PCIE SATA 6.0 GB/s controller. Only with the 9123 driver loaded and no disks detected. There are currently two 1 TB disks attached to the 2 ports on the SATA card.
Hi, I am researching the options for using Apricorn Velocity Solo x2 Extreme Performance SSD Upgrade Kit as a PCI-E SSD for ESXi 5.5. I followed the instructions and installed sata-xahci. After rebooting the ESXi server lspci shows: # lspci -v grep 'Class 0106' -B 1 0000:06:00.0 SATA controller Mass storage controller: Marvell Technology Group Ltd. 88SE9182 SATA 6Gb/s Controller vmhba2 Class 0106: 1b4b:9182 The vSphere Windows client shows: 88SE9182 SATA 6Gb/s Controller vmhba2 vmhba32 No attached devices are recognized. Any ideas why the attached SSD drive is not visible? Anonymous Hey Andreas and Svetlin, Andreas, you created version 1.8 after I requested for 1b4b:9182 (for the solo x2). Thanks for your help!
Eventually I discovered that ESXi was detecting the controller but not the drives connected to it. The same was true for a completely different card with the same chipset.
Recently, I gave up and used a different card (solo x1) with an asmedia chipset that works fine thanks to your sata-xahci. Strangely my vmkernel.log file seemed to suggest that everything was fine except that ESXi apparently had no idea that there was a drive connected. Anonymous Hi Andreas, I have a short question about your changes to the driver. I assume you have added further PCI device/vendor IDs to the driver to get AHCI compliant interfaces working with the driver. Do you know if the PCI sub-vendor/device IDs are also taken into account when loading the driver? I'm asking because I have a board with 2x Marvell 9172 controller and it seems there are no devices detected.
I'm currently at the beginning of my investigations so I'm not sure if it's a problem of the ISO image I created thanks to your tool, a problem with the board or with the detection of the drive itself. As far as I can see in mapping file extracted from the vib file, there's something which could be a sub-vendor/sub-device entry: regtype=linux,bus=pci,id=1b4b:9172 0000:0000,driver=ahci,class=storage Can you confirm that the 0000:0000 means what I assume? I'll have a look if I can manage to change the values according to the entries in the PCI headers of my motherboard (Asrock C226 WS) in order to operate the interfaces in ESXi 5.5. Best regards, Adalbert. Anonymous Hi all, I did some tests with a modified installation CD using the offered driver as well as with a driver which has added subdevice and subvendor IDs. Unfortunaltely that didn't help.
The driver seems to be included correctly into the image (logs show that the controller is available), but the system has problems to detect the attached device. According to the output of dmesg, the ESXi 5.5 detects that something is connected, but me error message says that it cannot identify the device. The situation is the same on the two Marvell 9172 controllers as well as on a add-on card I found using the Marvell 9120 controller. Not yet tried with ESXi 5.1.
Best regards, Adalbert. Anonymous Hi all, I'm ahead with the investigations. The problem is not the driver or the iso creation. The problem seems to be linked to the controller itself.
The problem seems to be caused by the Marvell when it's using PCIe phantom functions - a VT-D related functionality. These functions are disabled in the PCIe capability of the Marvell controller. But according to the logs of ESXi, it uses phantom functions and confuses VT-D/IOMMU. Disabling VT-D in the EFI setup 'fixes' the detection problem.
Unfortulately I have planned to use VT-D. Google revealed a bug report, which indicates the problem is not limited to ESXi or anyhow related to it. It seems to me to be clearly an issue of the controller. Therefore for anybody who plans to use VT-D and want to use it for ESXi: Avoid using a Marvell controller. Assigning this controller to a VM may work. Best regards, Adalbert. Anonymous Hey Andreas, this is Gianluca.
I've been trying to add my old Adaptec Ultra320 series RAID controller for awhile now. The controller will show up on ESXI 5.0 but not 5.5. I've tried a myriad of things to get it to work on a clean install ISO of 5.5, including adding the.VIBs you've created but to no avail. I did the instructions you suggested within the installation console and here are the results.
Well, at least of the things that seemed like they'd be relevant to the controller (There was a lot of side stuff about the Motherboard North and South bridges). Anyway: 0000:001F.1 IDE Interface Mass Storage Controller: Intel Corporation 631xESB/632xESB IDE Controller vmhba0 Class 0101: 8886:269e 0000:05:03.0 RAID bus controller Mass storage controller: Adaptec AIC-7902(B) U320 w/HostRAID Class 0104: 9005:889d 0000:05:03.1 SCSI bus controller Mass storage controller: Adaptec AIC-8982 U320 vmhba1 Class 0100: 9005:881d I'd like to mention that I have 4 Fujitsu 300gb hard drives that are set up in a RAID10 at the moment. Out of curiosity in a Windows 7 install, the drives show up as one 600gb hard drive. Though, in the ESXI 5.0 install, when they show up, all 4 of them are selectable individually at 300gb a piece rather than the one 600gb it should be considered.
Will having the correct VIBs installed fix that issue of them being 4 different drives rather than the one 600gb? Worse comes to worst, could I install ESXI 5.0 (Cause the 4 drives show up) and then upgrade to 5.5 (Where the drives don't show up)? I feel like the install would detect that there's an ESXI installed somewhere and then ask if I want to update it.
That being said, would the rest of the drives work or just a single 300gb after updating? Is there any disadvantages to updating rather than installing cleanly? HI Andreas, Im struggling to get a Vertex OCX 60GB drive working. The host controller is. # lspci -v grep 'Class 0106' -B 1 0000:00:1f.2 SATA controller Mass storage controller: Intel Corporation Lynx Point AHCI Controller vmhba0 Class 0106: 8086:8c02 and I can see my SATA disks fine.
The Vertex SSD worked well in my ESXi 5 Machine, however im moving it to a new machine (new processor, new motherboard) for which the Realtek NIC drivers have been brought back and work well. Its just the SSD thats not being recognised. VT-D is off in the Bios and the Bios does see the disk. Esxcli storage nmp device list does not show the SSD, but does show the other three disks and iSCSI (moving all over to iSCSI, just the SSD will remain as local cache file. Thanks for all your help, SimonZ. Unfortunately, I can confirm that Marvell 92xx series chips also suffer from the VT-D bug. My motherboard has a 9120 that wasn't working and I needed the missing ports, so I bought a 9230-based PCI add-on card and it's displaying the same symptoms (Storage adapter is recognized, but no devices are visible with VT-D enabled) in ESXi 5.0 U3.
Can anyone recommend a low-cost SATA add-on card that doesn't suffer from this issue? I know the IBM M1015 and LSI-based cards work, but I would really rather not spend $100+ just to replace the two ports that aren't working. SATAIII would be preferable, but I can live with SATAII if need be.
I've continued my research for a different SATA add-on card to try (keep in mind this is specifically for ESXi 5.0 U3, but I'm guessing Andreas' patch should make it applicable to 5.5 users as well). Here's what I'm thinking/finding so far: -I'm just going to assume that everything Marvell-based won't work.LSI-based controllers such as the IBM M1015 are known to work, but aren't cheap ($100) if you're just looking to add a couple of ports.I can't find much of anything about the Silicon Image 3124/3132 chips with recent (5.0 and later) builds of ESXi work when passthrough is used, but it seems a lot of the reviews I've found consider them unreliable in general. This is what I'm looking at right now: It's based on the ASMedia 1061. I've found one or two reviews that had problems with it, but I think they were trying to pass through the entire onboard SATA controller and use the add-on card for datastores or something along those lines. I've also found other reviews (such as those in the Newegg link above) that says it works natively with ESXi 5.1, but one user was passing it through to a VM and it's not clear if the other was using VT-D. Does anyone have experience with ASMedia 1061-based cards? I'd be using it for datastores, but VT-D is enabled to pass through other devices to my VMs.
I've inserted into a DELL R710 server a Sonnet Temp SSD Pro PCIe SATA Controller with 2x512GB Samsung SSD Pro (Here you can see the lspci output: # lspci -v grep 'Class 0106' -B 1 0000:07:00.0 SATA controller Mass storage controller: Marvell Technology Group Ltd. Class 0106: 1b4b:9182 - 0000:08:00.0 SATA controller Mass storage controller: Marvell Technology Group Ltd. Class 0106: 1b4b:9182 I'm using vmware ESXi5.5.0-201312001 Build Number: 1474528 (DELL server has the latest firmwares) vmware ESXi 5.5 could not see the tempo ssd controller (but my server displayed controller information well) How can I create vib file with correct drivers to install it on my ESXi 5.5 server? Thank you in advance. Best Regards: Szabolcs. Hi Andreas, On last midnight I played your driver to revive it on ESXi 5.5. But I have same problem (Anonymous wrotten above): The Dell only has Enable/Disable 'Virtualization Technology' and it covers both VT-x and VT-d.
The drive works when I disable VT in bios, but I need VT-x for vCenter, too. I disabled the remapping and rebooted but it did not help me. #esxcli system settings kernel set -setting=iovDisableIR -v TRUE # esxcli system settings kernel list -o iovDisableIR Name Type Description Configured Runtime Default - - - - - - iovDisableIR Bool Disable Interrrupt Routing in the IOMMU TRUE FALSE FALSE - I'v read the 'DMA Read on Marvell 88SE9128 fails when Intel's IOMMU is on' bug report, too, but there isn't solving for this problem, yet.
What do you mean, when will be solving this Marvell chip and ESXi 5.5 bug? Sonnettech said me: 'At this time, I’m not aware of pending firmware updates for the Tempo SSD cards that would enhance this specific usage for the cards.'
- A global question is how can I disable VT-d only in DELL R710 or R720 bios, if there is no possibility separately? Thanks and Regards, Szabolcs. Hi Andreas, I've changed VPS host environment from ESXi5.5.0-201312001 to ESXi5.1.0-201402001 with newest install (separately) now to an USB thought I could test Sonnet Temp SSD PRO Card with your sata-xahci 1.10 driver under latest ESXi 5.1 U2- build:1612806 (I've created screenshots: ) and rebooted.
Jmicron Media Card Reader Driver
The results is same that on ESXi 5.5 U1, because of the storage adapter information displayed in vSphere Client under Storage adapters list (but device, targets, path are zero, there are missing details. I've modified the iovDisableIR configured value to TRUE (and rebooted. After I rebooted the host machine there were not displayed any disk from this list (I've tested your sata-xahci v1.15 under ESXi 5.1 U2- build:1612806, but it didn't work, too. In the Advanced settings /Configure Passthrough/ the controller information and device details showing well (but I wouldn't like to use this mode. What do you suggest, how can we resolve this driver problem under latest ESXi 5.1 U2 build number:1612806?
Thanks and regards, Szabolcs.
On Monday 25 September 2006 09:24, rob pfile wrote: On Sep 24, 2006, at 12:15 PM, mactel-linux-users- EMAIL PROTECTED wrote: Mac Pro and Linux AHCI SATA driver help Here's something of a dumb question: apparently the high-end Dell and HP server systems use this same chipset and motherboard, and they can be bought from dell/hp pre- configured with linux (RHEL4, i believe). do dell and HP do their own patches to the kernel for this stuff, or is it simply that these machines have BIOS and so linux can use the 'built in' drivers for these problematic devices? so far these kind of issues have stopped me, and a friend at another company, from buying mac pros to run linux-based chip cad tools. thanksrob I have yet to fully determine if the driver issues discovered on the Mac Pro will be the same as on the HP and Dell systems, but the legacy IDE controller issue is the only one I've uncovered that is isolated to the Mac Pros. Also, I'm not sure if all 6 SATA controllers are available on the HP and Dell systems, will have to research that. HP does offer a driver CD for their 5000X based workstations, but only for RHEL3 and 4.
I took a look at the updates, and it appears that they only support the 2.4.x kernels right now, and the driver CD only inlcudes ALSA updates and support for installing the NVIDIA drivers. On the otherhand, a price comparison will show that the HP and Dell workstations run about $700-$800 more than the Mac Pro for close to the same configurations. In my opinion, the Mac Pro case sold me on it vs. The Dell or HP. The driver issues are minor, and you can always fall back on Mac OS X or XP if you wanted.
Dave - Take Surveys. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash Mactel-linux-users mailing list Mactel-linux-users@lists.sourceforge.net.