Thanks for reviewing this and providing feedback, Doug and Martin. I
didn't actually get the messages until just now as it seems the replys
in gmail tacks on to the message from the "sent" folder, silly me
looking in the inbox for a new message ;-)
Anyway, long story short Martin was right, it was
also sprach Nathan O <[EMAIL PROTECTED]> [2007.09.02.0807 +0200]:
> booted back into Debian, created a partition on the device and (after
> some mdadm hiccups) managed to re-add the old drive to the array.
Care to elaborate about those hiccups?
Anyway, from the information you provide, all I can
On Sun, Sep 02, 2007 at 04:07:30PM +1000, Nathan O wrote:
[snip trouble re raid5 and kernel panics]
> it spent too long resyncing and all is well. The degraded array is
> mounted and working fine. I erased and created an ext3 partition on
> the suspect drive and data is being copied to it as I typ
I have a home-use fileserver running Etch and distro-supplied kernels,
software etc. It contains 2 x 4 drive raid5 arrays using mdadm. What I
initially thought was a samba issue led to a few kernel panics and
some "kernel bug" log messages. At first I had the bug messages when
running 2.6.18-4 so I
4 matches
Mail list logo
