Matteo Frigo writes:
> martin f krafft writes:
>> also sprach Matteo Frigo [2010.09.01.0139 +0200]:
>>> I have been hit by this bug. My analysis of the situation is
>>> the following.
>>
>> Nice analysis. I think that 3.1.4 now fixes this, as we reverted the
>> mapfile change.
>
> Yes, I have i
martin f krafft writes:
> also sprach Matteo Frigo [2010.09.01.0139 +0200]:
>> I have been hit by this bug. My analysis of the situation is
>> the following.
>
> Nice analysis. I think that 3.1.4 now fixes this, as we reverted the
> mapfile change.
Yes, I have installed 3.1.4 from sid and it f
also sprach Matteo Frigo [2010.09.01.0139 +0200]:
> I have been hit by this bug. My analysis of the situation is
> the following.
Nice analysis. I think that 3.1.4 now fixes this, as we reverted the
mapfile change.
--
.''`. martin f. krafft Related projects:
: :' : proud Debian deve
My system is debian lenny upgraded to testing with some parts from backports,
unstable
and experimental.
I've downgraded first to 3.1.1-1 to get a bootable system again.
Yesterday I upgraded to 3.4.1-1 from the unstable and the system is still
bootable.
So in my opinion the problem is gone with t
I have been hit by this bug. My analysis of the situation is
the following.
mdadm-3.1.2 introduced a change that stores a ``mapfile'' in
/lib/init/rw. The problem is that this directory does not exist in the
standard initramfs. Previous versions of mdadm were storing the file in
/dev/.mdadm (wh
Below is the complete log of the boot with the kvm commandline i use,
deleted by aprroximately 5K Lines, as noted inline between ### ###.
Should the full log be of interest I am happy to send, just let me know.
This is a vanilla install with the current alpha-installer,
installation was as stated i
> thanks for the analysis. I'm under the impression that mdadm does
> assemble the raids, but then fails to recognize the partition table.
> But I don't know whether this is still in the realm of mdadm's
> responsibility, or whether some other package (linux-image-*?) should
> be responsible instea
Hi,
On Mon, 30.08.2010 at 08:55:23 +0100, Dh H wrote:
> So this looks a bit like there are two erros:
> 1) mdadm is broken in 3.1.2 and brings up these errormessages.
> 2) Grub2 seems to be broken, as it does not start crypto,
> consecutively failing to bring up LVM
thanks for the analysis. I
On Sun, Aug 29, 2010 at 9:38 AM, Toni Mueller wrote:
>
> Hi,
>
> On Sun, 29.08.2010 at 07:18:36 +0200, Dh H wrote:
>> Downgrading MDADM helped for me, but not completely.
>> The behaviour at the beginning is still the same, such that it does
>> not find the volume-group.
>> But now I am dropped i
Downgrading MDADM helped for me, but not completely.
The behaviour at the beginning is still the same, such that it does
not find the volume-group.
But now I am dropped into a shell instead of getting these
/sys/devices/virtual/block/mdX
messages.
In that shell I can use lvm to bring the vg up and
Hi,
On Sun, 29.08.2010 at 02:35:09 +0200, Agustin Martin
wrote:
> May this be related to #583917, mdadm: long delay (6-200 minutes)
> during boot (root device detection) after upgrade on RAID/LVM/LUKS
> setup?
after reading this bug report, I'm not convinced. Contrary to my last
statement, my
2010/8/26 Toni Mueller :
> Package: grub-pc
> Version: 1.98+20100804-2
> Severity: important
>
>
> Hi,
>
> my machine is a standard PC with two SATA disks, bundled as md0 and md1,
> with /boot on md0, and everything else in a LUKS encrypted container on
> md1 with LVM inside. So, booting normally w
also sprach Javier Kohen [2010.07.04.2154 +0200]:
> Where can I find an official package of mdadm 3.1.1 in order to
> downgrade? Sorry for posting with another question, but I'm sure this
> information will be useful to those affected by this bug until there
> is a fix. I've looked around and coul
Where can I find an official package of mdadm 3.1.1 in order to
downgrade? Sorry for posting with another question, but I'm sure this
information will be useful to those affected by this bug until there
is a fix. I've looked around and couldn't find the package anywhere.
The snapshot.debian.net arc
Hi,
I have this problem too. One thing I notice is just before the list
of mdadm messages I get this:
udevadm settle timeout 30s reached event queue contains
/sys/devices/virtual/block (some incremented number ...)
Dick
--
Dick Middleton
--
To UNSUBSCRIBE, email to debi
Roland Mas, 2010-06-02 15:24:11 +0200 :
[...]
> I also see the series of udevd-work warnings. Interestingly (maybe),
> the time between two of them seems to grow geometrically.
I forgot to mention something that, again, might or might not be
relevant: the message about the cryptsetup being co
Hi,
I had the very same problem, and downgrading mdadm to 3.1.1-1 did fix it
for me too. In case additional information about my setup might be
useful in the general case, here's the symptoms I had.
Setup: two disks sda and sdb. Partitions sda1 and sdb1 are aggregated
in a RAID1 device /dev
retitle 583917 mdadm: long delay (6-200 minutes) during boot (root device
detection) after upgrade on RAID/LVM/LUKS setup
version 583917 3.1.2-1
thanks
control seems to have ignored above parts,
On Wed, Jun 02, 2010 at 01:49:50AM +0200, Paul Menzel wrote:
> Downgrading mdadm to 3.1.1-1 fixed thi
retitle 583917 mdadm: long delay (6–200 minutes) during boot (root device
detection) after upgrade on RAID/LVM/LUKS setup
reassign 583917 mdadm
version 583917 3.1.2-2
notfound 583917 3.1.1-1
quit
[ I took pkg-lvm-maintain...@lists.alioth.debian.org and Michael off the
receiver list. ]
Am Diensta
On Tue, Jun 01, 2010 at 04:50:56PM +0200, Agustin Martin wrote:
> On Tue, Jun 01, 2010 at 01:32:29PM +0200, martin f krafft wrote:
> > also sprach Paul Menzel [2010.06.01.1127 +0200]:
> > > Dear Debian mdadm maintainers and Debian LVM Team,
> > >
> > > could you please comment on the first issue
On Tue, Jun 01, 2010 at 01:32:29PM +0200, martin f krafft wrote:
> also sprach Paul Menzel [2010.06.01.1127 +0200]:
> > Dear Debian mdadm maintainers and Debian LVM Team,
> >
> > could you please comment on the first issue if it is related to your
> > packages.
>
> I don't see a way in which mda
also sprach Paul Menzel [2010.06.01.1127 +0200]:
> Dear Debian mdadm maintainers and Debian LVM Team,
>
> could you please comment on the first issue if it is related to your
> packages.
I don't see a way in which mdadm could be responsible for this. Have
you tried downgrading it to see if the e
Dear Debian mdadm maintainers and Debian LVM Team,
could you please comment on the first issue if it is related to your
packages.
Am Dienstag, den 01.06.2010, 00:59 +0200 schrieb Paul Menzel:
> Am Montag, den 31.05.2010, 22:29 +0200 schrieb Michael Prokop:
> > * Paul Menzel [Mon May 31, 2010 at
Am Montag, den 31.05.2010, 22:29 +0200 schrieb Michael Prokop:
> * Paul Menzel [Mon May 31, 2010 at 06:41:45PM
> +0200]:
>
> > yesterday I upgrade my Debian Sid/unstable system after over a
> > week. Several core packages were upgraded by doing this as lvm2,
> > mdadm, initscripts, initramfs-too
* Paul Menzel [Mon May 31, 2010 at 06:41:45PM +0200]:
> yesterday I upgrade my Debian Sid/unstable system after over a
> week. Several core packages were upgraded by doing this as lvm2,
> mdadm, initscripts, initramfs-tools. I have a standard md RAID1
> setup with LVM over it. Furthermore there i
Subject: initramfs-tools: long delay during boot after upgrade
Package: initramfs-tools
Version: 0.95.1
Severity: normal
Tags: sid
*** Please type your report below this line ***
Dear Debian folks,
yesterday I upgrade my Debian Sid/unstable system after over a week. Several
core packages were
26 matches
Mail list logo
