1

I have a Seagate 3TB drive with a USB 2.0 interface on it. I took it out of the case and installed into my PC (SATA). Physically, it’s like any other hard disk drive.

But all that Windows wants to do is format it. Even the Seagate utility “DiscWizard/Extended Capacity Manager” shows a small .34TB partition in the front (none of these are usable in Windows), then 1.66TB unallocated, then .73TB unallocated.

Looks like it’s offering the first 2TB as one unit, and the rest as another. I get that, but why is it unallocated? There’s definitely usable data on there, which I just saw when it was in the enclosure.

I’m on an ASUS F2A85-V PRO FM2 "AMD A85X (Hudson D4) 7 x SATA 6Gb/s USB 3.0 HDMI ATX" motherboard, and my older drive with Windows 7 is legacy, not UEFI.

Windows 7 shows the BIOS mode as “Legacy.” But I thought it wasn’t a requirement to boot via UEFI to use a data drive (non-boot) over 2TB.

I also have a 4TB that I’d love to put in my new big case, but while I’ll risk wiping the 3TB, I won’t play around with the 4TB until I figure this out.

1
  • More details are needed. A screen shot of whatever utility you are describing would help. Better yet would be the output of fdisk -l or parted -l from a linux live cd.
    – psusi
    Commented Oct 29, 2015 at 2:18

1 Answer 1

6

Most of the massive external hard drives are configured with 4KB LBAs (Logical Block Addresses), which would cause an issue like yours when plugged internally via SATA. Removing the enclosure exposes the HDD to its native 512e LBAs (which are typical for internal SATA drives). This is due to the fact that SATA ports on the motherboard use such native 512-byte LBAs. I’m afraid that you’d be able to access your data only if you have the drive in an external enclosure.

1
  • 3
    This is correct. You'll have to place it back in the enclosure, copy the data off, move into the PC and fomat it, then copy the data back.
    – Linef4ult
    Commented Oct 29, 2015 at 8:11

Not the answer you're looking for? Browse other questions tagged .