I wonder if you would be interested in investigating an issue I had between Intel RST in RAID mode and an optical drive.
I eventually made it worked but in such a odd way that I still want to investigate it further and go to the bottom of this issue so Intel can fix what's really looks like a bug in RST.
So here is the thing.
I have an ASRock Q170m vPro mobo:
built around 'SkyLake' Q170 chipset.
I have a 4 x 500 MB SSD in RAID 0 using the legacy INTEL RAID rom option (not UEFI) because it is < 2 TB
I have WIndows 10 Pro x64 recently re-installed from scratch with latest RST driver from Intel download (I provided the driver during installation à la 'F6'): Version: 220.127.116.110 (Latest) Date: 10/20/2016
So far so good.
In order to enjoy Blu Ray 3D I had NO choice but to buy an optical drive, and I got a PANASONIC/MATSHITA BD-MLT UJ265.
Although the drive was perfectly recognized by the BIOS and then Windows 10, as soon as I insert a data media, and click on it in Windows Explorer, the drive disappears and Windows is telling me that it has been unplugged.
I tried many times, and each time the drive vanishes with no recovery option than reboot.
Googling on internet, I found this on Microsoft
the last comment on page 2 says:
"Had the same issue with my custom build htpc. I'VE SOLVED THIS BY ENABLING HOT PLUG FUNCTIONNALITY FOR THE SATA-PORT WHERE where the dvd-rom was attached to. Afterwards the device was working properly :).
In my case, there weren't any UpperFilter or LowerFilter values set.
And I confirm it is also working perfectly for me right now.
So on one hand:
a configuration that does NOT work when Hot Plug is NOT enabled on the specific SATA Port used by the optical drive)
and on the other hand:
a configuration that DOES WORK (when Hot Plug IS ENABLED on the specific SATA Port used by the optical drive)
because other threads on internet confirmed that this situation only occurs when an Optical Drive is used with Intel RST RAID mode, would it be possible for Intel to investigate what is the differences and consequences (in the code, configuration, behavior, ...) that could explain this situation ?
because honestly I found odd to be forced to set an internal optical drive as 'hot plug' capable to make it fully work under windows.
What do you think ?
Please advise and Happy/Healthy New Year to all of you.