I'm now getting a similar issue. I'm upgrading from karmic to lucid using do-release-upgrade.

Whenever I boot the system using the latest paravirt kernel (Latest 2.6 Paravirt (2.6.32-x86_64-linode11)), I am unable to get to the recovery console, as the console prints out some text, then goes into a loop where three or four mountall errors are printed constantly.

Here is the startup sequence below (I apologize for any spelling mistakes, as I'm copying this from a screenshot and not able to copy-paste)

mountall: mount [6378] terminated with status 32
mou
uld not be mounted:
mountall: Skipping mounting since Plymouth is not available
does not exist
mountall: mount [6379] terminated with status 32
mountall: Filesys
nted:
mountall: Skipping mounting since Plymouth is not available
mount: mount p
mountall: mount [6380] terminated with status 32
mountall: Filesystem could not
: Skipping mounting since Plymouth is not available
mount: mount point does not
t [6381] terminated with status 32

I can get to the recovery image using finnix, however, I don't know what to do in there, as update-initramfs will create a ramfs for the finnix kernel, and not the one I want to boot!

Hmmm, what's in your /etc/fstab? It sounds like something weird is in there. This is probably going to be a different problem than the 9.04 -> 9.10 upgrades.

Note that 10.04 is still in beta, so there's a nonzero chance you hit some random bug at the wrong time... if worse comes to worse, revert to the image you cloned prior to attempting the upgrade and try it again in a few days.

Hmmm, what's in your /etc/fstab? It sounds like something weird is in there. This is probably going to be a different problem than the 9.04 -> 9.10 upgrades.

Note that 10.04 is still in beta, so there's a nonzero chance you hit some random bug at the wrong time... if worse comes to worse, revert to the image you cloned prior to attempting the upgrade and try it again in a few days.

Thanks for the help...

Just in case someone else runs into this problem, the looping occurred because I had an error in my /etc/fstab

I added the dev line to /etc/fstab, which did not fix the problem in and of itself. Switching the kernel from stable to paravirt did get me back up and running. I have not tried booting with paravirt and without the dev entry in fstab.

_________________"I'll say it again for the logic-impaired." -- Larry Wall