As an experiment, I'm trying to figure out what is the cheapest possible way to get an insane amount of storage for a home-based media server. RAID is important, since I don't want hardware failures destroying data. Here is one possibility, an 8 terabyte monster which would use NTFS dynamic disks to stripe multiple individual RAID-5 arrays into one single volume.
Cost per raw gig: $10999 for 12 TB, $0.89 per gig
Cost per RAID gig: $10999 for 10.4 TB, $1.05 per gig
I'm not really liking this plan too much due to the high costs of the PCI-X motherboard and the need for separate power supplies. With all the specialty components, it would need about $1500 worth of hardware just for the case, motherboard, power supplies, CPU, and memory, before I even get the first terabyte installed.
I'm looking at making smaller servers with just 8 drives per system, but AFAIK you can't merge RAID volumes across multiple servers with NTFS, so that limits the unified-storage capacity..
1. lesser power supplies are okay, no need for 2 700w
- estimated power consumption per drive: 10 watts
- 10w * 40 = 400 watts
- supermicro recommends 420w for motherboard
2. added CPU, memory, CD/DVD, and floppy costs to flesh out costs (newegg)
3. I had done some incorrect RAID5 efficiency calculations. A bigger array means more space available in the array set. An 8-drive array allows 87% efficiency rather than merely 66%, and gives a much lower cost per gig..<P ID="edit"><FONT SIZE=-1><EM>Edited by Scalar on 03/20/05 08:06 PM.</EM></FONT></P>
I don't think NTFS is goona work on there if it is made into one 8TB volume. NTFS can only support somewhere around 2TB I believe. You will need to put a linux distro or unix on there. That would make it more secure/reliable anyway, lol.
<i>In theory, the maximum NTFS volume size is 264 clusters minus 1 cluster.
However, the maximum NTFS volume size as implemented in Windows XP Professional
is 232 clusters minus 1 cluster. For example, using 64-KB clusters, the maximum
NTFS volume size is 256 terabytes minus 64 KB. Using the default cluster size
of 4 KB, the maximum NTFS volume size is 16 terabytes minus 4 KB.
Because partition tables on master boot record (MBR) disks only support
partition sizes up to 2 terabytes, you must use dynamic volumes to create NTFS
volumes over 2 terabytes. Windows XP Professional manages dynamic volumes in a
special database instead of in the partition table, so dynamic volumes are not
subject to the 2-terabyte physical limit imposed by the partition table.
Therefore, dynamic NTFS volumes can be as large as the maximum volume size
supported by NTFS. Itanium-based computers that use GUID partition table (GPT)
disks also support NTFS volumes larger than 2 terabytes.</i>
I don't think I'd want to boot off the thing anyway. Better to use a separate drive, so if Windows crashes and burns you only rebuild one drive..
It sounds like it might be a personal media server? If so then you probably don't need good access time or throughput?
What about simply buying the cheapest $/GB drives on the market and buying USB converters for them all, I'm pretty sure you could then hook all drives up to only ONE computer with by filling it with USB controller cards. You can then also create your own powersupply for the drives by getting a used high quality 5V+12V industrial power supply. It should be very easy to create and this it has to be the cheapest possible method of creating a big array out of standard components.
Also the easiness of setup and expandibility of this system would be unsurpassed, the only drawback of it is obviously the speed of the array being limited by USB 2.0, but as a media server this may not be an issue for you. I think you could even get around the speed issue by configuring the drives in the same RAID array on different USB controllers if you know what I mean.