**SOLVED** Straight Boot off Hardware RAID 1

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
shurguywutt

**SOLVED** Straight Boot off Hardware RAID 1

Post by shurguywutt »

Coming from this thread http://forum.linuxmint.com/viewtopic.php?f=49&t=63958 about my Highpoint Rocketraid 2640x4 controller that I am using for 4 hard drives set up in hardware RAID 1. I finally got the hardware working, now my problem is with the boot sector.

1. I boot from the Kernel 2.6.35-22-generic Linux Mint x64 Live CD

2. Desktop opens, I check my devices, no RAID devices are detected.

3. Using the terminal I do the following:

Code: Select all

# sudo apt-get update
# sudo apt-get install
No errors.

4. Download the Open Source Linux 2.6 driver from Highpoint-tech.com

5. Create a temporary file and extract the driver into the file.

6. Run the following in terminal:

Code: Select all

temp2/rr2640-linux-src-v1.2/product/rr2640/linux $ sudo make
... $ sudo make install
No errors. Drivers load (into LiveCD Physical memory hard drive).

7. Run terminal:

Code: Select all

$ sudo modprobe rr26xx
RAID devices show up in Live CD explorer.

Now I open the installation cd and continue to install Linux on the Hardware RAID1 device.

I clear the RAID1 device and do a fresh install in ext4 format.

8. Installation finishes, I remove the Live CD and I reboot. Check BIOS boot priority and ROCKETRAID hardware device is 2nd boot device after CD ROM. I continue through BIOS and exit.

9. Black screen loads with flashing "-" in the top left corner of the screen and idles (for at least an hour, I let it sit while I was researching some stuff).

I presume I need to install the RAID Drivers into the boot sector of my LM partition on the RAID. Bios did not say "please insert boot media or check boot device and restart" so I know for a fact that it is picking up the RAID1 device.

10. I use the Live Cd and restart. Booting to the LM Live desktop. I go through steps 2 - 7 and install drivers to physical memory hard drive of the Live CD.

Now the RAID devices are seen. I open the device that I installed the OS and I see all the files in there. Not including the new ROCKETRAID driver install files.

So, I need to figure out how to access my RAID device in the live CD terminal, update the drivers, and add step 7 to grub/initrd.img oh my RAID1 device hard drive.

Easier said than done.

Any suggestions will be much appreciated, I have been at this for about 2 days now.

Thanks.
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
shurguywutt

Re: Straight Boot off Hardware RAID 1

Post by shurguywutt »

Did a little bit more reading.

So I was looking at the driver readme file...
RocketRAID 26xx SATA Controller Linux Open Source Driver
Copyright (C) 2006-2007 HighPoint Technologies, Inc. All rights reserved.

1. Overview
2. Build the driver as a kernel module
3. Using the driver as a kernel patch
4. Revision History
5. Technical support and service

#############################################################################
1. Overview
#############################################################################

This package contains Linux driver code for HighPoint RocketRAID 231x/230x
SATA controller. You can use it to build the driver module for custom
Linux kernels.

NO WARRANTY

THE DRIVER SOURCE CODE HIGHPOINT PROVIDED IS FREE OF CHARGE, AND THERE IS
NO WARRANTY FOR THE PROGRAM. THERE ARE NO RESTRICTIONS ON THE USE OF THIS
FREE SOURCE CODE. HIGHPOINT DOES NOT PROVIDE ANY TECHNICAL SUPPORT IF THE
CODE HAS BEEN CHANGED FROM ORIGINAL SOURCE CODE.

LIMITATION OF LIABILITY

IN NO EVENT WILL HIGHPOINT BE LIABLE FOR DIRECT, INDIRECT, SPECIAL,
INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF OR
INABILITY TO USE THIS PRODUCT OR DOCUMENTATION, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES. IN PARTICULAR, HIGHPOINT SHALL NOT HAVE
LIABILITY FOR ANY HARDWARE, SOFTWARE, OR DATA STORED USED WITH THE
PRODUCT, INCLUDING THE COSTS OF REPAIRING, REPLACING, OR RECOVERING
SUCH HARDWARE, OR DATA.


#############################################################################
2. Build the driver as a kernel module
#############################################################################

1) Install kernel build tools (gcc, binutils, make, etc.)

2) Setup the kernel source/headers

To build driver modules for a specific kernel, you shall use same
configuration for the kernel and the driver. Otherwise, the driver may
be unable to load, or behave abnormally.

- For Linux kernel 2.6 -

On most distributions based on kernel 2.6, an exploded source tree is not
required to build a driver against the currently in-use kernel. As long
as the system has kernel headers setup under /lib/modules/`uname -r`/build,
you can simply run "make" to build the driver.

If you want to build the driver against a custom kernel source, you must
setup the kernel source manually and run "make" under kernel source tree
to setup kernel headers.

- For Linux kernel 2.4 -

You need a full kernel source tree to build the driver. If you are building
a driver for the currently in-use kernel, the kernel source should match
the version of the running kernel. In addition, you must obtain the config
file for the running kernel:

For Red Hat or Fedora Linux, you can find the stock kernel config files
under {kernel-source-dir}/configs, named kernel-*.config. Select the one
matches your hardware and copy it to {kernel-source-dir}/.config.

For SuSE Linux, the config files for current kernel is under /boot dir
so you can the kernel source by

# cd /usr/src/linux-{kernel-version}.SuSE
# cp /boot/vmlinuz.config .config
# cp /boot/vmlinuz.version.h include/linux/version.h
# cp /boot/vmlinuz.autoconf.h include/linux/autoconf.h

For other distributions please refer to the distribution documents to
obtain the config file.

If you are building a custom kernel and a driver, you can setup the kernel
config by yourself, using "make config" or "make menuconfig" commands
under kernel source directory.

Once the kernel config file is ready, run following commands under kernel
source directory to setup kernel headers:

# make oldconfig
# make dep

On some Red Hat versions, {kernel-source-dir}/include/linux/modversions.h
may be incorrect after "make dep", you need check if there is a line
"#include <linux/rhconfig.h>" before "#include <linux/modsetver.h>" in that
file. If not, please add the line manually.

3) Build the driver

After you have configured the kernel source/headers you can build the driver
by following commands (assume you have extracted the driver source under
directory rr26xx-linux-src-1.xx):

# cd rr26xx-linux-src-1.xx/product/rr26xx/linux/
# make

You can append below options to "make" command:

KERNELDIR=...
Specify kernel source directory. If not specified the driver will
use /lib/modules/{kernel-version}/build/ as the default location.
This option is needed if you have a manually configured kernel
source tree.

CROSS_COMPILE=...
Specify cross compiler prefix.

ARCH=...
Specify target system machine architecture.
Currently only i386 and x86_64 is supported.

4) Install/upgrade the driver

If you are building driver for currently in-use kernel you can use
"make install" to install or upgrade the driver:

# cd rr26xx-linux-src-1.xx/product/rr26xx/linux/
# make install

The KERNELDIR=... parameter may be required, e.g.

# make install KERNELDIR=/usr/src/linux-2.4

"make install" command will copy the driver module to the directory
/lib/modules/`uname -r`/kernel/drivers/scsi, and update the initrd file
if it contains an old version driver.

If your system is installed on the controller, a reboot is required
to make the new driver take effect.

Please note "make install" may not work on some distributions. In that
case you have to install the driver manually.

After the driver is installed, it can be loaded manually by

# modprobe rr26xx

To load the driver automatically during system startup, you can either
put it into initrd file or configure a /etc/rc.d script to load it.



#############################################################################
3. Using the driver as a kernel patch
#############################################################################

You must have a full kernel source tree to use the driver as a patch.
To patch a kernel source tree, run the command

# cd rr26xx-linux-src-1.xx/product/rr26xx/linux/
# make patchkernel KERNELDIR=<kernel-source-dir>

For an unconfigured 2.6 kernel source tree, include/linux/version.h may
not exist so you should add "KERNEL_VER=2.6" to the command:

# make patchkernel KERNELDIR=<kernel-source-dir> KERNEL_VER=2.6

Then you can configure the driver into kernel during the kernel
configuration process (e.g. "make menuconfig"). It is listed under
scsi low level drivers.

Below is an example to make and install a kernel with the driver built-in:

# cd /usr/src/linux-2.6.11
# make menuconfig

Select "Device Drivers --->" and press enter.
Select "SCSI device support", then press 'Y' to make it built-in.
Select "SCSI disk support" then press 'Y' to make it build-in.
Select "SCSI low-level drivers --->" and press enter.
Select "HighPoint RocketRAID 26xx support" and press 'Y'.
Exit and save the kernel configuration.

# make
# make modules_install
# make install

Then you can reboot from the new kernel.


#############################################################################
4. Revision History
#############################################################################


#############################################################################
5. Technical support and service
#############################################################################

If you have questions about installing or using your HighPoint product,
check the user's guide or readme file first, and you will find answers to
most of your questions here. If you need further assistance, please
contact us. We offer the following support and information services:

1) The HighPoint Web Site provides information on software upgrades,
answers to common questions, and other topics. The Web Site is
available from Internet 24 hours a day, 7 days a week, at
http://www.highpoint-tech.com.

2) For technical support, send e-mail to support@highpoint-tech.com

NOTE: Before you send an e-mail, please visit our Web Site
(http://www.highpoint-tech.com) to check if there is a new or
updated device driver for your system.
Apparently I still need to create script or edit the initrd file. Does anyone know how to do this?
shurguywutt

**SOLVED** Straight Boot off Hardware RAID 1

Post by shurguywutt »

After many hours I have completed the task of installing on my Hardware RAID array. Here is what I did.

First I booted off livecd.

Installed RocketRaid 2640x4 linux source drivers from http://www.support-highpoint-tech.com/M ... 932.tar.gz

Extracted the files. Opened the file /rr2640-linux-src-v1.2/product/rr2640 in terminal.

#sudo make
#sudo make install

Found my RAID array and installed the /root on it. Installed the /boot on my thumbdrive. Finally I installed /home on my second RAID array.

Went back to find the image that was created after installation. boot/initrd.img-2.6.35-22-generic (I mounted it using archive mounter in order to check that the drivers were installed on the ramdisk image). They were. I deleted the initrd.img on my thumbdrive boot partition and I replaced it with the one I got after installing the drivers (with the new drivers installed).

Ran my BIOS, selected the usb as boot device. Ran grub. As soon as I selected the kernel on the grub screen I started to hear the ticking of my dual WD 10000RPM raptors!!

Hope this info saves someone else about 100 hours. :D
BigBenCG
Level 1
Level 1
Posts: 18
Joined: Mon Feb 01, 2010 4:52 pm

Re: **SOLVED** Straight Boot off Hardware RAID 1

Post by BigBenCG »

This is a really great post, I too am having an issue with a HighPoint RocketRaid controller which I am currently running Windows 7 on, I want to change my Linux OS to the RAID and run Windows on a single drives (for gaming). I for one appreciate you posting the steps you have taken to come to a resolution, not only is it useful having the final fix, but understanding how that fix was achieved and the mechanics involved is of great benefit.

Ben
Locked

Return to “Installation & Boot”