Skip to main content

Sabrent 2TB Rocket NVME (TLC,pcie3.0) not recognised by Acronis connected via USB 3.1 NVME enclosure

Thread needs solution

Hello,

I've attached a pic of it but I've tried connecting a Sabrent Rocket 2TB NVME unit (TLC, PCIe3.0 variant) to my laptop with only one occupied NVME slot via usb 3.1 port. As per the picture the Acronis software they recommend doesn't recognise the Sabrent unit when connected via the enclosure.

I've tried two other methods via OS migration wizard (Minitool Partition Wizard) and Macrium Reflect clone disk but each time they complete and I try swapping out the drives, I get windows 10 boot errors (latest build etc.). I also tried repairing the boot sector via the Macrium tool. I'm a little worried about a couple of large read only partitions that have appeared too.

What is the best/recommended method to get the entire previous drive with all data/sectors/partitions onto the new drive? I didn't have this problem in the past with Samsung drives but have opened a support ticket with Sabrent before jumping to returning the unit to Amazon UK.

Thanks in advance for any help/advice. Funny this one still an issue and NVME still not very mature.

0 Users found this helpful

Lynton, welcome to these public User Forums.

See KB 2201: Support for OEM Versions of Acronis Products which applies to all OEM versions of ATI supplied with hardware purchases.

The core issue here is that using an external enclosure makes the Sabrent NVMe drive appear as something else due to the extra hardware it is connected via.  This is a known issue when using such adapters.

The second issue here is that cloning any laptop drive to an external drive will often cause that external drive to be non-bootable when installed inside the laptop, again because the connection method is no longer the same!

Please see KB 56634: Acronis True Image: how to clone a disk - and review the step by step guide given there.

Note: the first section of the above KB document directs laptop users to KB 2931: How to clone a laptop hard drive - and has the following paragraph:

It is recommended to put the new drive in the laptop first, and connect the old drive via USB. Otherwise you will may not be able to boot from the new cloned drive, as Acronis True Image will apply a bootability fix to the new disk and adjust the boot settings of the target drive to boot from USB. If the new disk is inside the laptop, the boot settings will be automatically adjusted to boot from internal disk. As such, hard disk bays cannot be used for target disks. For example, if you have a target hard disk (i.e. the new disk to which you clone, and from which you intend to boot the machine) in a bay, and not physically inside the laptop, the target hard disk will be unbootable after the cloning.

Personally I have not used cloning with my own NVMe SSD's as I have no suitable adapter to connect 2 with and have no systems with 2 slots for this type of drive, therefore I have always used Backup & Recovery to migrate to a new or larger drive.

The steps in outline are as follows:

  1. Create the Acronis Rescue Media (use the Simple option for WinPE)
  2. Test booting your laptop from the rescue media, ensuring you understand how to boot in UEFI mode and can 'see' your current SSD drive and an external backup drive to hold a full disk backup image.
  3. Make a new full Disk backup of the working SSD to an external drive as a one-off backup action.
  4. Shutdown the PC, remove the current SSD and install the new SSD.
  5. Boot from the Acronis Rescue Media with your backup drive connected.
  6. Recover the Backup from step 3. to the new SSD.
  7. Check the Log messages before exiting from the rescue media (all logs are lost on exit) to check all is OK.
  8. If all ok, disconnect the external drive, remove the rescue media and restart the PC normally from the new SSD.
  9. When you have confirmed all is ok with the new SSD, make a new backup again to include any new device drivers installed for the new SSD.

Note: if your new SSD is larger than the original one, then you may find that ATI has not expanded the C: OS partition to use the full new size of the new SSD.  If so, then this is quite simple to resolve as below:

First, download a copy of the free MiniTool Partition Wizard software, install this, then use it to move the Windows Recovery partition (that is shown after the C: OS partition) to the end of the available unallocated space. 

Next, resize the C: OS partition to use the available unallocated space.

See KB 63226: Acronis True Image 2020: how to create bootable media and KB 59877: Acronis True Image: how to distinguish between UEFI and Legacy BIOS boot modes of Acronis Bootable Media

KB 63295: Acronis True Image 2020: How to restore your computer with WinPE-based or WinRE-based media

 

Steve, legend indeed and thanks for all of this. I'd seen your other forum posts but the bit about the enclosure not detecting as Sabrent makes sense. I did migrate my original Asus G14 SSD to a Samsung one via these methods however which is why I thought something was different this time with Sabrent. 

I'll try some of these methods and get back to you. Something's got to work eventually :)

@Steve Smith reporting back:

So good news I have managed to achieve the migration by (eventually) finding the mediacreation tool (exe) in the Acronis win explorer folder and putting the tool on a spare usb drive. I then used the 'simple' option from the ui menu option when booting from the drive (after selecting in BIOS), and this did a very straightforward clone from source (now my 'original' drive connected in the external usb3.1 nvme enclosure) to destination/target Sabrent drive (now in the m.2 pcie slot in my laptop). I then shut down, did the swap. There was a blue screen startup error after this which then seemed to repair but only after I went into advanced startup and applied the 'startup repair' option. A reboot after that miraculously made it all the way through windows10 bootup, no data loss and as I was before but now with double the space via the 2tb nvme Rocket. A bit of a process though and someone not so confident with this stuff might have struggled. A couple of suggestions:

1. The information via a hyperlink or something re media creation tool for using external drives to migrate (rather than the simple error 'not-detected' as per my screenshot here would surely be a better user experience?

2. why not uplift the True Image tool to be able to detect beyond the enclosure's hw signature to recognise the inserted Sabrent drive?

should I mark your message above as 'solution' based on this?

Thanks, Lynton

Lynton, good to read of your successful migration.

You can use the Feedback tool to pass on suggestions to Acronis about hyperlinks etc.

With regards to hardware detection, that is only a limitation in the OEM versions which have been 'crippled' to have a requirement to identify a drive of the vendor make - this does not apply to the full commercial version, but that isn't given away for free with hardware purchases!