Problem with Kernel upgrade

[maverick0815]

I wanted to run an update on my md, running 12.04
And get this :

root@moon37:~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]? y
Setting up linux-image-3.2.0-74-generic (3.2.0-74.109) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.2.0-74-generic /boot/vmlinuz-3.2.0-74-generic
run-parts: executing /etc/kernel/postinst.d/dkms 3.2.0-74-generic /boot/vmlinuz-3.2.0-74-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.2.0-74-generic /boot/vmlinuz-3.2.0-74-generic
update-initramfs: Generating /boot/initrd.img-3.2.0-74-generic
cryptsetup: WARNING: failed to detect canonical device of 192.168.80.1:/usr/pluto/diskless/37
cryptsetup: WARNING: could not determine root device from /etc/fstab
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.2.0-74-generic /boot/vmlinuz-3.2.0-74-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 3.2.0-74-generic /boot/vmlinuz-3.2.0-74-generic
run-parts: executing /etc/kernel/postinst.d/update-symlinks 3.2.0-74-generic /boot/vmlinuz-3.2.0-74-generic
chmod: cannot operate on dangling symlink `/boot/initrd.img'
chmod: cannot operate on dangling symlink `/boot/vmlinuz'
chmod: cannot operate on dangling symlink `/boot/initrd.img'
chmod: cannot operate on dangling symlink `/boot/vmlinuz'
/ /
/
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.2.0-74-generic /boot/vmlinuz-3.2.0-74-generic
/usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?).
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.2.0-74-generic.postinst line 1010.
dpkg: error processing linux-image-3.2.0-74-generic (--configure):
 subprocess installed post-installation script returned error exit status 2
No apport report written because MaxReports is reached already
                                                              dpkg: dependency problems prevent configuration of linux-image-generic:
 linux-image-generic depends on linux-image-3.2.0-74-generic; however:
  Package linux-image-3.2.0-74-generic is not configured yet.
dpkg: error processing linux-image-generic (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
                                                              Errors were encountered while processing:
 linux-image-3.2.0-74-generic
 linux-image-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@moon37:~#

[phenigma]

make sure you do this on the running MD (local terminal or ssh, not in chroot).

if you continue to have problems then try:

Code: [Select]

rm /boot/initird.img
rm /boot/vmlinuz

and then retry you upgrade

J.

[maverick0815]

I tried, but the error remains the same.

[phenigma]

Re-run Diskless_CreateTBZ.sh on the core and then choose "Rebuild MD" from the webadmin for that Media Director.  Something is not right.

J.

[maverick0815]

it seems there is a regularly occuring problems with those upgrades on the md. Sometimes its ok, other times it give the same error as before. Then I will rerun Diskless_CreateTBZ.sh and rebuild the image of the md.

The other thing I noticed today with a kernel upgrade on the core. After the upgrade, I rebooted the server. When it was finished, none of the phones were registered again. So I rebooted the server once more, but still no luck. In the end I had to reinstall Asterisk and now its working again.

[phenigma]

You must run the dist-upgrade on the running MD.  I have not had any issues with dist-upgrading any of my MDs so I cannot re-create this.

The asterisk issues have not been seen before, sounds like a dkms issue with the dahdi components.  Without specific errors from the upgrade and following reboot I cannot speculate further.

J.