help about JBOD

[isaacyang]

I have some questions about JBOD mode.
As I know,it is a kind of RAID.
When I read reviews about NF3 chipset,I found some articles say that NF3 support JBOD.
But when I go to NVIDIA homepage, I found they only claim to support RAID 0,1,0+1.And actually I found this in THG.
Then my question is
1. Do NF3 support it?
2. Which chipset or southbridge support it?
3. Is there any guide on how to build a JBOD system? Is it just like building a RAID 0,1 system?


thanks

 

[Gamingphreek]

All JBOD does it combine 2 drives. It is essentially a slower version of RAID-0 in which you dont have to have 2 of the same size drive.

If you can help it stay away from it, go RAID-0 or no RAID (of course if RAID-1 or 5 if you have reasons for them).

-Kevin

 

[RaymondY]

I too second that unless u need RAID-0, stay far away from it. I experimented with RAID-0 sometime back and found that there was a slight benefit from it in terms of speed but when one of my HDD took a dump I lost everything. What u pick up in speed is conversely offset by the increase chance of RAID failure because of the 2 or more HDD u have tied to RAID.

 

[beatle]

You could always run the disks as a spanned volume in Windows. No special hardware needed.

I'd only do this if my data were backed up, as this is just as risky as RAID 0.

 

[isaacyang]

I know that there is no performance boost with JBOD.
But you can use some of your little HD together as one single HD.
I just want to know if NF3 or NF4 series support it.
As I know via's VT8237 support it.
And I want to know how to build one JBOD system,and how to install OS on it.
I guess you have to press F6 when installing Windows to recognize the SATA HD first.
But when and how to build the JBOD?
Just after F6?

I just want to know it technically,thanks for the reply.

 

[sunase]

>You could always run the disks as a spanned volume in Windows. No special hardware needed.
>I'd only do this if my data were backed up, as this is just as risky as RAID 0.

Actually I had a drive die when part of a span. After forcing it to activate in disk management all of the files were still visible, files that used to be on the dead drive gave an error when you tried to access them, and files on the surviving drive were usable and copied off fine. So no more risk than using them singly IME, although, it's always possible they don't duplicate the file table and the drive that survived just happened to have it.