Sabrent 2TB Rocket NVME (TLC,pcie3.0) not recognised by Acronis connected via USB 3.1 NVME enclosure
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.
Attachment | Size |
---|---|
Sabrent Acronis recognition issue via NVME SSD USB enclosure.jpg | 26.07 KB |
Sabrent Acronis recognition issue via NVME SSD USB enclosure2.jpg | 219.62 KB |


- Log in to post comments

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 :)
- Log in to post comments

@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
- Log in to post comments

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!
- Log in to post comments