Hi,
I know the feeling. I have a 40GB raid-1 array and that takes a good 20 mins to re-write parity. During this time I cannot use my computer. Ideally the system should come up, and re-write in the background. I'm sure there is a very important reason as to why it is done in this order. Edd On 7/7/2005, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: >Hi. > > Since "raidctl -P all" in /etc/rc parity is verified/reconstructed >_before_ system runs. This lead to bad effect for me, while I have >"root on RAID", as described in http://www.nomoa.com/bsd/raid_ide.htm >- when machine has lost power, before mounting there are parity >checks. This is so long with my more that 150G on RAID. > > I want ask, what will occur if not do "raidctl -P all" in /etc/rc, >but set it in /etc/rc.local, after daemons started? > What can fsck with such "uncleaned/unreconstructed" RAID? > >-- >engineer > >-- >This email has been verified as Virus free >Virus Protection and more available at http://www.plus.net
