Theo Van Dinter writes:
> On Wed, 27 Oct 1999, Bruno Prior wrote:
>
> BP> (a) Getting the latest patched lilo from RedHat or applying the lilo.raid1 patch
> BP> and rebuilding it yourself (if /dev/md0 is RAID-1)
> BP> (b) Providing lilo with the geometry of one of the devices in the array (a
On Wed, Nov 03, 1999 at 09:28:54AM +0100, Martin Schulze wrote:
> > syslogd 378 root5w REG9,18548 192396
> > /var/log/boot.log
> > klogd 389 root2r REG8,1 191102 12
> > /boot/System.map-2.2.12-20
> >
> > Is it safe to kill these?
>
> Better add
Marcos Lopez wrote:
> I am attempting to get my system to run RAID 1 for /, /usr, /var, /home
>
> I have moved over all except for / and it works fine.
>
> After reading the howto "Root file system on RAID. by - Jakob
> OEstergaard" I have decided to take the first approach, unfortunately I
>
On Sun, Oct 31, 1999 at 11:50:26PM -0200, Christian Robottom Reis wrote:
> On Wed, 27 Oct 1999, Jakob Østergaard wrote:
>
> > Because LILO doesn't understand RAID, and thus cannot (yet) load the kernel
> > of it.
>
> Doesn't the lilo.raid1 patch included in RH6.1 permit booting off a raid1
> arr
On Wed, 27 Oct 1999, Admin Mailing Lists wrote:
> The thing I TOTALLY don't get is if the first drive dies, how can
> you boot the 2nd drive (mirror) when you're still losing the small
> bootable partition (as it's still part of drive 1). Of course you can put
> this bootable partition on a seper
> The thing I TOTALLY don't get is if the first drive dies, how can
> you boot the 2nd drive (mirror) when you're still losing the small
> bootable partition (as it's still part of drive 1).
You can mirror that partition manually by using 2 dd commands - see one of my
earlier messages here (if ne
> > Wouldn't it be easier to stick the kernel, lilo config, relevant boot info
> > on a floppy and boot raid1 systems from that?
> > perhaps i'm missing something..more likely that not :-)
>
> Because LILO doesn't understand RAID, and thus cannot (yet) load the kernel
> of it.
Actually, I think T
On Wed, 27 Oct 1999, [iso-8859-1] Jakob Østergaard wrote:
>
> True. That's why you put identical /boot partitions on all the drives
> in your array if you want to be really safe.
>
i c
> > Wouldn't it be easier to stick the kernel, lilo config, relevant boot info
> > on a floppy and boot ra
On Wed, Oct 27, 1999 at 11:19:38AM -0400, Admin Mailing Lists wrote:
>
...
> The thing I TOTALLY don't get is if the first drive dies, how can
> you boot the 2nd drive (mirror) when you're still losing the small
> bootable partition (as it's still part of drive 1). Of course you can put
> this bo
ke My home page
FAX 407-676-2355
- Original Message -
From: Jakob Østergaard <[EMAIL PROTECTED]>
To: Linux-Raid <[EMAIL PROTECTED]>
Sent: Wednesday, October 27, 1999 12:31 PM
Subject: Re: Root RAID and unmounting /boot
On Wed, Oct 27, 1999 at 11:19:38AM -0400, Admin Mailing
; the system map, boot.b and associated files. In other words, the files that live
> in /boot by default. So the simplest strategy is to stick with the default
> filesystem structure, and have /boot on its own tiny partition. Then you can use
> a bog standard /etc/lilo.conf, and run lilo straight witho
>In the context of booting from RAID, the disk geometry is only needed if the
>boot-loader is trying to read from or write to a file on a RAID-1 array that
>contains that partition. But in that case, the disk= and partition= lines
>would
>point to RAID arrays, not normal disks and partitions (se
On Wed, 27 Oct 1999, Bruno Prior wrote:
BP> (a) Getting the latest patched lilo from RedHat or applying the lilo.raid1 patch
BP> and rebuilding it yourself (if /dev/md0 is RAID-1)
BP> (b) Providing lilo with the geometry of one of the devices in the array (again
BP> if /dev/md0 is RAID-1)
BP> (c)
ystem structure, and have /boot on its own tiny partition. Then you can use
a bog standard /etc/lilo.conf, and run lilo straight without the need to pass it
parameters.
Cheers,
Bruno Prior [EMAIL PROTECTED]
> -----Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PR
Marcos,
> My boot partition is on sda1 and that is on that partition.
What do you mean by this? What is on that partition? Is /dev/sda1 mounted on
/boot with all the normal /boot files on it? If so, your setup sounds fine.
Assuming the setup is OK, you have 2 alternatives. Kill klogd, as you su
ice number is
particularly crucial. Could you try it again and check? Be careful that the only
change you make it is to remove the geometry lines. And if you get an error, see
if it is _exactly_ as stated above. Because as it stands, your solution doesn't
make sense, as you yourself recognize.
C
On Tue, Oct 26, 1999 at 09:07:34AM -0600, Marcos Lopez wrote:
> Egon Eckert wrote:
> >
> > > syslogd 378 root5w REG9,18548 192396
> > > /var/log/boot.log
> > > klogd 389 root2r REG8,1 191102 12
> > > /boot/System.map-2.2.12-20
> > >
> > > Is it s
> to /mnt/newroot/boot. Then after running "lilo -r /mnt/newroot" I get
> the following error:
> "Sorry, don't know how to handle device 0x0900"
>
> What does the above mean and how to i fix it?
It does mean that lilo doesn't know anything about md device. Change the
line containing "root=" i
At 09:07 26/10/99 -0600, Marcos Lopez wrote:
>Egon Eckert wrote:
> >
> > > syslogd 378 root5w REG9,18548 192396
> > > /var/log/boot.log
> > > klogd 389 root2r REG8,1 191102 12
> > > /boot/System.map-2.2.12-20
> > >
> > > Is it safe to kill these?
Egon Eckert wrote:
>
> > syslogd 378 root5w REG9,18548 192396
> > /var/log/boot.log
> > klogd 389 root2r REG8,1 191102 12
> > /boot/System.map-2.2.12-20
> >
> > Is it safe to kill these?
>
> These are loggers, so I guess nothing terrible would h
> syslogd 378 root5w REG9,18548 192396
> /var/log/boot.log
> klogd 389 root2r REG8,1 191102 12
> /boot/System.map-2.2.12-20
>
> Is it safe to kill these?
These are loggers, so I guess nothing terrible would happen. But I
wouldn't kill them anyw
21 matches
Mail list logo
