HighPoint RocketRAID raidtool

Thanks to Gegereka I managed to download the raidtool.exe, and share it here for your convenience.

I could not locate it on the manufacturer's website, although they do have a good driver selection, e.g. for the Highpoint Rocketraid 2300
Update: HighPoint's customer support provided a newer version of the tool to me. I did not try it, but I have uploaded it for you. They took approximately 2 business days replying. See below for their reply and instructions:

Hello,

You can try using the tool, but it's hard to say what state the data is in, as the failure occurred during recovery mode (rebuild).

The disabled status is assigned in cases where multiple disks have failed, or the parity is faulty.

It requires that the system be booted to DOS mode, and is able to access the card's BIOS/firmware.
It is a graphical utility that is similar to our controller cards' BIOS display.

Instructions:

The utility is as a compressed file (.zip format).

It's DOS based, and graphical – it responds to standard keyboard inputs.
If you need a DOS boot diskette or CD image, we recommend visiting this site (downloads are free):

http://www.bootdisk.com

To run, boot to a DOS floppy, and use the following command:

raidtool.exe

Use the arrow, Alt, and Tab keys to navigate the windows, and the Enter key to select a device (disk, array), and execute a command.

It is capable of many different functions.
The functions you will want to use are:

Save Array Info
Delete Array
Create Array

1) Use the arrow/tab keys to highlight the array, then press the Spacebar or Enter to select it.

2) Click Alt and use the arrow keys to highlight the "Array" tab. Press down and select the "Save Array Info" option – this will save the current RAID configuration to the boot media (floppy or USB drive required).
Next, use the "Save MBR" option – as above, this will save the configuration data to the floppy.

3) Next, use the Delete option, and delete the RAID arrays.
This option will not delete actual, useable data from any of the disks, and will not damage the partition tables – it was designed specifically not to. It is simply a way clear out any junk RAID data, or "disabled" status from the disks.

4) Next, use the Create option and recreate the array. This is similar to the card's BIOS menu.
Do not worry about the Build options in this case.
If it insists you select an option, choose "No Initialization".

Once recreated, exit the utility and reboot – make sure the card's BIOS recognizes the array correctly (Press Control + H when prompted).
If not, you can always run this utility again – it can be used as many times as needed. Do not attempt to rebuild or verify the array unless you can access the volume.

Regards,

Customer Support Department

If you're under no time pressure you might consider getting in touch with HighPoint's customer support yourself.

You have to run the raid tool from DOS. Download a boot disk creator from here. I used DOS 6.22 without problems, having DOS on one floppy disk and the rocketraid tool on another floppy (you can just switch them after booting, use dir to show the contents and type raidtool to start the raidtool).

Before you do anything else: write down the information about your current RAID setup. You can get it by using ARRAY->Information / other self-explanatory menu entries. You will need it later to recreate the RAID. Information you will need includes: Array name, RAID type, Cache policy, Block size and sector size.

Tip: also write down the exact identifiers of your harddrives (even same models have unique numbers in the end) and which channel and place which harddrive is assigned. You might need it later to recreate the exactly same RAID setup you had.

You have to delete the RAID(s) and create a new one (use enter in the drives window to enumerate the drives in the correct order, numbers will appear beside them, then use create from the Array menu.)

You also might want to save the previous configuration to the floppy before deleting.

Attention!! Ensure that no initialization / keep old data is selected! () The tool will apply the new RAID information once you OK the dialog.

I Repeat: do NOT initialise the drives – this means actually deleting the data which is on them! (There's also an option to do that in the BIOS / boot time configuration. Do not use it!)

Be sure to check out this very helpful thread in it's completeness on the hardforum before working with the tool. Below, I reproduce an essential part from it – should the hardforum ever remove the thread.

"Hello,

Attached is a RAID recovery utility – it may be able to remove the disabled status.
The disabled status is assigned in cases where multiple disks have failed, or the parity is faulty.
Try using the all of the original disks first (including the drive originally listed as failed).

It requires that the system be booted to DOS mode, and is able to access the card's BIOS/firmware.
It is a graphical utility that is similar to our controller cards' BIOS display.

Instructions:

The utility is as a compressed file (.zip format).

It's DOS based, and graphical – it responds to standard keyboard inputs.
If you need a DOS boot diskette or CD image, we recommend visiting this site (downloads are free):

http://www.bootdisk.com

To run, boot to a DOS floppy, and use the following command:

raidtool.exe

Use the arrow, Alt, and Tab keys to navigate the windows, and the Enter key to select a device (disk, array), and execute a command.

It is capable of many different functions.
The function you will want to use are:

Save Array Info
Delete Array
Create Array

1) Use the arrow/tab keys to highlight the array, then press the Spacebar or Enter to select it.

2) Click Alt and use the arrow keys to highlight the "Array" tab. Press down and select the "Save Array Info" option – this will save the current RAID configuration to the floppy – we can have engineering analyze this necessary (default disk order is sequential – channels 1 through 4).

Next, use the "Save MBR" option – as above, this will save the configuration data to the floppy.

3) Next, use the Delete option, and delete the RAID arrays.
This option will not delete actual, useable data from any of the disks, and will not damage the partition tables – it was designed specifically not to. It is simply a way clear out any junk RAID data, or "disabled" status from the disks.

4) Next, use the Create option and recreate the array. This is similar to the card's BIOS menu.
Do not worry about the Build options in this case.
If it insists you select an option, choose "No Initialization".

Once recreated, exit the utility and reboot – make sure the card's BIOS recognizes the array correctly (Press Control + H when prompted).
If not, you can always run this utility again – it can be used as many times as needed. Do not attempt to rebuild or verify the array unless you can access the volume. "

