VMWare virtual machine won't boot after 12.04 upgrade












1















I was running an 11.10 virtual machine on VMWare Workstation 7.1.5 build-491717.



I tried to upgrade the other day to 12.04. After everything was downloaded and installed, the system asked to be booted.



I've confirmed, and since then I've never been able succeed loading the system.
When I boot, the screen shows nothing but a blinking cursor, and my caps-lock seems to repeatedly turn on and off. (which freaked me out :-) )



When I try to load my previous system (11.10), it manage to load, but everything is strange+no network connection.



Does anyone familiar with the issue? I've read some posts but it seems to be ages ago and non-relevant.





The gist of the panic from the screenshot is:



VFS: cannot open root device sda1
Please append correct root= boot option
Available partitions are: sr0 only
Kernel panic: VFS: unable to mount root fs




Never had problems before. In fact, Linux always ran better on the VM than the MS-win7. I'm not such a linux expert - nooB treatment would be preferred :-D



EDIT:



Physical System:




  • i5 2.66 quad, 12 GB ram

  • Graphic card (sux) nVidia 210

  • OS, win7 Ultimate.


I've tried installing the VM toolkit, so I can gain some extra features, but it didn't succeed as well, so my guess is nothing was installed.



The console output when TRYing 2 boot on recovery mode:



https://www.dropbox.com/sh/7vgz3vw5kyv5n9f/M1Ifv0rOtM



@izx, What am I suppose to do with it? :-) What do I need to do to fix the sda1 device? Is this a VM issue? Should I need to copy the settings as appeared on the previous version?



Edit
Tried to run update-initramfs as @psusi suggested, but got another error.
Apparently, my /lib/modules/3.2.0.24-generic has nothing in it.
I tried copying the modules.dep from another kenrnel (previous 1) but nothing.
Here's the console output.



Dismissed, final solution:
fresh install.










share|improve this question
















bumped to the homepage by Community 2 days ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Are you able to boot in to recovery mode (press shift right before your OS would boot)?

    – Bruno Pereira
    Jun 4 '12 at 13:19











  • Did you install any extra vmware kernel modules or anything of that sort on 11.10? What OS is your physical host running?

    – ish
    Jun 4 '12 at 13:36











  • @izx, 10x 4 the replay.. Now, what am I suppose to do with it? :-) What do I need 2 do to fix the sda1 device? Is this a VM issue??

    – OBY
    Jun 4 '12 at 16:03


















1















I was running an 11.10 virtual machine on VMWare Workstation 7.1.5 build-491717.



I tried to upgrade the other day to 12.04. After everything was downloaded and installed, the system asked to be booted.



I've confirmed, and since then I've never been able succeed loading the system.
When I boot, the screen shows nothing but a blinking cursor, and my caps-lock seems to repeatedly turn on and off. (which freaked me out :-) )



When I try to load my previous system (11.10), it manage to load, but everything is strange+no network connection.



Does anyone familiar with the issue? I've read some posts but it seems to be ages ago and non-relevant.





The gist of the panic from the screenshot is:



VFS: cannot open root device sda1
Please append correct root= boot option
Available partitions are: sr0 only
Kernel panic: VFS: unable to mount root fs




Never had problems before. In fact, Linux always ran better on the VM than the MS-win7. I'm not such a linux expert - nooB treatment would be preferred :-D



EDIT:



Physical System:




  • i5 2.66 quad, 12 GB ram

  • Graphic card (sux) nVidia 210

  • OS, win7 Ultimate.


I've tried installing the VM toolkit, so I can gain some extra features, but it didn't succeed as well, so my guess is nothing was installed.



The console output when TRYing 2 boot on recovery mode:



https://www.dropbox.com/sh/7vgz3vw5kyv5n9f/M1Ifv0rOtM



@izx, What am I suppose to do with it? :-) What do I need to do to fix the sda1 device? Is this a VM issue? Should I need to copy the settings as appeared on the previous version?



Edit
Tried to run update-initramfs as @psusi suggested, but got another error.
Apparently, my /lib/modules/3.2.0.24-generic has nothing in it.
I tried copying the modules.dep from another kenrnel (previous 1) but nothing.
Here's the console output.



Dismissed, final solution:
fresh install.










share|improve this question
















