Firewire RAID bootparameters?
----- Original Message -----
From: "Rechenberg, Andrew" <[email protected]>
Date: Fri, 12 Dec 2003 14:19:52 -0500
To: Christer Bäckström <[email protected]>
Subject: Re: Firewire RAID bootparameters?
Quoted 25 lines
I'm not sure which distro you're running, but we needed a module to load before another one and I modified the linuxrc script in our initrd image to change the load order.
Red Hat (and probably other distros) initrd images have a script in the initrd image to load drivers. You can loop mount the current image, add the modules you need, modify the script, and then copy it back into /boot.
The initrd image in Red Hat is gzipped so this is the procedure that I follow:
. *** MAKE A BACKUP COPY OF YOUR CURRENT INITRD AND BOOTLOADER CONF *** . cp
/boot/initrd.img/tmp
. cd /tmp
. mv initrd.img initrd.img.gz
. gunzip initrd.img
. mount -o loop initrd.img/mnt/cdrom
. Copy any necessary modules to/mnt/cdrom/lib
. Edit/mnt/cdrom/linuxrcand add a couple of lines to load your firewire module in the proper order.
. umount/mnt/cdrom
. gzip/tmp/initrd.img
. cp/tmp/initrd.img.gz/boot/mynewinitrd.img
Quoted 6 lines
Then what I would do is make a new bootloader (LILO/GRUB) entry with all the same options except use your edited initrd image instead of the stock one. That way you can test it, but still be able to boot with you known-good initrd image.
This is probably a big hack, but it worked for me :)
Yes, this is new information for me. I never considered (or knew how to) manipulate the initrd loading. I got two more mails saying about the same thing, but they weren't cc:ed to the list. (Thanks Joe Pruett and David Haring) This would enable me to put even my root-filesystem on the firewire drive. Very nice. In my case, as I only keep my /home on the raid1 mirror, it was even simpler. I looked into the initrd man page, and found a reference to append "noinitrd" to lilo.conf, which stops loading of modules by initrd altogether. The rc.sysinit will then, in my case (Mandrake-9.2), load the modules in the right order. I stiil wonder if the loading sequence should not be different when loading compiled-in modules. Nowadays firewire and usb2 drives are fast and commonplace, and an excellent way of securing the regular harddrive. Especially on a laptop, where the regular drives are small a
nd singular. To load the raid subsystem before these systems can't be right. I wonder if i
t should not be changed? Anyways: Me happy. Thanks all for the help!
/Chris
Quoted 32 lines
Hope this helps,
Andy.Quoted 19 lines · Christer Bäckström
Hi,
I've recently bought a 160Gb firewire drive and RAID1:ed it to mirror my main harddrive. Unfortunately, the md subsystem seems to load before the firewire in the kernel bootsequence, which mean I have to do some weird stuff to make it work. Basically, I compiled the md system as modules (with the SCSI patch to make it work a bit better), and hid the modules in a different directory, so they wouldn't load. I later load them in manually rc.sysinit. This work, but is a little clumsy. Is there a way to use append any boot-parameters to lilo to make the RAID subsystem load the firewire system? Or is there another solution? Thanks,
/Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.htmlSignature · 3 lines
Regards, Andrew Rechenberg Infrastructure Team, Sherman Financial Group
Signature · 3 lines
___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm
Quoted 8 lines · Christer Backstrom
Yes, this is new information for me. I never considered (or knew how to) manipulate the initrd loading. I got two more mails saying about the same thing, but they weren't cc:ed to the list. (Thanks Joe Pruett and David Haring) This would enable me to put even my root-filesystem on the firewire drive. Very nice. In my case, as I only keep my /home on the raid1 mirror, it was even simpler. I looked into the initrd man page, and found a reference to append "noinitrd" to lilo.conf, which stops loading of modules by initrd altogether. The rc.sysinit will
Quoted 8 lines
then, in my case (Mandrake-9.2), load the modules in the right order. I stiil wonder if the loading sequence should not be different when loading compiled-in modules. Nowadays firewire and usb2 drives are fast and commonplace, and an excellent way of securing the regular harddrive. Especially on a laptop, where the regular drives are small and singular. To load the raid subsystem before these systems can't be right. I wonder if i t should not be changed? Anyways: Me happy. Thanks all for the help!
uhm, you should not need to modify the initrd scripts by hand to make it do what you need, (and mdk-9.2 initrd should not load raid modules if it does not need it to boot, but this i already fixed).
having a correct scsi_hostadapter line in /etc/modules_conf should deal with loading the firewire module before, or you could use --preload <module> argument.
i don't have firewire hw to test this, and i'll never buy an usb drive if i can avoid it :-)
would you be willing to test the alternative mkinitrd/initscripts/mdadm packages i built for mandrake cooker and report success/failure on your configuration?
they are found at: http://www.comedia.it/~bluca/cooker/lvm2/
Regards,
L.
Signature · 6 lines
Luca Berra -- [email protected] Communication Media & Services S.r.l. /"\ \ / ASCII RIBBON CAMPAIGN X AGAINST HTML MAIL / \