Bug#369861: confusing output when trying to run an incomplete array
martin f krafft
madduck at debian.org
Sat Sep 29 19:18:25 UTC 2007
> I fail to understand the problem. I admit that the second error
> message could be better - It is asking the kernel to start the
> array, and the kernel says 'no'. Look in kernel logs to
> understand why.
Well, yes. It would be nice if the second error
mdadm: failed to RUN_ARRAY /dev/md0: Input/output error
could just say what the real cause was, instead of expecting the
user to go to the kernel logs.
I'll leave this open for now and hope you might get around to it.
.''`. martin f. krafft <madduck at debian.org>
: :' : proud Debian developer, author, administrator, and user
`. `'` http://people.debian.org/~madduck - http://debiansystem.info
`- Debian - when you have better things to do than fixing systems
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature (see http://martin-krafft.net/gpg/)
Url : http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20070929/a72eec7a/attachment.pgp
More information about the pkg-mdadm-devel