bumped to the homepage by Community 2 days ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Are you able to boot in to recovery mode (press shift right before your OS would boot)?

    – Bruno Pereira
    Jun 4 '12 at 13:19











  • Did you install any extra vmware kernel modules or anything of that sort on 11.10? What OS is your physical host running?

    – ish
    Jun 4 '12 at 13:36











  • @izx, 10x 4 the replay.. Now, what am I suppose to do with it? :-) What do I need 2 do to fix the sda1 device? Is this a VM issue??

    – OBY
    Jun 4 '12 at 16:03
















1












1








1


0






I was running an 11.10 virtual machine on VMWare Workstation 7.1.5 build-491717.



I tried to upgrade the other day to 12.04. After everything was downloaded and installed, the system asked to be booted.



I've confirmed, and since then I've never been able succeed loading the system.
When I boot, the screen shows nothing but a blinking cursor, and my caps-lock seems to repeatedly turn on and off. (which freaked me out :-) )



When I try to load my previous system (11.10), it manage to load, but everything is strange+no network connection.



Does anyone familiar with the issue? I've read some posts but it seems to be ages ago and non-relevant.





The gist of the panic from the screenshot is:



VFS: cannot open root device sda1
Please append correct root= boot option
Available partitions are: sr0 only
Kernel panic: VFS: unable to mount root fs




Never had problems before. In fact, Linux always ran better on the VM than the MS-win7. I'm not such a linux expert - nooB treatment would be preferred :-D



EDIT:



Physical System:




  • i5 2.66 quad, 12 GB ram

  • Graphic card (sux) nVidia 210

  • OS, win7 Ultimate.


I've tried installing the VM toolkit, so I can gain some extra features, but it didn't succeed as well, so my guess is nothing was installed.



The console output when TRYing 2 boot on recovery mode:



https://www.dropbox.com/sh/7vgz3vw5kyv5n9f/M1Ifv0rOtM



@izx, What am I suppose to do with it? :-) What do I need to do to fix the sda1 device? Is this a VM issue? Should I need to copy the settings as appeared on the previous version?



Edit
Tried to run update-initramfs as @psusi suggested, but got another error.
Apparently, my /lib/modules/3.2.0.24-generic has nothing in it.
I tried copying the modules.dep from another kenrnel (previous 1) but nothing.
Here's the console output.



Dismissed, final solution:
fresh install.










share|improve this question
















I was running an 11.10 virtual machine on VMWare Workstation 7.1.5 build-491717.



I tried to upgrade the other day to 12.04. After everything was downloaded and installed, the system asked to be booted.



I've confirmed, and since then I've never been able succeed loading the system.
When I boot, the screen shows nothing but a blinking cursor, and my caps-lock seems to repeatedly turn on and off. (which freaked me out :-) )



When I try to load my previous system (11.10), it manage to load, but everything is strange+no network connection.



Does anyone familiar with the issue? I've read some posts but it seems to be ages ago and non-relevant.





The gist of the panic from the screenshot is:



VFS: cannot open root device sda1
Please append correct root= boot option
Available partitions are: sr0 only
Kernel panic: VFS: unable to mount root fs




Never had problems before. In fact, Linux always ran better on the VM than the MS-win7. I'm not such a linux expert - nooB treatment would be preferred :-D



EDIT:



Physical System:




  • i5 2.66 quad, 12 GB ram

  • Graphic card (sux) nVidia 210

  • OS, win7 Ultimate.


I've tried installing the VM toolkit, so I can gain some extra features, but it didn't succeed as well, so my guess is nothing was installed.



The console output when TRYing 2 boot on recovery mode:



https://www.dropbox.com/sh/7vgz3vw5kyv5n9f/M1Ifv0rOtM



@izx, What am I suppose to do with it? :-) What do I need to do to fix the sda1 device? Is this a VM issue? Should I need to copy the settings as appeared on the previous version?



Edit
Tried to run update-initramfs as @psusi suggested, but got another error.
Apparently, my /lib/modules/3.2.0.24-generic has nothing in it.
I tried copying the modules.dep from another kenrnel (previous 1) but nothing.
Here's the console output.



Dismissed, final solution:
fresh install.







12.04 boot kernel virtualization vmware-workstation






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jun 22 '14 at 13:10









jobin

19.3k1277109




19.3k1277109










asked Jun 4 '12 at 12:52









OBYOBY

613




613





bumped to the homepage by Community 2 days ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 2 days ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • Are you able to boot in to recovery mode (press shift right before your OS would boot)?

    – Bruno Pereira
    Jun 4 '12 at 13:19











  • Did you install any extra vmware kernel modules or anything of that sort on 11.10? What OS is your physical host running?

    – ish
    Jun 4 '12 at 13:36











  • @izx, 10x 4 the replay.. Now, what am I suppose to do with it? :-) What do I need 2 do to fix the sda1 device? Is this a VM issue??

    – OBY
    Jun 4 '12 at 16:03





















  • Are you able to boot in to recovery mode (press shift right before your OS would boot)?

    – Bruno Pereira
    Jun 4 '12 at 13:19











  • Did you install any extra vmware kernel modules or anything of that sort on 11.10? What OS is your physical host running?

    – ish
    Jun 4 '12 at 13:36











  • @izx, 10x 4 the replay.. Now, what am I suppose to do with it? :-) What do I need 2 do to fix the sda1 device? Is this a VM issue??

    – OBY
    Jun 4 '12 at 16:03



















Are you able to boot in to recovery mode (press shift right before your OS would boot)?

– Bruno Pereira
Jun 4 '12 at 13:19





Are you able to boot in to recovery mode (press shift right before your OS would boot)?

– Bruno Pereira
Jun 4 '12 at 13:19













Did you install any extra vmware kernel modules or anything of that sort on 11.10? What OS is your physical host running?

– ish
Jun 4 '12 at 13:36





Did you install any extra vmware kernel modules or anything of that sort on 11.10? What OS is your physical host running?

– ish
Jun 4 '12 at 13:36













@izx, 10x 4 the replay.. Now, what am I suppose to do with it? :-) What do I need 2 do to fix the sda1 device? Is this a VM issue??

– OBY
Jun 4 '12 at 16:03







@izx, 10x 4 the replay.. Now, what am I suppose to do with it? :-) What do I need 2 do to fix the sda1 device? Is this a VM issue??

– OBY
Jun 4 '12 at 16:03












1 Answer
1






active

oldest

votes


















0














It looks like your new kernel is missing its initramfs. If you can boot the old kernel, then run sudo update-initramfs to generate one.






share|improve this answer



















  • 1





    The OP indicated they are not very adept with such things; can you explain how to do so?

    – hexafraction
    Aug 18 '12 at 17:09











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f146324%2fvmware-virtual-machine-wont-boot-after-12-04-upgrade%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














It looks like your new kernel is missing its initramfs. If you can boot the old kernel, then run sudo update-initramfs to generate one.






share|improve this answer



















  • 1





    The OP indicated they are not very adept with such things; can you explain how to do so?

    – hexafraction
    Aug 18 '12 at 17:09
















0














It looks like your new kernel is missing its initramfs. If you can boot the old kernel, then run sudo update-initramfs to generate one.






share|improve this answer



















  • 1





    The OP indicated they are not very adept with such things; can you explain how to do so?

    – hexafraction
    Aug 18 '12 at 17:09














0












0








0







It looks like your new kernel is missing its initramfs. If you can boot the old kernel, then run sudo update-initramfs to generate one.






share|improve this answer













It looks like your new kernel is missing its initramfs. If you can boot the old kernel, then run sudo update-initramfs to generate one.







share|improve this answer












share|improve this answer



share|improve this answer










answered Jun 4 '12 at 23:11









psusipsusi

31.1k15088




31.1k15088








  • 1





    The OP indicated they are not very adept with such things; can you explain how to do so?

    – hexafraction
    Aug 18 '12 at 17:09














  • 1





    The OP indicated they are not very adept with such things; can you explain how to do so?

    – hexafraction
    Aug 18 '12 at 17:09








1




1





The OP indicated they are not very adept with such things; can you explain how to do so?

– hexafraction
Aug 18 '12 at 17:09





The OP indicated they are not very adept with such things; can you explain how to do so?

– hexafraction
Aug 18 '12 at 17:09


















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f146324%2fvmware-virtual-machine-wont-boot-after-12-04-upgrade%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

數位音樂下載

When can things happen in Etherscan, such as the picture below?

格利澤436b