New
#21
Macrium Reflect has a boot-fix feature. Look it up.
Macrium Reflect has a boot-fix feature. Look it up.
Thanks, I'll check it out.
I should say that my source SSD had a handful of bad sectors. Thats why I'm cloning. Reflect failed to clone citing Error 0 (read errors)
I did try a clone with AOMEI Backuper, and that purported to do a full clone, so I tried it and plugged in my target into the computer and tried to boot but it didn't boot.
I examined the partitions on the target and they were slightly smaller than the source (my target ssd is actually a few less GB in size, but my source was nowhere near full).
Anyway, I did a partition by partition clone. I'll check on Monday morning to see if that worked and it boots.
A lot of trouble you're going to when you've already been advised to simply image the source drive and restore to the destination drive. If you know how to set Macrium, a difference in size between the two makes no difference.
He hasn't gone to any trouble yet.
The OP cloned partitions because, as he has just revealed,
I should say that my source SSD had a handful of bad sectors. Thats why I'm cloning. Reflect failed to clone citing Error 0 (read errors)
Firstly, why would you want to clone a faulty/failing drive?? In any case, don't waste any more time with cloning, imaging or whatever. If there are bad sectors, there is a higher risk of corrupted system files (albeit possibly "dead", just taking up space)
Uh oh! The more "actions/steps" the more opportunity for errors to occur.Anyway, I did a partition by partition clone. I'll check on Monday morning to see if that worked and it boots.
Might be OK now, but who knows what's going to fall over at any stage in the future.
Given your piece-by-piece contribution to this thread, I think we now have enough information to suggest that perhaps you should be looking at a clean install. I wouldn't be trusting your patched up system if it was on any of my devices
I looked at the Macrium Reflect boot fix feature and created rescue media.
I clicked on fix boot problems and it found my Win10 partition. But then the next step in the wizard said, "no active partition" and would not go any further. GPT disks are not supposed to need an "active partition" as far as I know.
I was running Reflect in UEFI mode.
curious message. If you post a screenie of diskmgmt window that might provide a clue as to what is going on with your target disk.
thanks...
Disc 3 (H:) is the new target disk. Disk 4 (I:) is the old source disk with a couple of bad sectors.
The source drive is just a little larger, so annoyingly the sector-by-sector-clone refuses because the "source is larger than the destination." Thats why I am trying to create appropriate sized partitions and do a partition-by-partition copy.
If your copying from a drive with bad sectors they will be written to the new drive which cant be reversed if you have 2 bad blocks you have a lot more as first it fill enginering sectors so there are a lot more