"David Wilk" writes:
> this was exactly my thought. I was hoping someone would have some
> 'official' knowledge, or opinion. I still can't get over having to
> wait several hours for my root partition to become available after an
> improper shutdown.
>
> On 3/18/06, Joachim Schipper <[EMAIL PROT
this was exactly my thought. I was hoping someone would have some
'official' knowledge, or opinion. I still can't get over having to
wait several hours for my root partition to become available after an
improper shutdown.
On 3/18/06, Joachim Schipper <[EMAIL PROTECTED]> wrote:
> On Sat, Mar 18,
Here it works just fine, done some power-offs by hand and the system
recovers without problems. The only problem I may think of is about
the timing of the fsck checks during the boot process. Perhaps I have
been lucky so far.
Then again, I might just be inexcusably blind to an obvious flaw that
wil
On Sat, Mar 18, 2006 at 12:59:30PM +0200, Antonios Anastasiadis wrote:
> I had the same question, and just changed the relevant line in /etc/rc
> adding '&' in the end:
>
> raidctl -P all &
Then again, why is this not the default? Are you certain this actually
works?
Joachim
I had the same question, and just changed the relevant line in /etc/rc
adding '&' in the end:
raidctl -P all &
On 3/17/06, John Eisenschmidt <[EMAIL PROTECTED]> wrote:
> - David Wilk ([EMAIL PROTECTED]) wrote: -
> > Howdy all,
> >
> > I've been testing a 3.8 system with RAIDframe and root on raid in a
> > RAID1 configuration. Performance and stability are quite good, but
> > there's one thing that
- David Wilk ([EMAIL PROTECTED]) wrote: -
> Howdy all,
>
> I've been testing a 3.8 system with RAIDframe and root on raid in a
> RAID1 configuration. Performance and stability are quite good, but
> there's one thing that's a bit irksome and I wonder if I might not be
> doing something rig
7 matches
Mail list logo
