The system doest reconize my SSD disk M.2 Brand new alienware
I boot from the cd of acronis 2017 and the system doest see my c: dirve ssd m.2
I created bootable on usb drive same thing the system dont see my ssd m.2
I am not sure if I need to created WINPE-BASE bootable maybe


- Se connecter pour poster des commentaires

Mike,
Have a look at your machine bios and the SATA mode setting. If your setting is RAID, which I suspect it is then you will need to create WinPE boot media and inject Intel RST storage controller drivers into that build so that you can work with your drive.
- Se connecter pour poster des commentaires

I wonder if Acronis has yet to get to grips with m.2 drives.
The ATI2016 > ATI2017 update caused me minor grief because the PC would not boot after the update:
PC will not boot after ATI2016 to AT2017 upgrade | Acronis Forum
ATI2017, and ATI2016 before it, had no problem seing the drive, but the update process fell over because Acronis recovery's boot manager could not find the drive. I had to dive into the BIOS and remove that entry from the boot order.
- Se connecter pour poster des commentaires

Michael,
Would you send in feedback on this? Use the in app feedback feature and include a system report. The ASRM uses the default Linux recovery environment which at this time does support PCIe NVMe drives if the installed OS was performed as an SATA AHCI mode installation. If the OS install was performed with SATA mode set as RAID then the ASRM/Linux re4covery media does not recognize the drive due to the absence or lack of RAID controller drivers.
Additionally, would you PM Mikhail Krivtsov at the link below and provide all details that you possibly can including letting him know that you sent in feedback with the system report attached?
https://forum.acronis.com/messages/new/228599
It is possible that support in the ASRM has issue which is something that needs to be investigated along with that of the stand alone Linux recovery media.
Thanks.
- Se connecter pour poster des commentaires

Hello Mike, Michael,
Thank you for reporting the issues here on the forum. Like Enchantech said, a WinPE with custom drivers would be a good alternative to the normal bootable media which is based on Linux.
To help us in resolving the original issue in the first place please contact us. Issues with bootable Acronis environment, boot order and Acronis loader require a system report collected from the default Linux-based bootable media. It contains diagnostic information about your particular setup that would help to address the issue in the future versions of the software.
Regards,
Slava
- Se connecter pour poster des commentaires

In mos t cases, the M.2 drives are not detected if they are
1) PCIE
2) the sata mode is set as RAID
Current versions of 2016 and 2017 work fine with all versions of M.2 drives when the SATA mode is AHCI. If you have a non-RAID setup and the bios is SATA, it should be picked up. If you have a single NVME PCIE m.2 drive, many OEM's are putting them in RAID on the bios, even though they are a single drive. This is because PCIE can take advantage of deeper queue depths (increasing perfomance) when the controller mode is RAID, as AHCI queue is more limited.
If using a single NVME PCIE m.2 drive, you can change the bios SATA mode to AHCI temporarily and then backup or restore with the default Linux media. Then switch the bios SATA mode back to RAID before booting.
Ideally though, to keep things as they are are and get the best performance out of your drive, WinPE is the way to go. Do submit details to support for review, but I would suggest downloading the Windows 10 ADK (1511) - it's linked below and install the top 3 items (3.4Gb though!). Once installed, Acronis can make a WinPE bootable disc.
To take this a step further and ensure you have the proper Intel Rapid Storage Technology (IRST RAID Controller) drivers in your WinPE already, try using our MVP ATI WinPE builder - it's really simple to use and works great. The link for the download is also below.
- Se connecter pour poster des commentaires