Thanks a lot for your help.
I'm very satisfied with your explanation. And my problem this now is well
done.
I meant for this time I has successfully to run RAID5 with the raid devices
coming up at reboot.
Once again thanks a lot for your help.
Best Regards,
Y.N Rijanto
-----Original Message-----
From: David Neilson [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 01, 1999 11:04 PM
To: Topan
Subject: RE: md0 stopped at autorun
Here are the complete procedures I used to get raid1 working on RH 6.0. I
had the same problem you experienced with the raid devices coming up at
reboot.
Verify raid is installed, or else install the raid package using rpm
* To verify raid is installed: rpm -q -a | grep -i raid
* To install raid version 0.90-3: rpm -ivh raidtools-0.90-3.rpm
Set up the /etc/raidtab file to look like the lines below. (This assumes
you are trying to mirror /dev/hda6 and /dev/hdb5, with no spares):
raiddev /dev/md0
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
chunk-size 4
persistent-superblock 1
device /dev/hda6
raid-disk 0
device /dev/hdb5
raid-disk 1
Issue the command mkraid /dev/md0, and look in /proc/mdstat. This file
should indicate raid has started. If it hasn't, run raidstart /dev/md0.
After you have created a raid device, you can run either raidstart /dev/md0
or raidstop /dev/md0 to manually start and stop raid on the device /dev/md0.
Ensure autodetection is set up by verifying/implementing the following (this
assumes your boot image is in /boot):
* Add the following line to the /etc/conf.modules file:
alias md-personality-3 raid1
You may want to run the kernelcfg command and restart kerneld to see
if the raid type comes up. This will let you know the Kernel Configurator
sees the raid personality.
* Build a new initrd image:
mkinitrd -f --with=raid1 /boot/newinitrd-image 2.2.5-15
* Update the /etc/lilo.conf file to include the
initrd=/boot/newinitrd-image line.
Add the initrd line after the label line. For example, assuming your
boot image is named /boot/vmlinux-2.2.5-15, and the root device = /dev/hda1:
.
.
image=/boot/vmlinux-2.2.5-15
label=linux
initrd=/boot/newinitrd-image
root=/dev/hda1
read-only
image=/boot/vmlinux.old
label=old
root=/dev/hda1
read-only
* Run /sbin/lilo
* Verify that you have created RAID devices using the
persistent-superblock (the parameter persistent-superblock should equal "1"
in the /etc/raidtab file).
* Make sure raid is not running (raidstop /dev/md0). Using fdisk, set
the partition-types of the devices to mirror (e.g., /dev/hda6, /dev/hdb5) to
fd . Use the "t" option to accomplish this task.
* Verify no init-scripts (/etc/rc.d) have any raidstart/raidstop
commands. If they do, comment them out.
Update the /etc/fstab file to automatically mount /dev/md0, if necessary.
Reboot your system, and cat /proc/mdstat. It should indicate raid is
running.
> -----Original Message-----
> From: Topan [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, September 28, 1999 6:10 PM
> To: [EMAIL PROTECTED]
> Subject: md0 stopped at autorun
>
> I am having trouble getting the raid devices to come up at reboot.� I am
> running
> kernel 2.2.5-15 also i am using raidtools-0.90 to mkraid.
> I has recompile kernel with some modules�installed.
> Configuration on kernel :
> RAID4 / RAID5 (builtin)
> Autodetection RAID
> Linear (eppend) mode
> Boot Support (linear,striped) (NEW)
> �
> Below�is my�dmesg error:
>
> #####################
> autodetecting RAID arrays
> (read) sda2's sb offset: 3582400 [events: 00000004]
> (read) sdb2's sb offset: 3582400 [events: 00000004]
> (read) sdc5's sb offset: 3582336 [events: 00000004]
> autorun ...
> considering sdc5 ...
> � adding sdc5 ...
> � adding sdb2 ...
> � adding sda2 ...
> created md0
> bind<sda2,1>
> bind<sdb2,2>
> bind<sdc5,3>
> running: <sdc5><sdb2><sda2>
> now!
> sdc5's event counter: 00000004
> sdb2's event counter: 00000004
> sda2's event counter: 00000004
> md: md0: raid array is not clean -- starting background reconstruction
> kmod: failed to exec /sbin/modprobe -s -k md-personality-4, errno = 2
> do_md_run() returned -22
> unbind<sdc5,2>
> export_rdev(sdc5)
> unbind<sdb2,1>
> export_rdev(sdb2)
> unbind<sda2,0>
> export_rdev(sda2)
> md0 stopped.
> ... autorun DONE.
> ######################
> ��
> 1. Why md0 has stopped ?
> 2. How to solve this problem ?
> �
> �Regards
> �
