NVME M.2 Passthrough


Recommended Posts

Wow...just stumbled upon this thread trying to get my intel 660p nvme drive working. I was optimistic with all of the back and forth support from limetech on this but see that it has basically been abandoned.

 

I guess I am returning my intel and forking over the cash for a Samsung...

Edited by WexfordStyle
Link to comment
2 hours ago, WexfordStyle said:

Wow...just stumbled upon this thread trying to get my intel 660p nvme drive working. I was optimistic with all of the back and forth support from limetech on this but see that it has basically been abandoned.

 

I guess I am returning my intel and forking over the cash for a Samsung...

It is a kernel problem which is outside of LT control.

Kernel-related issues will never be fixed until it's fixed by the power-that-be (the elite few who control the Linux kernel codes) or someone creates a patch (that doesn't end up breaking other stuff) or Intel fixes it on their end (e.g. firmware update).

 

The 660p is dirt cheap for a reason. QLC NVMe is like running a Ferrari with bicycle tires.

Link to comment
  • 1 month later...

Given that I already have an Intel 660p, what would be the best course of action? I want to dual-boot an existing Windows installation (installed on said device), should I buy a new SSD (TLC or MLC?) and migrate my existing Windows installation to that new disk? 

 

I get the following error, which I assume is caused by the Intel 660p:

table & pba overlap, or they don't fit in BARs, or don't align

 

Thanks in advance!

Link to comment
52 minutes ago, Emptyless said:

Given that I already have an Intel 660p, what would be the best course of action? I want to dual-boot an existing Windows installation (installed on said device), should I buy a new SSD (TLC or MLC?) and migrate my existing Windows installation to that new disk? 

 

I get the following error, which I assume is caused by the Intel 660p:


table & pba overlap, or they don't fit in BARs, or don't align

 

Thanks in advance!

So are you wanting to run a Windows VM and pass the NVME through (the subject of this thread), or just use it to boot Windows instead of Unraid? 

Link to comment
1 minute ago, trurl said:

So are you wanting to run a Windows VM and pass the NVME through (the subject of this thread), or just use it to boot Windows instead of Unraid? 

 

Both actually. I have a bare metal windows install which I want to still be able to boot when shutting down Unraid. But whenever I have started Unraid I want to be able to spin up a VM with Windows 10 by using passthrough for the NVME drive as per guide:

 

 

I don't foresee shutting down Unraid often (maybe once / twice a month) but nevertheless I still want to retain the possibility of booting bare metal Windows.

 

Link to comment
  • 2 months later...
On 12/28/2018 at 9:45 PM, aw_ said:

Everyone experiencing this issue who has an NVMe drive making use of the SM2262 controller, please:

 - Report the device model

 - Report the PCI vendor and device IDs (lspci -nn)

 - Step through comments 1 and 10 in https://bugzilla.kernel.org/show_bug.cgi?id=202055 to verify the device behaves the same, particularly the MSI-X Count is initially 16, after reset it's reported as 22, but the value remains 16 if a secondary bus reset is triggered via setpci.

 

There's also a patch there for testing, but it only includes the Intel 760p device ID, we'll need to compile a list of all affected device IDs or figure out if there's a way to interrogate the NVMe controller interface to find the these chips since it seems to be in use by Intel, Mushkin, ADATA, and WD.  Thanks

Hi,

 

im getting this error with a Crucial CT500P1SSD8 P1 500 GB, I need to buy a larger nvme anyway but how do I know what controller each NVME uses before I buy? 
For example, do all Samsung use the same controller or do I have to go by specific model?

 

thanks

Link to comment
  • 2 weeks later...
  • 2 months later...
  • 2 weeks later...

Does anyone know if an Intel 660p would be okay with being run in the cache pool? I know hardware passthrough doesn't work, I am curious, if I can buy a few of these on the cheap, and replace them with my exist 500GB sata ssds for my cache pool. I never tested that when I had the 660p originally, before I returned it and got a samsung drive. 

Link to comment
  • 1 month later...
On 7/25/2020 at 12:40 AM, raujaku said:

You cant pass through the NVME through stubbing but you can use it by changing your vdisk path to your /dev/disk/by-id/(your-nvme) location.

it worked for me. But I want to know what's the difference between stubbing and the 'by-id' method?

Link to comment
  • 3 weeks later...
On 7/24/2020 at 10:40 PM, raujaku said:

You cant pass through the NVME through stubbing but you can use it by changing your vdisk path to your /dev/disk/by-id/(your-nvme) location.

I tried this but it didn't work. 

 

Just making sure I did the correct thing: completely new install. I had stubbed the NVMe, then unstubbed it, and referred to the NVMe by it's id (the whole drive). Did I do that correctly? Should I refer to one of the partitions in particular?

Link to comment
  • 2 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.