Update: the AXXP3SWX08080 (card), A2U8PSWCXCXK1 (cables), and A2U8X25S3PHS (drive bay) are installed. I have one Intel P4510 (4T) and one Samsung PM961 (256G, M.2) in a cheap M2 adapter. They both show up just fine in Windows 10, with no special work needed. The P4510 benchmarks in CrystalDiskMark 6.0.1 at 2,923 MB/s reading and 2,889 MB/s writing. The Samsung gets 3,263 MB/s reading and 743 MB/s writing. Running both tests concurrently gives me 2,760+3,196 reading and 2,911+663 writing.
The drive activity LEDs blink on both drives when they're being accessed, but when the drives are idle the Intel LED stays on and the Samsung LED stays off.
Windows 10 doesn't recognize hot-plugged drives. That's not surprising. I suspect that Linux would, and Windows server might.
I didn't test SAS/SATA drives. They should be easier to get right than NVMe.
That one is a SATA device, it's only useful if you have M.2 SATA SSDs, which are kinda rare (and pointless) these days.
I'm using this one:
https://www.amazon.com/gp/product/B01HR0PKJQ/ref=oh_aui_detailpage_o02_s00?ie=UTF8&psc=1
It simply adapts a x4 PCIe M.2 slot to a x4 PCIe U.2/SFF-8639 connector, in a form factor that will work in a hot-swap sled. It shouldn't have a performance impact, although PCIe signal integrity may be an issue at some point.
I think it would depend on the 5.25" setup in your specific case.Does anyone know if there's a way to mount the A2U8X25S3PHS on a regular pc case with 2x 5.25" bay available ??
I plan to get this for my desktop, so I can run a few U2 NVME drive that I have, but I am concerned that there's no way to secure the drive bay in my case (HAF932 Advanced). I would appreciate it if someone who owned one of these can take a picture from the side angle, I am curious to see whether I can use some powerful double tape or hot glue to secure it.
Did you check the pictures on the first post? Not sure if that answers your question. These are created for 2U Intel servers to be secured on the top and bottom of the carrier. OP used them on HP Z840 which has a latch for securing modules in the 5.25 bays.Does anyone know if there's a way to mount the A2U8X25S3PHS on a regular pc case with 2x 5.25" bay available ??
I plan to get this for my desktop, so I can run a few U2 NVME drive that I have, but I am concerned that there's no way to secure the drive bay in my case (HAF932 Advanced). I would appreciate it if someone who owned one of these can take a picture from the side angle, I am curious to see whether I can use some powerful double tape or hot glue to secure it.
The A2U8X25S3PHS is the right height for 2x 5.25 bays, but (as mentioned) has no screw holes on the side and is 4mm narrower than expected. You could probably shim 2mm on each side and use some tape to hold it if you're not picky.Does anyone know if there's a way to mount the A2U8X25S3PHS on a regular pc case with 2x 5.25" bay available ??
I plan to get this for my desktop, so I can run a few U2 NVME drive that I have, but I am concerned that there's no way to secure the drive bay in my case (HAF932 Advanced). I would appreciate it if someone who owned one of these can take a picture from the side angle, I am curious to see whether I can use some powerful double tape or hot glue to secure it.
I never installed a driver. I should check and see if it's still griping about a missing one or not. Since the card is really just a PLX PCIe bridge (which shouldn't need a driver) and the drives are PCIe devices, there shouldn't really be anything that *needs* drivers, although perhaps one could help to deal with port->bay mapping.Greetings,
I picked up the Intel pci switch (AXXP3SWX08080) and was wondering about where the driver was sourced? I'm using an MSI MEG Creation x399 w/a 2990WX and win10 pro. The card is showing up as a driver-less memory controller. Windows claims to not be able to locate a driver on its own and I've looked all over and can't seem to locate one either. Even tried Intel's less-than-friendly dl center for an R2000WF family to see if I could find a suitable discrete driver there; no joy.
Any assistance would be grand.
Thanks!
Well, Intel's 2U server chassis would be easiest. After that, most desktop chassis that will take double-height 5.25 devices shouldn't be *too* bad, but you'll have to improvise some sort of mounting system. They're exactly the same height and 4mm narrower than 2 optical drives stacked. Like I said above, double-sided tape and 2mm shims would probably work fine, especially if you have something underneath to support the weight a bit.What chassis' would these easily install into?
That was my initial expectation but when it didn't work as expected, self-doubt crept in.I never installed a driver. I should check and see if it's still griping about a missing one or not. Since the card is really just a PLX PCIe bridge (which shouldn't need a driver) and the drives are PCIe devices, there shouldn't really be anything that *needs* drivers, although perhaps one could help to deal with port->bay mapping.
Yuck. At the very least, I never had any issues with NVMe devices showing up in my BIOS, which obviously doesn't require any extra drivers. This sounds like a cable problem to me, but I'd expect the oculink->8639That was my initial expectation but when it didn't work as expected, self-doubt crept in.
Operating back on the no driver required idea, I am still unable to see any of my NVMe devices. The bay I'm attempting to use is the icydoc NVMe 4 bay widget. I have two, nothing from same/different 960 or 970 Pro devices in u.2 sleds 2 different manufacturers (one was linked earlier in this thread (red pcb a bit naked), the other is fully enclosed aluminum black powder coated) works.
I have:
oculink -> sff8643 minSAS HD cables.
oculink -> sff8639 cables.
No joy from any of the above even direct 8639 to either sled.
SSDs themselves _do_ work just fine in the motherboard m.2 slots and in an ASUS hypercard.
I also have a Broadcom 9405W-16i which requires sff9402 (refclk) wiring of the sff8643 miniSAS HD cable. My initial set of cables were _NOT_ of the new hotness. I now have part no. rhs36-2583 from microsatacables which they claim to be of the new hotness. And they also provide no joy. I'm wondering if the icydoc units are just plain still born pieces of trash. Every port in 2 units being bad seems problematic. Nor does it seem probable that the design could work at all w/out being plumbed to expect the 9402 wiring variant of the 8643 connector.
On boot, the legacy bios init of the Broadcom board does not detect any devices beyond itself and a virtualses device. In Linux, this gets enumerated as the first entry in /proc/scsi/scsi. But no nvme devices show up.
I'm just about ready to beat everything w/a hammer, burn it all in effigy, and send the ashes back to each vendor w/notes telling them to die in a fire. This should.not.be.this.hard.
Other than, apparently wasting stupid sums of $$$ at the moment, I don't see the error(s) in my process.
Any ideas? Has anyone gotten the icydoc cages to work? I was going to call them later on this morning for clarity on their wiring expectation. Beyond that I'm out of ideas. Well outside microsatacables not being truthful regarding their claimed adherence to the sff9402 wiring spec anyway.
Thoughts?