WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud
  • Tanzu
    • Application Modernization
    • Tanzu services
    • Tanzu Community Edition
    • Tanzu Kubernetes Grid
    • vSphere with Tanzu
  • Home Lab
  • Nested Virtualization
  • Apple
You are here: Home / ESXi / New storage devices added to Community NVMe Driver for ESXi Fling

New storage devices added to Community NVMe Driver for ESXi Fling

07.12.2021 by William Lam // 16 Comments

We have an exciting update for the VMware Community today with the release of the Community NVMe Driver for ESXi Fling v1.1. After the release of ESXi 6.7, a number of consumer NVMe devices were no longer bering detected which had previously worked with ESXi 6.5.

One workaround that many folks had to implement, including myself, was to replace the 6.7 NVMe driver. with the previous 6.5 version of the NVMe driver. Although this method still works with the latest ESXi 7.0 Update 2, it is less than ideal as you are using an extremely old version of the NVMe driver and you are giving up new NVMe device enablement, bug fixes and enhancements with the latest version of the driver.

Given the amount of comments and feedback that I had received in the previous blog post, I wanted to explore a way in which we can enable some of these consumer NVMe devices for the community. With the help from Yibo, we have updated the Community NVMe Driver for ESXi Fling to include support for the following storage devices:

VendorName VendorId DeviceId
ADATA 0x1cc1 0x8201
Micro/Crucial 0xc0a9 0x2263
Silicon Motion/Transcend 0x126f 0x2262

With this update, we have also added support for ESXi 7.0 or greater when using the new driver which should hopefully be a welcome update for VMware Homelabs!

Here is a screenshot of my Intel NUC 9 running ESXi 7.0 Update 2 which now recognizes my Crucial 1TB NVMe (CT1000P1SSD8)


To help others in the community, if folks want to share the specific brand and model of their NVMe device that can now be enabled by the new driver, feel free to leave a comment. Other consumer NVMe devices may be considered in the future, but will soley be based on feedback from the community. If your particular NVMe device is not being picked up, please share the vendor/device ID by using lspci -v command on ESXi Shell.

More from my site

  • Updates to USB Network & NVMe Community Driver for ESXi 7.0 Update 3
  • Apple NVMe driver for ESXi using new Community NVMe Driver for ESXi Fling 
  • Removable M.2 NVMe SSD PCIe enclosure by Icy Dock
  • Thunderbolt 3 enclosures with (Single, Dual & Quad) M.2 NVMe SSDs for ESXi
  • Quick Tip - Crucial NVMe SSD not recognized by ESXi 6.7 & 7.0

Categories // ESXi Tags // NVMe

Comments

  1. WelshWizard says

    07/12/2021 at 1:15 pm

    Oooh, this is awesome. Excellent work team.

    Now if Realtek could come to the party and make a native driver for their NICs.

    Reply
    • Admin says

      07/14/2021 at 1:18 pm

      Will this fling support Patriot 512GB NMVe module? I have 4 of them in 4 different ESXi boxes and had to downgrade to the 6.5 driver to make it work.

      Reply
      • William Lam says

        07/14/2021 at 3:42 pm

        Take a look at the Vendor/DeviceID as mentioned in blog post to see if your device is included 🙂

        Reply
  2. fugtui3 says

    07/13/2021 at 12:30 am

    unbelievable - I really appreciate the effort you put into making this work again! Great to be able to update properly again 🙂

    Reply
  3. Yuki Kawamitsu says

    07/13/2021 at 5:13 am

    Thanks for the great update!
    It worked fine with the ESXi 7.0u2 and Transcend NVMe SSD.

    Driver :
    nvme-community-driver_1.0.1.0-2vmw.700.1.0.15843807-component-18290856.zip

    Tested SSD :
    Transcend PCIe SSD 220S TS2TMTE220S
    * controller: Silicon Motion, VID:0x126f, PID:2262

    ----
    [[email protected]:~] lspci -v
    0000:3a:00.0 Mass storage controller Non-Volatile memory controller: Silicon Motion, Inc. Device 2262 [vmhba1]
    Class 0108: 126f:2262
    [[email protected]:~] vdq -q
    [
    {
    "Name" : "t10.NVMe____TS2TMTE220S_____________________________G095430113__________00000001",
    "VSANUUID" : "",
    "State" : "Ineligible for use by VSAN",
    "Reason" : "Has partitions",
    "IsSSD" : "1",
    "IsCapacityFlash": "0",
    "IsPDL" : "0",
    "Size(MB)" : "1953514",
    "FormatType" : "512e",
    "IsVsanDirectDisk" : "0",
    },
    ]

    Reply
  4. Kenichi Kagami says

    07/22/2021 at 9:35 pm

    PLEXTOR PX-2TM10PY

    0000:02:00.0 Mass storage controller Non-Volatile memory controller: Vendor 1e95 Device 1005 [vmhba1]
    Class 0108: 1e95:1005

    Reply
  5. shinichi.tym says

    08/25/2021 at 10:08 pm

    Unfortunately I did not recognize.

    Silicon Motion / TEAMGROUP (MP33 M.2 PCIe SSD)
    0000:01:00.0 Mass storage controller Non-Volatile memory controller: Silicon Motion, Inc. Device 2263 [vmhba1]
    Class 0108: 126f:2263

    from [email protected]

    Reply
  6. Tyrone Matthews says

    08/31/2021 at 1:58 pm

    Hello William,

    Unfortunately after trying to update to 7.0u2a the storage was not recognized for my servers. Details below for the storage controller

    0000:01:00.0 Mass storage controller Mass storage controller: Apple Inc. ANS2 NVMe Controller [vmhba1]
    Class 0180: 106b:2005

    Reply
  7. Russell Baker says

    10/06/2021 at 4:17 pm

    Hi William, thanks for this. Actually this is an Intel 660p 1Tb, not sure why it's showing up as 2Tb?

    0000:05:00.0 Mass storage controller Non-Volatile memory controller: Intel Corporation SSDPEKNW020T8 [660p, 2TB] [vmhba4]
    Class 0108: 8086:f1a8

    Reply
  8. Anthony says

    10/25/2021 at 9:09 am

    William, did you ever run into an issue with your CT1000P1SSD8 where it seems to just disconnect from ESXI whenever it hits some mysterious threshold of throughput? Happens to me on 7.0 (up to update, tested on most releases) using vSAN or just dumping files on it directly attached to test. Reboot brings it back, but it will drop again whenever I hit a high iops on it again. I have four of them on two r720s, all do the same thing.

    While I have the same device and IDs as you - mine is recognized without this community driver, and.. I get the same behavior with it.

    Reply
    • Russell Baker says

      10/25/2021 at 7:04 pm

      Ran into an issue with a Seagate Barracuda 510 1Tb NVMe on ESXi 6.5 U3, where if it hit its max temp threshold (75 deg) ESXi would simply detach the storage. I expected it to just throttle itself like my Samsung 970 EVO. Since using a proper heatsink it never goes over 55 deg

      Reply
      • Anthony says

        10/30/2021 at 9:24 pm

        That was exactly it, found a similar comment right after I wrote this. I came back to comment on that for anyone else who shares the problem. After putting heatsinks on them the issue went away.

        Reply
  9. patrickdk says

    11/04/2021 at 4:24 pm

    Samsung PM961, 144d:a804

    Reply
  10. Devin says

    05/28/2022 at 7:00 am

    0000:3a:00.0 Mass storage controller Non-Volatile memory controller: Phison Electronics Corporation E12 NVMe Controller [vmhba1]
    Class 0108: 1987:5012

    I wrote out a long comment, but it got eaten lol. William, thank you for the work you do for the home user, it is invaluable. If you can find a way to add this controller, it would be huge for me as these are 8tb Inland Platinum drives, of which I have 5 that I cannot return and are sitting in 5x intel nucs 10th gen)

    Reply
  11. sonymuzik says

    08/08/2022 at 10:19 am

    Hello

    ID PCI 1cc1:5350:1cc1:5350
    Class 01-08-02 »
    Type storage/nvme »
    Vendor ADATA Technology »
    Name A Non-Volatile memory controller
    Subsystem ADATA Technology

    0000:27:00.0 Mass storage controller Non-Volatile memory controller: ADATA Technology Co., Ltd. Device 5350 [vmhba3]
    Class 0108: 1cc1:5350

    unfortunately she didn't recognize me what should i do please help

    Thansk.

    Reply
  12. sonymuzik says

    08/08/2022 at 10:32 am

    Adata XPG Gammix S50 Lite m2 Nvme SSD

    Reply

Thanks for the comment! Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Author

William Lam is a Senior Staff Solution Architect working in the VMware Cloud team within the Cloud Infrastructure Business Group (CIBG) at VMware. He focuses on Cloud Native technologies, Automation, Integration and Operation for the VMware Cloud based Software Defined Datacenters (SDDC)

Connect

  • Email
  • GitHub
  • LinkedIn
  • RSS
  • Twitter
  • Vimeo

Recent

  • How to bootstrap ESXi compute only node and connect to vSAN HCI Mesh? 01/31/2023
  • Quick Tip - Easily move or copy VMs between two Free ESXi hosts? 01/30/2023
  • vSphere with Tanzu using Intel Arc GPU 01/26/2023
  • Quick Tip - Automating allowed and not allowed Datastores for use with vSphere Cluster Services (vCLS) 01/25/2023
  • ESXi with Intel Arc 750 / 770 GPU 01/24/2023

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2023

 

Loading Comments...