Installation on P6T6 WS Revolution SAS Drives
I've done some googling on this issue and haven't found much. I have 2 Seagate Cheetah 300GB SAS drives in RAID 0. They are split into 3 partitions which have Windows Vista 64, Microsoft Hyper-V Server 2008 R2, and hopefully Slackware 12.2. The RAID group is set up and functioning as I have loaded Vista and Microsoft Hyper-V Server 2008 R2. When I enter the fdisk section (after loading the default kernel) of the setup I can edit /dev/sda - sdf which, tells me that it can see the drives and partitions but it doesn't recognize that they are in RAID 0. On the disk that came with the mobo I have redhat drivers but I am not sure if they will help me or how to attempt to load them. Anyone have any ideas?
|
The most likely culprit is that you are not running the module to properly see your drives. What kernel are you loading when booting off the disc?? Make sure you are running the huge (although I can't remember the exact command to invoke it).
|
I have tried the default hugesmp.s and huge.s kernals. Today, I fired up cfdisk on /dev/sda and /dev/sdb. It did not recognize any partitions just a 300GB drive.
|
Try adding this to the boot parameters
Code:
raid-extra-boot = "/dev/sda, /dev/sdb" |
I'm still a n00b... I don't know how to add boot parameters
|
When it first boots and shows the screen after your bios (where most people hit enter), try typing that in and hit enter, then it will load all the slack stuff and hopefully your raid drives with it.
EDIT: Although it has been a while since I have booted the install disc (haven't had time to install 13.0 yet), so I don't remember exactly what the screen looks like or what it says. |
Quote:
I have the P6T Deluxe and did manage to get Slackware working with an Intel Matrix Storage Manager RAID 0 array. To do that I had to use a program called "dmraid" that can detect the RAID 0 metadata and then configure the Linux device mapper to access the array. I recommend that you take a look at some of my previous responses to people asking about fake hardware RAID. http://www.linuxquestions.org/questi...e-raid-727299/ http://www.linuxquestions.org/questi...k-12.0-586440/ http://www.linuxquestions.org/questi...e-12.2-728419/ I'm about to put Slackware 13 on my RAID array so I should have updated scripts in a few days. If you want to see what I did on Slackware 12.2 look here. http://personalpages.bellsouth.net/e/r/erikfl/raid/ The boot CD is for Slackware 12.2 and is compatible with the P6T. It has a copy of "dmraid" on it. After booting, log in as root with no password. Then you can use this command to detect the RAID arrays. dmraid -ay To look at the detected arrays do this. ls -l /dev/mapper Then you can mount RAID arrays using the names you find in "/dev/mapper". mount /dev/mapper/longnameofarray /mnt Replace "longnameofarray" with the actual name for the partition in "/dev/mapper". The number at the end of each name is a partition number. |
I do believe that mdadm now has support for the Intel ICHXR RAID *cough* controllers.
|
Quote:
If there's a way to use mdadm I'd rather do that than use "dmraid". |
This only pertains to version 3.x of mdadm.
I haven't tried it myself but according to the announcement you can use the metadata from BIOS level RAID http://www.kernel.org/pub/linux/util...mdadm/ANNOUNCE |
Thanks for the replies all. Erik, in response to your question I am on the Marvell controller. I'll dig through your posts a little later this afternoon and give a shot tomorrow night. Also, I'd be interested to hear how it goes with ver 13.0 as that is where I'll most likely be heading next ;)
|
Quote:
Please note that all of this is only necessary if you actually want to boot Slackware from a partition on the RAID array. If you just want to boot Slackware from a non-RAID disk and then access the RAID array then you don't need the rest of this. Here is the script that I used to make the "initrd". Code:
ROOTDEVNAME="/dev/sdr2" # Name of root device Code:
# Parse command line Code:
# Load a custom keyboard mapping: In order to create some more friendly device names I added a file, "/etc/udev/rules.d/10-local.rules" containing the following. Code:
KERNEL=="dm-0", NAME="sdr", OPTIONS+="last_rule" ls -l /dev/mapper The minor device ID corresponds to the number after "dm-". I used a name of "sdrX" where X is the partition number. sdr is actually a valid scsi disk device name but it's very unlikely to be used since it corresponds to the 28th SCSI disk. Depending on what device names you decide to use for your root and swap device you have to specify those in the grub boot loader "/boot/grub/menu.lst" file. Also, make sure that you create the device names in the "/dev" folder of your root device BEFORE "udev" runs or using some other boot CD. Example grub "/boot/grub/menu.lst" entry. Code:
title Linux Code:
/dev/sdr5 swap swap defaults 0 0 You can install Slackware directly to the RAID array, but it is a bit messy. Here are the steps required.
For Slackware setup to recognize "dmraid" created devices, edit the "setup" script used by Slackware. You will have to edit it each time you boot since it's stored in a file on the boot CD. You can copy the edited script to a floppy disk and save it for the next time if you want. cd /usr/lib/setup vi setup Do the editing and then use the script. setup The full path (including the name) of the script is "/usr/lib/setup/setup". The "setup" script file is in the "/usr/lib/setup" directory. What you have to edit is two lines. I showed the edited text in bold. Before. Code:
vgchange -ay 1> /dev/null 2> /dev/null Code:
vgchange -ay 1> /dev/null 2> /dev/null That will fix ONLY the list of TARGET partitions. You will have to set up the swap space in "/etc/fstab" after installing Slackware. Assuming that you have successfully install Slackware, you now have to make the RAID array able to boot. Mount the new Slackware system on the RAID array. mount /dev/mapper/pdc_ccfafbbhc1 /mnt Replace "pdc_ccfafbbhc1" with the correct device name for your Linux partition on the RAID array. Change to the root of the new system chroot /mnt Mount other needed devices mount -t proc none /proc mount -t sysfs none /sys Create the devices required for your root and swap devices using "mknod". mknod -m u=rw,g=rw,o= /dev/sdr2 b X Y chown root:disk /dev/sdr2 Replace "X" and "Y" with the correct major and minor device ID's displayed previously by "ls -l /dev/mapper". Replace "sdr2" with whatever device name you want to use to refer to the RAID partition. Build or select the kernel you want to use. Create your initrd using the script that I provided. Install the "grub" package from the "extra" folder on the Slackware CD. Edit the "/boot/grub/menu.lst" file. Installing "grub" to the RAID array can be a bit tricky and I've had better luck using a "grub" boot CD to do that. The commands are similar to this. grub root (hd0,1) setup (hd0,1) quit Replace "(hd0,1)" with the correct designation for your Linux system. "hd0" is the first hard disk and "1" is the second partition (partition 2). If you want to install to the MBR (which I don't recommend) you can use "setup (hd0)". From a grub boot CD, press the "C" key on the keyboard for command mode instead of typing in "grub". The commands following grub are the same. Another useful command that you may want to use first in grub is this one. find /boot/grub/menu.lst That will list the grub device names where the file is seen by grub. When you think that you have the system ready to boot, unmount everything and try it. umount /sys umount /proc exit umount /mnt Ctrl Alt Del to reboot. If you have a problem you will have to go through the steps again from the beginning except for running Slackware "setup". Use "chroot" again and fix any problems. I found it much easier to temporarily connect a non-RAID hard disk to test all this out and provide something that can boot if Slackware in the RAID array doesn't. Alternatively you can use a boot CD with grub and "dmraid". I wrote a script to create a CD. First I had to build the kernel with a "-CD" suffix. Code:
#!/bin/sh I'll be glad to provide a copy of the boot CD image and files that I have. I'm not sure if I compiled the Marvell driver into the kernel but I can check that. |
Sorry I haven't responded, work has been killing me, but WOW you are WAY beyond me! Very impressive! There is no way that I would have made even a little headway on this. In any event, I am downloading Slackware 13 as I type this an would greatly appreciate if I could get a copy of the boot CD image with the Marvell driver in the Kernel to see if I can get a tri-boot going. I haven't used Slack in a while and have been missing it. Thanks in advance!
|
Quote:
The boot CD will let you log in as "root" with no password after booting. Use the following command to detect RAID arrays. dmraid -ay Then look at detected device names. ls -l /dev/mapper Mount the devices or do whatever else you want. Usually that will be copying an existing Slackware system or installing "grub". To use Slackware Setup you need to follow my posted instructions or install to a "normal" hard disk first. It's a lot easier if you install to a normal hard disk and get RAID working first. Then use the boot CD to copy the files with "cp -a". mkdir /mnt/nonraid mkdir /mnt/raid mount /dev/hda1 /mnt/nonraid mount /dev/mapper/blah-blah /mnt/raid cp -a /mnt/nonraid/* /mnt/raid umount /mnt/raid umount /mnt/nonraid Replace that "blah-blah" with the very long file name for the partition where you want to install Linux in the RAID array. |
The files you want to download are "sasraid.zip" and "sasbootcd.zip". If those aren't the ones you downloaded then download those files. The other ones I had there didn't support SAS.
|
All times are GMT -5. The time now is 11:33 AM. |