After manually updating to grub2 (the grub-pc package) and removing legacy grub, I installed the proposed mdadm on my development trusty system. I haven't looked at the SRU verification tests yet. I realise the cryptsetup warning is not directly related to mdadm, but sdb is the second disk in my soft raid array and I don't have ANY encrypted volumes. This would make me nervous about upgrading my production system! Here is the console log:
brian@schizo:/etc/apt$ sudo apt-get install mdadm/trusty-proposed
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version '3.2.5-5ubuntu4.1' (Ubuntu:14.04/trusty-proposed [i386]) for 'mdadm'
The following packages will be upgraded:
mdadm
1 to upgrade, 0 to newly install, 0 to remove and 95 not to upgrade.
Need to get 362 kB of archives.
After this operation, 1,024 B of additional disk space will be used.
Get:1 http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty-proposed/main mdadm i386 3.2.5-5ubuntu4.1 [362 kB]
Fetched 362 kB in 1s (258 kB/s)
Preconfiguring packages ...
(Reading database ... 340057 files and directories currently installed.)
Preparing to unpack .../mdadm_3.2.5-5ubuntu4.1_i386.deb ...
* Stopping MD monitoring service mdadm --monitor [ OK ]
Unpacking mdadm (3.2.5-5ubuntu4.1) over (3.2.5-5ubuntu4) ...
Processing triggers for man-db (2.6.7.1-1) ...
Processing triggers for doc-base (0.10.5) ...
Processing 6 changed doc-base files...
Registering documents with scrollkeeper...
Processing triggers for ureadahead (0.100.0-16) ...
ureadahead will be reprofiled on next reboot
Setting up mdadm (3.2.5-5ubuntu4.1) ...
Removing any system startup links for /etc/init.d/mdadm-raid ...
update-initramfs: deferring update (trigger activated)
Generating grub configuration file ...
File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30372: /usr/sbin/grub-probe
File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30372: /usr/sbin/grub-probe
File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30423: /usr/sbin/grub-probe
File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30423: /usr/sbin/grub-probe
File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30474: /usr/sbin/grub-probe
File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30474: /usr/sbin/grub-probe
File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30525: /usr/sbin/grub-probe
File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30525: /usr/sbin/grub-probe
File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30701: /usr/sbin/grub-probe
File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30701: /usr/sbin/grub-probe
Found linux image: /boot/vmlinuz-3.13.0-24-generic
Found initrd image: /boot/initrd.img-3.13.0-24-generic
Found linux image: /boot/vmlinuz-3.11.0-19-generic
Found initrd image: /boot/initrd.img-3.11.0-19-generic
File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 31336: /usr/sbin/grub-probe
File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 31336: /usr/sbin/grub-probe
Found memtest86+ image: /memtest86+.elf
Found memtest86+ image: /memtest86+.bin
File descriptor 3 (pipe:[112701]) leaked on lvs invocation. Parent PID 31926: /bin/sh
done
* Starting MD monitoring service mdadm --monitor [ OK ]
Processing triggers for initramfs-tools (0.103ubuntu4) ...
update-initramfs: Generating /boot/initrd.img-3.13.0-24-generic
cryptsetup: WARNING: failed to detect canonical device of /dev/sda2
brian@schizo:/etc/apt$
After manually updating to grub2 (the grub-pc package) and removing legacy grub, I installed the proposed mdadm on my development trusty system. I haven't looked at the SRU verification tests yet. I realise the cryptsetup warning is not directly related to mdadm, but sdb is the second disk in my soft raid array and I don't have ANY encrypted volumes. This would make me nervous about upgrading my production system! Here is the console log:
brian@schizo: /etc/apt$ sudo apt-get install mdadm/trusty- proposed 14.04/trusty- proposed [i386]) for 'mdadm' mirror. ox.ac.uk/ sites/archive. ubuntu. com/ubuntu/ trusty- proposed/ main mdadm i386 3.2.5-5ubuntu4.1 [362 kB] 3.2.5-5ubuntu4. 1_i386. deb ... d/mdadm- raid ... grub-probe grub-probe grub-probe grub-probe grub-probe grub-probe grub-probe grub-probe grub-probe grub-probe 3.13.0- 24-generic img-3.13. 0-24-generic 3.11.0- 19-generic img-3.11. 0-19-generic grub-probe grub-probe img-3.13. 0-24-generic /etc/apt$
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version '3.2.5-5ubuntu4.1' (Ubuntu:
The following packages will be upgraded:
mdadm
1 to upgrade, 0 to newly install, 0 to remove and 95 not to upgrade.
Need to get 362 kB of archives.
After this operation, 1,024 B of additional disk space will be used.
Get:1 http://
Fetched 362 kB in 1s (258 kB/s)
Preconfiguring packages ...
(Reading database ... 340057 files and directories currently installed.)
Preparing to unpack .../mdadm_
* Stopping MD monitoring service mdadm --monitor [ OK ]
Unpacking mdadm (3.2.5-5ubuntu4.1) over (3.2.5-5ubuntu4) ...
Processing triggers for man-db (2.6.7.1-1) ...
Processing triggers for doc-base (0.10.5) ...
Processing 6 changed doc-base files...
Registering documents with scrollkeeper...
Processing triggers for ureadahead (0.100.0-16) ...
ureadahead will be reprofiled on next reboot
Setting up mdadm (3.2.5-5ubuntu4.1) ...
Removing any system startup links for /etc/init.
update-initramfs: deferring update (trigger activated)
Generating grub configuration file ...
File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30372: /usr/sbin/
File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30372: /usr/sbin/
File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30423: /usr/sbin/
File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30423: /usr/sbin/
File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30474: /usr/sbin/
File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30474: /usr/sbin/
File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30525: /usr/sbin/
File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30525: /usr/sbin/
File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30701: /usr/sbin/
File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 30701: /usr/sbin/
Found linux image: /boot/vmlinuz-
Found initrd image: /boot/initrd.
Found linux image: /boot/vmlinuz-
Found initrd image: /boot/initrd.
File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 31336: /usr/sbin/
File descriptor 3 (pipe:[112701]) leaked on vgs invocation. Parent PID 31336: /usr/sbin/
Found memtest86+ image: /memtest86+.elf
Found memtest86+ image: /memtest86+.bin
File descriptor 3 (pipe:[112701]) leaked on lvs invocation. Parent PID 31926: /bin/sh
done
* Starting MD monitoring service mdadm --monitor [ OK ]
Processing triggers for initramfs-tools (0.103ubuntu4) ...
update-initramfs: Generating /boot/initrd.
cryptsetup: WARNING: failed to detect canonical device of /dev/sda2
brian@schizo: