On Friday, May 26, 2000, Thomas Gebhardt said:
> /proc/mdstat says that the new disk is resyncing but there is no
> progress at all. There is only 1% of the mirror in sync now and
> the estimated time of completion grows continuously. There is
> a load average of about 1.0 caused by this proces
g/lnxlists/linux-raid/
between May 8th & 10th this year.
Regards
Martin Munt
Draugen Project, SubSea Offshore Limited
Rockwater Building, Stoneywood Park, Dyce, Aberdeen, AB21 7DZ
Tel: +44 1224 795433 Fax: +44 1224 795582
mailto:[EMAIL PROTECTED]
> -Original Message-
> From:
l to mount something
else with, for example, "root=/dev/hdc1".
Of course, when I come to fdisk /dev/hdc linux complains that it's busy.
Martin Munt
[EMAIL PROTECTED] or [EMAIL PROTECTED]
> -Original Message-
> From: Harry Zink [SMTP:[EMAIL PROTECTED]]
> Sent: W
haviour that Chance describes below.
Does anyone have any ideas why lilo-0.21.15 messes up writing both
partitions when given "boot=/dev/mdN"??
I have not attempted to apply Richard Bollinger's 'lilo.raid1.also'
patch yet.
But I will now!
K, I confess to just spouting the words from <[EMAIL PROTECTED]>'s
Software-RAID HOWTO:
"NOTE: Be sure that your RAID is NOT RUNNING before changing the
partition types. Use raidstop /dev/md0 to stop the device."
As you say, it's awkward for a root array.
Regards,
Martin Munt
org/pub/linux/daemons/raid/alpha.
I used RAIDTOOLS-19990824-0_90_TAR.GZ and this works fine with the
2.2.14 kernel. Note that some facilities (eg failed-disk) are not available
in earlier raidtools-0.9 packages.
Michael Robinton has published an excellent howto
http://www.bzs.org/~michael/working/BootRootRaidLilominihowto.html in which
adding devices to running arrays is covered very clearly.
Regards,
Martin Munt
ut that would be admiting defeat.
BTW, kernel=2.2.14, patched with mingo's 2.2.14-B1 with
raidtools-19990824-0_90_tar.gz. The rest (including lilo) is vanilla Redhat
6.0
Thanks & Regards,
Martin Munt
[EMAIL PROTECTED] or [EMAIL PROTECTED]
