Ubuntu starts in BusyBox v1.21.1 and built in shell, help!
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I'm new in this community and I really need help. I decided to start my computer as usual, got my hard drive divide in two, one part for Ubuntu and the other one for Windows.
I chose the Ubuntu option during the boot, but instead of starting with the usual Desktop, it appears completely black, with the BusyBox v1.21.1 built in shell terminal. Excuse my ignorance, but, is there a way I can recover my Desktop and all my files? 'Cause I don't have the Ubuntu CD with me, and don't even have time.
Thank you so much.
kubuntu
asked Mar 30 at 2:26
AruzabAruzab
11
|
show 2 more comments
I'm new in this community and I really need help. I decided to start my computer as usual, got my hard drive divide in two, one part for Ubuntu and the other one for Windows.
I chose the Ubuntu option during the boot, but instead of starting with the usual Desktop, it appears completely black, with the BusyBox v1.21.1 built in shell terminal. Excuse my ignorance, but, is there a way I can recover my Desktop and all my files? 'Cause I don't have the Ubuntu CD with me, and don't even have time.
Thank you so much.
kubuntu
asked Mar 30 at 2:26
AruzabAruzab
11
What are (or were) you running? Ubuntu 14.04 LTS looks like it used BusyBox 1.21.0 (packages.ubuntu.com/search?keywords=busybox) though this may be helpful - askubuntu.com/questions/137655/… (most of these answers imply afsckis needed & install media is the fastest fix)
– guiverc
Mar 30 at 2:46
Yes, I'm running Ubuntu 14.04 LTS, sorry for not mentioning it. Thanks for the info, I'll check it and see If it fixes the situation.
– Aruzab
Mar 30 at 2:53
For what I've read, I should be able to use the command exit or have the CD, but whenever I introduce exit, it just shows an error. Really need help.
– Aruzab
Mar 30 at 3:14
If you have a 'dirty` fs (filesystem), this must be fixed first (fsck=file system check; it'll do nothing if no errors, but will fix detected errors & if this is your issue, your system will boot after this). If your fs is mounted; you can't fsck it (with minor exceptions), which is why install-media (or a 'live' environment) is the quick fix. You boot the 'live' (install media) and your fs won't be in use, so can be checked (fsck) without issues, then you'll likely find it boots correctly.
– guiverc
Mar 30 at 3:31
I tried and it only shows "system: not found" :/
– Aruzab
Mar 30 at 4:37
|
show 2 more comments
I'm new in this community and I really need help. I decided to start my computer as usual, got my hard drive divide in two, one part for Ubuntu and the other one for Windows.
I chose the Ubuntu option during the boot, but instead of starting with the usual Desktop, it appears completely black, with the BusyBox v1.21.1 built in shell terminal. Excuse my ignorance, but, is there a way I can recover my Desktop and all my files? 'Cause I don't have the Ubuntu CD with me, and don't even have time.
Thank you so much.
kubuntu
asked Mar 30 at 2:26
AruzabAruzab
11
I'm new in this community and I really need help. I decided to start my computer as usual, got my hard drive divide in two, one part for Ubuntu and the other one for Windows.
I chose the Ubuntu option during the boot, but instead of starting with the usual Desktop, it appears completely black, with the BusyBox v1.21.1 built in shell terminal. Excuse my ignorance, but, is there a way I can recover my Desktop and all my files? 'Cause I don't have the Ubuntu CD with me, and don't even have time.
Thank you so much.
kubuntu
kubuntu
asked Mar 30 at 2:26
AruzabAruzab
11
asked Mar 30 at 2:26
AruzabAruzab
11
edited Mar 30 at 2:34
Aruzab
asked Mar 30 at 2:26
AruzabAruzab
11
asked Mar 30 at 2:26
AruzabAruzab
11
asked Mar 30 at 2:26
AruzabAruzab
11
11
What are (or were) you running? Ubuntu 14.04 LTS looks like it used BusyBox 1.21.0 (packages.ubuntu.com/search?keywords=busybox) though this may be helpful - askubuntu.com/questions/137655/… (most of these answers imply afsckis needed & install media is the fastest fix)
– guiverc
Mar 30 at 2:46
Yes, I'm running Ubuntu 14.04 LTS, sorry for not mentioning it. Thanks for the info, I'll check it and see If it fixes the situation.
– Aruzab
Mar 30 at 2:53
For what I've read, I should be able to use the command exit or have the CD, but whenever I introduce exit, it just shows an error. Really need help.
– Aruzab
Mar 30 at 3:14
If you have a 'dirty` fs (filesystem), this must be fixed first (fsck=file system check; it'll do nothing if no errors, but will fix detected errors & if this is your issue, your system will boot after this). If your fs is mounted; you can't fsck it (with minor exceptions), which is why install-media (or a 'live' environment) is the quick fix. You boot the 'live' (install media) and your fs won't be in use, so can be checked (fsck) without issues, then you'll likely find it boots correctly.
– guiverc
Mar 30 at 3:31
I tried and it only shows "system: not found" :/
– Aruzab
Mar 30 at 4:37
|
show 2 more comments
What are (or were) you running? Ubuntu 14.04 LTS looks like it used BusyBox 1.21.0 (packages.ubuntu.com/search?keywords=busybox) though this may be helpful - askubuntu.com/questions/137655/… (most of these answers imply afsckis needed & install media is the fastest fix)
– guiverc
Mar 30 at 2:46
Yes, I'm running Ubuntu 14.04 LTS, sorry for not mentioning it. Thanks for the info, I'll check it and see If it fixes the situation.
– Aruzab
Mar 30 at 2:53
For what I've read, I should be able to use the command exit or have the CD, but whenever I introduce exit, it just shows an error. Really need help.
– Aruzab
Mar 30 at 3:14
If you have a 'dirty` fs (filesystem), this must be fixed first (fsck=file system check; it'll do nothing if no errors, but will fix detected errors & if this is your issue, your system will boot after this). If your fs is mounted; you can't fsck it (with minor exceptions), which is why install-media (or a 'live' environment) is the quick fix. You boot the 'live' (install media) and your fs won't be in use, so can be checked (fsck) without issues, then you'll likely find it boots correctly.
– guiverc
Mar 30 at 3:31
I tried and it only shows "system: not found" :/
– Aruzab
Mar 30 at 4:37
What are (or were) you running? Ubuntu 14.04 LTS looks like it used BusyBox 1.21.0 (packages.ubuntu.com/search?keywords=busybox) though this may be helpful - askubuntu.com/questions/137655/… (most of these answers imply a
fsck is needed & install media is the fastest fix)– guiverc
Mar 30 at 2:46
What are (or were) you running? Ubuntu 14.04 LTS looks like it used BusyBox 1.21.0 (packages.ubuntu.com/search?keywords=busybox) though this may be helpful - askubuntu.com/questions/137655/… (most of these answers imply a
fsck is needed & install media is the fastest fix)– guiverc
Mar 30 at 2:46
Yes, I'm running Ubuntu 14.04 LTS, sorry for not mentioning it. Thanks for the info, I'll check it and see If it fixes the situation.
– Aruzab
Mar 30 at 2:53
Yes, I'm running Ubuntu 14.04 LTS, sorry for not mentioning it. Thanks for the info, I'll check it and see If it fixes the situation.
– Aruzab
Mar 30 at 2:53
For what I've read, I should be able to use the command exit or have the CD, but whenever I introduce exit, it just shows an error. Really need help.
– Aruzab
Mar 30 at 3:14
For what I've read, I should be able to use the command exit or have the CD, but whenever I introduce exit, it just shows an error. Really need help.
– Aruzab
Mar 30 at 3:14
If you have a 'dirty` fs (filesystem), this must be fixed first (fsck=file system check; it'll do nothing if no errors, but will fix detected errors & if this is your issue, your system will boot after this). If your fs is mounted; you can't fsck it (with minor exceptions), which is why install-media (or a 'live' environment) is the quick fix. You boot the 'live' (install media) and your fs won't be in use, so can be checked (
fsck) without issues, then you'll likely find it boots correctly.– guiverc
Mar 30 at 3:31
If you have a 'dirty` fs (filesystem), this must be fixed first (fsck=file system check; it'll do nothing if no errors, but will fix detected errors & if this is your issue, your system will boot after this). If your fs is mounted; you can't fsck it (with minor exceptions), which is why install-media (or a 'live' environment) is the quick fix. You boot the 'live' (install media) and your fs won't be in use, so can be checked (
fsck) without issues, then you'll likely find it boots correctly.– guiverc
Mar 30 at 3:31
I tried and it only shows "system: not found" :/
– Aruzab
Mar 30 at 4:37
I tried and it only shows "system: not found" :/
– Aruzab
Mar 30 at 4:37
|
show 2 more comments
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1129826%2fubuntu-starts-in-busybox-v1-21-1-and-built-in-shell-help%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
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1129826%2fubuntu-starts-in-busybox-v1-21-1-and-built-in-shell-help%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
What are (or were) you running? Ubuntu 14.04 LTS looks like it used BusyBox 1.21.0 (packages.ubuntu.com/search?keywords=busybox) though this may be helpful - askubuntu.com/questions/137655/… (most of these answers imply a
fsckis needed & install media is the fastest fix)– guiverc
Mar 30 at 2:46
Yes, I'm running Ubuntu 14.04 LTS, sorry for not mentioning it. Thanks for the info, I'll check it and see If it fixes the situation.
– Aruzab
Mar 30 at 2:53
For what I've read, I should be able to use the command exit or have the CD, but whenever I introduce exit, it just shows an error. Really need help.
– Aruzab
Mar 30 at 3:14
If you have a 'dirty` fs (filesystem), this must be fixed first (fsck=file system check; it'll do nothing if no errors, but will fix detected errors & if this is your issue, your system will boot after this). If your fs is mounted; you can't fsck it (with minor exceptions), which is why install-media (or a 'live' environment) is the quick fix. You boot the 'live' (install media) and your fs won't be in use, so can be checked (
fsck) without issues, then you'll likely find it boots correctly.– guiverc
Mar 30 at 3:31
I tried and it only shows "system: not found" :/
– Aruzab
Mar 30 at 4:37