Your message dated Tue, 17 Feb 2009 21:03:55 +0100
with message-id <20090217200355.ga30...@piper.oerlikon.madduck.net>
and subject line Re: Bug#515676: After "dist-upgrade" from etch to lenny the
system can no longer assemble and mount mdadm RAID drives
has caused the Debian Bug report #515676,
regarding After "dist-upgrade" from etch to lenny the system can no longer
assemble and mount mdadm RAID drives
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
515676: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515676
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mdadm
Version: 2.6.7.2-1
Subject: After "dist-upgrade" from etch to lenny the system can no longer
assemble and mount mdadm RAID drives
After "dist-upgrade" from etch to lenny the system can no longer assemble and
mount mdadm RAID drives under the etch kernel 2.6.26. I still can assemble and
mount mdadm RAID drives under the kernel 2.6.18 that I have left over from etch.
When running the upgraded system under kernel 2.6.18, the output of the
"/usr/share/bug/mdadm/script" is as follows:
--- mount output
/dev/md2 on / type ext3 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/md1 on /boot type ext3 (rw,errors=remount-ro)
--- mdadm.conf
ARRAY /dev/md1 level=raid1 num-devices=3
UUID=bdf8a211:fcf6d2af:d7771298:fac716d3
ARRAY /dev/md2 level=raid5 num-devices=3
UUID=2ed75bfb:aed804cd:7cc7e04b:e56f1452
ARRAY /dev/md3 level=raid5 num-devices=3
UUID=3232181c:698319a1:67aa3321:ae8fa7a3
MAILADDR root
--- /proc/mdstat:
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4]
md1 : active raid1 sda1[0] sdc1[2] sdb1[1]
40064 blocks [3/3] [UUU]
md2 : active raid5 sda2[0] sdc2[2] sdb2[1]
486351616 blocks level 5, 64k chunk, algorithm 2 [3/3] [UUU]
md3 : active raid5 sda3[0] sdc3[2] sdb3[1]
1959680 blocks level 5, 64k chunk, algorithm 2 [3/3] [UUU]
unused devices: <none>
--- /proc/partitions:
major minor #blocks name
8 0 244197527 sda
8 1 40131 sda1
8 2 243175905 sda2
8 3 979965 sda3
8 16 244198584 sdb
8 17 40131 sdb1
8 18 243175905 sdb2
8 19 979965 sdb3
8 32 244198584 sdc
8 33 40131 sdc1
8 34 243175905 sdc2
8 35 979965 sdc3
9 3 1959680 md3
9 2 486351616 md2
9 1 40064 md1
--- initrd.img-2.6.18-6-686:
gzip: /boot/initrd.img-2.6.18-6-686: not in gzip format
cpio: premature end of archive
This issue was discussed at some length at
http://groups.google.com/group/linux.debian.user/browse_thread/thread/b97fd9b0a450370f#
Thanks
--- End Message ---
--- Begin Message ---
also sprach S D <sund...@yahoo.com> [2009.02.17.2038 +0100]:
> W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf
> W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz .
There's your answer.
--
.''`. martin f. krafft <madd...@d.o> Related projects:
: :' : proud Debian developer http://debiansystem.info
`. `'` http://people.debian.org/~madduck http://vcs-pkg.org
`- Debian - when you have better things to do than fixing systems
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
--- End Message ---
