From: "Rechenberg, Andrew" <ARechenberg@shermanfinancialgroup.com>
To: "Christer Bäckström" <cbackstrom@chemist.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Firewire RAID bootparameters?
Date: Fri, 12 Dec 2003 14:19:52 -0500 [thread overview]
Message-ID: <1071256791.13023.3009.camel@localhost.localdomain> (raw)
In-Reply-To: <3FD9B878.3070002@chemist.com>
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/linuxrc and 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
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 :)
Hope this helps,
Andy.
On Fri, 2003-12-12 at 07:45, Christer Bäckström wrote:
> 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 majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Regards,
Andrew Rechenberg
Infrastructure Team, Sherman Financial Group
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2003-12-12 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-12 12:45 Firewire RAID bootparameters? Christer Bäckström
2003-12-12 19:19 ` Rechenberg, Andrew [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-13 11:19 Christer Backstrom
2003-12-13 12:14 ` Luca Berra
2003-12-13 13:26 AndyLiebman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1071256791.13023.3009.camel@localhost.localdomain \
--to=arechenberg@shermanfinancialgroup.com \
--cc=cbackstrom@chemist.com \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox