Bug#574817: libata transition breaks mdadm arrays

2010-04-01 Thread Mathieu Parent (Debian)
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

Bug#574817: Fwd: Bug#574817: libata transition breaks mdadm arrays

2010-03-27 Thread Mathieu Parent (Debian)
Hmm, Forgot to send the following mail to BTS: -- Forwarded message -- From: Mathieu Parent (Debian) sath...@debian.org Date: Thu, Mar 25, 2010 at 2:01 PM Subject: Re: Bug#574817: libata transition breaks mdadm arrays To: martin f krafft madd...@debian.org On Thu, Mar 25, 2010

Bug#574817: libata transition breaks mdadm arrays

2010-03-25 Thread Mathieu Parent (Debian)
Hi, On Tue, Mar 23, 2010 at 10:26 AM, martin f krafft madd...@debian.org 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

Bug#574817: libata transition breaks mdadm arrays

2010-03-25 Thread martin f krafft
also sprach Mathieu Parent (Debian) sath...@debian.org [2010.03.25.1132 +0100]: Do I need to update-initramfs? Yes, to install the mdadm.conf file. -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'`

Bug#574817: libata transition breaks mdadm arrays

2010-03-23 Thread martin f krafft
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. --

Bug#574817: libata transition breaks mdadm arrays

2010-03-23 Thread Mathieu Parent (Debian)
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.

Bug#574817: libata transition breaks mdadm arrays

2010-03-22 Thread martin f krafft
tags 574817 moreinfo thanks also sprach Mathieu Parent sath...@debian.org [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

Bug#574817: libata transition breaks mdadm arrays

2010-03-22 Thread Mathieu Parent (Debian)
Mathieu Parent On Mon, Mar 22, 2010 at 2:56 PM, martin f krafft madd...@debian.org wrote: tags 574817 moreinfo thanks also sprach Mathieu Parent sath...@debian.org [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

Bug#574817: libata transition breaks mdadm arrays

2010-03-22 Thread Mathieu Parent (Debian)
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?

Bug#574817: libata transition breaks mdadm arrays

2010-03-21 Thread Mathieu Parent
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

Bug#574817: libata transition breaks mdadm arrays

2010-03-21 Thread Mathieu Parent (Debian)
Hi, On Sun, Mar 21, 2010 at 1:35 PM, Bastian Blank wa...@debian.org 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

Bug#574817: libata transition breaks mdadm arrays

2010-03-21 Thread Bastian Blank
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

Bug#574817: libata transition breaks mdadm arrays

2010-03-21 Thread Bastian Blank
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 wa...@debian.org 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

Bug#574817: libata transition breaks mdadm arrays

2010-03-21 Thread Mathieu Parent (Debian)
On Sun, Mar 21, 2010 at 3:03 PM, Bastian Blank wa...@debian.org 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 wa...@debian.org wrote: This is expected and not an error. Don't list device-names in

Bug#574817: libata transition breaks mdadm arrays

2010-03-21 Thread Ben Hutchings
On Sun, 2010-03-21 at 15:20 +0100, Mathieu Parent (Debian) wrote: On Sun, Mar 21, 2010 at 3:03 PM, Bastian Blank wa...@debian.org 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 wa...@debian.org wrote: This is