Package: mdadm Version: 3.3.2-2 On the next reboot after upgrading mdadm from 3.2.5-5 to 3.3.2-2 I was greeted with a fatal fsck error. Turned out symlinks like /dev/md/boot were missing. Manual creation of the necessary symlink allowed boot to continue. Then I upgraded udev from 175-7.2 to 215-5+b1. After reboot /dev/md/* symlinks were back.
Probably mdadm needs a versioned Depends: on udev. I wouldn't want to run into this issue on some remote server. This is easily reproducible within qemu: Install Debian 7.7 with / on raid1. /dev/md/0 symlink exists. Add jessie to /etc/apt/sources.list. # apt-get update # apt-get install mdadm # reboot /dev/md is empty. # apt-get install udev # reboot /dev/md/0 is back. -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (900, 'stable') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mdadm depends on: ii debconf [debconf-2.0] 1.5.49 ii initscripts 2.88dsf-41+deb7u1 ii libc6 2.19-13 ii lsb-base 4.1+Debian8+deb7u1 ii udev 215-5+b1 Versions of packages mdadm recommends: ii exim4-daemon-light [mail-transport-agent] 4.80-7+deb7u1 ii kmod 18-3 ii module-init-tools 18-3 mdadm suggests no packages. -- debconf information: mdadm/autostart: true * mdadm/initrdstart: all * mdadm/initrdstart_notinconf: false mdadm/initrdstart_msg_errexist: mdadm/initrdstart_msg_intro: mdadm/initrdstart_msg_errblock: * mdadm/start_daemon: true * mdadm/mail_to: root mdadm/initrdstart_msg_errmd: mdadm/initrdstart_msg_errconf: * mdadm/autocheck: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
