I've just added a pair of new hard drives (4TB each) to my Windows 7 64-bit PC - they are identical.
For identification purposes, let's call them Disk 1 and Disk 2.
Disk 1 is for storing images. Disk 2 will be a backup of Disk 1.
The intention is to leave Disk 1 in the PC and put Disk 2 in an external USB 3.0 enclosure (this one).
Here's what I've done so far:
So, my question is: why does a drive that's already been initialised in the PC need to be initialised again when it's put into the USB 3.0 enclosure?
NB. Obviously, both drives were formatted (in Disk Management) after being initialised. My motherboard has UEFI, hence it supports disks larger than 2TB.
For identification purposes, let's call them Disk 1 and Disk 2.
Disk 1 is for storing images. Disk 2 will be a backup of Disk 1.
The intention is to leave Disk 1 in the PC and put Disk 2 in an external USB 3.0 enclosure (this one).
Here's what I've done so far:
Disk 1 is in the PC and (being larger than 2TB) has been initialised as GPT. It works fine, appears in Windows Explorer, and acts exactly as any other drive of 2TB or less would do - so I've copied 1.5TB of images onto it.
To create the backup more quickly, I put Disk 2 into another bay in the PC and initialised it as GPT. The drive also appeared in Windows Explorer so I copied the contents of Disk 1 onto it. I then removed it from the PC and put it into the USB 3.0 enclosure. This time it did not appear in Windows Explorer. It was present in Disk Management but was showing as unallocated - i.e. not being initialised. The only way I can get it working in the enclosure is to initialise it again (as GPT) and re-copy all the data from Disk 1 - which takes hours.
So, my question is: why does a drive that's already been initialised in the PC need to be initialised again when it's put into the USB 3.0 enclosure?
NB. Obviously, both drives were formatted (in Disk Management) after being initialised. My motherboard has UEFI, hence it supports disks larger than 2TB.
Last edited: