hi philippe
if you are getting li- or lil- problems...
-- easiest fix is to boot linux with some other media
( floppy or other working linux box... move your target
( hd to that other box....
-- once you have linux booted on that box... than re-run lilo
and see if that fixed your booting of the target
( your raid box in this case )
-- fixing lilo is not too easy...but not too hard either...
- just have to tweek things...
===
=== first thing to do.... i claim there is no valid reason to
=== have /boot partition in your case .... combine it into one
=== / as you already have the rest of your system
===
re-install suse-7.1 or suse-7.2 without using a separate /boot partition
than see if it boots
if not... do the same test with rh-7.1
=== all this testing is faster than trying to fix the lilo problem
=== you are having...
if you have properly installed raid1 mirroring... if hda crashes...
yo can still boot from hdc
c ya
alvin
and fixing LI- or LIL- problems remotely is too hard...
On Thu, 10 May 2001, Philippe Trolliet wrote:
> hi alvin,
> my config looks like this:
> df -h shows:
> Filesystem Size Used Avail Use% Mounted on
> /dev/md0 28G 3.5G 23G 14% /
> /dev/md1 99M 5.3M 88M 6% /boot
...
> thanks
> regards
> phil
>
> PS: when the system is running and one disk fails, does the system crash or
> not?
>
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
