well... I thought I was in the clear, but even though
I had a valid raidtab when I did mkinitrd, it still didn't
put the raidautorun line in my linuxrc... so I guess that's
a bug? I looked at the script and it looks like it should...
Don't know if anyone can confirm or not that this is working,
I've hacked the script so it forces it at the moment... guess
I'll open a bug unless someone else can confirm it does work...
Thanks
Bill
Bill Dossett wrote:
hmmm, ok, didn't realize initially that mkinitrd
was a script.. and it needs up-to-date raidtab in order to
work correctly with softare raid... guess that will fix it...
sorry for waste of bandwidth.
thanks
Bill
Bill Dossett wrote:
Hi,
Thanks for this... it has gotten me about 99% of the way
there, however. I have created an initrd and it has the raid
module in it, however, I am still missing one line
in my linuxrc and I don't know how to get mkinitrd to
put the line in as there doesn't seem to be any option for
it in mkinitrd...the
raidautorun /dev/md0
is not in my linuxrc... script
I've googled around and it seems to be saying mkinitrd
should put in in, if raid modules are loaded, but
I am loading raid modules and I'm not getting this...
could mkinitrd be broken? I don't see any option
in the man pages that seemns to tie in with this...
Thanks
Bill Dossett
Samuel Flory wrote:
Bill Dossett wrote:
Hi,
Does anyone from redhat ever hang out on these lists?
I REALLY, need to figure out how the hell they do bootable
software RAID as modules....
Is this some form of mystic secret that redhat don't want
us to know? Or doesn't anyone from Redhat read these lists?
I am trying to convert a system to bootable software raid
from a single disk system.
I really really really do not want to have to spend three
days configuring this server after a reload.
However.. all documents that I read about bootable software
raid assume you are building your own kernel... and I know
that redhat loads the raid modules .. most likely via initrd
I guess, but try as I might, I can't get this into a bootable
system.
[root@sflory sflory]# cd /boot/
[root@sflory boot]# zcat initrd-2.4.18-18.8.0.img >1
[root@sflory boot]# mount -o loop 1 m1
[root@sflory boot]# cat m1/linuxrc
#!/bin/nash
echo "Loading raid0 module"
insmod /lib/raid0.o
echo "Loading jbd module"
insmod /lib/jbd.o
echo "Loading ext3 module"
insmod /lib/ext3.o
echo Mounting /proc filesystem
mount -t proc /proc /proc
raidautorun /dev/md0
echo Creating block devices
mkdevices /dev
echo Creating root device
mkrootdev /dev/root
echo 0x0100 > /proc/sys/kernel/real-root-dev
echo Mounting root filesystem
mount -o defaults --ro -t ext3 /dev/root /sysroot
pivot_root /sysroot /sysroot/initrd
umount /initrd/proc
[root@sflory boot]#
If I build my own kernel, then I will continue to have
problems every time I run up2date and I'll have to constantly
build new kernels and while I don't mind building a kernel,
I used to do it all the time, I am trying to make things easier
to maintain around here.. not harder.
Why do you need to build a custom kernel. Red Hat always compiles
the raid driver as a module. If you install a kernel it should
create an initrd for you. (At least it has for me for years.) Also
if you just install a kernel instead of upgrading you should still
have your old config.
Can anyone point me in the right direction to any documents about
how to do this?
Look and the linux documentation project.
And secondly.... is there any further info on bootable sofware
raid and what I do if one of the disk fails? I pulled one of the
disks the other day while the system was powered down, and it wouldn't
boot at all while it was out... that certainly is _not_ the way
my hardware RAID systems work. I am using the GRUB boot loader
and I assumed that each disk was bootable, but no go here, I had
to put the disk back in before it would boot up again.. if they
are going to offer us software raid, then I think they should follow
thru and tell us how to use it.
On older releases of Redhat lilo/grub was installed on only the 1st
drive. You can manually install lilo on both disks fairly easily.
(I don't use grub.)
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
