Multiples packages fails to install when using NFS root

[Jarmo]

I have an nfs root on one of my boxes - I made it to upgrade for ubuntu version 12.
I have not installed grub on the box but seems the installation requires it (and some other packages); thus upgrade installed but failed to configure these packages:

 friendly-recovery
 linux-image-3.2.0-24-generic-pae
 linux-image-generic-pae
 grub-pc

After upgrade, I removed friendly-recovery, grub-pc-bin, grub2-common, grub-common and grub-pc, which enabled the kernel package(s) to be configured correctly.

Also; I got these warnings while configuration was being made:

update-initramfs: Generating /boot/initrd.img-3.2.0-24-generic-pae
cryptsetup: WARNING: failed to detect canonical device of /dev/nfs
cryptsetup: WARNING: could not determine root device from /etc/fstab

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: friendly-recovery 0.2.25
ProcVersionSignature: Ubuntu 3.0.0-19.32-generic-pae 3.0.27
Uname: Linux 3.0.0-19-generic-pae i686
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
Date: Sat Apr 28 12:35:08 2012
ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu-Server 10.10 "Maverick Meerkat" - Release i386 (20101007)
PackageArchitecture: all
SourcePackage: friendly-recovery
Title: package friendly-recovery 0.2.25 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to precise on 2012-04-28 (0 days ago)

[mythsmith (mythsmith)]

I had exactly the same problem.
The only way managed to get the system past kernel update is to manually edit this file:
/etc/kernel/postinst.d/zz-update-grub
And modify the start of the script so it immediately exit with successful state=0:

#! /bin/sh
exit 0
[...] etc...

This will allow the installation of the new kernel to proceed. You will have to edit that file again each time you want to upgrade the kernel.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.