On Wed, Aug 02, 2006 at 03:47:07PM +0100, martin f krafft wrote:
> Could you please run
>
> rm /dev/md?
> update-initramfs -t -u
>
> and confirm that this fixes it?
It does indeed.
> If it does, then this is an upstream problem I need to work around!
Or get upstream to fix it. ;-)
> Any
On Wed, Aug 02, 2006 at 02:57:22PM +0100, martin f krafft wrote:
> Can you please try (cut&paste into the shell should work):
>
> apt-get install -d mdadm=2.5.2-9
> dpkg --unpack /var/cache/apt/archives/mdadm_2.5.2-9_*.deb
> wget -O /tmp/mdadm.config http://madduck.net/~madduck/scratch/mdadm
also sprach Bas Wijnen <[EMAIL PROTECTED]> [2006.08.02.1523 +0100]:
> Here's the output. It seems something went wrong after all, even though
> there's no error message. This doesn't sound like it's good:
> I: mdadm: no RAID devices selected for initrd initialisation.
> I: mdadm: not including RA
Can you please try (cut&paste into the shell should work):
apt-get install -d mdadm=2.5.2-9
dpkg --unpack /var/cache/apt/archives/mdadm_2.5.2-9_*.deb
wget -O /tmp/mdadm.config http://madduck.net/~madduck/scratch/mdadm.config
echo -e '887ce8e8e8e5dd261216774847b6866fd3e2423f /tmp/mdadm.con
Does /dev/md_d0 exist on your system, and does
mdadm --detail /dev/md_d0 || echo ERROR
return something useful, or does it result in ERROR?
--
Please do not send copies of list mail to me; I read the list!
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' :proud Debian developer and
also sprach Bas Wijnen <[EMAIL PROTECTED]> [2006.08.02.1116 +0100]:
> Some testing shows that I did get further, it is now actually
> running the postinst (and failing that) instead of the
> preconfigure.
could you run
sed -i -e '1s,$,x,' /var/lib/dpkg/info/mdadm.postinst
and rerun dpkg-reconf
also sprach Bas Wijnen <[EMAIL PROTECTED]> [2006.08.02.1206 +0100]:
> On my system it shouldn't, but it seems fragile to need a name
> that you recognised when the script was written for things to work
> (assuming that that isn't really needed).
Yes, I am working on that right now.
--
Please do
also sprach Bas Wijnen <[EMAIL PROTECTED]> [2006.08.02.1051 +0100]:
> > The loop should stay endless, IMHO, to ensure that the user passes
> > a proper device string (or 'all' or 'none').
>
> The loop being endless if the user actually gets to answer the quesion is
> fine. But my debconf priority
On Wed, Aug 02, 2006 at 11:44:08AM +0100, martin f krafft wrote:
> also sprach Bas Wijnen <[EMAIL PROTECTED]> [2006.08.02.1051 +0100]:
> > > The loop should stay endless, IMHO, to ensure that the user passes
> > > a proper device string (or 'all' or 'none').
> >
> > The loop being endless if the u
On Wed, Aug 02, 2006 at 11:51:51AM +0200, Bas Wijnen wrote:
> On Tue, Aug 01, 2006 at 04:19:34PM +0100, martin f krafft wrote:
> > also sprach Bas Wijnen <[EMAIL PROTECTED]> [2006.08.01.1322 +0100]:
> > > This, plus the while true, which perhaps should be
> > > while [ $ERROR -eq 0 ], leads to the
On Tue, Aug 01, 2006 at 04:19:34PM +0100, martin f krafft wrote:
> also sprach Bas Wijnen <[EMAIL PROTECTED]> [2006.08.01.1322 +0100]:
> > This, plus the while true, which perhaps should be
> > while [ $ERROR -eq 0 ], leads to the endless loop.
>
> The loop should stay endless, IMHO, to ensure tha
tags 381007 + confirmed pending
thanks
also sprach Bas Wijnen <[EMAIL PROTECTED]> [2006.08.01.1322 +0100]:
> Anyway, the problem is that during preconfigure, the script hangs while
> continuously saying "E: unrecognised device string: /dev/md/0"
> Looking at the script, the problem is that this ma
Package: mdadm
Version: 2.5.2-7
Severity: grave
Justification: renders package unusable
Ok, not quite unusable, but unupgradable. Which I suppose may have
security concequences as well.
Anyway, the problem is that during preconfigure, the script hangs while
continuously saying "E: unrecognised d
13 matches
Mail list logo
