Oh, man, I just ride in 'em ... I don't what makes 'em work.
1- SYSTEM_DRV (None) FAT32 (LBA) Primary
2- (None) Unformatted Primary
but when the cloning process gets to Volume "3 - Windows (C) NTFS Primary I immediately get the error.
Note both drives pass chkdsk /f successfully, and Win 10 Pro "Disk Management" reports both drives as healthy. Initialization of the 256 GB SSD goes smoothly / quickly, the computer finds the new "D" drive and volumes on it with no problem (once intialized*), and I can store typical files such large jpg's, or docx or odt or pdf's and retrieve them later with no problem.**
I have not yet tried running chkdsk /r, nor have I tried running the utility "ExactFile".
**Note that trying to clone the eMMC boot / OS drive to the SATA drive and failing renders the SATA drive unusable until I initialize it again, but it does re-initialize without any problem, and again initialized, again it does not show any errors via chkdsk or Windows.
A discussion of this issue (or at least quite similar) from person (not me) on the Macrium forum abruptly ended without resolution. Initial comments narrowed the problem down to the source data, as that's what is verified at this point in the process.
https://forum.macrium.com/55180/Full-Disk-Image-fails-when-Verify-File-System-is-set-to-Y
Macrium indicated they thought it was a hardware problem, but, also indicated that an older version (Macrium 6) might "stress the hardware less", implying there might be a heating problem. In my case it appears that's not "it": I tried (still using Macrium 8) to run the clone process with the N22 allowed to stabilize in a room at 74 deg. F, and again at 50 deg. F, and detected no difference in the timing / onset of the error.
Macrium also has this page on verification errors, but it appears to be devoted to verification of the backed up files on the destination drive. (I may try cloning to a large flash drive or external SSD as a check, and IIRC I also have another M.2 SATA drive here somewhere... However, again this appears to be a data source error.)
http://reflect.macrium.com/help/v5/restore/troubleshooting_verification_problems.htm
Since the computer seems to function otherwise error free ((I'm just looking for higher speed and more storage space out of the SSD vs the eMMC), I suppose I can try turning the verification off and then see if the machine will boot and operate well off the SSD.
As it is possible(?) the eMMC is developing some problem that ordinary checks do not catch, moving the OS over to the SSD takes on a new importance... :-(
- - - - - - - -
An interesting parallel issue with the above machine is that there seems to be no hotkey to interrupt a boot and get into BIOS. Reading up on this, apparently there are other ways to set this up in Windows prior to a restart -- this is another "new one to me. Maybe the Lenovo N22 has an unadvertised call-BIOS-during-boot-up hotkey?
- - - - - - - -
Somewhat related, I read that NAND memory is best refreshed every couple years or so. This seems to me to definitely have critical implications for USB flash memory sticks used for bootable rescue and repair, not to mention long term data storage. The question is, would it be best to use somethig like Macrium Reflect to rotate data amongst similar size flash drives, rather than cloning to a destination drive, and then back, reusing the destination drive many times? I suppose all should be backed up to magnetic media (a HDD) as well -- at least big HDD's are cheap these days. But, for rescue / bootable flash drives, I'm unsure how to proceed. Set up a partition on the HDD for each bootable drive?
- - - - - - - -
Computers sure are time savers, aren't they...
https://forum.macrium.com/55180/Full-Disk-Image-fails-when-Verify-File-System-is-set-to-Y
http://reflect.macrium.com/help/v5/restore/troubleshooting_verification_problems.htm
If the filesystem is encrypted with a TPM
based key, you might not be able to clone
for a different motherboard.
As someone else says above - it may be encrypted, in which case you’re not going to get anywhere in a useful amount of time. Is the machine still bootable? If so, fire the machine up and find out if the drive has BitLocker or other encryption turned on.
Also, flash drives are *not* to be considered viable long term storage. Archival is best done to high quality optical at this time - but you’d best save a compatible optical drive.
Oh, man, I just ride in 'em ... I don't what makes 'em work.
From the sequence of events, it sounds like your EFI system partition is not being cloned correctly. You might try a different free disk imaging tool from Hiren’s Boot CD PE. You might also compare your partitions using Minitool Partition Wizard free edition.
Even though it is called Hirens Boot CD these days most of the time people make a bootable USB Drive. There are simple instructions and tools for this on the website
It is also possible that you will have to change settings in BIOS for boot order, enable legacy support or possibly change your “secure boot” settings.
Your problem reminds me of when one is trying to make a bootable standalone USB drive with Linux on it. It is very easy to make a “Live” Linux USB Drive that you can run Linux from, but lose whatever changes you have made each time you start it up. If you want to install the system on another USB drive instead of your hard drive... so that you can run Linux standalone with changes being saved... things get much trickier. You have to either do a lot of futzing around with the uefi partition that will not be written correctly after you have completed the process, or you have to temporarily disable the existing uefi boot partition while you are installing the system on your USB drive. This is because the system will not write a new uefi boot partition so that another can become active and be written properly.
AH! A PC hard drive transfer question. Great timing.
I have six hard drives (HDDs). Recently upgraded my OS (C) drive to an SSD.
Used Acronis software, and it worked great.
Now my H drive is bogging my system down, and I just received another 2TB SSD to replace it.
Shouldn’t be that difficult to clone a non-boot OS drive, right?
Sorry, I am having a hard time describing how one uefi partition cannot be written correctly on a new drive while the original uefi partition is active. This is a security feature in newer systems.
You are wasting your time cloning. Just install your fresh 256 GB SDATA M.2 and install Windows Ten into it. Get a fresh start.
Now before you do this, save your essential files from the 64 GB eMMC onto a flash drive or USB external storage. Then place them onto the 256GB drive (In Documents, perhaps) after Win Ten has been installed.
I suspect there is a 128 GB limitation in the BIOS/Motherboard for that tiny M.2 board.
Suggest an 128GB or better yet, sell that N22 on Ebay (etc.) and get a laptop that supports windows 11 and much larger storage. Windows 10 is going away.
I use a USB 3.0 to 2.5" Hard Drive cable and HDD. Yes bootable and yes backup for multiple systems.
If you use 4 USB 3.0 to HDDs, you can have one Grandfather and 3 son backups.
Yes, I've been told that about USB flash drives need to be plugged in periodically to keep them alive.
When Macrium failed to work properly on my recent SSD to M.2 conversion, I used EaseUS Todo with success. It handled the hidden partitions and allowed me to expand the boot partition easily.
Are you logged in?
Sorry, FR protocol.