โSep-20-2016 05:02 AM
โSep-21-2016 06:49 PM
โSep-21-2016 11:46 AM
1492 wrote:
Does your WIN x64 PC use GPT? Then it can utilize internal SATA drives larger than 2.2TB. The 2.2TB limitation comes in when using the older MBR NTFS standard.
Generally, not an issue either way if using an external USB drive enclosure with firmware support.
โSep-21-2016 10:42 AM
โSep-20-2016 09:10 PM
1492 wrote:TenOC wrote:
Could it be that I hit the 2.2Tb limit? Disk Manager show it as a 2794.39 Gb.
Are you running 32bit version of WIN 7 Ultimate? If that was the case, you'd only see 2T as usable storage. It would ignore the extra space.
You can avoid drive space limitations by installing the HD in an external USB2/3 enclosure that has built-in firmware support for larger drives. Most do nowadays.
โSep-20-2016 05:52 PM
TenOC wrote:
Could it be that I hit the 2.2Tb limit? Disk Manager show it as a 2794.39 Gb.
โSep-20-2016 05:26 PM
โSep-20-2016 05:21 PM
bob_nestor wrote:
Sometimes the MBR gets trashed on a disk. It contains the disk partition setup and boot blocks if the disk is bootable. The good news is it's usually possible to restore the MBR by just running fdisk, provided you remember how the disk was partitioned. In this case I suspect the entire disk was allocated to be a FAT-32 partition and the remaining three disk partition entires were unused. You'll know if the MBR was blown when you run fdisk if it doesn't identify any FAT-32 partitions in any of the 4 slots. If this is the case then fixing it with fdisk usually causes the entire volume and its contents to magically reappear.
โSep-20-2016 04:51 PM
TenOC wrote:1492 wrote:
This can also be caused by a USB controller or HD controller failure which is not allowing WIN to read the drive properly. First, try using a different USB port on the PC. If still reading similar, than most likely the issue is within the drive itself.
The V: drive in an internal drive.
โSep-20-2016 03:29 PM
โSep-20-2016 03:02 PM
1492 wrote:
This can also be caused by a USB controller or HD controller failure which is not allowing WIN to read the drive properly. First, try using a different USB port on the PC. If still reading similar, than most likely the issue is within the drive itself.
โSep-20-2016 12:24 PM
โSep-20-2016 08:23 AM
Sam Spade wrote:wa8yxm wrote:
I think I'd start by REPLACING the "V" drive
+1
And.....you aren't set to do an ENTIRE mirror image backup every time, are you ?? That is an unnecessary waste of time and space.
โSep-20-2016 07:08 AM
wa8yxm wrote:
I think I'd start by REPLACING the "V" drive
โSep-20-2016 06:41 AM