Hi,
It is now working! I don't know what changed since last failure (no
package upgrade as ftp-master.d.o is borken).
Summary:
- Upgrade from linux 2.6.32-9 to 2.6.32-10 (the libata transition big
bang release), then reboot
- Only 2 disks of the 4-disk array are assembled
Summary of all the chan
Hmm,
Forgot to send the following mail to BTS:
-- Forwarded message --
From: Mathieu Parent (Debian)
Date: Thu, Mar 25, 2010 at 2:01 PM
Subject: Re: Bug#574817: libata transition breaks mdadm arrays
To: martin f krafft
On Thu, Mar 25, 2010 at 11:49 AM, martin f krafft wrote
also sprach Mathieu Parent (Debian) [2010.03.25.1132
+0100]:
> Do I need to "update-initramfs"?
Yes, to install the mdadm.conf file.
--
.''`. martin f. krafft Related projects:
: :' : proud Debian developer http://debiansystem.info
`. `'` http://people.debian.org/~ma
Hi,
On Tue, Mar 23, 2010 at 10:26 AM, martin f krafft wrote:
...
>> I have upgraded to mdadm 3.1.1-1+incremental+4, without success.
>> The array is broken in the same state (only 2 components).
>
> You'll need to reassemble it, of course, but then the problem should
> not occur anymore. Hence r
found 574817 3.1.1-1+incremental+4
thanks
Hi,
I have upgraded to mdadm 3.1.1-1+incremental+4, without success. The
array is broken in the same state (only 2 components).
Mathieu Parent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trou
notfound 574817 3.1.1-1+incremental+4
thanks
> I have upgraded to mdadm 3.1.1-1+incremental+4, without success.
> The array is broken in the same state (only 2 components).
You'll need to reassemble it, of course, but then the problem should
not occur anymore. Hence removing the found tag.
--
It seems that what Ben Hutchings said is true: "mdadm is not waiting
long enough to find all the devices".
If I put "bash" in the mdadm-raid script to investigate, the array is
already built as in the broken state: The array is build within an
early process (initrd?). How to delay mdadm a bit?
R
Mathieu Parent
On Mon, Mar 22, 2010 at 2:56 PM, martin f krafft wrote:
> tags 574817 moreinfo
> thanks
>
> also sprach Mathieu Parent [2010.03.21.1250 +0100]:
>> Following an upgrade to the Big bang release (2.6.32-10), my mdadm
>> arrays stopped to work.
>
> I fail to see how this has anythin
tags 574817 moreinfo
thanks
also sprach Mathieu Parent [2010.03.21.1250 +0100]:
> Following an upgrade to the Big bang release (2.6.32-10), my mdadm
> arrays stopped to work.
I fail to see how this has anything to do with mdadm.
> I have to do the following at EACH boot to solve temporaly the p
On Sun, 2010-03-21 at 15:20 +0100, Mathieu Parent (Debian) wrote:
> On Sun, Mar 21, 2010 at 3:03 PM, Bastian Blank wrote:
> > On Sun, Mar 21, 2010 at 01:38:53PM +0100, Mathieu Parent (Debian) wrote:
> >> On Sun, Mar 21, 2010 at 1:35 PM, Bastian Blank wrote:
> >> > This is expected and not an erro
On Sun, Mar 21, 2010 at 3:03 PM, Bastian Blank wrote:
> On Sun, Mar 21, 2010 at 01:38:53PM +0100, Mathieu Parent (Debian) wrote:
>> On Sun, Mar 21, 2010 at 1:35 PM, Bastian Blank wrote:
>> > This is expected and not an error. Don't list device-names in
>> > /etc/mdadm.conf.
>> I am not using devi
On Sun, Mar 21, 2010 at 01:38:53PM +0100, Mathieu Parent (Debian) wrote:
> On Sun, Mar 21, 2010 at 1:35 PM, Bastian Blank wrote:
> > This is expected and not an error. Don't list device-names in
> > /etc/mdadm.conf.
> I am not using device names, see attached file.
Hmm, the file is /etc/mdadm/mda
On Sun, Mar 21, 2010 at 12:50:42PM +0100, Mathieu Parent wrote:
> Following an upgrade to the Big bang release (2.6.32-10), my mdadm arrays
> stopped to work.
>
> They were on /dev/sd{a,b,c,d} and went /dev/sd{b,c,d,e} as /dev/hda went
> /dev/sda.
This is expected and not an error. Don't list d
Hi,
On Sun, Mar 21, 2010 at 1:35 PM, Bastian Blank wrote:
> On Sun, Mar 21, 2010 at 12:50:42PM +0100, Mathieu Parent wrote:
>> Following an upgrade to the Big bang release (2.6.32-10), my mdadm arrays
>> stopped to work.
>>
>> They were on /dev/sd{a,b,c,d} and went /dev/sd{b,c,d,e} as /dev/hda
Package: linux-2.6
Version: 2.6.32-10
Severity: important
Subject: libata transition breaks mdadm arrays
Package: linux-2.6
Version: 2.6.32-10
Severity: normal
Following an upgrade to the Big bang release (2.6.32-10), my mdadm arrays
stopped to work.
They were on /dev/sd{a,b,c,d} and went /dev/
15 matches
Mail list logo
