Your message dated Wed, 27 Jul 2016 10:37:25 +0000
with message-id <e1bsmdn-0000in...@franck.debian.org>
and subject line Bug#830770: fixed in mdadm 3.4-3
has caused the Debian Bug report #830770,
regarding mdadm: initramfs broken
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.)
--
830770: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830770
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mdadm
Version: 3.4-2
Severity: important
With 3.4-2 my lvm on partitioned md system has stopped initializing
correctly. For starters when upgrading from 3.4-1 to 3.4-2 I get
this:
W: mdadm: the array /dev/md/d0 with UUID 4c4bcb71:267c92fc:fe08e7ef:27569e0b
W: mdadm: is currently active, but it is not listed in mdadm.conf. if
W: mdadm: it is needed for boot, then YOUR SYSTEM IS NOW UNBOOTABLE!
W: mdadm: please inspect the output of /usr/share/mdadm/mkconf, compare
W: mdadm: it to /etc/mdadm/mdadm.conf, and make the necessary changes.
This is thanks to the change of:
if ! grep -qi "uuid=$uuid" $DESTMDADMCONF; then
to
if ! grep -q "UUID=$uuid" $DESTMDADMCONF; then
The manpage uses uuid=, the examples use both uuid= and UUID=, and the
uuid itself had better be treated as case-insensitive... so if you ask
me, it's cleaner and more correct, to just do:
uuid=`echo "$params" | grep -oi ' uuid=[0-9a-f:]\+'`
if ! grep -qi "$uuid" $DESTMDADMCONF; then
...
That said, this isn't why my system stopped booting after updating to
3.4-2, it's just an irritating distraction.
AFAICT, the new initramfs-tools scripts simply never assemble
any arrays. The old local-top/mdadm script ran either
$MDADM --assemble --scan --run --auto=yes${extra_args:+ $extra_args}
or $MDADM --assemble --scan --run --auto=yes $dev
depending on $MD_DEVS.
If run I mdadm --assemble --scan manually after the initramfs has
dumped me to a shell, and then keep kicking various lvm scripts until
I get my root device to show up, I can proceed, but this new package
strikes me as very, very broken.
Here's some of the blather from /usr/share/bug/mdadm/script but let me
prefix this with, I've pruned out detail that wasn't germane, and my
topology is lvm on top of md raid1 on a traditional sysvinit system.
--- mdadm.conf
DEVICE /dev/sd[ab]
HOMEHOST <system>
MAILADDR root
ARRAY /dev/md/d0 metadata=1.0 UUID=4c4bcb71:267c92fc:fe08e7ef:27569e0b
name=cucamonga:d0
--- /etc/default/mdadm
AUTOCHECK=true
START_DAEMON=true
DAEMON_OPTIONS="--syslog"
VERBOSE=false
--- /proc/mdstat:
Personalities : [raid1]
md_d0 : active raid1 sda[0] sdb[1]
976762448 blocks super 1.0 [2/2] [UU]
unused devices: <none>
--- /proc/partitions:
major minor #blocks name
8 0 976762584 sda
8 16 976762584 sdb
253 0 976762448 md_d0
253 1 968373248 md_d0p1
253 2 8388176 md_d0p2
--- LVM physical volumes:
File descriptor 3 (/dev/pts/5) leaked on pvs invocation. Parent PID 16632:
/bin/bash
PV VG Fmt Attr PSize PFree
/dev/md_d0p1 S lvm2 a-- 923.51g 545.51g
--- /proc/modules:
dm_crypt 24576 1 - Live 0xffffffffa0222000
raid1 32768 1 - Live 0xffffffffa0016000
md_mod 98304 4 raid1, Live 0xffffffffa0021000
dm_mod 86016 26 dm_crypt, Live 0xffffffffa0000000
--- volume detail:
/dev/sda:
Magic : a92b4efc
Version : 1.0
Feature Map : 0x0
Array UUID : 4c4bcb71:267c92fc:fe08e7ef:27569e0b
Name : cucamonga:d0 (local to host cucamonga)
Creation Time : Fri Feb 11 07:29:10 2011
Raid Level : raid1
Raid Devices : 2
Avail Dev Size : 1953524896 (931.51 GiB 1000.20 GB)
Array Size : 976762448 (931.51 GiB 1000.20 GB)
Super Offset : 1953525152 sectors
Unused Space : before=0 sectors, after=256 sectors
State : clean
Device UUID : 03d87172:57951a8c:b9b40189:051ed01b
Update Time : Mon Jul 11 09:27:06 2016
Checksum : b10e71e7 - correct
Events : 2479
Device Role : Active device 0
Array State : AA ('A' == active, '.' == missing, 'R' == replacing)
--
/dev/sdb:
Magic : a92b4efc
Version : 1.0
Feature Map : 0x0
Array UUID : 4c4bcb71:267c92fc:fe08e7ef:27569e0b
Name : cucamonga:d0 (local to host cucamonga)
Creation Time : Fri Feb 11 07:29:10 2011
Raid Level : raid1
Raid Devices : 2
Avail Dev Size : 1953524896 (931.51 GiB 1000.20 GB)
Array Size : 976762448 (931.51 GiB 1000.20 GB)
Super Offset : 1953525152 sectors
Unused Space : before=0 sectors, after=256 sectors
State : clean
Device UUID : dcee8016:570d79ee:40fd87f0:26c35131
Update Time : Mon Jul 11 09:27:06 2016
Checksum : 3483ee6a - correct
Events : 2479
Device Role : Active device 1
Array State : AA ('A' == active, '.' == missing, 'R' == replacing)
--- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.6.1 root=/dev/mapper/S-root ro
rng-core.default_quality=512
--- udev:
ii udev 230-7 amd64 /dev/ and hotplug management daem
aa83f41de49462d05e446cfc5e14e74b /lib/udev/rules.d/63-md-raid-arrays.rules
5de7d0b70cd948d00bb38ca75ad5f288 /lib/udev/rules.d/64-md-raid-assembly.rules
--- /dev:
brw-rw---- 1 root disk 253, 0 Jul 11 05:47 /dev/md_d0
brw-rw---- 1 root disk 253, 1 Jul 11 05:47 /dev/md_d0p1
brw-rw---- 1 root disk 253, 2 Jul 11 05:47 /dev/md_d0p2
--
Jamie Heilman http://audible.transient.net/~jamie/
--- End Message ---
--- Begin Message ---
Source: mdadm
Source-Version: 3.4-3
We believe that the bug you reported is fixed in the latest version of
mdadm, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 830...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dimitri John Ledkov <x...@ubuntu.com> (supplier of updated mdadm package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Tue, 26 Jul 2016 17:09:54 +0100
Source: mdadm
Binary: mdadm mdadm-udeb
Architecture: source
Version: 3.4-3
Distribution: unstable
Urgency: high
Maintainer: Debian mdadm maintainers <pkg-mdadm-de...@lists.alioth.debian.org>
Changed-By: Dimitri John Ledkov <x...@ubuntu.com>
Description:
mdadm - tool to administer Linux MD arrays (software RAID)
mdadm-udeb - tool to administer Linux MD arrays (software RAID) (udeb)
Closes: 830300 830770
Changes:
mdadm (3.4-3) unstable; urgency=high
.
* Fix UUID= grep for configured RAIDs to be case incesetive, regression from
3.4-2.
.
* Re-trigger block devices at the start of local-block mdadm loop, to
re-incrementally assemble disks that appeared before RAID
personalities were registered with the kernel.
.
* Also, invoke non-incremental assembly of raid arrays in the
local-block loop to support running mdadm with user-exported variables
specified via param.conf.
.
* Set Vcs- fields to dgit repositories.
.
* Closes: #830770, #830300.
Checksums-Sha1:
73ed0f5357342f0cc9d16f2bc3d471d7c2ea5d84 1598 mdadm_3.4-3.dsc
08f9e5ea7cc6a6f0f89eeeaed939040f72dcc7f1 82272 mdadm_3.4-3.debian.tar.xz
Checksums-Sha256:
b1d30140b19653669dad249c19df184f77a44a5139728417a27e9e41b8271bc6 1598
mdadm_3.4-3.dsc
98baaa5380ed5b80d981f23df67c85c673e9a4d2c301698e15941b3e516b2044 82272
mdadm_3.4-3.debian.tar.xz
Files:
2378d3d1d3e1f6a5f1f61d206be70c9d 1598 admin optional mdadm_3.4-3.dsc
5239a0838735e48f3188977a0b1cbaab 82272 admin optional mdadm_3.4-3.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJXmI0BAAoJEMrC2LnNLKX5YUIH/0QQAOIZKW9GIHdylJxJl9se
TbOeORG2K6tRBT6pqogD1L6oMEYb2D2oQyQ+uDaz+Sflc0iFyYnhDDxVlXhyTxCF
/B/dI08yiB8GId5kOyr49xse9PgyGCNef8Jml6T+L7V0YKjPJ1ghZnZGTNldXykb
5nMx8WBisI2rcaOT/6ucWa/YSToxGgEOUdoRy+3HXqOruk2LLUdjHQTqpIEvNj6O
CUkAHYgpdJ6r5roeeeMGKHyTvzxoxf1amxQwAldIc3B8EIx/KdgHcpowdJhiYVtn
G3aQdEDlrz2i+vcru/lpS6+5FBAm6PLhLbYLkxBmxzcZDPAULiS9t0wpnJ0qfyg=
=HDFL
-----END PGP SIGNATURE-----
--- End Message ---
