Re: Problems generating a raid0 device

Subject: Re: Problems generating a raid0 device
From: Ken Schweigert (ken@byte-productions.com)
Date: Mon Oct 22 2001 - 14:00:03 MDT

Alexander,

I don't think modprobe is having a problem with loading your raid modules, at
least not directly. It appears to be having problems loading your the modules
for your actual block devices.

From /usr/src/linux/Documentation/devices.txt :

block-major-8 == 8 block SCSI disk devices (0-15)
block-major-33 == 33 block Third IDE hard disk/CD-ROM interface
block-major-34 == 34 block Fourth IDE hard disk/CD-ROM interface
block-major-11 == 11 block SCSI CD-ROM devices

You may have to specify these in your /etc/modules.conf file. Maybe :
  alias sdc sr_mod # load scsi cd-rom

I've never done software-RAID, only hardware RAID and only on linux x86, but
hopefully this sparks something you might've forgotten.

Good luck, 

-- 
-Ken Schweigert, Aspiring Network Administrator
Byte Productions, LLC
http://www.byte-productions.com

On Mon, Oct 22, 2001 at 11:35:05AM +0200, Alexander Holst wrote:
> Hi everybody,
> 
> I am experiencing trouble in making a raid0 device with two of my drives.
> Running mkraid /dev/md0 gives the following output:
> 
> handling MD device /dev/md0
> analyzing super-block
> disk 0: /dev/hdc2, 2062335kB, raid superblock at 2062208kB
> disk 1: /dev/hda9, 2332550kB, raid superblock at 2332480kB
> mkraid: aborted, see the syslog and /proc/mdstat for potential clues
> 
> 
> /proc/mdstat looks like:
> 
> Personalities :
> read_ahead not set
> md0 : inactive
> md1 : inactive
> md2 : inactive
> md3 : inactive
> 
> 
> The last lines in /var/log/messages were:
> 
> Oct 22 00:56:15 eternie-d PAM_pwdb[1396]: (netatalk) session opened for
> user holale by (uid=0)
> Oct 22 00:56:15 eternie-d afpd[1396]: login holale (uid 500, gid 500)
> Oct 22 01:00:00 eternie-d CROND[1414]: (root) CMD (   /sbin/rmmod -as)
> Oct 22 01:01:00 eternie-d CROND[1417]: (root) CMD (run-parts /etc/cron.hourly)
> Oct 22 01:03:29 eternie-d modprobe: modprobe: Can't locate module block-major-8
> Oct 22 01:03:29 eternie-d modprobe: modprobe: Can't locate module
> block-major-33
> Oct 22 01:03:29 eternie-d modprobe: modprobe: Can't locate module
> block-major-33
> Oct 22 01:03:29 eternie-d modprobe: modprobe: Can't locate module
> block-major-34
> Oct 22 01:03:29 eternie-d modprobe: modprobe: Can't locate module
> block-major-34
> Oct 22 01:03:29 eternie-d modprobe: modprobe: Can't locate module
> block-major-11
> 
> 
> The /etc/raidtab file looks like:
> 
> # Sample raid-0 configuration
> raiddev			/dev/md0
> raid-level		0    # it's not obvious but this *must* be
> 			     # right after raiddev
> persistent-superblock   1    # set this to 1 if you want autostart,
>                              # BUT SETTING TO 1 WILL DESTROY PREVIOUS
>                              # CONTENTS if this is a RAID0 array created
>                              # by older raidtools (0.40-0.51) or mdtools!
> chunk-size		64
> nr-raid-disks		2
> nr-spare-disks		0
> device			/dev/hdc2
> raid-disk		0
> device			/dev/hda9
> raid-disk		1
> 
> 
> Anyone got some clues? What am I missing here? The installation is a YDL2.0
> Home/Office with the default kernel. According to /proc/mdstat, md support
> is enabled in the kernel - modprobe complains about missing modules, but
> all the neccessary raidX.o files are in my modules directory.
> 
> Any help appreciated.
> 
> 
> 
> 
> Alexander Holst
> SysAdmin MacLabor Visuelle Kommunikation
> Pforzheim University of Applied Sciences
> Germany
> ph.: +49 [0]7231 28-6837
> fx.: +49 [0]7231 28-6040
> <holst@fh-pforzheim.de>
>

This archive was generated by hypermail 2a24 : Mon Oct 22 2001 - 13:10:57 MDT