Well, I've repeatedly tried to actually recreate this now. I upgraded from 6.0.0-1ubuntu2 to 6.0.0-1ubuntu2.1 I did a force reconfigure I purged portmap/nfs-common and re-installed I tried upgrading just portmap and incrementally nfs-common
In all cases my systems boot fine now. I reverted to a snapshot of my system which exhibits the problem (which is still there) and made the requested changes, but I still just see the screen stop updating after 'init: portmap main process ended, respawning' The only additional message I see is: portmap[219]: cannot bind udp: Cannot assign requested address I verified I don't get that message with the same changes to portmap.conf on a working system, instead I get this one: portmap-wait: Main process killed by term I then tried to remove portmap-wait.conf, this seemed to prevent the hang, but I got a message about eth1 being busy (which didn't seem to effect anything) Replacing portmap-wait.conf and removing statd-mounting.conf also prevented the hang, and I didn't get the message about eth1 Removing portmap-boot.conf had no effect I diffed the above files (portmap.conf, portmap-boot.conf, portmap- wait.con, statd-mounting.conf) between the working and hanging snapshot and see no differences. I'm not sure any of the above helps, but I found it frustrating taht I couldn't put the machine back in a broken state. As my working configuration has moved forward since I got it functional, it isn't trivial to diff the 2 environments, though if you have ideas where I should look, I can take a more targetted approach -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/719143 Title: portmap 6.0.0-1ubuntu2.1 makes nfs boot machine unbootable -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
