12harry
Prominent Member
Bought a new HDD WD Red = 6Tb... but of course it comes unformatted so it just sits there. Plugged it into an External caddy whose drive had croaked... Went through the DiskMgmt routine, selected GPT and when formatted it shows only 1.4Tb (=one point four), now on my Win10 PC and today on Win7 (32b) PC.
I conclude that the "old Caddy" has a limit and cannot address any larger drive... but of course no-one thought to write a line of code saying this would happen.- Oh dear.
Bought a new caddy which claims it can address 16Tb (wow!), but the WD drive still appears as 1.4Tb - presumably the platters are only showing what the FAT ( or whatever else...I used GPT and NTFS as it's a large drive....) were previously formatted for..... in error as it happens
The Q. is this... how do I erase the old formatting ( pref. using the new "up to 16Tb" Caddy ), as the previous DskMgmt route now appears to miss the selection GPT pop-up.... BUT as I only format very rarely it is quite possible I'm not following the best route.... but know no better.
I prefer to use my Win7 PC (as I write this), but do have a Win10(64b), PC if that's the only option...
So, a second Q is there a limit for 32bit OS as to their HDD size? . . . I don't understand why, as it is only a container of data and normally one is fetching only v.small %. . . . I knew there was a limit if using FAT32, but NTFS overcame this and the limit then was about 2Tb... so clearly I must have overcome this with the Win7 external 4Tb drive - which consistently shows itself as 4Tb ( under Properties and shows about half of it unused... with no partition that I'm aware of, ).
FWIW Existing "External" HDDs (=4Tb) work OK as expected, on the Win7 - 32b PC and with some messing of the Drive Letter, on the Win10 - 64b PC as well . . . . So I am able to work on files with both . . . but over time I expect to favour the Win10, because it's faster and modern software is often 64b since it needs more RAM.
My Win7-32b has 3Gb and by contrast the Win10 64b has 16Gb.
Unfortunately, I'm finding it difficult to move the software over, hence using Win7 is my preferred system.
I haven't written any data to this HDD, so Recovery isn't necessary. (?)
Any thought folks?
Cheers....H.
I conclude that the "old Caddy" has a limit and cannot address any larger drive... but of course no-one thought to write a line of code saying this would happen.- Oh dear.
Bought a new caddy which claims it can address 16Tb (wow!), but the WD drive still appears as 1.4Tb - presumably the platters are only showing what the FAT ( or whatever else...I used GPT and NTFS as it's a large drive....) were previously formatted for..... in error as it happens
The Q. is this... how do I erase the old formatting ( pref. using the new "up to 16Tb" Caddy ), as the previous DskMgmt route now appears to miss the selection GPT pop-up.... BUT as I only format very rarely it is quite possible I'm not following the best route.... but know no better.
I prefer to use my Win7 PC (as I write this), but do have a Win10(64b), PC if that's the only option...
So, a second Q is there a limit for 32bit OS as to their HDD size? . . . I don't understand why, as it is only a container of data and normally one is fetching only v.small %. . . . I knew there was a limit if using FAT32, but NTFS overcame this and the limit then was about 2Tb... so clearly I must have overcome this with the Win7 external 4Tb drive - which consistently shows itself as 4Tb ( under Properties and shows about half of it unused... with no partition that I'm aware of, ).
FWIW Existing "External" HDDs (=4Tb) work OK as expected, on the Win7 - 32b PC and with some messing of the Drive Letter, on the Win10 - 64b PC as well . . . . So I am able to work on files with both . . . but over time I expect to favour the Win10, because it's faster and modern software is often 64b since it needs more RAM.
My Win7-32b has 3Gb and by contrast the Win10 64b has 16Gb.
Unfortunately, I'm finding it difficult to move the software over, hence using Win7 is my preferred system.
I haven't written any data to this HDD, so Recovery isn't necessary. (?)
Any thought folks?
Cheers....H.
Last edited: