Hi there

To people implementing Software RAID systems there seems to be a confusion over JBOD (just a Bunch of Disks) and RAID 0.

JBOD is simply that -- the system treats a bunch of HDD's as a SINGLE HDD -- but data is read / written to each HDD in turn -- once one is full the next one gets written to. No striping or increase in performance. It's also a bit useless if you want to share data between LINUX / NAS type systems and Windows.

RAID 0 - treats the same set of HDD's as a SINGLE HDD - but has parallel I/O paths so READ / WRITE is much faster - all HDD's in the array are used. RAID 0 arrays also can be shared / moved across systems and can also be used as shared networked drives on Linux / Windows. You can create any recognizeable file system on a Linux software RAID 0 device -- I recommend EXT4 as it's fast, reliable and can be shared with Windows (via SAMBA) on Networked devices.

For both these systems of course if one HDD in the array / JBOD set fails then you lose everything but in a lot of cases provided you have some backup the performance gain in using RAID 0 is very worth while - especially with older and slower HDD's.

These days also HDD failures on HOME type gear are relatively rare -- HDD's if they fail will usually fail fairly quickly from new -- and often you'll get some type of (non system) warning they might be going such as intermittent "funny" noises etc.

I know NAS systems are being used by load more people these days --it's also important to ensure NAS data is also backed up too !!!!!!.

Personally I'd steer well clear of JBOD and choose RAID 0 over that any time !!! especially on Linux type systems where the software RAID built into the kernels and configured with MDADM is almost as good as Hardware RAID itself. - especially if you boot from a separate SSD and use the other HDD's purely as storage data.