Just started using Ubuntu again, I had a major crash












-1















My system hung up while installing Virtualbox, I had to do a hard reset. After the system came back up, it's stuck in some Terminal screen. Just a cursor at the corner, but I cannot enter any commands. I tried some recovery options, still stuck. Just wanted to know if there was some way out of it. I previously got stuck at 640x480 resolution But I edited my grub file to add the other resolutions back in. was working fine for a few days until it hung up during VBox install, I could not even open a Term to tell it to reboot. Now the system won't some up. Just need to know if there is some trick to get it to come back up. e;se I'll just reinstall, no problem really. Don't want to lose the files I got saved in Home. Reinstall to the system partition? Checked through the listed questions, didn't see anything similar that had any answers. Thank you.










share|improve this question


















  • 1





    If you can provide more details we may be able to help more. What release of Ubuntu? Stick in some 'terminal screen'? If you can provide detail about this we may be able to help more. Your forced-shutdown may have introduced fs (file-system) errors & you only need to fsck (file system check) which you can do from a 'live' (or install media). The commands needed vary on fs & release (which can influence fs used). Yes you can re-install, I'd suggest with 'something else' & select your existing partitions. It'll erase your system directories (not $HOME) keeping as much as possible.

    – guiverc
    Feb 8 at 1:56











  • I had a response all typed up but it was “too big“, and I don’t have time to deal with this right now, i’ll have to come back to this in a couple of days. It was the very latest version, not the version with the lifetime support.

    – Jonny Vee
    Feb 9 at 2:21


















-1















My system hung up while installing Virtualbox, I had to do a hard reset. After the system came back up, it's stuck in some Terminal screen. Just a cursor at the corner, but I cannot enter any commands. I tried some recovery options, still stuck. Just wanted to know if there was some way out of it. I previously got stuck at 640x480 resolution But I edited my grub file to add the other resolutions back in. was working fine for a few days until it hung up during VBox install, I could not even open a Term to tell it to reboot. Now the system won't some up. Just need to know if there is some trick to get it to come back up. e;se I'll just reinstall, no problem really. Don't want to lose the files I got saved in Home. Reinstall to the system partition? Checked through the listed questions, didn't see anything similar that had any answers. Thank you.










share|improve this question


















  • 1





    If you can provide more details we may be able to help more. What release of Ubuntu? Stick in some 'terminal screen'? If you can provide detail about this we may be able to help more. Your forced-shutdown may have introduced fs (file-system) errors & you only need to fsck (file system check) which you can do from a 'live' (or install media). The commands needed vary on fs & release (which can influence fs used). Yes you can re-install, I'd suggest with 'something else' & select your existing partitions. It'll erase your system directories (not $HOME) keeping as much as possible.

    – guiverc
    Feb 8 at 1:56











  • I had a response all typed up but it was “too big“, and I don’t have time to deal with this right now, i’ll have to come back to this in a couple of days. It was the very latest version, not the version with the lifetime support.

    – Jonny Vee
    Feb 9 at 2:21
















-1












-1








-1








My system hung up while installing Virtualbox, I had to do a hard reset. After the system came back up, it's stuck in some Terminal screen. Just a cursor at the corner, but I cannot enter any commands. I tried some recovery options, still stuck. Just wanted to know if there was some way out of it. I previously got stuck at 640x480 resolution But I edited my grub file to add the other resolutions back in. was working fine for a few days until it hung up during VBox install, I could not even open a Term to tell it to reboot. Now the system won't some up. Just need to know if there is some trick to get it to come back up. e;se I'll just reinstall, no problem really. Don't want to lose the files I got saved in Home. Reinstall to the system partition? Checked through the listed questions, didn't see anything similar that had any answers. Thank you.










share|improve this question














