M.2 NVMe Clone BOX Bus Power USB 10G allows you to copy M.2 NVMe SSD without a PC
Click here to post a comment for M.2 NVMe Clone BOX Bus Power USB 10G allows you to copy M.2 NVMe SSD without a PC on our message forum
Loobyluggs
Nice
Jagman
Useful. I've only got a single USB 3 M.2 NVMe adaptor at the moment so I'll need this or something like it in the near future.
schmidtbag
The phrasing of "an external SSD enclosure" is a bit ambiguous if you're able to access both drives or if the secondary drive is strictly limited to cloning. If it is limited to just cloning, I don't understand the appeal of this enclosure, considering there are faster or more cost-effective ways of cloning something.
If something like this could support JBOD or perhaps even RAID, that would be pretty cool.
This adapter is also a USB 3.2, unless you're saying you've got a gen1 port (which is slower).
Jagman
@schmidtbag The single one I have is USB 3.1 and yes I use it for cloning.
schmidtbag
Oh whoops I read it as 3.2 but you said USB 3 M.2, my bad.
Also just to clarify: I think it makes perfect sense to have an external enclosure for cloning purposes - I've done the same. What I don't get is having the enclosure itself do the cloning. It would be faster, more user-friendly, and more cost effective to just get single-M.2 external enclosure and clone the internal drive to the external enclosure.
The only time this enclosure would make sense is if you're trying to clone 2 external drives, but if they're both already external, I'd rather just take the slower bandwidth than to keep swapping enclosures.
TLD LARS
This is made for me, I have somehow managed to fuck up the OS on 4 drives when 1:1 cloning with 2 different software.
Never lost data from the doner disk but somehow messed up the boot on it anyway. I am suspecting I am fighting with the running OS when copying busy or protected system files.
schmidtbag
Depending on what happened, your clones might have actually been fine but not under the conditions you expected. There's a lot that can go wrong with cloning where the donor is fine. Off the top of my head:
If the destination drive is smaller and you do a byte-for-byte clone, you can corrupt the filesystem since it's missing the end piece. This is worse if you're using NTFS or FAT since the data isn't written consistently contiguously (hence the need for defragging, when other filesystems don't). Often, I'll shrink the partitions with about a GB of headroom. A byte-for-byte clone will still produce an error but it should still yield a fully functional clone. From there, I expand the partitions to the full size of the new disk.
If the UUID is also cloned and both drives are accessible to the same PC, the OS is going to be confused about which one to read from.
If you have SecureBoot on and the clone isn't used as a byte-for-byte replacement, I'm sure you're going to have a bad time, though I've never experimented with this.
If you're trying to transplant the clone into another system with different specs and you're running Windows, you might have issues with ACPI table conflicts
Some drives are formatted with MBR, some with GPT. The OS and the cloning tool have to agree with which one you're using.
stereoman
Too expensive for what it is, you can get a cheap m.2 enclosure off amazon for a quarter of the price and just use macrium reflect or one of the other cloning softwares, job done.
rl66
It's not for the same user 🙂
From my experience, everything cheap from amazon, ali, and so... are not reliable on long time use (and some can even be worse (maybe i point some ali stuff))
The main important info there is "direct cloning", usefull to prepare on mobility, a small quantity of M2 to deploy on PC as the quick release is indicated there.
