Seagate Confirms 3TB Hard Drive 467
Stoobalou writes "After a few weeks of rumours, Seagate's senior product manager Barbara Craig has confirmed that the company is announcing a 3TB drive later this year, but the move to 3TB of storage space apparently involves a lot more work than simply upping the areal density. The ancient foundations of the PC's three-decade legacy has once again reared its DOS-era head, revealing that many of today's PCs are simply incapable of coping with hard drives that have a larger capacity than 2.1TB."
does it work with Windows 98? (Score:5, Funny)
i have to know because i have a Win98 PC that i use to play some old games and i wanted to upgrade it
Re: (Score:2)
The 32-bit Windows XP only sees 0.99 terabyte (from the article). Win98 probably has the same limitation.
Re: (Score:2)
Re: (Score:2)
Re: (Score:3, Informative)
Re:does it work with Windows 98? (Score:5, Funny)
I think you could probably install EVERY game from the 90s on that hard drive and still have 2.09 TB left over. :-)
Re: (Score:3, Interesting)
If games are the only thing holding you back, let me recommend GOG.com or if you're really old school Dos Box.
Both are awesome suggestions, but I still like having a top-of-the-line PC circa the year 2000 with Windows 98 installed on it laying around. It's like using an NES emulator vs. playing a game on NES hardware. Sure, you technically are playing the same game...but the experience isn't quite the same :-)
Re: (Score:2, Funny)
Same experience exactly.
Seagate reliability (Score:4, Interesting)
But I seem to detect that quality and reliability is returning to Seagate's devices. Does anybody have any recent experience with Seagate to share?
Re: (Score:3, Insightful)
Re: (Score:2)
It doesn't work. You're at the mercy of hobby fixes.
Re: (Score:2)
WHOOOSH
2TB with 512-byte sectors (Score:5, Insightful)
If you move to 4K sectors, that should change the limit to 16TB, meaning that this shouldn't be an issue for several years. Why would you want .5K sectors on such a large drive anyway?
Re: (Score:2)
Or just properly support 48-bit LBA, which is a limit of 128 PiB even at 512 byte sectors.
And GUID partition tables of course.
Re: (Score:3, Insightful)
Because 512 byte sectors allow for less empty space waste than anything larger.
Imagine wasting 4095 vs 511 bytes for every file on your system (worst case scenario)
Re:2TB with 512-byte sectors (Score:5, Informative)
Re: (Score:2, Informative)
And if their sectors don't fall on a physical boundary, then you've just used 8KB on the physical drive.
Re: (Score:2, Informative)
And if the physical boundary is 512 bytes, this won't happen.
Re: (Score:2)
Which is exactly what I was implying (see up-thread).
Re:2TB with 512-byte sectors (Score:5, Informative)
And if their sectors don't fall on a physical boundary, then you've just used 8KB on the physical drive.
100% false.
You still only use 4K on the physical drive. You just have to read & write 8K at a time because the misaligned 4K filesystem block straddles two physical blocks. But since filesystem blocks are packed sequentially there is no wasted space, they are just all misaligned by the same offset.
Re: (Score:3, Informative)
That's what I get for responding too quickly. You're totally right.
Re: (Score:2)
Because 512 byte sectors allow for less empty space waste than anything larger.
Imagine wasting 4095 vs 511 bytes for every file on your system (worst case scenario)
Why not use a sane FS, then?
Re: (Score:2, Funny)
because then we wouldn't be using NTFS.
Re:2TB with 512-byte sectors (Score:5, Funny)
Yeah, you would only be able to store 800 million of your oddly small files on this new drive. What a disaster.
Re:2TB with 512-byte sectors (Score:5, Funny)
Seriously? If you've got a 3TB drive, are you seriously suggesting a person be counting wasted bytes? You lose more space than what you're suggesting just in the conversion from "vendor measurement" to "OS measurement" of space on the disk.
Re: (Score:2)
You lose more space than what you're suggesting just in the conversion from "vendor measurement" to "OS measurement" of space on the disk.
That's the funniest thing I've read in a long long time. I wish I hadn't posted so I could mod you +10 Funny.
Re:2TB with 512-byte sectors (Score:4, Informative)
Because 512 byte sectors allow for less empty space waste than anything larger.
Um, no. The sector size dictates what boundaries the OS has to do reads and writes on. It doesn't dictate how the OS uses the space. 4k sectors means that to read or write an aligned 4k filesystem block, the OS has to do one I/O operation instead of eight; and that if it wants to write a 512-byte block, it has to do a read-modify-write cycle.
How efficiently small files get stored is a property of the filesystem, which doesn't even know about the sector size. Common filesystems all use 4k blocks or bigger anyway. Some filesystems store files smaller than 4k efficiently by packing them in with the metadata or dedicating some blocks to store several files per block. Filesystems that do this include, most notably, NTFS, and also some Linux filesystems like ReiserFS and btrfs. Wikipedia calls this block suballocation [wikipedia.org] (don't know if this term is standard). This is totally orthogonal to the sector size.
Re: (Score:3, Informative)
If you're on windows, you'll either need EFI or a separate boot drive.
Windows cannot boot from driver larger than 2 TB [microsoft.com]
The issue is, MBR doesn't support drives that big, so you have to use GPT (which Windows won't boot from w/o EFI). ;)
So if you're on Windows, but without EFI, you're SOL.
Also, kind of a pain [rodsbooks.com] on *nix+BIOS combos too.
Re: (Score:3, Funny)
Quick access means updating from a mechanical to an optical paper tape reader.
Linux can handle it just fine (Score:4, Informative)
I ran into that a few years ago when I added a 4TB hardware RAID5 to my Linux server. The partition table that is made by fdisk can't handle it. I was forced to use parted to make an EFI partition table instead. It was a little different but completely doable. Took me about 2 minutes on Google to find a howto.
Re: (Score:2)
EFI... Or LVM. LVM gives you additional benefits you may want to consider.
Re: (Score:2)
I'm not familiar with LVM. Mind giving a quick "noob's guide on what you should know"?
Re: (Score:3, Informative)
I'm not familiar with LVM. Mind giving a quick "noob's guide on what you should know"?
Its a "pulling oneself up by ones bootstraps" thing. He was trying to make a "funny". So, on my AMD64 from like five years ago, running linux 2.6 from like five years ago, I can theoretically provision a 8 Exabyte LVM logical volume (LV) which would seem to mean a 4TB LV is small potatoes. But LVs live inside PVs (simplification). All you gotta do, is use fdisk to create a honking big 4TB physical volume partition with type 8E. Oh wait, the problem was fdisk doesn't work. A real knee slapper. But not
Re:Linux can handle it just fine (Score:4, Informative)
Not exactly a "noob's" guide, and it hasn't been updated in awhile, but: http://tldp.org/HOWTO/LVM-HOWTO/ [tldp.org]
Think of LVM as a layer of abstraction between physical devices (your disks and/or arrays) and the logical devices that you can then put a filesystem on. LVM lets you break your physical disks into bite-sized pieces called extents (say, 32MB each, but it's configurable), and then you can add/remove extents to a logical disk device. If you have a filesystem that supports it, you can then grow/shrink the filesystem to use the space you've allocated.
There are also other benefits (snapshots, etc.).
Re: (Score:3, Informative)
Not exactly a "noob's" guide, and it hasn't been updated in awhile, but: http://tldp.org/HOWTO/LVM-HOWTO/ [tldp.org]
Not a bad noob reference. Its funny in a quaint way how it squeals about root LVM... that hasn't been a serious problem since like the Clinton administration. I know I've got vanilla out of the box Debian boxes from like half a decade ago with root LVM, just not an issue.
It does suck in the "Why" section, in that all it does is list "What" it can do.
Assuming the prerequisite of understanding what Xen/KVM/VMware does, think about how it wedges a layer in between the OS and the CPU so you can pool, combine,
Re:Linux can handle it just fine (Score:5, Informative)
Re:Linux can handle it just fine (Score:5, Informative)
The Bios doesn't know anything about partitioning. It only knows it needs to read sector 0 of a disk into memory at 0x7c00 and jump to it. If the disk is MBR partitioned that's the MBR and the code there knows how to scan the partition table, and load the boot sector of the partition table using INT 13h. If it's not partitioned sector 0 is the boot sector of the partition table already and will use INT 13h to load the OS boot loader.
GPT is different because sector 0 contains a "Protective MBR" that just reserves the whole disk. That doesn't contain any code - EFI Bioses need to read boot code from a special FAT formatted partition (Macs apparently use HFS+ instead [ntlworld.com]). EFI Bioses offer a much more complicated API than the Bios, which is good in some ways (flexibility) and bad in others (more chance of bugs).
But non partitioned disks have always been supported. In fact floppy disks are always non partitioned.
Actually it's a shame that sector 0 of an GPT disk doesn't contain code to load a boot manager that understands GPT to allow booting from a GPT disk with an old fashioned Bios. Or that some way for old style Bioses to boot from disks with a partition table with 64 bit LBAs in wasn't developed - MBR partitioning only has space for 32 bit LBAs. Which means no support for disks bigger than 2TB.
Re:Linux can handle it just fine (Score:4, Informative)
They do just as soon as you install Grub on it (either version 2 or a patched older version).
EFI is uncommon, but raid arrays with 4 or more TB+ HDDs are VERY COMMON. What do you think everyone's been doing with those TB+ enterprise HDDs for the past couple years?
Re: (Score:3, Informative)
You mean GUID partition Table [wikipedia.org]. It is part of the EFI standard, however you can use a GUID partition with BIOS. Linux and FreeBSD are the only 2 OSs that can Boot from a BIOS/GUID setup.
Windows can boot from a GUID partition table, but only on an EFI motherboard and those aren't exactly falling from the sky right now.
Personally all of my disks are on GUID because my main OSes are Linux/MacOS X, other than my OpenSolaris server which just uses ZFS on the devices.
Booting Linux with a workaround, added benefits (Score:3, Insightful)
There's a simple workaround for the MBR problem with 2TB+ hard drives - for Linux.
1) Store your boot files on a small secondary device, e.g. a USB stick. That includes: Master Boot Record, boot loader (e.g. GRUB or LILO), kernel, initrd - about 10 megabytes are easily enough. /sbin/init process.
2) Boot the USB stick. The initrd mounts your hard drive and starts the actual
This comes with several nice options:
- Encrypt every single byte of your hard drive. A script in the initial ram disk asks for the passphr
Mac OS X (Score:2)
Re:Mac OS X (Score:5, Informative)
Everything works on Mac, because Apple doesn't support legacy stuff. They assume any Mac older than ~5 years is obsolete, and therefore moved to 64-bit addressing long ago.
(No I'm not trolling. I'm bitter. I had to toss a perfectly good Mac G4, just because Apple stopped supporting it, and its ancient Safari 2 browser could no longer render the web properly.)
Re: (Score:2)
Correction:
>>>I had to [sell] a perfectly good Mac G4
Re:Mac OS X (Score:5, Funny)
Some dude had to buy a perfectly good Mac G4, just because Apple stopped supporting it, and its ancient Safari 2 browser could no longer render the web properly.
Re:Mac OS X (Score:4, Insightful)
Safari 3.0.4 runs on 10.4.x
Safari 4 runs on 10.5+
What G4 do you have that you can't install leopard on? I shoehorned Tiger onto an ancient G3 iMac from 2000, surely you can install leopard on a fairly recent G4, and if you can't you could have tried this http://lowendmac.com/osx/leopard/openfirmware.html [lowendmac.com]
Perhaps you simply wanted a new Mac?
Re: (Score:3, Informative)
Re: (Score:3, Insightful)
I won't argue about what wikipedia and apple.com say, but I will add an anecdote. I just checked the versions and I'm posting this from Safari 4.0.5 running on MacOS X 10.4.11. I don't remember doing anything special to install Safari. I may have downloaded it separately rather than using the Software Updater, but it seems to be working fairly well. I'm also running Firefox 3.6.3 and it's running well too. This is on an iMac G5.
Re:Mac OS X (Score:4, Insightful)
Re:Mac OS X (Score:4, Insightful)
And Firefox wouldn't work? If the machine still works for what you need to do, then you don't need to upgrade for the sake of upgrading. If it doesn't meet your needs anymore, then why complain about upgrading?
Vendor support doesn't dictate what use you can get out of a machine. I have friends who are still running OS 9 (eek) on a G3, because it does what they need it to.
Re:Mac OS X (Score:4, Insightful)
What price? He bought hardware that got old. It wasn't new enough to run the latest version of Mac OS X. He had many other options. He could have upgraded to Safari 3.0 which was supported on his machine. He may have been able to install Leopard with a new version of Safari. He could have moved to Firefox. He could have moved to Linux. He had plenty of options, I'm not sure why he didn't take any of them.
As far as being able to upgrade the hardware, most things in an iMac G4 are perfectly upgradable, however, the CPU isn't. This is true of most all in one computers and laptops. I don't see anything implicitly Apple about any of this.
Re: (Score:2)
What is really going to hurt is when 48bit memory addressing ceases to be adequate.
at which point your computer will be ungodly slow because of memory bus width and caching needs, running on a 200THz processor and getting speeds similar to your old 200MHz 586.
We know cache will get bigger though. Back in the day we had 32MB of RAM (64MB for my awesome system) and a whopping 256K of cache in some high-end systems. Now we have 4GB of RAM (at least, I do) and a whole 2MB of cache (4MB in some systems). Memory's gotten 128 times bigger, and cache got 16 times bigger to compensate; die sp
Re: (Score:3, Informative)
3TB - that's all you'll ever need! (Score:3, Funny)
Re:3TB - that's all you'll ever need! (Score:5, Funny)
Re: (Score:2)
Re: (Score:2)
XP + 3 TB?? (Score:3, Insightful)
Why would anyone running XP fork over the dough for a 3TB HDD? XP is 9 years old and Win7 is a very good replacement for newer machines, particularly ones who's owners might want a 3TB drive for.
Re: (Score:2, Insightful)
Re: (Score:2)
They wouldn't, but consider this: what's the smallest hard drive you can buy, and when was that capacity first launched? In 10 years, this drive will be the only type of technology available...
Re: (Score:3, Insightful)
Why would anyone running XP fork over the dough for a 3TB HDD? XP is 9 years old and Win7 is a very good replacement for newer machines, particularly ones who's owners might want a 3TB drive for.
Because some people are perfectly happy running XP, or don't want to pay $100-$200 for a legal copy of windows 7, and don't want to pirate.
I have a perfectly good fileserver at home that just runs XP. I use XP because it is also my backup computer for various tasks, and mostly I've just been too lazy to move it to linux.
Either way, i've got 5TB of storage and I'd love to throw in another 3TB. Even if I fork over the money for a 3TB drive, i might not want to spend *another* $100 just for a compatible OS, ev
Not a huge deal (Score:4, Insightful)
FTFA:
According to Seagate, this includes the 64-bit versions of Windows 7 and Vista, as well as modified versions of Linux, but it doesn’t include Windows XP. Not only that, but you may not even be able to see 2.1TB of a 3TB drive when using Windows XP.
Sure, Windows XP won't allow it - but your grandmother who is still running XP isn't going out to buy a 3 TB drive. The early adopters who want or need this are the ones who are already running a compatible OS.
Re: (Score:3, Insightful)
Wow dude, you have totally missed out on the last 10 years of OS improvements then.
Takes me back... (Score:2, Funny)
I had a sudden and vivid memory of the little blue ASCII box displayed by the special Western Digital bootloader I needed to bypass my old BIOS's 2GB drive size limit.
Re:Takes me back... (Score:4, Funny)
Re: (Score:2)
lawns? you had lawns?
Everything old is new again. And again. And again. (Score:2)
Re: (Score:2)
It's not a filesystem problem, it's an LBA problem.
Re:Everything old is new again. And again. And aga (Score:2)
The problem isn't so much the partition size limitation. It's a problem that the partition schema (fdisk [wikipedia.org] in this case?) can't describe the entire drive (partition layout) of that size.
I suppose they need to be using GPT [wikipedia.org] at this point.
The problem is probably a combination of (1) too many blocks on the drive, and/or nonstandard block sizes. (1024/2048/4096 instead of 512 byte) - one or the other has to increase to grow the size of the device. There's been a lot of noise lately about OSs that won't like driv
How long can the growth last? (Score:5, Interesting)
Is there anyone who currently works in that area or has a background in magnetic storage who has a better idea?
Re: (Score:2)
Without multi-core, Moore's law would have ended recently. Seagate has taken that design philosophy to heart and will soon be releasing 7" and 10.5" drives to meet demand.
Re:How long can the growth last? (Score:5, Insightful)
Without multi-core, Moore's law would have ended recently.
Since Moore's law is about the number of transistors on a die and nothing to do with performance (except to the extent that more transistors allows higher performance), multiple cores are irrelevant: we could be running Pentium-4s with 16MB of cache instead of hexa-cores with 12MB of cache and Moore's Law would be just as valid.
Re: (Score:2)
While I'm sure you meant that in jest, with the current popularity of external drives, increasing physical form factor actually could be an option in the market.
Re: (Score:2)
No, Moore's is still valid. It proposes that transistor count on IC double around 18 months. Dose not impose anything on clock rate or core count on a single die.
Moore's law is also unrelated to mass storage.
Technically, hard drives are a very different problem domain.
Re: (Score:2, Interesting)
I think we're coming close to the limits now. I've heard that there's already interference in the data tracks from the other nearby tracks' magnetic fields, and to make it much smaller will need some advances in error checking/correction.
Re:How long can the growth last? (Score:5, Insightful)
Do you know how long that question has been asked, and how many times "theoretical limits" would be reached within a year at the current rate, and each time, new techniques have been developed which increase density many times more than anyone previously imagined? I think storage density will be increasing for that much longer.
15 years ago when you were paying $500 for a 320MB hard drive, did you ever anticipate your home PC would someday have a capacity of multiple terabytes? Could you imagine that a laptop would ever be able to hold over a terabyte? The capacity we have nowadays is staggering, and when back when you had your 320MB to 512MB hard drive and were thinking "I'll never fill this up" only a few were bothering with MP3s and PVR technologies (I bought my first video capture/TV tuner card around that time) and I'll bet few ever fathomed that a user could fill terabytes' worth of hard drives. Now it's cheap to build home recording studios, or even engage in amateur independent movie production with only a few hundred dollars' worth of equipment, running free software.
It's amazing, and with storage capacity growth increasing (not decreasing) we'll find new ways to fill up the storage media, very likely doing things we haven't anticipated even today.
Re:How long can the growth last? (Score:4, Informative)
15 years ago when you were paying $500 for a 320MB hard drive, did you ever anticipate your home PC would someday have a capacity of multiple terabytes? Could you imagine that a laptop would ever be able to hold over a terabyte?
Yes, yes I did. I notice your very high six digit UID. Now when my father's employer paid something like $20K for a 5 meg DASD the size of a filing cabinet when I was a little kid, I never imagined I could buy my own personal "winchester disc" for less than "a buck a meg" but I finally did that on sale around 1990-ish timeframe. At that point you kind of get the idea that increasing capacity is a way of life. And its been that way for decades.
Re: (Score:2)
It is already over now, to put more data onto a magnetic HD you add more platters or increase the radius, that's all.
Re: (Score:2)
While CPU power seems to double every 18 months or so, for the past (almost) 20 years hard drive size has doubled every 14 months*. Eventually hard drives will be so large that CPUs will never be able to access all the information. I guess then the key is being able to find the information you want to access, which is why I suppose it would be good to buy GOOG even now.
* 40 MB in 1991, 3 TB in 2010. This trend has held true at many points in between.
Re: (Score:2)
Memristor technology is promising 2 petabytes in a cm^3
Re:How long can the growth last? (Score:4, Funny)
Can we move on? (Score:2)
Why can't we just move on and apply the sweet R&D money on the SSDs?
I guess that the "classic" hard drives will reach some sort of physical limit sometime in the (not so distant) future.
Why won't the big boys start to work hard on the SSDs?
It's almost as reading a headline like this "New awesome floppies will be released in a new 10 MB size! - 'USB flash disks are overrated and expensive, nothing beats a good old floppy disk' a spokesperson for a floppy disk manufacturer said"
Re: (Score:2)
"Why can't we just move on and apply the sweet R&D money on the SSDs?"
We already are spending money on SSD's, just because you can afford them doesn't mean everyone or every business needs them. It's a simple cost benefit analysis.
Re:Can we move on? (Score:4, Insightful)
Even the controller/controller firmware design isn't all that similar. HDD controllers have the task of extracting useful digital data from the ever fainter and denser analog magnetic fields on the platter. SSD controllers basically spend their time papering over the fact that Flash has highly asymmetric read/write behavior.
Unless they fancy the idea of trying to recast themselves as semiconductor companies all of a sudden, the HDD guys are doing pretty much the most sensible thing available to them: running like hell in the direction of capacities that SSDs can't touch for less than a king's ransom.
Re: (Score:2)
For the same reason that we haven't all been using Fibre Channel drives for the last 10 years; just because there's something "faster" available doesn't mean that it's good value for money.
I'm quite happy with my cheap & slowish 1Tb magnetic drives for large amounts of infrequently accessed data and don't really want to spend multiple times that for sub-ms access times. Yes, eventually SSDs will probably overtake magnetic storage simply because they have the potential to outdo them in the capacity stake
Re: (Score:2)
I guess that the "classic" hard drives will reach some sort of physical limit sometime in the (not so distant) future.
I believe you'll find that SSDs are closer to their physical limits than hard drives are at this point, though both are likely to hit those limits before long; as I understand it flash memory isn't expected to scale down more than another two or three generations of transistor size.
And there are far more people willing to spend $200 on a 3TB hard drive than there are willing to spend $200 on an 80GB SSD.
Re: (Score:2)
Re:Can we move on? (Score:4, Insightful)
Why can't we just move on and apply the sweet R&D money on the SSDs?
They are.
I guess that the "classic" hard drives will reach some sort of physical limit sometime in the (not so distant) future.
Of course they will. But at that point they'll start talking about alternative form factors if they can't squeeze more bits into the same space.
Why won't the big boys start to work hard on the SSDs?
They are. The problem is that they're still expensive to manufacture and they still need to pay off their R&D.
It's almost as reading a headline like this "New awesome floppies will be released in a new 10 MB size! - 'USB flash disks are overrated and expensive, nothing beats a good old floppy disk' a spokesperson for a floppy disk manufacturer said"
More like "New awesome floppies will be released in 500MB size and cost 10 bucks a pop" circa 2002 when 128MB USB flash disks cost nearly $100. the proportions might be off, but ultimately flash media outran the floppy disk 'cuz it quickly outpaced it in cost/MB, transfer rates were dog slow, and they were incredibly unreliable. Note that in 2010, I bought a 250GB external hard drive for $50 at Wal-Mart, whereas a 256GB flash drive costs over $800 on Newegg. A 1TB Seagate spinning platter drive costs $85 on Newegg, wheras 1TB of OCZ flash memory costs over $3,000 and is the highest I've seen commercially avaialable. I personally don't mind saving $2,915 by using an older technology.
use a 64-bit OS and GUID disk partitioning (Score:4, Informative)
You need to be able to use larger than 32-bit block addresses. This is possible since the LBA spec uses 48-bit addresses. But the internals of some OSes use only 32-bit block addresses. The solution to this is to use a 64-bit OS. That allows 48-bit addresses (and then some).
Another other problem is that the MBR disk partitioning scheme uses 32-bit block addresses, so you can't partition a disk larger than 2TB. But the answer to this is to use GUID disk partitioning.
Finally there's your BIOS, it probably only supports MBR and 32-bit LBA. GUID disk partitioning supports making your disk look like an MBR disk so you can boot off it. You'll have to boot off a partition that starts within the first 2TB of the disk, but other than that you should be okay. Just make sure to never use any tools that think your disk is an MBR disk when you are repartitioning it or otherwise accessing it directly.
Windows 7 (or Vista) 64-bit supports >32-bit LBA and GUID disk partitioning.
And then finally hope you don't get any nasty viruses that try to go around the OS to access the disk (so as not to be detected) and mess it up when the calculations overflow 32 bits.
nominees of the future (Score:4, Funny)
Am I the only one who misread this as "Senate Confirms 3TB Hard Drive"? I didn't even know that machines could be nominated to the Supreme Court!
Re: (Score:2)
Re: (Score:3, Informative)
(a hardware RAID ..... but you get massive speed increases).
Hasn't been true since like the 90s. Linux software raid is always quicker, and far more interoperable and standardized.
Re: (Score:3, Insightful)
Yes, let's design and manipulate an entire standard in order to work around a problem based entirely on the fact that people won't upgrade. And then you just need them to buy this and upgrade their compu...
waaaaaaaaaaaaaait a second.
Re: (Score:2)
Ah, the joy of a really long defrag! And should we use file compression?
Re: (Score:2)
While it's true that FAT32 with 4K cluster size is limited to 2TB, Windows XP defaults to NTFS which can go MUCH higher than 100TB.
LBA also uses 4K sectors, and that's how the BIOS and Windows address the disk. That's as high as you can go with the current implementation of LBA and it goes much deeper than partitioning.
Re:Legacy be damned. (Score:4, Interesting)
We are counting in binary are we not?
Not when it comes to disk drives. The total storage in a spinning media drive is based on the number of platter sides used, which can range from 1 to 6 (or perhaps 8 ... does anyone still use four platters?), the areal density of storage on the surface, and how much of the surface is devoted to spare tracks to cover for manufacturing defects (and probably other factors I'm forgetting). None of these are based on powers of two phenomena.
Re:Legacy be damned. (Score:4, Informative)
No, we are not. We may count in binary for memory, but it's different for physical hard drives with spinning disks. For these, we count in platters (the actual physical disk(s) spinning in the drive).
Hard drives typically have somewhere between 1 to 4 platters. Drives with more platters exist, but they're less common.
Common platter sizes: 500GB, 375GB, 333G, 250GB
I didn't RTFA (this is slashdot, come on), but I'm guessing what Seagate really did was come out with a 750GB platter, that can be used to produce a 3GB drive with 4 of those platters. You'll probably see the 4TB drive you want when they come out with a 1TB platter.
Re: (Score:3, Interesting)
I'm guessing what Seagate really did was come out with a 750GB platter, that can be used to produce a 3GB drive with 4 of those platters.
Minor nitpick but that would be a 6TB drive. Probably 2 dual sided platters at 0.750TB per side.
Re: (Score:3, Insightful)
To any average user the GB on the box is one thing and the GB Windows shows is another. They look at it just like they do CRT diagonal size of advertised vs visible.
Yes both measurements of the CRT are just measurements. One matters to the manufacturer one matters to the consumer.
Take the WD6400AAKS
BOX Windows
640GB = 596.13GB*
Yes 1000/1024 conversion takes me from 640GB advertised to 596GB usable. In your case you mentioned 3TB on the box is about 2,794GB in Windows.
I know this is /. and MacOS/Ubuntu ar
Re: (Score:3, Funny)
why did they bother with 3TB? Should the next step be 4TB? We are counting in binary are we not?
Ok.... then lets call it an 11TB drive then and the next one can be an 100TB drive :)
Re: (Score:2)
Most people can't even fill a 500 GB disk even with all the music they love, their photos and a few movies. Granted, if you digitize -everything- torrent -massive- amounts of music and want lots and lots of HD movies, you might fill one of these disks, however, the number of people who would say "oh, I'm now switching to Windows 7" is low because most of the time people would either A) partition it and put it on a NAS box or B) upgrade t