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)
Code:
EXT3-fs: mounted filesystem with writeback data mode.
VFS: Mounted root (ext3 filesystem) readonly on device 202:0.
Freeing unused kernel memory: 496k freed
Write protecting the kernel read-only data: 7192k
init: ureadahead main process (987) terminated with status 5
init: ureadahead-other main process (996) terminated with status 4
init: ureadahead-other main process (997) terminated with status 4
then, I get into the mountall loop
Code:
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!