Your message dated Thu, 02 Sep 2010 14:47:10 +0000
with message-id <[email protected]>
and subject line Bug#585015: fixed in mdadm 3.1.4-1
has caused the Debian Bug report #585015,
regarding mdadm: long delay (6-200 minutes) during boot (root device detection)
after upgrade on RAID/LVM/LUKS setup
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 [email protected]
immediately.)
--
585015: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585015
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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 upgraded by doing this as lvm2, mdadm, initscripts,
initramfs-tools. I have a standard md RAID1 setup with LVM over it. Furthermore
there is a partition for `/boot` and a LUKS encrypted `/`.
Now I am seeing the following behavior. After GRUB2 started (`linux
/vmlinuz-2.6.32-5-amd64 root=/dev/mapper/lvm-root …`) I first get to see a lot
of lines
sys/devices/virtual/block (some incremented number in 80??)
(this is from memory). Afterward I am asked for the LUKS passphrase. After that
nothing happens. Just a lot of – according to my Web research unrelated
–udev-work messages about `NAME` and `SYMLINK` stuff and nothing happens. Then
after six to ten minutes booting finally continues.
$ dmesg
[…]
[ 1.588141] usbcore: registered new interface driver usbhid
[ 1.588144] usbhid: v2.6:USB HID core driver
[ 1.676754] md: raid1 personality registered for level 1
[ 1.689704] md: md0 stopped.
[ 1.690573] md: bind<sda1>
[ 1.692913] raid1: raid set md0 active with 1 out of 2 mirrors
[ 1.692944] md0: detected capacity change from 0 to 509804544
[ 1.694098] md0: unknown partition table
[ 1.701276] md: md1 stopped.
[ 1.703642] md: bind<sda2>
[ 1.706108] raid1: raid set md1 active with 1 out of 2 mirrors
[ 1.706140] md1: detected capacity change from 0 to 499595214848
[ 1.707746] md1:
[ 1.715665] device-mapper: uevent: version 1.0.3
[ 1.715825] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01)
initialised: [email protected]
[ 1.745488] unknown partition table
[ 1144.682200] PM: Starting manual resume from disk
[ 1144.682205] PM: Resume from partition 253:2
[ 1144.682207] PM: Checking hibernation image.
[ 1144.693923] PM: Error -22 checking image file
[ 1144.693927] PM: Resume from disk failed.
[…]
Is that related to the `root` argument passed in GRUB to `linux`. In [1] the
solution is to use a UUID instead of the path. Though I did not find how I can
find out the correct value for my RAID device or LVM partition.
Sorry if I filed this against the wrong package. Any hints are welcome. Please
ask for additional information if needed.
Thanks,
Paul
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583284
PS: Upgrading from 0.95 to 0.95.1 today did not help.
-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 9.8M May 31 11:28 /boot/initrd.img-2.6.32-5-686
-rw-r--r-- 1 root root 9.9M May 31 11:29 /boot/initrd.img-2.6.32-5-amd64
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-2.6.32-5-amd64 root=/dev/mapper/speicher-root ro quiet
-- resume
RESUME=/dev/mapper/speicher-swap
-- /proc/filesystems
ext3
fuseblk
xfs
reiserfs
-- lsmod
Module Size Used by
binfmt_misc 6399 1
via 32847 0
drm 142199 1 via
ppdev 5030 0
lp 7462 0
ip6table_filter 2384 0
ip6_tables 14867 1 ip6table_filter
iptable_filter 2258 0
ip_tables 13675 1 iptable_filter
x_tables 12685 2 ip6_tables,ip_tables
kvm_amd 31222 0
kvm 213448 1 kvm_amd
powernow_k8 10978 1
cpufreq_conservative 5162 0
cpufreq_userspace 1992 0
cpufreq_stats 2659 0
cpufreq_powersave 902 0
reiserfs 193756 1
xfs 436189 2
exportfs 3122 1 xfs
fuse 49982 1
loop 11607 0
firewire_sbp2 11418 0
firewire_core 36624 1 firewire_sbp2
crc_itu_t 1307 1 firewire_core
snd_hda_codec_realtek 235026 1
snd_hda_intel 19907 4
snd_hda_codec 53892 2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 5236 1 snd_hda_codec
snd_pcm_oss 32415 0
snd_mixer_oss 12478 1 snd_pcm_oss
snd_pcm 60119 4 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq_midi 4256 0
snd_rawmidi 15323 1 snd_seq_midi
snd_seq_midi_event 4628 1 snd_seq_midi
snd_seq 41281 2 snd_seq_midi,snd_seq_midi_event
snd_timer 15486 2 snd_pcm,snd_seq
snd_seq_device 4493 3 snd_seq_midi,snd_rawmidi,snd_seq
amd64_edac_mod 13630 0
tpm_tis 7336 0
parport_pc 18855 1
edac_core 29197 3 amd64_edac_mod
snd 45918 18
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
tpm 9549 1 tpm_tis
i2c_viapro 5483 0
parport 27682 3 ppdev,lp,parport_pc
soundcore 4566 1 snd
psmouse 49777 0
asus_atk0110 7686 0
tpm_bios 4489 1 tpm
edac_mce_amd 6433 1 amd64_edac_mod
k8temp 3139 0
shpchp 26232 0
snd_page_alloc 6217 2 snd_hda_intel,snd_pcm
pcspkr 1699 0
serio_raw 3752 0
evdev 7352 16
i2c_core 15328 2 drm,i2c_viapro
pci_hotplug 21203 1 shpchp
processor 30167 1 powernow_k8
button 4650 0
ext3 106326 5
jbd 36861 1 ext3
mbcache 5050 1 ext3
sha256_generic 8644 2
aes_x86_64 7340 2
aes_generic 25714 1 aes_x86_64
cbc 2507 1
dm_crypt 10491 1
dm_mod 53434 27 dm_crypt
raid1 17999 2
md_mod 73040 3 raid1
usbhid 33244 0
hid 62793 1 usbhid
sg 18632 0
sr_mod 12250 0
sd_mod 29553 3
crc_t10dif 1276 1 sd_mod
cdrom 28631 1 sr_mod
ata_generic 2983 0
sata_via 7789 2
uhci_hcd 18521 0
pata_via 7461 0
libata 133008 3 ata_generic,sata_via,pata_via
ehci_hcd 31023 0
thermal 11610 0
thermal_sys 11942 2 processor,thermal
scsi_mod 121717 5 firewire_sbp2,sg,sr_mod,sd_mod,libata
via_rhine 17371 0
mii 3210 1 via_rhine
usbcore 121671 4 usbhid,uhci_hcd,ehci_hcd
nls_base 6361 1 usbcore
-- /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = no
-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=y
KEYMAP=n
COMPRESS=gzip
BOOT=local
DEVICE=
NFSROOT=auto
-- /etc/crypttab
# <target name> <source device> <key file> <options>
md1_crypt /dev/md1 none luks
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages initramfs-tools depends on:
ii cpio 2.11-4 GNU cpio -- a program to manage ar
ii findutils 4.4.2-1 utilities for finding files--find,
ii klibc-utils 1.5.18-1 small utilities built with klibc f
ii module-init-tools 3.12~pre2-3 tools for managing Linux kernel mo
ii udev 154-1 /dev/ and hotplug management daemo
Versions of packages initramfs-tools recommends:
ii busybox 1:1.15.3-1 Tiny utilities for small and embed
initramfs-tools suggests no packages.
-- no debconf information
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: mdadm
Source-Version: 3.1.4-1
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:
mdadm-udeb_3.1.4-1_amd64.udeb
to main/m/mdadm/mdadm-udeb_3.1.4-1_amd64.udeb
mdadm-udeb_3.1.4-1_i386.udeb
to main/m/mdadm/mdadm-udeb_3.1.4-1_i386.udeb
mdadm_3.1.4-1.debian.tar.gz
to main/m/mdadm/mdadm_3.1.4-1.debian.tar.gz
mdadm_3.1.4-1.dsc
to main/m/mdadm/mdadm_3.1.4-1.dsc
mdadm_3.1.4-1_amd64.deb
to main/m/mdadm/mdadm_3.1.4-1_amd64.deb
mdadm_3.1.4-1_i386.deb
to main/m/mdadm/mdadm_3.1.4-1_i386.deb
mdadm_3.1.4.orig.tar.bz2
to main/m/mdadm/mdadm_3.1.4.orig.tar.bz2
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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
martin f. krafft <[email protected]> (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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Format: 1.8
Date: Sun, 29 Aug 2010 13:44:59 +0200
Source: mdadm
Binary: mdadm mdadm-udeb
Architecture: amd64 i386 source
Version: 3.1.4-1
Distribution: unstable
Urgency: low
Maintainer: Debian mdadm maintainers <[email protected]>
Changed-By: martin f. krafft <[email protected]>
Closes: 508123 539154 583545 585015 587550 589493 589833 589836 592149 595039
Description:
mdadm - tool to administer Linux MD arrays (software RAID)
mdadm-udeb - tool to administer Linux MD arrays (software RAID) (udeb)
Changes:
mdadm (3.1.4-1) unstable; urgency=low
.
* New upstream release, which closes:#595039 and addresses the following
issues too:
- reverts move of incremental map (closes: #585015).
- fixes mdadm monitor in the case of an inactive (or start-failed) raid0
or linear array (closes: #539154).
- prevent --remove faulty from skipping renumbered devices
(closes: #587550).
- fixed overflow when growing a RAID6 (closes: #589493).
* However, disable the incremental assembly upstream turned on in 3.1.3 for
now, this will have to wait until after the squeeze release.
* initramfs/hook: make sure configuration file exists before accessing it;
thanks to Michael Prokop for the fix and NMU (closes: #589836).
* initramfs/hook: Match UUID case-insensitive while checking for running
arrays not listed in mdadm.conf; thanks to Mario 'BitKoenig' Holbe for the
patch (closes: #583545).
* Fix URL in the bug reporting preamble (presubj) (closes: #589833).
* Add I/O rescheduling functionality to the checkarray script and make the
cronjob use the idle priority; this should now minimise the impact of the
monthly re-check on the running system; Florian Heigl had the idea
(closes: #592149, #508123).
Checksums-Sha1:
4b394e76fd8524d1f6f3288c47346c561c82cfa9 1264 mdadm_3.1.4-1.dsc
4ee43922d38b15a930daaaa026ef1b4efacdbc8a 288578 mdadm_3.1.4.orig.tar.bz2
6809f25c344ea3398b5be6cb229ced13b63e846a 149194 mdadm-udeb_3.1.4-1_amd64.udeb
80b4e4fb3871c1b242e3f533af4d8d3ca669632f 463680 mdadm_3.1.4-1_amd64.deb
9f6aeb857e2312ac8a3dc33103a79d6f4fc236eb 452524 mdadm_3.1.4-1_i386.deb
f494b7d94f1cb9872172ba02a61a2da1993260b1 136054 mdadm_3.1.4-1.debian.tar.gz
ff534bb80c83b3655cc41baccd8e416290ae8205 144080 mdadm-udeb_3.1.4-1_i386.udeb
Checksums-Sha256:
4de462be6bb005c0a9eb4db0b8579c7c72c2ec134b0616493f37c61332ec4fe9 136054
mdadm_3.1.4-1.debian.tar.gz
574aa07386c7bac30e7cae3511ce54c509b1f33a59283fe83a74ca57feb83771 144080
mdadm-udeb_3.1.4-1_i386.udeb
849ad0ad4ad3c1d2d8806a16b30e1f59ab2daf313cb103807207f7cba889ea63 288578
mdadm_3.1.4.orig.tar.bz2
47ebe383ffb39211dc50d6f4f167fc55695ccb9b77bf590a6c3347a022b4edd5 1264
mdadm_3.1.4-1.dsc
f1da9e2aabd9e0c779ae4a2de0463027e3e355f5c3411130ff1aea3fee533342 463680
mdadm_3.1.4-1_amd64.deb
f6baefc11b29796a8dd6bd7ff43100ef3711f0c97198339665d6acc46780ac2b 452524
mdadm_3.1.4-1_i386.deb
fb64f21a18cd4324f66f9f42c4d2b40a78fa732d5c466bef410a0685c96c11da 149194
mdadm-udeb_3.1.4-1_amd64.udeb
Files:
0046231a53920f796ab6cb282a1701b3 463680 admin optional mdadm_3.1.4-1_amd64.deb
0e7dcb5cc4192ae3abd9956bac475576 288578 admin optional mdadm_3.1.4.orig.tar.bz2
67bebc9b4a499b8530aa845cf4fad602 452524 admin optional mdadm_3.1.4-1_i386.deb
695c5d69f500c48390468befe2af5dab 149194 debian-installer optional
mdadm-udeb_3.1.4-1_amd64.udeb
3dd99e5613949d0b08476b9fd8ecd968 1264 admin optional mdadm_3.1.4-1.dsc
890087bdcf25bf4718e94567c02892ca 136054 admin optional
mdadm_3.1.4-1.debian.tar.gz
c56789de930909d8f989b16e3012c4f3 144080 debian-installer optional
mdadm-udeb_3.1.4-1_i386.udeb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEAREDAAYFAkx/tOsACgkQIgvIgzMMSnV1PgCfRv46dF6pDLl6KKzKtuiH7bqU
m4MAmgLk8xB68XvPCKrqM2VkJON8uqTM
=FLUK
-----END PGP SIGNATURE-----
--- End Message ---
