I would suggest that you go for one that uses a RAID solution to get the TB of storage, rather than one with a single drive. As you'll generally get better performance from a RAID array. Also, if you're able to make use of it, eSATA will give you much better performance than firewire.
Of course there are other ways to use RAID that will offer other benefits.. most notably data redundancy.
Here's how it breaks down:
RAID 0: "stripes" the drives. Which means that 2 or more drives will appear as one -- like 2 500G drives appearing on the system as a single 1TB drive.
RAID 1: mirrors your data. This is great because you always have full access to all of your data, even if a disk goes bad, the backup takes over. This requires identical pairs (2 500G drives would show up as a single 500G drive) and the cost is more expensive to get to your target storage size.
RAID 1+0: This setup uses both RAID 0 and RAID 1 configurations simultaneously. The first half of your drives are striped together, then the second half are striped together and mirror the data of the first half. Example, 4 500G drives are visible to the system as a single 1TB drive, but you have data redundancy.. it would essential set up the 4 drives as 1a, 2a, 1b, 2b the a's are striped together, and the b's are striped together so you end up with 1a+2a, 1b+2b. This configuration would allow for up to half of your drives to go bad before you have data loss, as long as you don't loose the same number drive from both arrays (ie: 1a and 1b.. but 1a and 2b would be ok, as would 1a and 2a)
These are the most commonly used in the non business world. As for me, I'm going for a RAID 5 array...
RAID 5: More or less gives similar protection as RAID 1, or RAID 1+0, but the investment is lower. Technically it's not the same protection as the data isn't mirrored, but rather parity checksum information is generated so the data can be rebuilt. The way this works is the total storage size is equal to (((number of drives) - 1) * size of single drive). So, suppose you were using 3 500G drives, the total storage available would be 1TB. At that size it doesn't offer much cost saving over RAID 1+0, but now imagine you wanted a 2TB array using the same size disks: with RAID 1+0 that would take 8 500G drives, with RAID 5 it would only take 5 500G drives... etc. However, the limitation here is you can only loose one drive, and when one goes down you have to replace it before you can access your data -- it would still be good to replace a failed drive ASAP in a RAID 1+0 array, but it would still work without doing so.
Here's more complete info about RAID (including the other RAID levels I didn't speak about):
http://en.wikipedia.org/wiki/Standard_RAID_levels
As for the original question --
spinner said:
Can anyone tell me the differences in hard drives besides the make and costs?
Interface(s) -- USB 2.0, ieee 1394a, ieee 1394b, esata... generally the more they have the more it will cost, but not always.
RPM -- The speed the drive spins. Two most common speeds are 5400 or 7200 revolutions per minute. However there are also 10000 rpm drives. The faster it spins the better, because it will speed up read & write times.
Seek Time -- Also important, though most drives are somewhere between 8 and 13 milliseconds for average seek time. This is the average speed it takes for the drive to locate where on the disk something is stored. The faster this is, the more quickly the drive will respond.
Cache -- Hard disk cache's are an important element of a computer system whose primary aim is to increase overall system performance by saving data in faster banks of RAM. Hard drives have a cache built in to hold data that is being written to or read from the hard disk. The purpose of doing so tries to reduce the number of occasions in which data has to be physically written and read from the hard disk platter. By retaining recent data within the cache performance is increased as this memory is much faster and saves time on repeat recalls. So, you want the largest cache you can get. (typically the largest you can find is 16MB)