no ssh or console after upgrade to 12.04

[holtzermann17]

 I am having troubles after upgrading from 11.10 on a Linode.

 "Your Linode appears to have stalled mid-boot at around the time that the start up process is handed off to init. It looks like the kernel handed off control to init, as it didn't panic, however it doesn't appear that any further services were started after that."

 "You'll want to contact the Ubuntu community for more information on known issues with 12.04 and virtualized environments."

This is what the support person at Linode.com told me.

Since I can't SSH in and can't get Console access, I seem somewhat hosed. (When I try to access the machine via LISH, I just get the log, not a real console - the log is copied here: http://pastebin.com/raw.php?i=4cMh5Gcr .)

I don't know if there's anything that can be done to help fix my virtual server, but maybe this bug report will help keep others from trying the same thing.

If this always happens on Linodes, it should be listed among the known issues at

https://wiki.ubuntu.com/PrecisePangolin/TechnicalOverview/Alpha1

along with the issues for Users of VMWare Workstation 8 or VMWare Player, #858122.

[holtzermann17 (holtzermann17)]

Note that (thankfully) I can access the machine via Linode's "Rescue" mode, so if you have advice for me on how to tweak things so I can get the machine to boot properly, this may be useful...

 http://library.linode.com/troubleshooting/finnix-rescue-mode

And if anyone wants to get access to the machine to inspect it themselves, feel free to contact me by email <email address hidden>.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/942907/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[holtzermann17 (holtzermann17)]

kklimonda in #ubuntu-server and dariti on staff at Linode suggest that I *could* install a custom kernel and get more debugging information out of the system as it tries to initialize, by setting the " init=/sbin/init --verbose " option for GRUB. Installing a custom kernel on a non-operational OS is beyond what I want to work on at this hour, however, I would again be happy to give access to the machine to an interested party who would like to attempt this, if the situation is of interest.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 942907

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[holtzermann17 (holtzermann17)]

@brad-figg: I can't run apport-collect because I can't log in to the server. I DO have access to the file system through Linode's "Rescue" mode, so if there are specific log files that you would like to see, just let me know which ones they are and I can post them.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.