Robert in CA wrote:
Here's the Disk Management in the 8500:

#3 hd
https://postimg.cc/nj3vVyvt

original hd

https://postimg.cc/xXGN1r2F

but I don't see how I can compare #4hd if it
won't connect other than to put inside the 8500
itself?

I also have the unknown hd which may or may
not work in the 8500 or 780.

I think at this point we could try putting in #4 in
the 8500 and run the Rescue CD and repair its
boot menu if possible because you said every hd I
attached after I changed the battery would be corrupted.

If that doesn't work I suggest we try the unknown
hd in both computers to check it. Starting with the
8500.

I just find it hard to believe changing the battery
caused all this and stopped our cloning dead in it's
tracks after all the work we've already done.

Thanks for the VLC link,

Thoughts/suggestions
Robert

Thanks for taking the time to shoot pictures of those.

The #4 disk (the clone) hasn't had the C: partition
resized to use up the "Unallocated space" to the right
of it. In Disk Management, you can right-click the C: partition
and select the option to Expand the volume. Shrink and
Expand are built-in functions in Disk Management.

This is independent of any other issue at the moment, and
can be done when you have the time or inclination to fix it up.

*******

If you want to repair the boot menu on #4, you can, but I fail
to see how that will affect whatever is bothering the enclosure
setup.

When the 1TB is booting the computer, and the 2TB is in the
enclosure and connected to the USB port, both drives should
show up in Disk Management. You say it is not there.

I've seen one of your pictures, showing the new drive getting
a "driver", and there was a notice in the lower right corner
to that effect. When I see that, it means a disk is being
recognized somewhere.

I'm still not seeing anything that tells me what could be up
with the thing. USB enclosures generally should not respond to
being plugged in, unless the drive inside the enclosure spins
up and the disk identifier string is extracted. At that point,
the enclosure chip starts responding to queries from the OS.
That's how it's supposed to work.

And once we get past that point (the setting up of Endpoints
at USB transport level), then soon you would see an entry in
Disk Management. Disk Management is a key part of observation,
rather than File Explorer. Checking File Explorer is a step
after checking Disk Management. First you see an item in
Disk Management, but no drive letters will go into File
Explorer, unless the item in Disk Management is "Online".

The Boot Repair operation in Macrium, might change the GUID
of the disk partitions, and the Boot Repair puts the new
values in the Boot Menu. But as far as the "seeing the disk
contents" goes, the DiskID in the MBR plays a role in that.
I don't think Macrium changes the VolumeID in the header of
each of the disk partitions. And as far as I know, if two
VolumeIDs are equal on the PC, there's no harm done. The
sequential assignment of drive letters, helps make each
one unique as they're discovered.

*******

When Disk Management is open, the USB3 Enclosure will be
probably closer to the bottom of the display. That's
because E,F,G,H got there first during discovery. You may have
to scroll down, to see an item below the D: optical drive.

There are various ways to modify the drive lettering of
the card reader, but none of them is ideal. One of the
ideas, I think it's similar to the DOS "SUBST" command
which substitutes a folder for something. You can convert
the USB card reader volumes, into folders that sit
within a master folder. That's one of the ideas here. But
again, not an ideal solution. From Disk Management, if
you right clicked the E: one, you could select "Change drive letter"
kind of thing, and assign the four drives M,N,O,P and lift
the drives up higher. Using the letter Q is not recommended,
because that might conflict with a features used by
Microsoft Office years ago.

https://superuser.com/questions/3421...drives-letters

Summary: You can Boot Repair the new drive if you feel like it.
I'm not convinced this will improve the behavior.
Perhaps the behavior is related to the USB card reader,
but I thought part of that was interference with network
shares rather than with other USB storage devices like the
enclosure. Make sure to scroll down in Disk Management
and make sure you can see everything. Disk Management
seldom makes good usage of display space when it renders.

Paul