G. Ross wrote:
G Ross wrote:
My hard disk occasionally emits a squealing sound. I want to clone it
to a same size, same brand drive. My drive is set up as a C: drive and
a D: Drive.
Question: Will Macrium set on clone set up the two drives or will I have
to format and set them up myself before cloning?
Thanks in advance.

Got it hooked up and it works fine for 30% then stops with error Read
Failed. Said was blocked from reading files in root. I disabled
firewall, had already turned off any running programs. Turned off
windows defender and windows firewall and antivirus. It still stalls
at 30%.
What else should I do?

G.Ross

Assuming the feature is still present, see the dialog
box at the bottom of this page.

https://blog.macrium.com/techie-tues...i=a8ebc97e3f0e

"If running chkdsk is unsuccessful, force Macrium Reflect to continue on Error 23.

Select Other tasks Edit defaults Advanced.
Select "Ignore bad sectors".
Click OK.
"

That would be the equivalent (sort of) of using gddrescue.

Note: I do *not* recommend running CHKDSK as a method to
nuke and pave file systems (as the top of that article
suggests). You can experience severe tire damage doing
that. Hundreds of thousands of errors could result.
CHKDSK is a good thing to do on *healthy* hardware and
systems. Don't be kicking *sick* stuff with CHKDSK.
This is generally true of any tool which attempts
"repair in-place" - you could lose your only copy if
damage or total failure is the result.

*Always* try to make a clone first, even if it's a
crappy clone. Make sure you've rescued as many files
as possible. Then, if some subsequent experiments
result in total destruction of the source drive, you
still have (most of) the files.

I would be torturing you with tales about using
Linux "gddrescue" as the way to do this, but try
Macrium with the "Ignore bad sectors", then see
how many files you got. It could be that the disk
is mechanically too sick to get past that point, and
then using gddrescue would end the same way.

(sector by sector copy with a tool for the purpose, under Linux)
https://www.cgsecurity.org/wiki/Damaged_Hard_Disk

(available as the gddrescue package, with ddrescue executable maybe)
(Can be installed from package manager, doesn't need compile)
(rescued.log has a terse format recording success/failure of copy)

# first, grab most of the error-free areas in a hurry:
./ddrescue -n /dev/old_disk /dev/new_disk rescued.log
# then try to recover as much of the dicy areas as possible:
./ddrescue -r 1 /dev/old_disk /dev/new_disk rescued.log

*******

You *can* compare disks afterwards, using hashdeep
and generating checksums for every file. (That
will help tell you what clusters didn't copy.)

But read the Hashdeep manual page thoroughly - you
will need the obscure command line parameters to turn off
checking of "Reparse Points" and "Named Pipes". The
file system is littered with crap that will prevent
a hashdeep checksum run from completing.

Do your hashdeep on the "dest" disk first, and perfect
your technique of generating a manifest on the working
disk. You don't want to tune up your hashdeep skill
set on the sick disk - it might take too many runs
until you figure out how to use it well.

And if I knew of a better option than hashdeep, I'd
be selling that. Hashdeep is useful, but it's not
as friendly as it could be.

Good luck with your sick disk,

Paul