I'm getting confused by driver requirements for creating a recovery environment on my desktop system. I'm using Reflect 7.2.4557, and using the default WinRE for the recovery environment.
On this system, disk storage is all set up in Intel RAID.
  System is 2 x Samsung 970 EVO 2TB M.2 SSDs inh a RAID 1 volume
  Data is a 4 x HDs in a RAID 5 volume
Controller is the chipset Intel SATA/PCIe RST controller (i9-9900X processor)

When I look at the driver tab I was expecting to see something relating to that, but what I get is in the image below. 
Am I understanding this right??
Thanks
Alan

I admit I wouldn't have expected that if you've got the system in RAID mode to use the RST controller's RAID capabilities rather than "standard" AHCI mode.  And in fact even with a system in AHCI mode like mine, I see "Standard NVM Express Controller" listed.  But the real test will be to build your Rescue Media and test boot your system from it to see if it detects all of your storage -- which it might, because the WinRE kernel you're using might have a sufficiently new Intel RST driver already built-in.  But if your Rescue Media can't see your storage, then as a workaround, you can go to the Intel RST driver download page here.  Click the item for the Rapid Storage Technology User Interface and Driver and download the "F6 Floppy" version (a reference to the WinXP days) that's available as a ZIP file.  Then go to C:\boot\macrium\WinREDrivers\64Bit\Disk on your system, create a new folder with a name of your choice (e.g. "IntelRST") and extract the contents of that zip file into that new folder.  Even though you won't see anything new in the hardware list you posted above, since that only shows hardware that Reflect detects on that system, the driver you manually put into that folder will always be included into any Rescue Media you generate.  That should make your storage visible in Rescue, and then hopefully Macrium can provide insight into why Rescue Media Builder isn't grabbing a driver automatically if Rescue wouldn't be able to see your storage otherwise, or why it isn't displaying the device at all, which again seems odd even if no driver copy is necessary.

By the way, just as a minor note for future reference in addition to my above reply, you posted this in the Reflect V6 subsection of the forum even though you're running Reflect V7.  Just something to watch out for going forward, especially since V6 is technically no longer supported

+x

 

jphughan - 11 December 2019 8:50 PM

By the way, just as a minor note for future reference in addition to my above reply, you posted this in the Reflect V6 subsection of the forum even though you're running Reflect V7.  Just something to watch out for going forward, especially since V6 is technically no longer supported

Thanks for that reply. And sorry for the misplaced post - I've not used the forum before so I missed how the toipics were grouped.
I'll take this up in a new thread in the proper place if I need

Alan