unable to boot ubuntu 16.04 after using win 7
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I have a problem trying to boot Ubuntu 16.04.
I have 2 hard disk drives. One contains Windows 7 and the other contains Ubuntu 16.04.
I had to swap to the win drive to use a piece of hardware I purchased, I unplugged the Ubuntu drive and plug in the win drive. All OK so far, I then went back and used the Ubuntu drive, all 'seems' OK boots, runs programs, then suddenly stopped working completely. Reboot and go into bios settings, the hard drive does not show. I only have the option of using the CD drive and use Ubuntu without installing, this is to prevent the loss of all my programs and data. Without the CD in the drive, the fault is "no media, insert media drive and press a key."
Did anyone face this situation?
If you know how to fix this I would like to hear from you please.
Regards, Rod
boot grub2
edited Feb 7 at 10:25
singrium
1,276524
asked Feb 7 at 10:15
Rodney JacksonRodney Jackson
105
add a comment |
I have a problem trying to boot Ubuntu 16.04.
I have 2 hard disk drives. One contains Windows 7 and the other contains Ubuntu 16.04.
I had to swap to the win drive to use a piece of hardware I purchased, I unplugged the Ubuntu drive and plug in the win drive. All OK so far, I then went back and used the Ubuntu drive, all 'seems' OK boots, runs programs, then suddenly stopped working completely. Reboot and go into bios settings, the hard drive does not show. I only have the option of using the CD drive and use Ubuntu without installing, this is to prevent the loss of all my programs and data. Without the CD in the drive, the fault is "no media, insert media drive and press a key."
Did anyone face this situation?
If you know how to fix this I would like to hear from you please.
Regards, Rod
boot grub2
edited Feb 7 at 10:25
singrium
1,276524
asked Feb 7 at 10:15
Rodney JacksonRodney Jackson
105
I don't know your issue, but if was me, I'd boot your Ubuntu install/live media, and view your SMART data on the iffy drive. Thesmartctl(or gnome-disks or whichever tool you use to view SMART data from the drive) will show you the health of your drive from data stored on it's chips. I would rule out a failing drive before I explore the next possible cause... (if the case is easily opened; I'd also consider a cap-check or quick scan of your motherboard, check the voltage of your CMOS battery in case it's close to dead (3V or less) and thus causing you issues)
– guiverc
Feb 7 at 10:29
Thank you for your input singrium, I looked carefully at all the electro caps, none appeared to be stressed. I also tested the CMOS battery, this gave me an "AHA" moment, it was 2.92V. Quickly removed the battery and purchased a new CR2032 hoping this might be the answer. Sorry, still the same problem. This however has saved another failure in the near future. The system voltages all show correctly within .03 volts worst case. Hope there are others with more info on this problem. Regards, Rod
– Rodney Jackson
Feb 8 at 3:15
add a comment |
I have a problem trying to boot Ubuntu 16.04.
I have 2 hard disk drives. One contains Windows 7 and the other contains Ubuntu 16.04.
I had to swap to the win drive to use a piece of hardware I purchased, I unplugged the Ubuntu drive and plug in the win drive. All OK so far, I then went back and used the Ubuntu drive, all 'seems' OK boots, runs programs, then suddenly stopped working completely. Reboot and go into bios settings, the hard drive does not show. I only have the option of using the CD drive and use Ubuntu without installing, this is to prevent the loss of all my programs and data. Without the CD in the drive, the fault is "no media, insert media drive and press a key."
Did anyone face this situation?
If you know how to fix this I would like to hear from you please.
Regards, Rod
boot grub2
edited Feb 7 at 10:25
singrium
1,276524
asked Feb 7 at 10:15
Rodney JacksonRodney Jackson
105
I have a problem trying to boot Ubuntu 16.04.
I have 2 hard disk drives. One contains Windows 7 and the other contains Ubuntu 16.04.
I had to swap to the win drive to use a piece of hardware I purchased, I unplugged the Ubuntu drive and plug in the win drive. All OK so far, I then went back and used the Ubuntu drive, all 'seems' OK boots, runs programs, then suddenly stopped working completely. Reboot and go into bios settings, the hard drive does not show. I only have the option of using the CD drive and use Ubuntu without installing, this is to prevent the loss of all my programs and data. Without the CD in the drive, the fault is "no media, insert media drive and press a key."
Did anyone face this situation?
If you know how to fix this I would like to hear from you please.
Regards, Rod
boot grub2
boot grub2
edited Feb 7 at 10:25
singrium
1,276524
asked Feb 7 at 10:15
Rodney JacksonRodney Jackson
105
edited Feb 7 at 10:25
singrium
1,276524
asked Feb 7 at 10:15
Rodney JacksonRodney Jackson
105
edited Feb 7 at 10:25
singrium
1,276524
edited Feb 7 at 10:25
singrium
1,276524
edited Feb 7 at 10:25
singrium
1,276524
1,276524
asked Feb 7 at 10:15
Rodney JacksonRodney Jackson
105
asked Feb 7 at 10:15
Rodney JacksonRodney Jackson
105
asked Feb 7 at 10:15
Rodney JacksonRodney Jackson
105
105
I don't know your issue, but if was me, I'd boot your Ubuntu install/live media, and view your SMART data on the iffy drive. Thesmartctl(or gnome-disks or whichever tool you use to view SMART data from the drive) will show you the health of your drive from data stored on it's chips. I would rule out a failing drive before I explore the next possible cause... (if the case is easily opened; I'd also consider a cap-check or quick scan of your motherboard, check the voltage of your CMOS battery in case it's close to dead (3V or less) and thus causing you issues)
– guiverc
Feb 7 at 10:29
Thank you for your input singrium, I looked carefully at all the electro caps, none appeared to be stressed. I also tested the CMOS battery, this gave me an "AHA" moment, it was 2.92V. Quickly removed the battery and purchased a new CR2032 hoping this might be the answer. Sorry, still the same problem. This however has saved another failure in the near future. The system voltages all show correctly within .03 volts worst case. Hope there are others with more info on this problem. Regards, Rod
– Rodney Jackson
Feb 8 at 3:15
add a comment |
I don't know your issue, but if was me, I'd boot your Ubuntu install/live media, and view your SMART data on the iffy drive. Thesmartctl(or gnome-disks or whichever tool you use to view SMART data from the drive) will show you the health of your drive from data stored on it's chips. I would rule out a failing drive before I explore the next possible cause... (if the case is easily opened; I'd also consider a cap-check or quick scan of your motherboard, check the voltage of your CMOS battery in case it's close to dead (3V or less) and thus causing you issues)
– guiverc
Feb 7 at 10:29
Thank you for your input singrium, I looked carefully at all the electro caps, none appeared to be stressed. I also tested the CMOS battery, this gave me an "AHA" moment, it was 2.92V. Quickly removed the battery and purchased a new CR2032 hoping this might be the answer. Sorry, still the same problem. This however has saved another failure in the near future. The system voltages all show correctly within .03 volts worst case. Hope there are others with more info on this problem. Regards, Rod
– Rodney Jackson
Feb 8 at 3:15
I don't know your issue, but if was me, I'd boot your Ubuntu install/live media, and view your SMART data on the iffy drive. The
smartctl (or gnome-disks or whichever tool you use to view SMART data from the drive) will show you the health of your drive from data stored on it's chips. I would rule out a failing drive before I explore the next possible cause... (if the case is easily opened; I'd also consider a cap-check or quick scan of your motherboard, check the voltage of your CMOS battery in case it's close to dead (3V or less) and thus causing you issues)– guiverc
Feb 7 at 10:29
I don't know your issue, but if was me, I'd boot your Ubuntu install/live media, and view your SMART data on the iffy drive. The
smartctl (or gnome-disks or whichever tool you use to view SMART data from the drive) will show you the health of your drive from data stored on it's chips. I would rule out a failing drive before I explore the next possible cause... (if the case is easily opened; I'd also consider a cap-check or quick scan of your motherboard, check the voltage of your CMOS battery in case it's close to dead (3V or less) and thus causing you issues)– guiverc
Feb 7 at 10:29
Thank you for your input singrium, I looked carefully at all the electro caps, none appeared to be stressed. I also tested the CMOS battery, this gave me an "AHA" moment, it was 2.92V. Quickly removed the battery and purchased a new CR2032 hoping this might be the answer. Sorry, still the same problem. This however has saved another failure in the near future. The system voltages all show correctly within .03 volts worst case. Hope there are others with more info on this problem. Regards, Rod
– Rodney Jackson
Feb 8 at 3:15
Thank you for your input singrium, I looked carefully at all the electro caps, none appeared to be stressed. I also tested the CMOS battery, this gave me an "AHA" moment, it was 2.92V. Quickly removed the battery and purchased a new CR2032 hoping this might be the answer. Sorry, still the same problem. This however has saved another failure in the near future. The system voltages all show correctly within .03 volts worst case. Hope there are others with more info on this problem. Regards, Rod
– Rodney Jackson
Feb 8 at 3:15
add a comment |
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%2f1116353%2funable-to-boot-ubuntu-16-04-after-using-win-7%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%2f1116353%2funable-to-boot-ubuntu-16-04-after-using-win-7%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
I don't know your issue, but if was me, I'd boot your Ubuntu install/live media, and view your SMART data on the iffy drive. The
smartctl(or gnome-disks or whichever tool you use to view SMART data from the drive) will show you the health of your drive from data stored on it's chips. I would rule out a failing drive before I explore the next possible cause... (if the case is easily opened; I'd also consider a cap-check or quick scan of your motherboard, check the voltage of your CMOS battery in case it's close to dead (3V or less) and thus causing you issues)– guiverc
Feb 7 at 10:29
Thank you for your input singrium, I looked carefully at all the electro caps, none appeared to be stressed. I also tested the CMOS battery, this gave me an "AHA" moment, it was 2.92V. Quickly removed the battery and purchased a new CR2032 hoping this might be the answer. Sorry, still the same problem. This however has saved another failure in the near future. The system voltages all show correctly within .03 volts worst case. Hope there are others with more info on this problem. Regards, Rod
– Rodney Jackson
Feb 8 at 3:15