Hello,
Am Dienstag, den 04. August schrieb Frédéric Brière:
> On Mon, Jul 27, 2009 at 08:17:20AM -0400, Jeff King wrote:
> > So my problem has been resolved, but I am not sure whether there is a
> > bug that will affect other users (hence this bug report). Why is it that
>
> You're not alone; I h
On Tue, Aug 04, 2009 at 07:45:27PM -0400, Frédéric Brière wrote:
> Notice how they switched to the same suffix, which was already present
> in /dev/md2. (/dev/md2 is a one-drive RAID1 array, so it's always been
> a bit funky.) Also notice how md0 and md1 used to share the same
Come to think of i
On Mon, Jul 27, 2009 at 08:17:20AM -0400, Jeff King wrote:
> So my problem has been resolved, but I am not sure whether there is a
> bug that will affect other users (hence this bug report). Why is it that
You're not alone; I had the same experience this afternoon. (This was
my first reboot since
Package: mdadm
Version: 3.0-2
Severity: normal
Since upgrading to mdadm 3, my system fails to assemble the root raid1
array. The raid1 module is loaded properly, but running "mdadm
--assemble --scan --run" fails. It produces no error message, but exits
with status code '2' (which I determined by d
4 matches
Mail list logo
