Bug#813225: mdadm: insserv rejected the sript header
David
chernoff at astro.cornell.edu
Sat Jan 30 15:24:07 UTC 2016
Package: mdadm
Version: 3.2.5-5
Severity: important
Dear Maintainer,
* What led up to the situation?
apt-get used to install mdadm on raspbian/wheezy
* What exactly did you do (or not do) that was effective (or
ineffective)?
sudo apt-get update
sudo apt-get install mdadm
and answered 2 questions:
MD arrays needed for root file system: none
Do you want to start MD arrays automatically: Yes
* What was the outcome of this action?
After installing several dependencies succesfully
apt-get started to set up mdadm. This generated
several insserv errors/messages and
update-rc.d said "insserv rejected the script header"
dpkg returned error code (1)
* What outcome did you expect instead?
mdadm to be installed and startup scripts updated
*HERE IS A COMPLETE LISTING OF THE INSTALL TTY OUTPUT
sudo apt-get update
Get:1 http://archive.raspbian.org wheezy Release.gpg [490 B]
Get:2 http://archive.raspbian.org wheezy Release [14.4 kB]
Get:3 http://archive.raspbian.org wheezy/main armhf Packages [6909 kB]
Get:4 http://archive.raspbian.org wheezy/contrib armhf Packages [23.6 kB]
Get:5 http://archive.raspbian.org wheezy/non-free armhf Packages [49.3 kB]
Ign http://archive.raspbian.org wheezy/contrib Translation-en
Ign http://archive.raspbian.org wheezy/main Translation-en
Ign http://archive.raspbian.org wheezy/non-free Translation-en
Fetched 6997 kB in 1min 31s (76.8 kB/s)
Reading package lists... Done
pi at raspbmc:~$ sudo apt-get install mdadm
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libcups2 libpcap0.8 libxext6 libxmuu1 tdb-tools
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
exim4-base exim4-config exim4-daemon-light heirloom-mailx psmisc
Suggested packages:
mail-reader eximon4 exim4-doc-html exim4-doc-info gnutls-bin openssl
spf-tools-perl swaks exim4 mail-transport-agent
/mdadm
....skipping
mailx
The following NEW packages will be installed:
exim4-base exim4-config exim4-daemon-light heirloom-mailx mdadm psmisc
0 upgraded, 6 newly installed, 0 to remove and 6 not upgraded.
Need to get 3073 kB of archives.
After this operation, 6030 kB of additional disk space will be used.
Do you want to continue [Y/n]? Y
Get:1 http://archive.raspbian.org/raspbian/ wheezy/main exim4-config all 4.80-7+
deb7u1 [478 kB]
Get:2 http://archive.raspbian.org/raspbian/ wheezy/main exim4-base armhf 4.80-7+
deb7u1 [1033 kB]
Get:3 http://archive.raspbian.org/raspbian/ wheezy/main exim4-daemon-light armhf
4.80-7+deb7u1 [635 kB]
Get:4 http://archive.raspbian.org/raspbian/ wheezy/main heirloom-mailx armhf 12.
5-2+deb7u1 [254 kB]
Get:5 http://archive.raspbian.org/raspbian/ wheezy/main mdadm armhf 3.2.5-5 [542
kB]
Get:6 http://archive.raspbian.org/raspbian/ wheezy/main psmisc armhf 22.19-1+deb
7u1 [132 kB]
Fetched 3073 kB in 19s (160 kB/s)
Preconfiguring packages ...
/mdadm
....skipping
Package configuration
┌────────────────────────────Configuring mdadm───────────────────────────────â”─
│ f the system's root file system is located on an MD array (RAID), it │
│ eeds to be started early during the boot sequence. If it is located on │
│ logical volume (LVM), which is on MD, all constituent arrays need to │
│ e started. │
│ │
│ f you know exactly which arrays are needed to bring up the root file │
│ ystem, and you want to postpone starting all other arrays to a later │
│ oint in the boot sequence, enter the arrays to start here. │
│ lternatively, enter 'all' to simply start all available arrays. │
│ │
│ f you do not need or want to start any arrays for the root file │
│ ystem, leave the answer blank (or enter 'none'). This may be the case │
│ f you are using kernel autostart or do not need any arrays to boot. │
│ │
│ lease enter 'all', 'none', or a space-separated list of devices such │
│ s 'md0 md1' or 'md/1 md/d0' (the leading '/dev/' can be omitted). │
├────────────────────────────────────────────────────────────────────────────┤
│ < EXIT > │
└────────────────────────────────────────────────────────────────────────────┘
Package configuration
──────────────────────────────────────────────────────────────────────────────
┌──────────────Configuring mdadm────────────────â”
│ MD arrays needed for the root file system: │
│ ┌───────────────────────────────────────────┠│
│ │none │ │
├─└───────────────────────────────────────────┘─┤
│ < OK > │
└───────────────────────────────────────────────┘
Package configuration
──────────────────────────────────────────────────────────────────────────────
┌────────────────────────────Configuring mdadm───────────────────────────────â”
│ Once the base system has booted, mdadm can start all MD arrays (RAIDs) │
│ specified in /etc/mdadm/mdadm.conf which have not yet been started. │
│ This is recommended unless multiple device (MD) support is compiled │
│ into the kernel and all partitions are marked as belonging to MD │
│ arrays, with type 0xfd (as those and only those will be started │
│ automatically by the kernel). │
│ │
│ Do you want to start MD arrays automatically? │
│ │
│ │
├────────────────────────────────────────────────────────────────────────────┤
│ < Yes > < No > │
└────────────────────────────────────────────────────────────────────────────┘
Selecting previously unselected package exim4-config.
(Reading database ... 31261 files and directories currently installed.)
Unpacking exim4-config (from .../exim4-config_4.80-7+deb7u1_all.deb) ...
Selecting previously unselected package exim4-base.
Unpacking exim4-base (from .../exim4-base_4.80-7+deb7u1_armhf.deb) ...
Selecting previously unselected package exim4-daemon-light.
Unpacking exim4-daemon-light (from .../exim4-daemon-light_4.80-7+deb7u1_armhf.de
b) ...
Selecting previously unselected package heirloom-mailx.
Unpacking heirloom-mailx (from .../heirloom-mailx_12.5-2+deb7u1_armhf.deb) ...
Selecting previously unselected package mdadm.
Unpacking mdadm (from .../mdadm_3.2.5-5_armhf.deb) ...
Selecting previously unselected package psmisc.
Unpacking psmisc (from .../psmisc_22.19-1+deb7u1_armhf.deb) ...
Setting up exim4-config (4.80-7+deb7u1) ...
Adding system-user for exim (v4)
Setting up exim4-base (4.80-7+deb7u1) ...
exim: DB upgrade, deleting hints-db
Setting up exim4-daemon-light (4.80-7+deb7u1) ...
[ ok ] Starting MTA: exim4.
Setting up heirloom-mailx (12.5-2+deb7u1) ...
update-alternatives: using /usr/bin/heirloom-mailx to provide /usr/bin/mailx (ma
ilx) in auto mode
Setting up mdadm (3.2.5-5) ...
Generating mdadm.conf... done.
update-initramfs: deferring update (trigger activated)
insserv: Service mountkernfs has to be enabled to start service mdadm-raid
insserv: Service hostname has to be enabled to start service mdadm-raid
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error processing mdadm (--configure):
subprocess installed post-installation script returned error exit status 1
Setting up psmisc (22.19-1+deb7u1) ...
Processing triggers for initramfs-tools ...
Errors were encountered while processing:
mdadm
E: Sub-process /usr/bin/dpkg returned an error code (1)
pi at raspbmc:~$
-- System Information:
Debian Release: 7.8
Architecture: armhf (armv6l)
Kernel: Linux 3.12.31 (PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages mdadm depends on:
ii debconf 1.5.49
pn initscripts <none>
ii libc6 2.13-38+rpi2+deb7u8
ii libgcc1 1:4.7.2-5+rpi1
pn lsb-base <none>
ii makedev 2.3.1-92
Versions of packages mdadm recommends:
ii exim4-daemon-light [mail-transport-agent] 4.80-7+deb7u1
ii module-init-tools 9-3
mdadm suggests no packages.
More information about the pkg-mdadm-devel
mailing list