Tell me more ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.
up vote 1 down vote favorite

Several Ubuntu 10.04 VMs were restarted after few months and began getting "Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)" message. Restoring those VMs from backup (to the "paused" state) allows to boot normally. However restarting the VM again results in the mentioned error message. I suspect it's the updated kernel version (2.6.32-37-server, 2.6.32-38-server) that misbehave - another Ubuntu VM (that's used as template for those failing VMs) still has 2.6.32-24-server and reboots fine. We're using HyperV (2008R2) as the server host. Nothing were changed in it's configuration. Has anyone faced this issue, please advise the solution. Many Thanks in advance!

share|improve this question
1  
This question appears to be abandoned and unanswered. Could you perhaps add more detail to your question? If this question no longer applies then you can either delete it or answer it yourself if you've solved the problem. Thanks! – Seth Jan 26 at 15:42

closed as too localized by fossfreedom♦ Jan 26 at 19:46

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, see the FAQ.

1 Answer

up vote 0 down vote

We would not expect to see issue with these newer kernels on Hyper-V. You should be able to find the older kernels in the boot menu (holding shift in early boot) to recover the VMs.

To get this looked into you should file a bug in launchpad against the package linux and include as many details as you can. If there is a regression it would have occured in one of the kernels between the last working one and the latest. All of these kernels are available in the launchpad librarian (see the URL below) and if you could test those to find the first version which will not boot, that would be most instructive. Please include all of this in your bug:

https://launchpad.net/ubuntu/+source/linux/+publishinghistory
share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.