System is X299 Sage BIOS 3701, it does have PEX switches for the PCIE lane allocation and my system is full slot wise.
I’m thinking whether its because of the slot running at x8 and /or the fact I’m using the side ports of the P411-32P and not the top, several things to try I guess.
I can get Windows 11 22H2 to boot with the latest firmware but as you said no drives detected. Pre 22H2 also seems to work with old firmware.
BSOD’s happen even with no cables attached… issue is not memory related, no issues with the card removed.
You think I can get away with using the “Diamon PCI-E SFF-8643 Expansion Card” with linux? I know it explicitly says for windows only but I don’t see why it wouldn’t work.
Looks like it won’t even hit gen3 speeds though, which is all I need.
Yes, only second-gen Optane with the P5800X models are PCIe 4.0, everthing earlier is only PCIe 3.0.
PCIe 3.0 is “easily” doable with current products, I’d still go for components that claim to do even PCIe 4.0 to be as safe as possible.
Another short review of mine for 4 x U.2/U.3 is coming soon, seems to be in fact capable of PCIe 4.0 but I could only test it on an ASUS motherboard that doesn’t have an UEFI option to enable PCIe Advanced Error Reporting - what makes me relatively optimistic is that multiple units of the same U.2 SSD model perform very, very similarly at their maximum expected performance, meaning no data transfer seems to be lost to error correction.
If you’re having constant BSoD issues with the P411W-32P make sure to:
Flash the older firmware P14.2, not the current P14.3 (no SSDs show up).
Danger: Drivers P23 don’t work (signature issues), drivers P18_0 only work with the non-functional firmware P14.3, using them with the earlier working firmwares will lead to a BSoD during booting, even if there are no SSDs connected to the P411W-32P.
To get rid of problematic drivers remove the P411W-32P from the system, Windows should be able to boot again.
Then go into Windows Device Manager, show hidden devices and uninstall all Broadcom storage controller entries and be sure to check the option to also delete the driver files.
Then you should be able to reseat the P411W-32P, boot and use it with the old AF Windows default drivers or test Broadcom’s drivers up to P16. An issue I have not been able to address is the P411W-32P causing a BSoD after letting the system go to sleep (S3) and waking it up again. Connected SSDs still show up seemingly normal but no data on them can be changed and after a short while you’ll be greeted with a BSoD (something about Power State Failure).
If anyone is still interested in making an M.2-to-U.2 enclosure solution work, I found a set-up that’s working for me so far with 0 PCI Express AER events in my Windows Event Viewer system log after putting the PCI Express 4.0 drive under load for 30 minutes.
I used a passive M.2-to-OCuLink adapter, but a 25cm (yeah, this short length is the caveat) active OCuLink cable from LINKUP. They have a 50cm version too, but that one did not work for me. I got 42 error events after 30 minutes putting the drive under load.
I picked up this low profile delocke card and will be testing it later today when the cables arrive. Have x2 12.8tb micron 9300 max nvme ssd and some other dc Intel cards 400gb I think as cache maybe? I’m trying to fit it in 1u as I can but in practice much/most seems 2u (if only I’d gotten right or LT facing angled cables.) Still have to figure out a brack situation for them as they’re larger than my other ssd’s and not willing to spend the icydock cash again when something like sendcutsend with a little backplane could be done less expensively I think/maybe/idk.
Does something like this seem like a lie? They have lots of charts and graphs, supposedly supporting it’s viability – for whatever that’s worth.
It’s using a redriver card, and a 50cm length “Slim-SAS SFF-8654 4i to SFF-8639 U.2” cable.
I could probably live with using SlimSAS 4i SFF-8654, or even OCuLink 4i SFF-8612, cables in 25CM, but 50CM would be even easier. Maybe going straight to a U.2 SFF-8639 drive connector would be less demanding then piping into a drive bay, so PCIe 4 with a 50CM cable might be doable? Or no?
No, parts with PCIe Gen4 ReDrivers are available (for example various adapters sold by MicroSATACables).
I had a little bad luck with a few units arriving DOA (M.2-to-SFF-8654), but that can happen to any manufacturer when looking at how packages are handled.
I just tested the Micro SATA Cables M.2-to-OCuLink adapter with a redriver and a 50cm active OCuLink cable. There are less WHEA events, but still I got 6 in just a minute of random reads. Turning on the motherboard’s special redriver settings lowered the number of events by about a half (I was no longer getting them when the drive was not under load), but they were still there.
I even purchased the 75cm and 100cm ones (also claimed to be PCIe 4.0-ready) for testing in case the 50cm one worked with the redriver, but looks like even 50cm is too long of a length. I’m starting to think PCIe 4.0 over a cable is just not meant to be.
But don’t take my word for it. I’m just a newcomer to this stuff. Still hoping someone finds a workable and reproducible solution and shares it.
EDIT: Out of curiosity, I also tested the 75cm cable. 16 WHEA events in less than a minute. 100cm is out of the question. Supermicro sells a 37cm cable (not active AFAIK). Not sure if I want to buy one just to test the lengths in between 25cm and 50cm.
ohhh no~ help~after the step erase my p411w show the yellow led(system error ) and i can`t find any device in g4xflash tool…what happened!!!
is there any way to save my card byself？
Looking back, this should have been so obvious. I had already bought their adapter first thing, so why not their cables—which explicitly advertises PCIe 4.0 support—too?
I decided to reach out to Broadcom over the weekend regarding the missing drives issue when on the latest firmware.
Here’s a screen cap of the email I received.
Just sent an email requesting the beta too.
I’ll try to post it when I receive it.
On initial 0.1.0.0 firmware, everything shows up. However, upon updating to the latest (v4.1.3.1 - Shows up as v1.3.1), absolutely nothing will show up regardless of motherboard (Supermicro, Asus, etc…) or settings. HBA shows up in both Linux and Windows though.
With the previous update (v4.1.2.1 - shows up as v0.1.2.0), everything shows up and functions as it should.
A variety of systems and SSDs by various manufacturers were tested to no avail. Different cables were tried too. I have heard Seagate SSDs work, but have not been able to test that particular variable. I’ve personally tried SSDs by WD, Samsung, and MSI.
The latest firmware hates Samsung SSDs. Nothing shows up regardless of OS or motherboard firmware. It plays a little bit nicer with WD SSDs and will at least show the (WD SanDisk) NVMe controller when attached, but still no storage medium.
I have been working with another entity who suffers from the same issues. A new card does not resolve the issue.
but the bad news is they aren’t SFF-8654 to SFF-8639… They do have them here:
