Cannot see SSD Windows Drive
Hi all
Just bought a Lenovo Ideapad Y700 which comes with a 128GB SSD where Windows is installed and a 1TB hard disk. I boot TrueImage 2015 from a CD and want to image my SSD drive. However, it is not visible. Only the hard disk is. In disk management, both disks are "Basic" not "Dynamic".
Any clues?
(I also have a Dell XPS 13 with only a single SSD and that one IS visible)
Thanks to all and Happy New Year!
Alexis
Just to clarify... NVME drives are not an issue with the Linux media. The default linux media can see both NVME and eMMC hard drives. The issue occurs when the system bios is using RAID as the SATA mode instead of AHCI. When using RAID, the default Linux media does not have RAID controller drivers so will not detect the hard drive. As a result, using WinPE with the proper RAID controller drivers (usually IRST will work), is what is needed. However, others have also been able to use the Linux media, by temporarily changing the SATA mode in the bios from RAID to AHCI, then doing a backup or restore, and changing it back to RAID before booting the OS. This work-a-round will only work if you have a single drive in RAID mode though. If you are using an actual RAID set (0, 1, 5, 6, 10, etc), then you must use WinPE and include the RAID controller drivers in it.
The MVP WinPE tool makes all of this pretty simple though. Just install the Windows 10 ADK first (3.4Gb of items when you select the top 3 options which are needed). From there, run the MVP winPE builder and it will do the rest for you.
Rob, not sure you are correct with respect to NVMe drives and ATIH 2015 linux Rescue Media - my understanding is that support for these drives was added to the later builds of ATIH 2016 and to 2017, so would not expect to find this with the 2015 media. The MVP WinPE tool cannot be used with ATIH 2015 either.
Thanks Steve, You are correct. Forgot this was the 2015 forum. 2016 brought NVME support in the third to last release. With 2015, WinPE is the way to go. If the SATA mode is RAID they'd also have to install IRST drivers separately with dismgui or the default adk disk commands.
Hi to both and thank you for you detailed posts. Although I am an IT person I am not conversant with bus and protocol technologies like you are and I don't know whether my drive is NVMe. How do I tell? Perhaps your feedback on this will allow me to confirm why the Acronis CD works on my 1-yr old Dell with SSD and not on the new Lenovo Y700. Also, when creating the WinPE rescue image should this be created on the same PC that I want to use it on i.e. does it load that PC's drivers to the image or is the rescue image generic and can be used on any PC as is currently the case with Acronis CD?
In any case, I followed the Help instructions and installed the Acronis Media Add-on and then installed ADK for Windows 10 (I did this on my PC which has Acronis 2015 installed). I rebooted and then started Acronis, chose Tools, Acronis Rescue Media Builder, WINPE-BASEDMEDIA WITH ACRONIS PLUG-IN, and the next screen seems not to recognise that the above have been installed. I attach a Word file with some screenshots as well as MSINFO32 for the 2 disks on the Lenovo PC where I face the issue.
Many thanks for your help.
The msinfo.txt document shows your two disk drives as follows:
Seagate 2.5 inch mobile drive - ST1000LM035-1RK172 - which is a SATA 6GB/s connected drive.
Samsung NVMe M.2 PCI Express Gen3 x4 SSD on a card drive - SAMSUNG MZVLW128HEGR-000L2
I suspect that ATIH 2015 Rescue Media Builder is not recognising your Windows 10 ADK because it came a long time after the 2015 product, the ATIH 2015 User Guide - Acronis Media Builder section states:
-
To use this option, you need the following components to be installed:
- Acronis Media Add-on. You can download it from the Acronis website.
- One of the following:
- Windows Automated Installation Kit (AIK).
This component is required for creating WinPE 3.0.
- Windows Assessment and Deployment Kit (ADK).
This component is required for creating WinPE 4.0 and WinPE 5.0.
- Windows Automated Installation Kit (AIK).
Notes
- We recommend that you create a new bootable media after each Acronis True Image 2015 update.
- If you use non-optical media, the media must have FAT16 or FAT32 file system.
- Acronis Media Builder supports only x64 WinPE 3.0, WinPE 4.0 and WinPE 5.0.
This WinPE distribution cannot work on x86 hardware. - A PE image based on WinPE 3.0 requires at least 256MB RAM to work, for WinPE 4.0 and WinPE 5.0 this requirement is 512 MB.
Yeah, the Windows 10 ADK wasn't available when 2015 was released so it's looking for Windows 8.1 ADK. If you remove the Windows 10 ADK and install the latest 8.1 ADK, you should be able to build the Acronis WinPE (keep in mind, you're still going to need to inject the IRST drivers after it's created).
Build your rescue media with Windows 8.1 ADK - preferably to a USB flash drive.
Copy the boot.wim file from "sources" on your newly created USB and put it in a folder that's easy to find. Make sure the folder has "full access" for all users or authenticated users - just makes it easier.
Then grab DISM GUI - this will make it easier to inject the IRST RAID drivers into your boot.wim. Make sure to launch it with right-click and "run as administrator" when it's time (do this for any installer or application these days - it's the only way to give full admin access with UAC).
Then grab the latest Intel IRST RAID drivers and make sure you grab the right architecure - assuming x64. Have them extracted to a folder that's also easy to access.
Now, run DISM GUI. Point it to your copied boot.wim and to an empty folder (again something easy to get to and give all users or authenticated users full access first - just makes it easier). Then press mount and it will mount the boot.wim to that folder automatically.
Click on the next tab and point the drivers to your extracted IRST x64 driver folder and inject them.
Go back to the 1st tab and click on "dismount wim". When it asks if you want to commit the changes - say YES. When it's done, go and copy the boot.wim you just updated into the sources folder of your USB. You know have WinPE Acronis media with IRST drivers baked in.
In reply to Rob, not by truwrikodrorow…
I believe you are both erroneous , I have a Gigabyte gaming laptop NVMe SATA and a 2T Back up drive , No Raid.Using the latest 2018 Acronis only the 2T is recognized .
I was able to clone the NVMe to a 2.5" SATA using Mini Partition Tool , however i have not tested the 2.5 Sata as yet, I need to Clone it to an SSD .
I am not able to create an Image of the NVMe drive .
Windows built in image creator seems to create an image, however when using Rescue disk or USB and booting from either...apparently there is no Image back up ,even though I do see it on the 2T Hdd .
Reading on the net it is reported that there is No gain from NVMe drives as compared to a regular SSD .
Acronis support have not been able to understand the above problem and continued to placate me with some Mambo Jumbo ...they do not comment on the fact that Image creation is Not possible, with Acronis 2018 or any previous versions.
The universal Acronis boot disk is using "universal" drivers is not always able to handle the NVMe drives.
In order to sort it out we just need an installation of Acronis True Image under Windows 10.
Windows 10 has all the needed drivers to handle the M.2 NVMe so Acronis True Image will recognize the proper context of the environment and will offer to create the possible best boot disk based on the running Windows 10 system.
After booting up from the new boot disk, not only will recognize the NVMe drives but even the GUI will have the native resoultion.
Good Luck.
If you get a new SSD and it won't show up in the Windows Explorer, it's likely in the "uninitialized" state. You must initialize a disk before Logical Disk Manager can access it. Also, for an old SSD that shows the error 'disk unknown not initialized', the result is the same