New to RAID/Linux - PE2650, Redhat 7.3

Brian K. Jones jonesy at CS.Princeton.EDU
Mon Aug 5 08:39:01 CDT 2002

OK, I think I can figure this stuff out.  I'll likely build it into the
kernel as well, since there's no practical reason I can think of to make
aacraid a module (or the aic7xxx driver).  

My question *now* is: How do I control the RAID level?  How do I know
how the driver is treating the disks?  How do I know if it's being
mirrored? etc. etc.

Thanks again

On Mon, 2002-08-05 at 09:22, Seth Mos wrote:
> At 09:09 5-8-2002 -0400, Brian K. Jones wrote:
> >Thanks for the reply.  Sorry for the miscommunication - RAID 1
> >(mirroring) is what I want to do.  The question now is once I have my
> >root disk set up the way I want it, what's the device I'm aliasing in
> >modules.conf?  I don't remember ever putting a module into that file
> >just by itself on a line, but that appears to be what you're
> >suggesting.
> This from one of my PE2450 servers (perc2/dc controller)
> [seth at lsintra seth]$ cat /etc/modules.conf
> alias scsi_hostadapter aic7xxx
> alias scsi_hostadapter1 megaraid
> alias eth0 eepro100
> alias parport_lowlevel parport_pc
> So in your case it should look like this.
> alias scsi_hostadapter aacraid
> Then rebuild your initrd image.
> mkinitrd (see help)
> I always compile the scsi adapters that I need to access the root 
> filesystem into the kernel so I don't need to make initial ramdisk images.
> It also makes sure I can reach the root fs when something goes wrong.
> Cheers
> --
> Seth
> It might just be your lucky day, if you only knew.
> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge at
> Please read the FAQ at or search the list archives at

Brian K. Jones
System Administrator
Dept. of Computer Science, Princeton University
jonesy at
Voice: (609) 258-6080

More information about the Linux-PowerEdge mailing list