No symbol table. Press any key to continue
Whenever I boot Ubuntu 16.10, just before the Plymouth screen, I'm seeing this message:
No symbol table found.
Press any key to continue...
and it remains there for a minute or so before showing me the log in screen. If I press any key it will be stuck for ever and I'll have to restart the computer.
Any help is appreciated..
login-screen 16.10
asked Oct 14 '16 at 14:50
Ron
14.4k43957
add a comment |
Whenever I boot Ubuntu 16.10, just before the Plymouth screen, I'm seeing this message:
No symbol table found.
Press any key to continue...
and it remains there for a minute or so before showing me the log in screen. If I press any key it will be stuck for ever and I'll have to restart the computer.
Any help is appreciated..
login-screen 16.10
asked Oct 14 '16 at 14:50
Ron
14.4k43957
2
See also Bug #1633839 “No symbol table. Press any key to continue” : Bugs : linux package : Ubuntu
– wilx
Nov 6 '16 at 20:00
Found my particular problem in a Kubuntu forum in which a user reported his error--which I had repeated. He'd forgotten which of several hard drives he'd installed on. I followed the fdisk step here, but jumped at the indication which confirmed the drive I already had in my head. However, by the time I found my mistake, which I cannot confirm now, I had started a Hardcore Reinstall from DVD... Double-check the grub install if this you're seeing this error.
– quagmire
Sep 25 '18 at 22:55
add a comment |
Whenever I boot Ubuntu 16.10, just before the Plymouth screen, I'm seeing this message:
No symbol table found.
Press any key to continue...
and it remains there for a minute or so before showing me the log in screen. If I press any key it will be stuck for ever and I'll have to restart the computer.
Any help is appreciated..
login-screen 16.10
asked Oct 14 '16 at 14:50
Ron
14.4k43957
Whenever I boot Ubuntu 16.10, just before the Plymouth screen, I'm seeing this message:
No symbol table found.
Press any key to continue...
and it remains there for a minute or so before showing me the log in screen. If I press any key it will be stuck for ever and I'll have to restart the computer.
Any help is appreciated..
login-screen 16.10
login-screen 16.10
asked Oct 14 '16 at 14:50
Ron
14.4k43957
asked Oct 14 '16 at 14:50
Ron
14.4k43957
asked Oct 14 '16 at 14:50
Ron
14.4k43957
asked Oct 14 '16 at 14:50
Ron
14.4k43957
asked Oct 14 '16 at 14:50
Ron
14.4k43957
14.4k43957
2
See also Bug #1633839 “No symbol table. Press any key to continue” : Bugs : linux package : Ubuntu
– wilx
Nov 6 '16 at 20:00
Found my particular problem in a Kubuntu forum in which a user reported his error--which I had repeated. He'd forgotten which of several hard drives he'd installed on. I followed the fdisk step here, but jumped at the indication which confirmed the drive I already had in my head. However, by the time I found my mistake, which I cannot confirm now, I had started a Hardcore Reinstall from DVD... Double-check the grub install if this you're seeing this error.
– quagmire
Sep 25 '18 at 22:55
add a comment |
2
See also Bug #1633839 “No symbol table. Press any key to continue” : Bugs : linux package : Ubuntu
– wilx
Nov 6 '16 at 20:00
Found my particular problem in a Kubuntu forum in which a user reported his error--which I had repeated. He'd forgotten which of several hard drives he'd installed on. I followed the fdisk step here, but jumped at the indication which confirmed the drive I already had in my head. However, by the time I found my mistake, which I cannot confirm now, I had started a Hardcore Reinstall from DVD... Double-check the grub install if this you're seeing this error.
– quagmire
Sep 25 '18 at 22:55
2
2
See also Bug #1633839 “No symbol table. Press any key to continue” : Bugs : linux package : Ubuntu
– wilx
Nov 6 '16 at 20:00
See also Bug #1633839 “No symbol table. Press any key to continue” : Bugs : linux package : Ubuntu
– wilx
Nov 6 '16 at 20:00
Found my particular problem in a Kubuntu forum in which a user reported his error--which I had repeated. He'd forgotten which of several hard drives he'd installed on. I followed the fdisk step here, but jumped at the indication which confirmed the drive I already had in my head. However, by the time I found my mistake, which I cannot confirm now, I had started a Hardcore Reinstall from DVD... Double-check the grub install if this you're seeing this error.
– quagmire
Sep 25 '18 at 22:55
Found my particular problem in a Kubuntu forum in which a user reported his error--which I had repeated. He'd forgotten which of several hard drives he'd installed on. I followed the fdisk step here, but jumped at the indication which confirmed the drive I already had in my head. However, by the time I found my mistake, which I cannot confirm now, I had started a Hardcore Reinstall from DVD... Double-check the grub install if this you're seeing this error.
– quagmire
Sep 25 '18 at 22:55
add a comment |
1 Answer
1
active
oldest
votes
Try this one, first from USB/Live CD (if you can't access Ubuntu from HDD), and then, or directly from your "HDD OS":
sudo fdisk -l
This will list all partitions on your HDD. Find under the Type section your root partition labelled Ubuntu or Linux and its Device (like /dev/sda).
Then, do
sudo grub-install /dev/sdX
Where sdX is the device you found with fdisk. Note that you install GRUB to a drive, not a partition, so sda would be correct while sda1 would be incorrect.
Finally, run
sudo update-grub
sudo reboot
edited Sep 16 '18 at 18:51
Zanna
50k13131239
answered Apr 27 '17 at 8:58
Rafael SoWhat
11114
5
I got this on an update from 16.04 LTS to 18.04 LTS; the steps you outlined eliminated the problem. Thanks!
– Alex
May 26 '18 at 20:21
This also fixed one of my issues on updating to 18.04. Thanks
– aocall
Jun 15 '18 at 19:26
Also had 18.04 upgrade problem. This didn't work for me, I ended up re-installing 18.04 over the old install.
– dfrankow
Jul 7 '18 at 4:33
1
Doesn't work for me in 18.04 (upgraded from 16.04). As it seems to work after I press any key, I'm not going to do a clean install. But a solution would be nice!
– James Bradbury
Oct 8 '18 at 20:00
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%2f837035%2fno-symbol-table-press-any-key-to-continue%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
Try this one, first from USB/Live CD (if you can't access Ubuntu from HDD), and then, or directly from your "HDD OS":
sudo fdisk -l
This will list all partitions on your HDD. Find under the Type section your root partition labelled Ubuntu or Linux and its Device (like /dev/sda).
Then, do
sudo grub-install /dev/sdX
Where sdX is the device you found with fdisk. Note that you install GRUB to a drive, not a partition, so sda would be correct while sda1 would be incorrect.
Finally, run
sudo update-grub
sudo reboot
edited Sep 16 '18 at 18:51
Zanna
50k13131239
answered Apr 27 '17 at 8:58
Rafael SoWhat
11114
5
I got this on an update from 16.04 LTS to 18.04 LTS; the steps you outlined eliminated the problem. Thanks!
– Alex
May 26 '18 at 20:21
This also fixed one of my issues on updating to 18.04. Thanks
– aocall
Jun 15 '18 at 19:26
Also had 18.04 upgrade problem. This didn't work for me, I ended up re-installing 18.04 over the old install.
– dfrankow
Jul 7 '18 at 4:33
1
Doesn't work for me in 18.04 (upgraded from 16.04). As it seems to work after I press any key, I'm not going to do a clean install. But a solution would be nice!
– James Bradbury
Oct 8 '18 at 20:00
add a comment |
Try this one, first from USB/Live CD (if you can't access Ubuntu from HDD), and then, or directly from your "HDD OS":
sudo fdisk -l
This will list all partitions on your HDD. Find under the Type section your root partition labelled Ubuntu or Linux and its Device (like /dev/sda).
Then, do
sudo grub-install /dev/sdX
Where sdX is the device you found with fdisk. Note that you install GRUB to a drive, not a partition, so sda would be correct while sda1 would be incorrect.
Finally, run
sudo update-grub
sudo reboot
edited Sep 16 '18 at 18:51
Zanna
50k13131239
answered Apr 27 '17 at 8:58
Rafael SoWhat
11114
5
I got this on an update from 16.04 LTS to 18.04 LTS; the steps you outlined eliminated the problem. Thanks!
– Alex
May 26 '18 at 20:21
This also fixed one of my issues on updating to 18.04. Thanks
– aocall
Jun 15 '18 at 19:26
Also had 18.04 upgrade problem. This didn't work for me, I ended up re-installing 18.04 over the old install.
– dfrankow
Jul 7 '18 at 4:33
1
Doesn't work for me in 18.04 (upgraded from 16.04). As it seems to work after I press any key, I'm not going to do a clean install. But a solution would be nice!
– James Bradbury
Oct 8 '18 at 20:00
add a comment |
Try this one, first from USB/Live CD (if you can't access Ubuntu from HDD), and then, or directly from your "HDD OS":
sudo fdisk -l
This will list all partitions on your HDD. Find under the Type section your root partition labelled Ubuntu or Linux and its Device (like /dev/sda).
Then, do
sudo grub-install /dev/sdX
Where sdX is the device you found with fdisk. Note that you install GRUB to a drive, not a partition, so sda would be correct while sda1 would be incorrect.
Finally, run
sudo update-grub
sudo reboot
edited Sep 16 '18 at 18:51
Zanna
50k13131239
answered Apr 27 '17 at 8:58
Rafael SoWhat
11114
Try this one, first from USB/Live CD (if you can't access Ubuntu from HDD), and then, or directly from your "HDD OS":
sudo fdisk -l
This will list all partitions on your HDD. Find under the Type section your root partition labelled Ubuntu or Linux and its Device (like /dev/sda).
Then, do
sudo grub-install /dev/sdX
Where sdX is the device you found with fdisk. Note that you install GRUB to a drive, not a partition, so sda would be correct while sda1 would be incorrect.
Finally, run
sudo update-grub
sudo reboot
edited Sep 16 '18 at 18:51
Zanna
50k13131239
answered Apr 27 '17 at 8:58
Rafael SoWhat
11114
edited Sep 16 '18 at 18:51
Zanna
50k13131239
edited Sep 16 '18 at 18:51
Zanna
50k13131239
edited Sep 16 '18 at 18:51
Zanna
50k13131239
50k13131239
answered Apr 27 '17 at 8:58
Rafael SoWhat
11114
answered Apr 27 '17 at 8:58
Rafael SoWhat
11114
answered Apr 27 '17 at 8:58
Rafael SoWhat
11114
11114
5
I got this on an update from 16.04 LTS to 18.04 LTS; the steps you outlined eliminated the problem. Thanks!
– Alex
May 26 '18 at 20:21
This also fixed one of my issues on updating to 18.04. Thanks
– aocall
Jun 15 '18 at 19:26
Also had 18.04 upgrade problem. This didn't work for me, I ended up re-installing 18.04 over the old install.
– dfrankow
Jul 7 '18 at 4:33
1
Doesn't work for me in 18.04 (upgraded from 16.04). As it seems to work after I press any key, I'm not going to do a clean install. But a solution would be nice!
– James Bradbury
Oct 8 '18 at 20:00
add a comment |
5
I got this on an update from 16.04 LTS to 18.04 LTS; the steps you outlined eliminated the problem. Thanks!
– Alex
May 26 '18 at 20:21
This also fixed one of my issues on updating to 18.04. Thanks
– aocall
Jun 15 '18 at 19:26
Also had 18.04 upgrade problem. This didn't work for me, I ended up re-installing 18.04 over the old install.
– dfrankow
Jul 7 '18 at 4:33
1
Doesn't work for me in 18.04 (upgraded from 16.04). As it seems to work after I press any key, I'm not going to do a clean install. But a solution would be nice!
– James Bradbury
Oct 8 '18 at 20:00
5
5
I got this on an update from 16.04 LTS to 18.04 LTS; the steps you outlined eliminated the problem. Thanks!
– Alex
May 26 '18 at 20:21
I got this on an update from 16.04 LTS to 18.04 LTS; the steps you outlined eliminated the problem. Thanks!
– Alex
May 26 '18 at 20:21
This also fixed one of my issues on updating to 18.04. Thanks
– aocall
Jun 15 '18 at 19:26
This also fixed one of my issues on updating to 18.04. Thanks
– aocall
Jun 15 '18 at 19:26
Also had 18.04 upgrade problem. This didn't work for me, I ended up re-installing 18.04 over the old install.
– dfrankow
Jul 7 '18 at 4:33
Also had 18.04 upgrade problem. This didn't work for me, I ended up re-installing 18.04 over the old install.
– dfrankow
Jul 7 '18 at 4:33
1
1
Doesn't work for me in 18.04 (upgraded from 16.04). As it seems to work after I press any key, I'm not going to do a clean install. But a solution would be nice!
– James Bradbury
Oct 8 '18 at 20:00
Doesn't work for me in 18.04 (upgraded from 16.04). As it seems to work after I press any key, I'm not going to do a clean install. But a solution would be nice!
– James Bradbury
Oct 8 '18 at 20:00
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f837035%2fno-symbol-table-press-any-key-to-continue%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
2
See also Bug #1633839 “No symbol table. Press any key to continue” : Bugs : linux package : Ubuntu
– wilx
Nov 6 '16 at 20:00
Found my particular problem in a Kubuntu forum in which a user reported his error--which I had repeated. He'd forgotten which of several hard drives he'd installed on. I followed the fdisk step here, but jumped at the indication which confirmed the drive I already had in my head. However, by the time I found my mistake, which I cannot confirm now, I had started a Hardcore Reinstall from DVD... Double-check the grub install if this you're seeing this error.
– quagmire
Sep 25 '18 at 22:55