My own story

I was asked to help with file recovery on a Windows 2003 server running completely off a RocketRAID 2300. 4 drives à 400 GB capacity connected together in a RAID 5. The problem was: the second drive was marked "critical", and the fourth drive failed completely once it was accessed, and was marked "disabled". Meaning, I would not be able to run the RAID at all, even for recovery purposes.

As things were, it would not even boot into Windows Server 2003 – it would keep restarting before reaching the login screen. After using F8 to enter the advanced  boot options, I disabled "automatic restart on failure" (translated from German), and got a blue screen instead: "UNMOUNTABLE_BOOT_VOLUME"

If I would rescan from the management tool, the RAID would come up again, trying to rebuild itself – and failing.

After using the raidtool.exe to rebuild the RAID properly, I could not boot into the (native) Windows on the RAID anymore: "NTLDR is damaged".

File recovery software

Linux

There are drivers for Linux, also this document unspecifically about dmraid might be of some interest. Unfortunately, I fear, that it is too complicated to set up a new Linux with correctly installed drivers and settings for recovery purposes and could even destroy data. I have not tried it and advise against it for people who are not Linux-savvy and know their way around the tools already.

Further reading

Here's a good overview introduction to RocketRAID cards (RR 2340) – they're not "entirely" a hardware RAID system.

Use Wikipedia to read more about RAIDs.


7 Responses to “HighPoint RocketRAID raidtool”

  1. Andrew Says:

    What if i don't have a floppy drive ? any way to this ?

  2. Andrew Says:

    i just heard from Highpoint, its now biult into the windows gui (high point web raid) it worked perfect and only took about 2 minutes here's the text for it (they include screen shots)

    1.
    select “Manage – Array" from the
    menu.

    2.When two disks are offline,the RAID array status
    is Disable.Click  “Maintenance” on the top
    right corner ,pop-up a dialog box”Array Information”.

    3.     
    Delete the array—from the Array Information
    dialoge box ,select “Delete”button, at this time it will prompt: “The data on
    the array will be deleted,will you continue ?”, then select OK.

     

    4.     
    Return to the Mnange/Array page, at this time
    the array has been deleted. Then double-click “Create Array”button,it will display
    a page “Create Array”. Select “Keep old Data”(required) from Initialization
    Method column, As for other options,keep the same as the original RAID6 setting.

    5.     
    Click”Create”and the initialization will start
    automatically. After RAID6 recovery has finished, it will prompt:successfully
    creat. Select OK.

     

    6.     
    Right-click on “my computer”,and select
    management,then select disk management, on the right column below you can see
    restruction of RAID6 partition. The information should be the same as the
    original RAID6.

     

    7.     
    Open RAID6, and the data has been restored, and
    the rebuiled RAID6 shows nomal.

    oh and High point got back to me in less than 24 hours :)

  3. Andrew Says:

    also this worked perfect on my Raid 10.

  4. Ray Says:

    Will this work for RAID 5?

  5. Max Says:

    Hello Ray,

    In fact the problem I had with the Rocket RAID Controller was with a RAID 5.
    I highly recommend you to consider another option, RAID 5 may fail catastrophically, and you may lose all your data. It is not state of the art to use it anymore.
    Also you may be better off with a software RAID solution, i.e. under Linux.
    Good luck!

    Please take a look at my project surfnext.com and tell me what you think about it. Thank you!

    Max

  6. Max Says:

    Ray,

    Is Windows being booted off this RAID array?
    If so, I advise against using the GUI utility or working in Windows (well I think if the array is broken it should not boot, thus actually answering my question but just in case …)

    Also you might want to take the time to double-secure your operations and note down the parameters of the current RAID using the DOS utility, as I have described in the article.
    Even if rebuilding it with the GUI utlity would fail, you would still have a second option to try to do it using the DOS utility.

    As to whether it will work or not – my educated guess is, it should, but be extra careful to select “Keep old Data”(required) from Initialization
    Method column as Andrew described. If you want a 100 % reliable answer you probably should contact Highpoint support.
    I actually rebuilt my RAID 5 array, but using the DOS utility.

    Be aware, that the data may be out of sync already, so some information might be lost after restoring // or might be junk.
    But, using a file recovery utility you might manage to get at some of the data at least.

    Good luck, please post if you have been successful or not and what steps you have taken.
    Max

  7. Chris K Says:

    I just performed Andrew's steps (details on Apr 28) in Ubuntu and it is working. I *had* the raid6 running as a spare drive in CentOs. The big San Diego power outage made it so CentOs wouldn't boot as it wanted to fsck the raid. The raid didn't want to rebuild because it said a drive was bad.I went around and around with this just like I see all over the forums. So I install a new OS on the not-raid hdd. I chose ubuntu 10.04 LTS. I did the steps in the 1st post here: http://ubuntuforums.org/showthread.php?p=10712667  to install the "driver" and get the web GUI running. THEN I followed Andrew's steps the same as he did for Windows, only I had to "Delete" the RAID twice. The first time was the 3 remaining drives and the 2nd time was to catch the "failed" drive. THEN I created a new RAID 6 using old data. I ssh'd into the server (has gnome-core) and ran gparted & and gparted sees the disk but it's not formatted or anything…I click on the raid via the htpserver and asked it to verify. In 10 hours, I'll know if I get to keep my recent work. Last backup was a couple weeks ago… :P I've ordered the battery module for the raid card, and once ubuntu is installed, it will monitor the UPS via usb cable and do a shutdown… like I should have made it do years ago. Oh, and 5 new drives are coming… going to check them all then have 4 in with a ready spare.

Leave a Reply