Package: multipath-tools Version: 0.4.8-3 Severity: critical Justification: breaks the whole system
My system does not use multipath but I installed multipath-tools to get kpartx (I know now this is a separate package). When my ramdisk was next generated (new kernel or initramfs-tools I suppose) I ended up with an initrd which did not boot (hence severity: critical). This seems to be because the multipath tools hooks "dmsetup create" on my root disk but do not undo this when no multipath configuration is discovered (or whatever I don't really know what is supposed to happen) therefore the device is busy when the initrd comes to mount it. Console log, copied by hand since no serial or netconsole available, is pasted below. Thanks, Ian. ---start console output--- Begin: Mounting root file system... ... Begin: Running /scripts/local-top ... device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: [EMAIL PROTECTED] device-mapper: multipath: version 1.0.5 loaded device-mapper: multipath emc: version 0.0.3 loaded Discovering multipaths... device-mapper: multipath round-robin: version 1.0.0 loaded Done. Begin: Running /scripts/local-premount kinit: name_to_dev_t(/dev/sda4) = sda4(8,4) kinit: trying to resume from /dev/sda4 Attempting manual resume kinit: No resume image, doing normal boot... resume: libgcrypt version: 1.2.4 Done. mount: Mounting /dev/sda3 on /root failed: Device or resource busy Being: Running /scripts/local-bottom ... Done. Done. Begin: Running /scripts/init-bottom ... mount: Mounting /root/dev on /dev/.static/dev failed: No such file or directory Done. mount: Mounting /sys on /root/sys failed: No such file or directory mount: Mounting /proc on /root/proc failed: No such file or directory Target filesystem doesn't have /sbin/init BusyBox v1.1.3 (Debian 1:1.1.3-5) Built-in shell (ash) Enter 'help' for a list of built-in commands. /bin/sh: can't access tty; job control turned off (initramfs) mount /dev/sda3 /root mount: Mounting /dev/sda3 on /root failed: Device or resource busy (initramfs) ls /dev/mapper SATA_FUJITSU_MHV2080_NW9UT6C27043 SATA_FUJITSU_MHV2080_NW9UT6C27043-part2 SATA_FUJITSU_MHV2080_NW9UT6C27043-part4 SATA_FUJITSU_MHV2080_NW9UT6C27043-part1 SATA_FUJITSU_MHV2080_NW9UT6C27043-part3 control (initramfs) dmsetup remove /dev/mapper/SATA_FUJITSU_MHV2080_NW9UT6C27043-part1 (initramfs) dmsetup remove /dev/mapper/SATA_FUJITSU_MHV2080_NW9UT6C27043-part2 (initramfs) dmsetup remove /dev/mapper/SATA_FUJITSU_MHV2080_NW9UT6C27043-part3 (initramfs) dmsetup remove /dev/mapper/SATA_FUJITSU_MHV2080_NW9UT6C27043-part4 (initramfs) dmsetup remove /dev/mapper/SATA_FUJITSU_MHV2080_NW9UT6C27043 (initramfs) mount /dev/sda3 /root kjournald starting. Commit interval 5 seconds EXT3 FS on sda3, internal journal EXT3-fs: mounted filesystem with ordered data mode. (initramfs) ls /root bin...[etc]... ---end console output--- -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages multipath-tools depends on: ii dmsetup 2:1.02.20-2 The Linux Kernel Device Mapper use ii initscripts 2.86.ds1-38.1 Scripts for initializing and shutt ii kpartx 0.4.8-3 create device mappings for partiti ii libaio1 0.3.106-6 linux kernel aio access library - ii libc6 2.6.1-1 GNU C Library: Shared libraries ii libdevmapper1.02.1 2:1.02.20-2 The Linux Kernel Device Mapper use ii libncurses5 5.6+20070825-1 Shared libraries for terminal hand ii libreadline5 5.2-3 GNU readline and history libraries ii lsb-base 3.1-24 Linux Standard Base 3.1 init scrip ii udev 0.114-2 /dev/ and hotplug management daemo multipath-tools recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
