I encountered the print_req_error while trying to open Ubuntu 16.04 on my dual booted HP laptop
So I have an HP Pavilion 15au627tx laptop and I had been using Ubuntu 16.04 for about 6 months before I first encountered this problem. Once when I logged in last November, everything was in a read only mode and I freaked out but nothing I tried seemed to work. I shut down my computer and Ubuntu never seemed to open, I seemed to get the BusyBox error. However as I had very little time to focus on that, I used Windows which worked perfectly fine. However, now that I have been trying to fix it, nothing seems to work. I tried fixing it but nothing seemed to work and eached time I went onto Ubuntu I got a huge list of corrupted sectors which made no sense to me. I finally decided to backup my data from Windows and decided to wipe the Ubuntu partition, and tried reinstalling. I installed it alongside windows using the same partition as before. However it didn't work and each time I've tried to log in, this thing comes on the screen. I'm really confused about this as I don't know what this means. All questions seemingly related to this state that my hard disk is dying. However, I've been working with Windows to do class work and it seems perfectly fine. How do I fix this? Do I replace the hard disk (I have an extended warranty on my laptop)? Is there any other way to fix it without any such drastic measures. Here's a screenshot if you want to know what I see https://i.imgur.com/umxENKJ.jpg
Also, it may or may not be relevant but I had to reinstall Ubuntu 16.04 twice before. Once when I downgraded from 18.04 to 16.04 and then the OS didnt work , reinstall Ubuntu 16.04 once again and things seemed perfectly fine. In case you want to know who the hard drive manufacturer is, let me know.
16.04 dual-boot hard-drive busybox
asked Jan 9 at 14:50
anshuman_kmranshuman_kmr
167
add a comment |
So I have an HP Pavilion 15au627tx laptop and I had been using Ubuntu 16.04 for about 6 months before I first encountered this problem. Once when I logged in last November, everything was in a read only mode and I freaked out but nothing I tried seemed to work. I shut down my computer and Ubuntu never seemed to open, I seemed to get the BusyBox error. However as I had very little time to focus on that, I used Windows which worked perfectly fine. However, now that I have been trying to fix it, nothing seems to work. I tried fixing it but nothing seemed to work and eached time I went onto Ubuntu I got a huge list of corrupted sectors which made no sense to me. I finally decided to backup my data from Windows and decided to wipe the Ubuntu partition, and tried reinstalling. I installed it alongside windows using the same partition as before. However it didn't work and each time I've tried to log in, this thing comes on the screen. I'm really confused about this as I don't know what this means. All questions seemingly related to this state that my hard disk is dying. However, I've been working with Windows to do class work and it seems perfectly fine. How do I fix this? Do I replace the hard disk (I have an extended warranty on my laptop)? Is there any other way to fix it without any such drastic measures. Here's a screenshot if you want to know what I see https://i.imgur.com/umxENKJ.jpg
Also, it may or may not be relevant but I had to reinstall Ubuntu 16.04 twice before. Once when I downgraded from 18.04 to 16.04 and then the OS didnt work , reinstall Ubuntu 16.04 once again and things seemed perfectly fine. In case you want to know who the hard drive manufacturer is, let me know.
16.04 dual-boot hard-drive busybox
asked Jan 9 at 14:50
anshuman_kmranshuman_kmr
167
add a comment |
So I have an HP Pavilion 15au627tx laptop and I had been using Ubuntu 16.04 for about 6 months before I first encountered this problem. Once when I logged in last November, everything was in a read only mode and I freaked out but nothing I tried seemed to work. I shut down my computer and Ubuntu never seemed to open, I seemed to get the BusyBox error. However as I had very little time to focus on that, I used Windows which worked perfectly fine. However, now that I have been trying to fix it, nothing seems to work. I tried fixing it but nothing seemed to work and eached time I went onto Ubuntu I got a huge list of corrupted sectors which made no sense to me. I finally decided to backup my data from Windows and decided to wipe the Ubuntu partition, and tried reinstalling. I installed it alongside windows using the same partition as before. However it didn't work and each time I've tried to log in, this thing comes on the screen. I'm really confused about this as I don't know what this means. All questions seemingly related to this state that my hard disk is dying. However, I've been working with Windows to do class work and it seems perfectly fine. How do I fix this? Do I replace the hard disk (I have an extended warranty on my laptop)? Is there any other way to fix it without any such drastic measures. Here's a screenshot if you want to know what I see https://i.imgur.com/umxENKJ.jpg
Also, it may or may not be relevant but I had to reinstall Ubuntu 16.04 twice before. Once when I downgraded from 18.04 to 16.04 and then the OS didnt work , reinstall Ubuntu 16.04 once again and things seemed perfectly fine. In case you want to know who the hard drive manufacturer is, let me know.
16.04 dual-boot hard-drive busybox
asked Jan 9 at 14:50
anshuman_kmranshuman_kmr
167
So I have an HP Pavilion 15au627tx laptop and I had been using Ubuntu 16.04 for about 6 months before I first encountered this problem. Once when I logged in last November, everything was in a read only mode and I freaked out but nothing I tried seemed to work. I shut down my computer and Ubuntu never seemed to open, I seemed to get the BusyBox error. However as I had very little time to focus on that, I used Windows which worked perfectly fine. However, now that I have been trying to fix it, nothing seems to work. I tried fixing it but nothing seemed to work and eached time I went onto Ubuntu I got a huge list of corrupted sectors which made no sense to me. I finally decided to backup my data from Windows and decided to wipe the Ubuntu partition, and tried reinstalling. I installed it alongside windows using the same partition as before. However it didn't work and each time I've tried to log in, this thing comes on the screen. I'm really confused about this as I don't know what this means. All questions seemingly related to this state that my hard disk is dying. However, I've been working with Windows to do class work and it seems perfectly fine. How do I fix this? Do I replace the hard disk (I have an extended warranty on my laptop)? Is there any other way to fix it without any such drastic measures. Here's a screenshot if you want to know what I see https://i.imgur.com/umxENKJ.jpg
Also, it may or may not be relevant but I had to reinstall Ubuntu 16.04 twice before. Once when I downgraded from 18.04 to 16.04 and then the OS didnt work , reinstall Ubuntu 16.04 once again and things seemed perfectly fine. In case you want to know who the hard drive manufacturer is, let me know.
16.04 dual-boot hard-drive busybox
16.04 dual-boot hard-drive busybox
asked Jan 9 at 14:50
anshuman_kmranshuman_kmr
167
asked Jan 9 at 14:50
anshuman_kmranshuman_kmr
167
asked Jan 9 at 14:50
anshuman_kmranshuman_kmr
167
asked Jan 9 at 14:50
anshuman_kmranshuman_kmr
167
asked Jan 9 at 14:50
anshuman_kmranshuman_kmr
167
167
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Considering no one answered this, I would just like to add that reinstalling it does the trick. I tried 18.04 once again and it seems fine.
answered Jan 22 at 22:48
anshuman_kmranshuman_kmr
167
add a comment |
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%2f1108310%2fi-encountered-the-print-req-error-while-trying-to-open-ubuntu-16-04-on-my-dual-b%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
Considering no one answered this, I would just like to add that reinstalling it does the trick. I tried 18.04 once again and it seems fine.
answered Jan 22 at 22:48
anshuman_kmranshuman_kmr
167
add a comment |
Considering no one answered this, I would just like to add that reinstalling it does the trick. I tried 18.04 once again and it seems fine.
answered Jan 22 at 22:48
anshuman_kmranshuman_kmr
167
add a comment |
Considering no one answered this, I would just like to add that reinstalling it does the trick. I tried 18.04 once again and it seems fine.
answered Jan 22 at 22:48
anshuman_kmranshuman_kmr
167
Considering no one answered this, I would just like to add that reinstalling it does the trick. I tried 18.04 once again and it seems fine.
answered Jan 22 at 22:48
anshuman_kmranshuman_kmr
167
answered Jan 22 at 22:48
anshuman_kmranshuman_kmr
167
answered Jan 22 at 22:48
anshuman_kmranshuman_kmr
167
answered Jan 22 at 22:48
anshuman_kmranshuman_kmr
167
167
add a comment |
add a comment |
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%2f1108310%2fi-encountered-the-print-req-error-while-trying-to-open-ubuntu-16-04-on-my-dual-b%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
