Setting up Highpoint Rocket Raid 100

jonthelam · 08-30-2004, 04:00 PM

Since I didn't get any response on the hardware section, I thought I might try here since I've noticed there seems to be more activity here.

I'm a bit confused to what's the difference between hardware disk RAID and software disk RAID. From what I understand, isn't hardware RAID a card that emulates a RAID array of multiple drives as 1 drive? If so then why am I seeing 2 drives, /dev/hde and /dev/hdg on my Rocket Raid 100 controller card? Can someone point me to the right HOW-TO? I'm trying to setup RAID 1 and found drivers for this RAID card and quite frankly, I don't know what to do with them after I compile them into a new kernel.

Thanks!

BTW, I am setting this up on Slackware 10 which explains why its on here.

rotvogel · 08-30-2004, 05:27 PM

I think Slackware is shipped with an ataraid kernel (kernels directory on installation cd) . Support is available in the (2.4) kernel , I'm not sure if 2.6 supports it. It wasn't supported in the first couple of 2.6 kernels.

So choose at the installation at first prompt ataraid.i as the kernel of your choice.

It is called ATARAID in the kernel. Some call it software RAID because a lot of the RAID functionality is handled by the driver, not by the hardware so it is not as fast as 'real hardware' RAID. But those 'real hardware' RAID controllers are much more expensive then the one you have.

Software RAID doesn't require any RAID capable controller.

jonthelam · 08-30-2004, 05:50 PM

Thank you rotvogel. Finally an answer! I guess it was pointless to get this RAID controller. Oh well, $45 isn't too bad. Again, thank you for your help.

rotvogel · 08-30-2004, 06:58 PM

It isn't useless, in 2.4 there's good support for the controller. You can setup the RAID partitions using the BIOS of your controller. The devices will appear in /dev/ataraid/d0p1 for example when your kernel will have support for it (compiled in or as module if it isn't your root disk).

I had this RAID0 diskset which was really fast (and unsafe) but it worked fine. I have an integrated Highpoint 370A controller, maybe the same as you have (lspci -v will tell). It will show up like this:

Code:

00:13.0 Unknown mass storage controller: Triones Technologies, Inc. HPT366/368/370/370A/372 (rev 03)
        Subsystem: Triones Technologies, Inc. HPT370A
        Flags: bus master, 66Mhz, medium devsel, latency 120, IRQ 11
        I/O ports at d400 [size=8]
        I/O ports at d800 [size=4]
        I/O ports at dc00 [size=8]
        I/O ports at e000 [size=4]
        I/O ports at e400 [size=256]
        Expansion ROM at <unassigned> [disabled] [size=128K]
        Capabilities: [60] Power Management version 2

jonthelam · 08-30-2004, 09:20 PM

Thanks again. Which HOW-TO do you recommend me reading? I have printed all of them and I'm eager to know which one to start in.

suslik · 08-31-2004, 12:04 AM

"Software" vs. "Hardware" RAID.
I think your card (HPT370-based) is "Semi-Software", like "Win Modem" is semi-software. But, for ease of use, just refer to it as "Hardware". Essentially you treat it like a fancy IDE controller, and as such, set up the RAID sets in "BIOS"-like manner, before booting OS.

The creation of RAID sets is external to Linux, Windows or Other. However, the manufacturer has the RAID tools for Linux for this particular controller on the web site. (see link bellow) Ideally, Linux will never know it is booting from a virtual RAID drive. With "software raid" (of which you probably have all the HOW-TO's) linux itself bunches up the IDE channels to create RAID disks. The key to hardware RAID: (a) easier to install OS onto RAID set and (b) less load on CPU.

For your card, the best approach is to follow the directions in the HPT's driver package. GO here to "Linux Source Code" section. Get the latest version package, and look for readme.

jonthelam · 08-31-2004, 02:07 PM

Cool! I booted from the Slackware CD and issued the ataraid.i kernel to load. This actually gave me the /dev/ataraid/d0 device which mirrored bot /dev/hde and /dev/hdg. I repartitioned and reinstalled Slack 10. Had some issues with LILO but is not resolved and I'm up and running.