Macrium Reflect Update

Deaf Dave · 22 Dec 2023

Thank you. I'll check Backblase out. Here's more on the disk I'm using..

Macrium Reflect Update-ssd-5291-status-12-22-23.jpg

- - - Updated - - -

Thank you. I'll check Backblase out. Here's more on the disk I'm using..

What I don't understand is why the source drive isn't or doesn't get compromised. Only the drive being cloned to is. It's my understanding that all Macrium's software does is copy from one drive to another. If the drive being copied is ok, why would the other not be unless the software made a mistake while doing the cloning process. I also almost always run SFC /SCANNOW before I open Macrium to do the cloning process just to make sure I'm 'good to go'.

cereberus · 22 Dec 2023

Deaf Dave said:

Thank you. I'll check Backblase out. Here's more on the disk I'm using..

- - - Updated - - -

Thank you. I'll check Backblase out. Here's more on the disk I'm using..

What I don't understand is why the source drive isn't or doesn't get compromised. Only the drive being cloned to is. It's my understanding that all Macrium's software does is copy from one drive to another. If the drive being copied is ok, why would the other not be unless the software made a mistake while doing the cloning process. I also almost always run SFC /SCANNOW before I open Macrium to do the cloning process just to make sure I'm 'good to go'.

You may think source drive is ok, but it may have damaged sectors e.g. a file you never use is corrupted. However cloning does not know that you do not use that file and cloning may fail.

If the source drive has issues, no tool can safely clone it.

You have to fix issues with source drive which may not be possible if too corrupted.

Using Macrium Reflect image backup and restore may have more chance of success than direct cloning as there is an option to ignore source disk errors but if the level of source disk errors is too high, it will probably fail as well. Only one way to find out ....

Deaf Dave · 22 Dec 2023

Hello Cereberus, The drive I'm using now (5291) I've been using this as the source drive since 10-30-23 doing 7 clones without any failure. the failure(s) started last week. you said "Only one way to find out" .... and that would be through what method and how? Thank you

cereberus · 22 Dec 2023

Trying image backup and restore, with setting to ignore source errors set.

Deaf Dave · 22 Dec 2023

While doing some digging a few days ago, I came across this saying to "ignore bad sectors when creating images". I checked the box and tried to clone but it didn't work. Is that because it doesn't work when doing a clone and only works by doing an image? Is the image done on an external drive? I've never worked with an image.

Macrium Reflect Update-ignore-bad-sectors.jpg

cereberus · 22 Dec 2023

Deaf Dave said:

While doing some digging a few days ago, I came across this saying to "ignore bad sectors when creating images". I checked the box and tried to clone but it didn't work. Is that because it doesn't work when doing a clone and only works by doing an image? Is the image done on an external drive? I've never worked with an image.

Yes that option only works for disk images.

Look in the tutorial section for using Macrium Reflect imaging.

dalchina · 23 Dec 2023

If you ignore bad sectors you will be potentially copying corrupted data.

Futher, the procedure involved in doing such a 'forensic image' is very much longer than restoring an image, as it's done sector by sector.

Essentially you're discarding protection.

I have said twice now- find out which partition is responsible for the error by imaging one partition at a time.
If no error is flagged, that partition is sound.

If an error is flagged, that partition is likely to be corrupt.

Your objective should be this:
To end up with a known sound disk which is free of errors.

If you don't currently have one, then start with the above. In particular if your Windows partition proves to be sound, then your installation can be rescued completely.

Or you can just try to copy corrupt data. The choice is yours.

Deaf Dave · 23 Dec 2023

Dalchina, I find many confusing things on this subject and apologize for my ignorance. My biggest fear is ruining the source drive! I would also be extremely happy to have an error free SSD. I wasn't aware that I can Image each partition separately. Can checking my source SSD partitions for the error be done by attaching another SSD to my PC to Image to? If I find the partition that has the error, how would I then go about correcting it?

dalchina · 23 Dec 2023

I wasn't aware that I can Image each partition separately.

This is easy- note the check boxes (example only) - you would just have 1 ticked.
- to be imaged- tick - I've shown these in green.
- not to be imaged - I've shown these in red.

That's the first step.

I suggest you start by selecting ONLY your Windows partition.

If that succeeds, there's a routine way to recover the whole installed O/S.

Here I'm assuming you have only one current system disk, and this is the one where you find the error reported when you attempt to clone it.

Please advise your results.

Deaf Dave · 23 Dec 2023

Yes, I only have one SSD installed. But wouldn't I need to attach another one to Image to? Also, I don't see ANY green or red check boxes.