Let's remember that JBOD means that all HDs are treated as a single, logical
volume, essentially "spanned". If you have two HDs in a JBOD array which
you intend to convert to RAID0 (stripped), then it's best to backup the JBOD
array to another HD, DVD/CD, whatever. You typically don't want to convert
spanned volumes directly to RAID0 since you can't be sure how the JBOD array
is populated (i.e., if any files actually span across the HDs), and how the
RAID controller will treat existing files. It's possible it wil destroy
everything across all HDs as part of initialization. At least I wouldn't
take the risk.
Remember also that I only provided a WARNING. What I recommend is TESTING
the current configuration w/ say, HDTach 3 (free for non-commerical use) so
you have a baseline for comparison! As I said, I found the problem w/
restoring images on *my* hardware, a Promise PCI RAID controller card. Each
RAID controller has its own BIOS/firmware and drivers, they may act very
differently across type and manufacturer. At this time, I'm only saying to
test it, before and after. Afterall, the whole point of using RAID0
(stripping) is to improve performance. If you don't realize the performance
increase, why bother and take the risk that comes from using RAID0
(remember, RAID0 increases the risk of data loss because failure of either
HD in the array typically means loss of ALL data).
If you find the array has NOT increased performance, is it better to do a
complete reinstall? Well, personally I wouldn't do it if I could avoid it.
There are ways to circumvent the problem, but I have to admit, it can get
rather complicated. In my case, I created a FAT32 partition and installed
MS-DOS 7.0 (part of Win98, and available from
www.bootdisk.com) and made it
bootable (as C
. I then restored my XP from image copy to another FAT32
partition as D: (luckily XP was in FAT32 format, not NTFS, or else MS-DOS
7.0 would not have recognized it). I then booted MS-DOS 7.0 and did an
XCOPY from D: to C: (thus I was able to run the file through the RAID0
array!). Finally, I did an XP repair install on C: so it would boot XP, not
MS-DOS 7.0.
Yeah, kind of compicated, and not workable for all cases, but depending on
circumstances, it's possible to make it happen. But again, it may all be a
moot issue if you don't have the hardware problems I found. You may be
perfectly ok, all I'm suggesting at this point is, CHECK. Get before and
after results so you can be sure this effort isn't in vain. Worry about
rectifying the situation later, should you experience the same problems as
me.
Jim
sauvagii said:
Ok - the drives are connected to a Silicon image RAID controller on the
motherboard (board is A8n SLI Deluxe from ASUS).
Disks at the moment are set up in the SI setup (upon boot) as JBOD.
So, by cloning and restoring to the array i'd get no benefit at all, unless
I did a full reinstallation?
I'd be better in that case trying to install from scratch then, wouldnt I?
Thing is, i've tried before (this pc has just been returned as it was sent
back with a perceived MB fault, as the setup BSOD'd after setup, when the
raid controllers were enabled, and the drivers installed during setup). Can
installXP normally if i dont enable the RAID features.
Its been returned with "no hardware fault" - so im reluctant to blitz it and
start again.
)