Two or more hard drives as one?

theDreamer

2[H]4U
Joined
Oct 11, 2006
Messages
2,513
I know the way everyone is going to say is to go RAID, but I would like to not go RAID.
My hope is there is an easy or just a way to combine hard drives.

Here is what I would like it to look like.
Hard drive 1
Hard drive 2+
Drive D:\
If I write to drive D:\ then the data is only on one drive so if one drive fails all that is lost is the data on that one hard drive. The two things I seem to be seeing the most of so far is dynamic volumes (wrong term maybe) where it combines two hard drives and splits the data (this sounds just like RAID). The other option I have heard but read less on is adding a hard drive not as a drive letter (like D:\ or E:\), but as a folder under another hard drive. My concern if this is possible, if the main hard drive (non-folder hard drive) fails, what happens to the data on the hard drive that is just a folder?

I am not sure if this was explained properly, but in the end I just want to combine two hard drives to be one physical drive letter in Windows. Also, I will be using Windows Vista with this build most likely, but if another OS is easier than let me know please.
 
You can do drive spanning in Windows 2K, XP, and Vista so long as the drives you want to span are not the boot drive and are converted to dynamic volumes (which you can do without losing data).
 
What you are describing is Raid 1 which is drive mirroring. I did this with my server boot drive incase one went belly up I'd still have a functioning server while I could source a replacement hd.

I'm not sure what your aversion to RAID is? Most motherboards have onboard raid which is slower but should work for what you want. Also Raid 1 can be acomplished with a software raid.

If you are totally not wanting to go with a raid type setup you could use a program like SyncToy (free from microsoft) that will copy folders to match. It wouldn't be instant copy but you could program it to run mulitple times a day so at worst a fatal crash would only result in losing what you haven't synched between synch's.

Zack
 
Correct me if I"m wrong BlueFalcon but I think the only version of Vista that does dynamic disks (assuming its the same as dynamic volumes) is Vista Ultimate.

I know I tried converting my disks to dynamic on vista home premium but it said that wasn't in my version of windows. I then did it on my Windows Server 2008 box and it worked fine.

Zack
 
No, I am not wanting to do mirroring, I might have wanted to describe what this build will be for.
This will be purely data storage in the 30-40TB size, but I know windows can only assign so many letters to drives and I will be running out of letters. Therefore I was hoping to combine drives, without RAID.
 
You can do drive spanning in Windows 2K, XP, and Vista so long as the drives you want to span are not the boot drive and are converted to dynamic volumes (which you can do without losing data).

So by having two (or more) hard drives I can do dynamic volume (spanned) and if one drive fails I only lose the data of that one drive? Also, these multiple hard drives can be displayed under Windows as a single drive letter?

If this is true, that seems like exactly what I want and just need a link to the proper setup of this.
 
Maybe give Windows Home Server a try? I haven't tried it myself yet, but it sounds like what you're looking for.
 
Just found some articles on Microsofts website about dynamic disks and it seems spanned volumes does what I want, but this worries me:

Spanned volumes do not provide fault tolerance. If one of the disks containing a spanned volume fails, the entire volume fails, and all data on the spanned volume becomes inaccessible. The reliability for a spanned volume is less than the least reliable disk in the set.

So if one drive fails, my whole set of data is lost.
 
I'm a bit curious why you want 40TB in one box. I'm not being condescending but I think I'd be worried about failures. I think with that many drive letters/ drives I'd want some sort of raid to help with failures.
 
I'm a bit curious why you want 40TB in one box. I'm not being condescending but I think I'd be worried about failures. I think with that many drive letters/ drives I'd want some sort of raid to help with failures.

I recently finished my HTPC and have realized that I can easily back-up my, rather large, DVD collection and stream it over my network nicely. While DVDs do not take up much space, I do 1:1 back-ups, and I have already bought into Blu-ray and have started building up a nice collection of movies and I will continue my 1:1 back-up with those also. Rather large downside to all of this, it takes up a lot of space to back-up my collection (have already bought four 750-1,000GB hard drives for my main desktop and almost through those).

No offense taken or anything, this was a massive undertaking when I started thinking about it and I keep trying to tell myself no, but in the end I really think I need to have good quality back-ups of my movie collection. Especially with the ease of streaming to my HTPC. Also, failures is a big concern of mine, which is why I do not want to do any stripping of data, and since I have all the movies if one drive fails I just need to re-buy a new hard drive. I just want to shrink the amount of drive letters I will end up with.
 
You can do drive spanning in Windows 2K, XP, and Vista so long as the drives you want to span are not the boot drive and are converted to dynamic volumes (which you can do without losing data).

This is true but if lose a disk you will lose all the data on that drive just as if it were a single drive...no redundancy

What you are describing is Raid 1 which is drive mirroring. I did this with my server boot drive incase one went belly up I'd still have a functioning server while I could source a replacement hd.

I'm not sure what your aversion to RAID is? Most motherboards have onboard raid which is slower but should work for what you want. Also Raid 1 can be acomplished with a software raid.

