<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
The reason why it was irritating was because the SiS965 Athlon 64
chipset was not supported in the 4.1 kernel, which resulted in a
miserably slow install which eventually ground to a halt because the
load average got too high as the system was stacked behind with its
disk writes....<br>
<br>
That is irritating, the rebuild should be on first boot.....<br>
<br>
P.<br>
<br>
<br>
Les Mikesell wrote:<br>
<blockquote type="cite"
cite="mid1121978314.29448.6.camel@moola.futuresource.com">
<pre wrap="">On Thu, 2005-07-21 at 11:48, Dan Pritts wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Thu, Jul 21, 2005 at 03:55:25PM +0100, Peter Farrow wrote:
</pre>
<blockquote type="cite">
<pre wrap="">"Don't know whether I understand you correctly, but RAID1 array sync is
started with firstboot after the installation finished."
Err....no it doesn't.... it syncs the array as it installs, do a
cntrl-alt-f3 when installing to bring a shell up then do a "watch cat
/proc/mdstat"
</pre>
</blockquote>
<pre wrap="">I've observed this too. Really irritating.
</pre>
</blockquote>
<pre wrap=""><!---->
RAID1 has to sync as you create it - and if it doesn't complete and
shut down cleanly it will do it again on the first boot. With
hardware that is reasonable to run as RAID1 it shouldn't be
noticeable. Why is it irritating?
</pre>
</blockquote>
</body>
</html>