Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

My understanding of RAID 0 is that the data is split and striped across all of the drives in the array. If there is only one drive in the array, then what is the point of a single drive RAID 0 array and how does it work?

From these ceph benchmarks it appears there is a tangible performance difference as compared to JBOD in at least some cases.

Despite my best Googling I could not find anything substantial. Thanks!

share|improve this question
The difference is whatever the particular implementation wants it to be. It can be everything or nothing. There's really no such thing as "single drive RAID 0", so a particular RAID implementation can mean anything by it. –  David Schwartz Jan 23 '13 at 5:05

4 Answers 4

up vote 5 down vote accepted

In the case of this implementation (the LSI SAS2208 controller), JBOD does not use on-board cache, single disk RAID0 uses on-board write-back cache. The ceph benchmark explains it in the test setup. The performance increase comes from caching not striping. Most RAID controllers allow you to setup single disk RAID0 or RAID1 as a way to support JBOD, this controller is a little different in that it also supports JBOD (without any controller cache).

There are cases where RAID levels can use less disks than you normally think, and still provide increased performance or redundancy. For example Linux md RAID10 can be used with two or more disks, including odd numbers of disks, unlike traditional RAID10 which would require four or more disks and even numbers. Linux md RAID10 with two disks is faster than RAID1.

share|improve this answer
Wow, thanks for the great answer! –  JKnight Jan 25 '13 at 5:12

There is no such thing as a single drive RAID 0 array. In order to setup a RAID 0 array, you would need two or more disks. I think you are mis-reading the test setup in the article you reference.

However, you are correct, in that in a RAID 0 array (note not RAID 0 mode) data is striped across all disks in the array. This is an odd RAID level as there is no real redundancy, as a failure of one drive will fail your array. RAID 0 will give you the total amount of space available on all disks for your array as long as they are the same size, with no redundancy or fault tolerance. If they differ in size, each disk will be relegated to the size of the smallest disk in the array.

share|improve this answer

It's also useful to mention here that some server configurations require you to load the RAID regardless of how many physical disks are actually present.

For example, a server chasis where you can only access the disks through a controller board.

In this scenario, RAID 0 is the default setup.

share|improve this answer

RAID-0 on single disk is used mostly on SSD disks, which acts as Cache disk (Intel Smart Response). When you activate "accelerate mode" for any HDD or RAID Volume via SSD Cache, IRST driver converts disk to RAID-0 Volume. If you are not using whole disk space, there will be automatically created second RAID-0 Volume, which can be used for other data. My example:

enter image description here

I am not sure, why it has to be in RAID mode, as I see no benefit from it. Maybe for some specific operations there is minor boost.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.