If you are totally not wanting to go with a raid type setup you could use a program like SyncToy (free from microsoft) that will copy folders to match. It wouldn't be instant copy but you could program it to run mulitple times a day so at worst a fatal crash would only result in losing what you haven't synched between synch's.

Zack


He does not want RAID1 or RAID at all.

Maybe give Windows Home Server a try? I haven't tried it myself yet, but it sounds like what you're looking for.

WHS FTW if you are wanting a massive storage server WHS is the way to go....most of the guys here that have massive storage servers are now running WHS because it provides fault tolerance on the data we choose, and NO RAID issues to deal with.
Check out Ockie, gjvrieze, or my worklog to see what we have done.

I'm a bit curious why you want 40TB in one box. I'm not being condescending but I think I'd be worried about failures. I think with that many drive letters/ drives I'd want some sort of raid to help with failures.

This way you never have to delete anything.
All my Data is either backed up or has at least some sort of redundancy.
Media Server
TS Gateway
Backup Server
VM Server
Etc.
 
nitrobass24, thank you, I did not even think about WHS, and that might be what I need. I have read through most of Ockie's build's, I will read yours and gjvrieze this week and see what you guys did. From just doing a quick read on WHS, it seems it eliminates the need for drive letters which is perfect.
 
If you want to do this in Linux you just have all your individual drives mounted whereever and then run use:

mhddfs /drive1,/drive2,/drive3 /alldrives

It'll merge all the dirves together and when you write it will write to the first drive until its filled then go to the second and so on... all drives have their own file system and everything.
 
If you want to do this in Linux you just have all your individual drives mounted whereever and then run use:

mhddfs /drive1,/drive2,/drive3 /alldrives

It'll merge all the dirves together and when you write it will write to the first drive until its filled then go to the second and so on... all drives have their own file system and everything.

If I were to go that way, what distro would be a good option to look at?
The most I have played with is Ubuntu.
 
This is true but if lose a disk you will lose all the data on that drive just as if it were a single drive...no redundancy




He does not want RAID1 or RAID at all.



WHS FTW if you are wanting a massive storage server WHS is the way to go....most of the guys here that have massive storage servers are now running WHS because it provides fault tolerance on the data we choose, and NO RAID issues to deal with.
Check out Ockie, gjvrieze, or my worklog to see what we have done.



This way you never have to delete anything.
All my Data is either backed up or has at least some sort of redundancy.
Media Server
TS Gateway
Backup Server
VM Server
Etc.

What I was mainly referring to is maybe using two 20TB arrays so that way if one whole computer fails traumatically you are not down the whole shebang. You can still backup/stream off of two seperate boxes just as easy as one.


I must admit though I'm going to try WHS soon, I already ordered the free trial from microsoft, just waiting for it.

Zack
 
If you want to do this in Linux you just have all your individual drives mounted whereever and then run use:

mhddfs /drive1,/drive2,/drive3 /alldrives

It'll merge all the dirves together and when you write it will write to the first drive until its filled then go to the second and so on... all drives have their own file system and everything.

Yea that would work but it is essentially the same thing as disk Spanning under Windows, you dont have redundancy and your data is at risk. If you dont care about the data you have then spanning or this is an option.

But I have had Data loss on stuff that I would deem not-critical, and replaceable....but it still SUCKED.
So for me I want to avoid Data loss.
And with an Array as big as you are talking about you will using at a minimum 20 drives, and with every drive that you add your chance for failure increases.
 
What, I thought he didn't want redundancy?

If a single drive fails thats the only data that is lost... the rest of drives data is fine. mhddfs is just to merge individual drives together and use as a single dirve... they're still all unique. Same as WHS without duplicating data.

--edit-- btw no its not like disk spanning
 
I was under the impression that he wanted some form of redundancy.
mhddfs is kind of like using libraries if you will....one folder with data from all sorts of physical places

as far as the losing data goes expalin how its not like disk spanning? I used Spanning at first when I only had two drives and when one died I still had the data that was on the other drive. Its not like RAID0 where if I lose one drive I lose it all.
 
Well typically spanning is like concatenating drives together to create a single large drive. It is working below the file system. The file system is put on this single large drive. If you lose one drive you've lost a chunk of th file system. You might be able to recover data but things will not go on working as normal.

Typically it is like RAID0... all the downsides with none of the upsides... really only reason to span is usually to use different sized drives and add on to a existing drive-- eg LVM's spanning. After you add to a single drive you then need to grow the file system.

I guess some other program might call merging to file systems together spanning but that'd be a poor name-- spanning has been around a long time as something else.
 
Well yeah sorta, JBOD has two meanings, come people say JBOD=Spanning=Concatinating others say JBOD is just totally individual disks. Really depends on the RAID controller you're using.
 
The other option I have heard but read less on is adding a hard drive not as a drive letter (like D:\ or E:\), but as a folder under another hard drive. My concern if this is possible, if the main hard drive (non-folder hard drive) fails, what happens to the data on the hard drive that is just a folder?

Yes, this is very possible if you are running NTFS.

Nothing will happen with the mapped drive, if the other one fails. If you map d: as c:\myDdrive, when you go into myDdrive, it would be as uif you went into d:

If c: fails, you just go into d: directly
 
Back
Top