I have a Seagate Goflex Desk 3Tb USB 3.0 external hard drive, which I recently took out from its casing (since it started to develop bad sectors [and is already out-of-warranty], and I'd like to use disk utilities to try to revive the bad sectors, most disk utilities don't work too well on USB, so I decided to take out the bare drive and connect it internally to the SATA port).
Anyway, my issue here is that while connected as an external USB 3.0 storage device, the hard drive properties will indicate it as NTFS file system, using MBR, Basic disk, and the 3Tb is in a single partition. I've been able to use this drive as such from a Windows 7 (32-bit) system to a Windows 10 (64-bit) system.
But right now, I took out the bare drive (which turns out to be a Seagate Barracuda XT ST33000651AS) 3Tb hard drive and connected it to the desktop PC's SATA port, and when Windows 10 boots up, it says file system not recognized for this 3Tb hard drive.
The test system:
Core i3-3240,
Asus B75M-A (afaik, it's a UEFI BIOS)
BIOS setting: SATA configured as AHCI mode;
Windows 10 Pro TH2 (64-bit),
Win10 Device Manager: driver indicated as "Intel 7 series/C216 Chipset Family SATA AHCI Controller - 1E02"
When connected internally, Windows 10 Disk Management sees the 3Tb hard drive as "RAW" file system, and it had 3 partitions (first one was 300+ Gb; forgot to take note the size of the other 2 partitions but I think they add up to 3Tb).
Seeing the above scenario, I thought my 3Tb drive had been corrupted, so I quickly shut down Windows, and placed the 3Tb drive back to the Goflex Desk enclosure/adapter, and everything's back to normal (single 3Tb partition). Fortunately, the drive's files are still intact.
What's causing the drive to work properly when connected as external USB 3.0 storage, but when connected internally as SATA, it suddenly has no recognizable file system)?
Also, more importantly, is it possible to configure the 3Tb as an internal SATA device with the files intact (to be used only as data drive, not for booting), similar to when it was being used as external USB 3.0 storage device?
Anyway, my issue here is that while connected as an external USB 3.0 storage device, the hard drive properties will indicate it as NTFS file system, using MBR, Basic disk, and the 3Tb is in a single partition. I've been able to use this drive as such from a Windows 7 (32-bit) system to a Windows 10 (64-bit) system.
But right now, I took out the bare drive (which turns out to be a Seagate Barracuda XT ST33000651AS) 3Tb hard drive and connected it to the desktop PC's SATA port, and when Windows 10 boots up, it says file system not recognized for this 3Tb hard drive.
The test system:
Core i3-3240,
Asus B75M-A (afaik, it's a UEFI BIOS)
BIOS setting: SATA configured as AHCI mode;
Windows 10 Pro TH2 (64-bit),
Win10 Device Manager: driver indicated as "Intel 7 series/C216 Chipset Family SATA AHCI Controller - 1E02"
When connected internally, Windows 10 Disk Management sees the 3Tb hard drive as "RAW" file system, and it had 3 partitions (first one was 300+ Gb; forgot to take note the size of the other 2 partitions but I think they add up to 3Tb).
Seeing the above scenario, I thought my 3Tb drive had been corrupted, so I quickly shut down Windows, and placed the 3Tb drive back to the Goflex Desk enclosure/adapter, and everything's back to normal (single 3Tb partition). Fortunately, the drive's files are still intact.
What's causing the drive to work properly when connected as external USB 3.0 storage, but when connected internally as SATA, it suddenly has no recognizable file system)?
Also, more importantly, is it possible to configure the 3Tb as an internal SATA device with the files intact (to be used only as data drive, not for booting), similar to when it was being used as external USB 3.0 storage device?
Facebook
Twitter
Instagram