I have this exact issue with Server 2019 Build 1809 (17763.737). I'm using an 9400-8i alongside a RES3FV288 with IOM6 modules on a NetApp DS4246. LSA in Windows shows all of the disk, but they will not show up in device manager. Latest firmware and drivers as of today.
Netapp DS2246 & LSI 3008 IT Mode Issues in Windows 10 for Workstations
- Thread starter thorondorwest
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
reviving this thread....any luck to show up the drives in Windows Disk Manager, with DS4246 and any LSI HBA card ??
I just had this adventure. When looking at the rear of the DS4246, use the left side SAS connections. The right ones will work for SAS, but not SATA as they are not electrically connected. Looking at the rear of my unit, I have it plugged into the right SAS connector, on the left SAS controller unit.
I've been struggling with getting my new (to me) DS4246 shelf, a 9300-8e, and Windows Server 2022 (on a Dell R730) all talking to each other. They all work great in Ubuntu, TrueNAS, and Proxmox. No issues, they can all see all 24 drives. I can even daisy chain to a DS2246 and it sees those 24 drives as well.
The problem is the blasted Windows support. Windows has the driver just fine for the 9300-8e. It sees it, I can query it with sas3flash, and I even updated the IT firmware on it from 10 to 16. But it will not see any drives at all. In the Windows event log it throws an error (presumably one error for each drive, plus maybe one for the entire enclosure) saying:
\Device\RaidPort0 Enclosure not found (ContinueIDReadsForPhyEvents)
What I'm getting from that is that Windows, for whatever nutty reason, just doesn't like that combo of the SAS3008 and the netapp drive shelves. The fact that it works great in any other OS is comforting because I know it works in general, but I was really hoping to do some things with Windows.
I may just "downgrade" myself to something like a 9200 model controller (9207-8e I think?). I mean, the shelves are IOM6 so I'm not really going to be pushing too much through it. For now it's just something for me to tinker with.
One "solution" I did try earlier was to use Proxmox on it, create some mega RAIDz2 pools on there and then install Windows Server as a VM. So, I mean, I could just do that if I wanted to have the large drives and Windows. Right now I'm reinstalling TrueNAS on there for some further fussing and tomorrow I'll decide if I'm happy with some Linux flavor in there with a sprinkling of Windows on the side, or if I just spring for a different card (and different cable as well since the 9300 uses different connectors). Even then, how could I be sure that Windows isn't also going to ignore it with those cards as well? Honestly, I just don't get what the deal is with Windows... you'd think it would just work, but no... So close, but so far.
The problem is the blasted Windows support. Windows has the driver just fine for the 9300-8e. It sees it, I can query it with sas3flash, and I even updated the IT firmware on it from 10 to 16. But it will not see any drives at all. In the Windows event log it throws an error (presumably one error for each drive, plus maybe one for the entire enclosure) saying:
\Device\RaidPort0 Enclosure not found (ContinueIDReadsForPhyEvents)
What I'm getting from that is that Windows, for whatever nutty reason, just doesn't like that combo of the SAS3008 and the netapp drive shelves. The fact that it works great in any other OS is comforting because I know it works in general, but I was really hoping to do some things with Windows.
I may just "downgrade" myself to something like a 9200 model controller (9207-8e I think?). I mean, the shelves are IOM6 so I'm not really going to be pushing too much through it. For now it's just something for me to tinker with.
One "solution" I did try earlier was to use Proxmox on it, create some mega RAIDz2 pools on there and then install Windows Server as a VM. So, I mean, I could just do that if I wanted to have the large drives and Windows. Right now I'm reinstalling TrueNAS on there for some further fussing and tomorrow I'll decide if I'm happy with some Linux flavor in there with a sprinkling of Windows on the side, or if I just spring for a different card (and different cable as well since the 9300 uses different connectors). Even then, how could I be sure that Windows isn't also going to ignore it with those cards as well? Honestly, I just don't get what the deal is with Windows... you'd think it would just work, but no... So close, but so far.
I recently did another experiment involving Windows Server. I setup Hyper-V and then configured the SAS 3008 / 9300e to pass through to a TrueNAS virtual machine under Hyper-V. That works fine and even though Windows never could see the drives in the Netapp shelf, the passed through card on TrueNAS saw all the drives just fine. That's a better solution in my case. For "reasons" I needed the bare metal to run Windows (running a virtualized Windows was showing some pretty severe performance issues for my use case) but letting TrueNAS talk directly to the adapter is fine and I haven't noticed any performance issues with that.
Another "solution" I found was to use a SAS 2308 adapter instead. Doing that, Windows was able to see the drives in the expander just fine. I could have just used it in this case and let Windows do all the heavy lifting for the drives, but honestly, after seeing what TrueNAS can do compared to the ghastly performance of Windows storage pools, I never want to let Windows manage large arrays again. It's a night and day difference. I could never get my interleaves and columns to work anywhere close to the performance of ZFS, and then just having the Z1 or Z2, being able to setup hot spares, allocating some faster drives to L2ARC or whatever. It's a no brainer.
So I'll probably stick that 2308 into another server connected to some other Netapp shelves where maybe I'm okay with Windows talking to things (or it's more necessary), but for this one particular use case, the 3008 passing through Hyper-V to TrueNAS is definitely a winner.
It's still baffling that Windows can't natively see any drives in that expansion chassis, and only with a 3008 adapter, but the 2308 (and presumably other SAS2) works fine. Whaddya gonna do though. As has been pointed out, you don't really need SAS3 when talking to the Netapp IOM6 controllers, but I got it originally over a 2308/9200 model just because the prices on ebay were so similar I figured I could future proof myself if I ever did move up to something else.
Another "solution" I found was to use a SAS 2308 adapter instead. Doing that, Windows was able to see the drives in the expander just fine. I could have just used it in this case and let Windows do all the heavy lifting for the drives, but honestly, after seeing what TrueNAS can do compared to the ghastly performance of Windows storage pools, I never want to let Windows manage large arrays again. It's a night and day difference. I could never get my interleaves and columns to work anywhere close to the performance of ZFS, and then just having the Z1 or Z2, being able to setup hot spares, allocating some faster drives to L2ARC or whatever. It's a no brainer.
So I'll probably stick that 2308 into another server connected to some other Netapp shelves where maybe I'm okay with Windows talking to things (or it's more necessary), but for this one particular use case, the 3008 passing through Hyper-V to TrueNAS is definitely a winner.
It's still baffling that Windows can't natively see any drives in that expansion chassis, and only with a 3008 adapter, but the 2308 (and presumably other SAS2) works fine. Whaddya gonna do though. As has been pointed out, you don't really need SAS3 when talking to the Netapp IOM6 controllers, but I got it originally over a 2308/9200 model just because the prices on ebay were so similar I figured I could future proof myself if I ever did move up to something else.
Best days of Windows as a product are behind it. Now it is ads in the start menu and below par technical solutions and enshittification wherever you look. Windows GUI designers are supposedly using Macs. They are not even dogfooding their own creation, what a management gaffe.
Maybe you picked a bad driver for the SAS 3008 card? Broken or no longer clean storport while the SAS 2308 driver is still okay.
Maybe you picked a bad driver for the SAS 3008 card? Broken or no longer clean storport while the SAS 2308 driver is still okay.