My system hung up while installing Virtualbox, I had to do a hard reset. After the system came back up, it's stuck in some Terminal screen. Just a cursor at the corner, but I cannot enter any commands. I tried some recovery options, still stuck. Just wanted to know if there was some way out of it. I previously got stuck at 640x480 resolution But I edited my grub file to add the other resolutions back in. was working fine for a few days until it hung up during VBox install, I could not even open a Term to tell it to reboot. Now the system won't some up. Just need to know if there is some trick to get it to come back up. e;se I'll just reinstall, no problem really. Don't want to lose the files I got saved in Home. Reinstall to the system partition? Checked through the listed questions, didn't see anything similar that had any answers. Thank you.







boot






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Feb 8 at 1:14









Jonny VeeJonny Vee

1




1








  • 1





    If you can provide more details we may be able to help more. What release of Ubuntu? Stick in some 'terminal screen'? If you can provide detail about this we may be able to help more. Your forced-shutdown may have introduced fs (file-system) errors & you only need to fsck (file system check) which you can do from a 'live' (or install media). The commands needed vary on fs & release (which can influence fs used). Yes you can re-install, I'd suggest with 'something else' & select your existing partitions. It'll erase your system directories (not $HOME) keeping as much as possible.

    – guiverc
    Feb 8 at 1:56











  • I had a response all typed up but it was “too big“, and I don’t have time to deal with this right now, i’ll have to come back to this in a couple of days. It was the very latest version, not the version with the lifetime support.

    – Jonny Vee
    Feb 9 at 2:21
















  • 1





    If you can provide more details we may be able to help more. What release of Ubuntu? Stick in some 'terminal screen'? If you can provide detail about this we may be able to help more. Your forced-shutdown may have introduced fs (file-system) errors & you only need to fsck (file system check) which you can do from a 'live' (or install media). The commands needed vary on fs & release (which can influence fs used). Yes you can re-install, I'd suggest with 'something else' & select your existing partitions. It'll erase your system directories (not $HOME) keeping as much as possible.

    – guiverc
    Feb 8 at 1:56











  • I had a response all typed up but it was “too big“, and I don’t have time to deal with this right now, i’ll have to come back to this in a couple of days. It was the very latest version, not the version with the lifetime support.

    – Jonny Vee
    Feb 9 at 2:21










1




1





If you can provide more details we may be able to help more. What release of Ubuntu? Stick in some 'terminal screen'? If you can provide detail about this we may be able to help more. Your forced-shutdown may have introduced fs (file-system) errors & you only need to fsck (file system check) which you can do from a 'live' (or install media). The commands needed vary on fs & release (which can influence fs used). Yes you can re-install, I'd suggest with 'something else' & select your existing partitions. It'll erase your system directories (not $HOME) keeping as much as possible.

– guiverc
Feb 8 at 1:56





If you can provide more details we may be able to help more. What release of Ubuntu? Stick in some 'terminal screen'? If you can provide detail about this we may be able to help more. Your forced-shutdown may have introduced fs (file-system) errors & you only need to fsck (file system check) which you can do from a 'live' (or install media). The commands needed vary on fs & release (which can influence fs used). Yes you can re-install, I'd suggest with 'something else' & select your existing partitions. It'll erase your system directories (not $HOME) keeping as much as possible.

– guiverc
Feb 8 at 1:56













I had a response all typed up but it was “too big“, and I don’t have time to deal with this right now, i’ll have to come back to this in a couple of days. It was the very latest version, not the version with the lifetime support.

– Jonny Vee
Feb 9 at 2:21







I had a response all typed up but it was “too big“, and I don’t have time to deal with this right now, i’ll have to come back to this in a couple of days. It was the very latest version, not the version with the lifetime support.

– Jonny Vee
Feb 9 at 2:21












0






active

oldest

votes











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%2f1116549%2fjust-started-using-ubuntu-again-i-had-a-major-crash%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















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%2f1116549%2fjust-started-using-ubuntu-again-i-had-a-major-crash%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

flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

Mangá

 ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