Re: ..chroot-installs onto RAID-1 disks ,was: Evolving Debian from Red Hat
On Sun, 14 Sep 2003 03:40:40 +0100,
"Karsten M. Self" <kmself@ix.netcom.com> wrote in message
<[🔎] 20030914024040.GA18694@guildenstern.dyndns.org>:
> on Sat, Sep 13, 2003 at 06:36:34AM +0200, Arnt Karlsen (arnt@c2i.net)
> wrote:> On Fri, 12 Sep 2003 21:31:38 -0400,
> > Greg Folkert <greg@gregfolkert.net> wrote in message
> > <[🔎] 1063416698.27592.5.camel@duke.gregfolkert.net>:
> > >
> > > On Fri, 2003-09-12 at 18:31, Arnt Karlsen wrote:
> > > > Hi,
> > > >
> > > > ..has anyone tried use these methods to intall to boxes with
> > > > RAID-1 etc disks?:
> >
> > ..note to self; heed ESR's advice on asking smart; I ofcourse meant
> > software RAID but never said so.
>
> I assume that's yourself, and not yours truly ;-)
..my what? ;-)
> As I frequently say, the advantage of a chroot install is that it
> allows you to tackle one problem rather than two. So while I haven't
> tackled your specific problem, I think you'll find it's not a
> show-stopper.
..well, in my case, comparing it to the 15 minute RH installs,
this is too damn close, I am missing some basic clue whack.
..I want the boot loader in the MBR's of /dev/hd[a|c], so in
/etc/lilo.conf and in /boot/grub/grub.conf, I put _what_ in
the "boot=/dev/$whatever"??? I use "root=/dev/md0", and this
works _beautifully_ with RH-7.3 on the very same damn box.
> That is: with a standard installation, you're conerned with booting
> and getting full support of the hardware you're installing onto, _and_
> loading a new distribution onto it.
>
> With a chroot install, you've already solved the hardware problem,
> whether by installing under an iexisting system, or by using a
> gneeral-purpose boot disk specializing in supporting a wide range of
> systems.
>
> The key with a chroot install is to identify your support requirements
> and ensure that you have them covered. In your case, that would mean
> installing a kernel with compiled-in SW RAID support, or ensuring your
> initrd loads the appropriate modules for this.
..done: gw:~# uname -a ; lsmod | grep -v ipt
Linux gw 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686 unknown
Module Size Used by Not tainted
i2c-proc 6272 0 (unused)
i2c-algo-pcf 4800 0 (unused)
i2c-algo-bit 6924 0 (unused)
i2c-core 12160 0 [i2c-proc i2c-algo-pcf i2c-algo-bit]
raid0 3104 0 (unused)
raid1 11876 0 (unused)
md 43488 7 [raid0 raid1]
keybdev 1664 0 (unused)
usbkbd 2848 0 (unused)
input 3072 0 [keybdev usbkbd]
usb-uhci 20708 0 (unused)
usbcore 48032 0 [usbkbd usb-uhci]
..and, yeah, I know I need to add these as "--failed-disk"'s.:
gw:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/hda9 486M 32M 429M 7% /
/dev/hda1 45M 5.9M 37M 14% /boot
/dev/hda3 30G 70M 28G 1% /var
/dev/hda6 1.4G 33M 1.3G 3% /home
/dev/hda5 478M 8.1M 445M 2% /tmp
/dev/hda8 1.9G 200M 1.5G 11% /usr
gw:~#
--
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.
Reply to: