Bug #1633839 “No symbol table. Press any key to continue” : Bugs : linux package : Ubuntu

Revision history for this message

Brad Figg (brad-figg) wrote on 2016-10-16: Status changed to Confirmed

#2

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

Alex N. (a-nox) on 2016-10-16

description:

updated

Alex N. (a-nox) on 2016-10-16

description:

updated

Alex N. (a-nox) on 2016-10-17

description:

updated

Revision history for this message

Michael (mike984) wrote on 2016-10-18:

#3

I also upgraded in place.

Revision history for this message

Michka Popoff (michkapopoff) wrote on 2016-10-18:

#4

boot-repair output Edit (51.1 KiB, text/plain)

I had the same problem. Updating from 16.04 to 16.10 in place.

I ran boot-repair, but the tool had not been updated during the migration (the update 16.10 removed the boot-repair ppa from the sources.list). Running the repair completely botched my grub.cfg files (update-grub was complaining about syntax errors). After a (painful) manual restart through the grub command line, I was able to boot.

The I did:
sudo add-apt-repository ppa:yannubuntu/boot-repair
sudo apt-get update
sudo apt-get upgrade

Using the new boot-repair (version 4ppa38, instead of the old 4ppa35), I ran the repair tool, setup grub again, rebooted, and the "error: no symbol table. Press any key to continue..." was gone.

People looking for a solution may update boot-repair to 4ppa38, run it, and see if it fixes it. Make sure to backup your data first, it worked for me but I can't guarantee that it will work for you.

I am attaching the boot-repair report done with 4ppa35, which may be of interest for people trying to debug this.

Revision history for this message

Alex N. (a-nox) wrote on 2016-10-18:

#5

That made me think about grub, so i reinstalled grub as described here https://help.ubuntu.com/community/Grub2/Installing#Reinstalling_GRUB_2_from_a_Working_System

sudo grub-install /dev/sdX
sudo update-grub
sudo reboot

and voila, the error message is gone.

Revision history for this message

David Oser (mirmos192) wrote on 2016-10-18: Re: [Bug 1633839] Re: No symbol table. Press any key to continue

#6

Download full text (4.7 KiB)

Thanks Michka
I had tried the boot-repair option, to no avail.
But this time I made sure I had the latest version (I do) by completely
removing boot-repair and reinstalling, including repository, and tried
'advanced' option. 'Successful' but didn't solve the problem.
Then I tried default version of boot-repair. Likewise, 'successful', but
didn't solve the problem.
I don't have a dual-boot system since I long ago removed Windows. But it is
a UEFI machine and I have a separate sda1 FAT 32 boot partition, then a
main sda2 ext4 partition, then a swap partition.
I'm wondering if I should remove the sda1 efi FAT 32 partition, which may
be causing the difficulty (even though in boot-repair 'advanced' option I
had ensured that grub would be 'additionally' be reinstalled in sda1)?
I'm a 'fiddler' rather than an expert so I'm reluctant to risk doing that
as I do have a working system right now, even though it is slightly
compromised at boot since the upgrade to 16.10.
What do you think?
By the way, Alex N's solution also did not work for me. Though I have not
tried simply using /dev/sda rather than sda1 or sda2.
Best
David

On 18 October 2016 at 21:11, Michka Popoff <email address hidden>
wrote:

> I had the same problem. Updating from 16.04 to 16.10 in place.
>
> I ran boot-repair, but the tool had not been updated during the
> migration (the update 16.10 removed the boot-repair ppa from the
> sources.list). Running the repair completely botched my grub.cfg files
> (update-grub was complaining about syntax errors). After a (painful)
> manual restart through the grub command line, I was able to boot.
>
> The I did:
> sudo add-apt-repository ppa:yannubuntu/boot-repair
> sudo apt-get update
> sudo apt-get upgrade
>
> Using the new boot-repair (version 4ppa38, instead of the old 4ppa35), I
> ran the repair tool, setup grub again, rebooted, and the "error: no
> symbol table. Press any key to continue..." was gone.
>
> People looking for a solution may update boot-repair to 4ppa38, run it,
> and see if it fixes it. Make sure to backup your data first, it worked
> for me but I can't guarantee that it will work for you.
>
> I am attaching the boot-repair report done with 4ppa35, which may be of
> interest for people trying to debug this.
>
> ** Attachment added: "boot-repair output"
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1633839/+attachment/4763425/+files/Boot-info.txt
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1633839
>
> Title:
> No symbol table. Press any key to continue
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> Ubuntu 16.10. shows "error: no symbol table. Press any key to
> continue..." after Kernel boot and before login screen. After pressing
> a key or waiting a few seconds, the boot process continues and login
> screen appears.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.10
> Package: linux-image-4.8.0-22-generic 4.8.0-22.24
> ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
> Uname: Linux 4.8.0-22-generic x86_64
> ApportVersion: 2.20.3-0ubuntu8
> Architecture: amd64
> Audio...

Thanks Michka
I had tried the boot-repair option, to no avail.
But this time I made sure I had the latest version (I do) by completely
removing boot-repair and reinstalling, including repository, and tried
'advanced' option. 'Successful' but didn't solve the problem.
Then I tried default version of boot-repair. Likewise, 'successful', but
didn't solve the problem.
I don't have a dual-boot system since I long ago removed Windows. But it is
a UEFI machine and I have a separate sda1 FAT 32 boot partition, then a
main sda2 ext4 partition, then a swap partition.
I'm wondering if I should remove the sda1 efi FAT 32 partition, which may
be causing the difficulty (even though in boot-repair 'advanced' option I
had ensured that grub would be 'additionally' be reinstalled in sda1)?
I'm a 'fiddler' rather than an expert so I'm reluctant to risk doing that
as I do have a working system right now, even though it is slightly
compromised at boot since the upgrade to 16.10.
What do you think?
By the way, Alex N's solution also did not work for me. Though I have not
tried simply using /dev/sda rather than sda1 or sda2.
Best
David

On 18 October 2016 at 21:11, Michka Popoff <1633839@bugs.launchpad.net>
wrote:

> I had the same problem. Updating from 16.04 to 16.10 in place.
>
> I ran boot-repair, but the tool had not been updated during the
> migration (the update 16.10 removed the boot-repair ppa from the
> sources.list). Running the repair completely botched my grub.cfg files
> (update-grub was complaining about syntax errors). After a (painful)
> manual restart through the grub command line, I was able to boot.
>
> The I did:
> sudo add-apt-repository ppa:yannubuntu/boot-repair
> sudo apt-get update
> sudo apt-get upgrade
>
> Using the new boot-repair (version 4ppa38, instead of the old 4ppa35), I
> ran the repair tool, setup grub again, rebooted, and the "error: no
> symbol table. Press any key to continue..." was gone.
>
> People looking for a solution may update boot-repair to 4ppa38, run it,
> and see if it fixes it. Make sure to backup your data first, it worked
> for me but I can't guarantee that it will work for you.
>
> I am attaching the boot-repair report done with 4ppa35, which may be of
> interest for people trying to debug this.
>
> ** Attachment added: "boot-repair output"
>    https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1633839/+attachment/4763425/+files/Boot-info.txt
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1633839
>
> Title:
>   No symbol table. Press any key to continue
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Ubuntu 16.10. shows "error: no symbol table. Press any key to
>   continue..." after Kernel boot and before login screen. After pressing
>   a key or waiting a few seconds, the boot process continues and login
>   screen appears.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.10
>   Package: linux-image-4.8.0-22-generic 4.8.0-22.24
>   ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
>   Uname: Linux 4.8.0-22-generic x86_64
>   ApportVersion: 2.20.3-0ubuntu8
>   Architecture: amd64
>   AudioDevicesInUse:
>    USER        PID ACCESS COMMAND
>    /dev/snd/controlC0:  xxxx       7722 F.... pulseaudio
>   CurrentDesktop: Unity
>   Date: Sun Oct 16 13:25:22 2016
>   EcryptfsInUse: Yes
>   HibernationDevice: RESUME=UUID=9d3bac9d-90f6-4fb6-ba39-e08ea2c3aa19
>   InstallationDate: Installed on 2013-10-28 (1083 days ago)
>   InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64
> (20131016.1)
>   MachineType: LENOVO 23255B2
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic
> root=UUID=3b21f524-fe80-4ab0-8b84-c03e44abcd8b ro elevator=deadline
>   RelatedPackageVersions:
>    linux-restricted-modules-4.8.0-22-generic N/A
>    linux-backports-modules-4.8.0-22-generic  N/A
>    linux-firmware                            1.161
>   SourcePackage: linux
>   UpgradeStatus: Upgraded to yakkety on 2016-10-16 (0 days ago)
>   dmi.bios.date: 03/03/2016
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: G2ETA6WW (2.66 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 23255B2
>   dmi.board.vendor: LENOVO
>   dmi.board.version: Not Defined
>   dmi.chassis.asset.tag: CS0000023589
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Not Available
>   dmi.modalias: dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:
> pn23255B2:pvrThinkPadX230:rvnLENOVO:rn23255B2:
> rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
>   dmi.product.name: 23255B2
>   dmi.product.version: ThinkPad X230
>   dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1633839/+subscriptions
>

Revision history for this message

David Oser (mirmos192) wrote on 2016-10-18:

#7

Download full text (3.7 KiB)

Thanks Alex
I had tried 'boot-repair' to no avail, although success was reported.
But I tried your solution twice by using dev/sda1 (the current efi FAT32
boot partition) and /dev/sda2 ( the main ext4 partition). Neither solved
the problem although there were no error messages only 'successful' report
in bash/command line.
Ahem...Then I read the link you kindly supplied (!) and found I should just
have used dev/sda. But unfortunately this also did not work to solve my
problem, although it also reported 'success' in bash.
I'm beginning to wonder if I shouldn't remove the separate FAT32 boot
partition which was probably a legacy from when I first installed Ubuntu on
this UEFI machine which used to run Windows, as I suspect this might be
what's causing the problem.
I'm fully backed up, but reluctant to go through the palava of a complete
reinstall of Ubuntu if I fully borked the system by removing the separate
boot partition.
Ho hum... I think I'll live with the issue for the time being.
Best
David

On 18 October 2016 at 21:31, Alex N. <email address hidden> wrote:

> That made me think about grub, so i reinstalled grub as described here
> https://help.ubuntu.com/community/Grub2/Installing#
> Reinstalling_GRUB_2_from_a_Working_System
>
> sudo grub-install /dev/sdX
> sudo update-grub
> sudo reboot
>
> and voila, the error message is gone.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1633839
>
> Title:
> No symbol table. Press any key to continue
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> Ubuntu 16.10. shows "error: no symbol table. Press any key to
> continue..." after Kernel boot and before login screen. After pressing
> a key or waiting a few seconds, the boot process continues and login
> screen appears.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.10
> Package: linux-image-4.8.0-22-generic 4.8.0-22.24
> ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
> Uname: Linux 4.8.0-22-generic x86_64
> ApportVersion: 2.20.3-0ubuntu8
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: xxxx 7722 F.... pulseaudio
> CurrentDesktop: Unity
> Date: Sun Oct 16 13:25:22 2016
> EcryptfsInUse: Yes
> HibernationDevice: RESUME=UUID=9d3bac9d-90f6-4fb6-ba39-e08ea2c3aa19
> InstallationDate: Installed on 2013-10-28 (1083 days ago)
> InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64
> (20131016.1)
> MachineType: LENOVO 23255B2
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic
> root=UUID=3b21f524-fe80-4ab0-8b84-c03e44abcd8b ro elevator=deadline
> RelatedPackageVersions:
> linux-restricted-modules-4.8.0-22-generic N/A
> linux-backports-modules-4.8.0-22-generic N/A
> linux-firmware 1.161
> SourcePackage: linux
> UpgradeStatus: Upgraded to yakkety on 2016-10-16 (0 days ago)
> dmi.bios.date: 03/03/2016
> dmi.bios.vendor: LENOVO
> dmi.bios.version: G2ETA6WW (2.66 )
> dmi.board.asset.tag: Not Available
> dmi.board.name: 23255B2
> dmi.board.ven...

Thanks Alex
I had tried 'boot-repair' to no avail, although success was reported.
But I tried your solution twice by using dev/sda1 (the current efi FAT32
boot partition) and /dev/sda2 ( the main ext4 partition). Neither solved
the problem although there were no error messages only 'successful' report
in bash/command line.
Ahem...Then I read the link you kindly supplied (!) and found I should just
have used dev/sda. But unfortunately this also did not work to solve my
problem, although it also reported 'success' in bash.
I'm beginning to wonder if I shouldn't remove the separate FAT32 boot
partition which was probably a legacy from when I first installed Ubuntu on
this UEFI machine which used to run Windows, as I suspect this might be
what's causing the problem.
I'm fully backed up, but reluctant to go through the palava of a complete
reinstall of Ubuntu if I fully borked the system by removing the separate
boot partition.
Ho hum... I think I'll live with the issue for the time being.
Best
David

On 18 October 2016 at 21:31, Alex N. <1633839@bugs.launchpad.net> wrote:

> That made me think about grub, so i reinstalled grub as described here
> https://help.ubuntu.com/community/Grub2/Installing#
> Reinstalling_GRUB_2_from_a_Working_System
>
> sudo grub-install /dev/sdX
> sudo update-grub
> sudo reboot
>
> and voila, the error message is gone.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1633839
>
> Title:
>   No symbol table. Press any key to continue
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Ubuntu 16.10. shows "error: no symbol table. Press any key to
>   continue..." after Kernel boot and before login screen. After pressing
>   a key or waiting a few seconds, the boot process continues and login
>   screen appears.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.10
>   Package: linux-image-4.8.0-22-generic 4.8.0-22.24
>   ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
>   Uname: Linux 4.8.0-22-generic x86_64
>   ApportVersion: 2.20.3-0ubuntu8
>   Architecture: amd64
>   AudioDevicesInUse:
>    USER        PID ACCESS COMMAND
>    /dev/snd/controlC0:  xxxx       7722 F.... pulseaudio
>   CurrentDesktop: Unity
>   Date: Sun Oct 16 13:25:22 2016
>   EcryptfsInUse: Yes
>   HibernationDevice: RESUME=UUID=9d3bac9d-90f6-4fb6-ba39-e08ea2c3aa19
>   InstallationDate: Installed on 2013-10-28 (1083 days ago)
>   InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64
> (20131016.1)
>   MachineType: LENOVO 23255B2
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic
> root=UUID=3b21f524-fe80-4ab0-8b84-c03e44abcd8b ro elevator=deadline
>   RelatedPackageVersions:
>    linux-restricted-modules-4.8.0-22-generic N/A
>    linux-backports-modules-4.8.0-22-generic  N/A
>    linux-firmware                            1.161
>   SourcePackage: linux
>   UpgradeStatus: Upgraded to yakkety on 2016-10-16 (0 days ago)
>   dmi.bios.date: 03/03/2016
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: G2ETA6WW (2.66 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 23255B2
>   dmi.board.vendor: LENOVO
>   dmi.board.version: Not Defined
>   dmi.chassis.asset.tag: CS0000023589
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Not Available
>   dmi.modalias: dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:
> pn23255B2:pvrThinkPadX230:rvnLENOVO:rn23255B2:
> rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
>   dmi.product.name: 23255B2
>   dmi.product.version: ThinkPad X230
>   dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1633839/+subscriptions
>

Revision history for this message

Alex N. (a-nox) wrote on 2016-10-19:

#8

The message "no symbol table found." seems to be a grub error. Can someone confirm this and tell if grub package is affected?

Revision history for this message

David Oser (mirmos192) wrote on 2016-10-19:

#9

I have tried 'boot-repair' in normal and advanced mode and have tried reinstalling grub via sudo grub-install /dev/sda1 (then sda2, and finally simply sda). All of these approaches have reported 'success' in bash/terminal etc - but none have actually solved my problem.
Actually I'm wondering where my 'working' grub is actually installed. I have a UEFI machine which originally came with Windows 8. On installing Ubuntu I did what was necessary to allow Ubuntu 14.04 to be installed successfully instead of Windows, and have 3 partitions: sda1 is allegedly my boot partition (Fat 32), sda2 my main partition and finally there is a sda3 - for Linux-Swap. I suppose it is possible I have two grubs installed, one in sda1 and the other in sda2. Is it possible that a delay in reaching the 'working' grub (say in sda2) is provoking the 'no symbol table found' error in Ubuntu 16.10?
I wonder what would happen if I deleted partition sda1, expanded sda2 into its space and then tried boot-repair via usb? Or maybe kept all 3 partitions but converted sda1 to ext4. However, I'm reluctant to risk these approaches for fear of not being able to recover my system.

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2016-10-19:

#10

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc1/

Changed in linux (Ubuntu):
importance:	Undecided → Medium
status:	Confirmed → Incomplete

Revision history for this message

Alex N. (a-nox) wrote on 2016-10-19:

#11

As stated before, i think this affects the grub instead of linux package, can someone confirm?

Revision history for this message

Roy Gilby (roy-gilbys) wrote on 2016-10-19:

#12

This Bug occurred immediately after doing a distro upgrade from 16.04 to 16.10.

Revision history for this message

David Oser (mirmos192) wrote on 2016-10-19:

#13

Download full text (3.4 KiB)

As other replies Joseph. The only thing I didn't try was an upstream
kernel. But in the end I've just done a completely fresh install - so
someone else will need to try the upstream kernel approach.. But I'm
intrigued that two people found their solution via a new grub install,
while I didn't
David

On 19 Oct 2016 19:31, "Joseph Salisbury" <email address hidden>
wrote:

Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc1/

** Changed in: linux (Ubuntu)
Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1633839

Title:
No symbol table. Press any key to continue

Status in linux package in Ubuntu:
Incomplete

Bug description:
  Ubuntu 16.10. shows "error: no symbol table. Press any key to
  continue..." after Kernel boot and before login screen. After pressing
  a key or waiting a few seconds, the boot process continues and login
  screen appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-22-generic 4.8.0-22.24
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0: xxxx 7722 F.... pulseaudio
  CurrentDesktop: Unity
  Date: Sun Oct 16 13:25:22 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=9d3bac9d-90f6-4fb6-ba39-e08ea2c3aa19
  InstallationDate: Installed on 2013-10-28 (1083 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64
(20131016.1)
  MachineType: LENOVO 23255B2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic
root=UUID=3b21f524-fe80-4ab0-8b84-c03e44abcd8b ro elevator=deadline
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic N/A
   linux-firmware 1.161
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-16 (0 days ago)
  dmi.bios.date: 03/03/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA6WW (2.66 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23255B2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: CS0000023589
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:
pn23255B2:pvrThinkPadX230:r...

As other replies Joseph. The only thing I didn't try was an upstream
kernel. But in the end I've just done a completely fresh install - so
someone else will need to try the upstream kernel approach.. But I'm
intrigued that two people found their solution via a new grub install,
while I didn't
David

On 19 Oct 2016 19:31, "Joseph Salisbury" <joseph.salisbury@canonical.com>
wrote:

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc1/

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1633839

Title:
  No symbol table. Press any key to continue

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.10. shows "error: no symbol table. Press any key to
  continue..." after Kernel boot and before login screen. After pressing
  a key or waiting a few seconds, the boot process continues and login
  screen appears.

ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-22-generic 4.8.0-22.24
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  xxxx       7722 F.... pulseaudio
  CurrentDesktop: Unity
  Date: Sun Oct 16 13:25:22 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=9d3bac9d-90f6-4fb6-ba39-e08ea2c3aa19
  InstallationDate: Installed on 2013-10-28 (1083 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64
(20131016.1)
  MachineType: LENOVO 23255B2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic
root=UUID=3b21f524-fe80-4ab0-8b84-c03e44abcd8b ro elevator=deadline
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware                            1.161
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-16 (0 days ago)
  dmi.bios.date: 03/03/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA6WW (2.66 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23255B2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: CS0000023589
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:
pn23255B2:pvrThinkPadX230:rvnLENOVO:rn23255B2:rvrNotDefined:cvnLENOVO:ct10:
cvrNotAvailable:
  dmi.product.name: 23255B2
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633839/+subscriptions

PANTALÉON Pierre (pipantal) on 2016-10-20

Changed in linux (Ubuntu):
status:	Incomplete → Confirmed

Revision history for this message

Rohan Dhruva (rohandhruva) wrote on 2016-10-21:

#14

I'm facing the same issue on my laptop after an upgrade from 16.04 to 16.10. I tried:
* grub-install
* boot-repair

Neither worked. I also tried installing the mainline linux kernel (4.9-rc1), that didn't help either. As others have mentioned, this is probably something in grub, not necessarily the kernel.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2016-10-21:

#15

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in grub2 (Ubuntu):
status:	New → Confirmed

Revision history for this message

Josimar Alves de Oliveira (josimar-oliveira88) wrote on 2016-10-23:

#16

For me the following commands worked:

sudo mount -t ext4 /dev/sda1 /mnt
sudo grub-install --root-directory=/mnt /dev/sda

Revision history for this message

Yu Lou (louyu1999) wrote on 2016-11-19:

#17

I have a dual system of Ubuntu and Windows 7 and encountered the same problem after in place upgrade from 16.04 to 16.10. I tried boot-repair before but it didn't work. Just a moment ago I tried this command and it worked:

sudo grub-install /dev/sda

Revision history for this message

David Oser (mirmos192) wrote on 2016-11-19:

#18

Thanks Yu Lou - in the end I did a fresh install. That was OK.
David

On 19 Nov 2016 02:00, "Yu Lou" <email address hidden> wrote:

> I have a dual system of Ubuntu and Windows 7 and encountered the same
> problem after in place upgrade from 16.04 to 16.10. I tried boot-repair
> before but it didn't work. Just a moment ago I tried this command and it
> worked:
>
> sudo grub-install /dev/sda
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1633839
>
> Title:
> No symbol table. Press any key to continue
>
> Status in grub2 package in Ubuntu:
> Confirmed
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> Ubuntu 16.10. shows "error: no symbol table. Press any key to
> continue..." after Kernel boot and before login screen. After pressing
> a key or waiting a few seconds, the boot process continues and login
> screen appears.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.10
> Package: linux-image-4.8.0-22-generic 4.8.0-22.24
> ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
> Uname: Linux 4.8.0-22-generic x86_64
> ApportVersion: 2.20.3-0ubuntu8
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: xxxx 7722 F.... pulseaudio
> CurrentDesktop: Unity
> Date: Sun Oct 16 13:25:22 2016
> EcryptfsInUse: Yes
> HibernationDevice: RESUME=UUID=9d3bac9d-90f6-4fb6-ba39-e08ea2c3aa19
> InstallationDate: Installed on 2013-10-28 (1083 days ago)
> InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64
> (20131016.1)
> MachineType: LENOVO 23255B2
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic
> root=UUID=3b21f524-fe80-4ab0-8b84-c03e44abcd8b ro elevator=deadline
> RelatedPackageVersions:
> linux-restricted-modules-4.8.0-22-generic N/A
> linux-backports-modules-4.8.0-22-generic N/A
> linux-firmware 1.161
> SourcePackage: linux
> UpgradeStatus: Upgraded to yakkety on 2016-10-16 (0 days ago)
> dmi.bios.date: 03/03/2016
> dmi.bios.vendor: LENOVO
> dmi.bios.version: G2ETA6WW (2.66 )
> dmi.board.asset.tag: Not Available
> dmi.board.name: 23255B2
> dmi.board.vendor: LENOVO
> dmi.board.version: Not Defined
> dmi.chassis.asset.tag: CS0000023589
> dmi.chassis.type: 10
> dmi.chassis.vendor: LENOVO
> dmi.chassis.version: Not Available
> dmi.modalias: dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:
> pn23255B2:pvrThinkPadX230:rvnLENOVO:rn23255B2:
> rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
> dmi.product.name: 23255B2
> dmi.product.version: ThinkPad X230
> dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/
> 1633839/+subscriptions
>

Thanks Yu Lou - in the end I did a fresh install. That was OK.
David

On 19 Nov 2016 02:00, "Yu Lou" <1633839@bugs.launchpad.net> wrote:

> I have a dual system of Ubuntu and Windows 7 and encountered the same
> problem after in place upgrade from 16.04 to 16.10. I tried boot-repair
> before but it didn't work. Just a moment ago I tried this command and it
> worked:
>
> sudo grub-install /dev/sda
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1633839
>
> Title:
>   No symbol table. Press any key to continue
>
> Status in grub2 package in Ubuntu:
>   Confirmed
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Ubuntu 16.10. shows "error: no symbol table. Press any key to
>   continue..." after Kernel boot and before login screen. After pressing
>   a key or waiting a few seconds, the boot process continues and login
>   screen appears.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.10
>   Package: linux-image-4.8.0-22-generic 4.8.0-22.24
>   ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
>   Uname: Linux 4.8.0-22-generic x86_64
>   ApportVersion: 2.20.3-0ubuntu8
>   Architecture: amd64
>   AudioDevicesInUse:
>    USER        PID ACCESS COMMAND
>    /dev/snd/controlC0:  xxxx       7722 F.... pulseaudio
>   CurrentDesktop: Unity
>   Date: Sun Oct 16 13:25:22 2016
>   EcryptfsInUse: Yes
>   HibernationDevice: RESUME=UUID=9d3bac9d-90f6-4fb6-ba39-e08ea2c3aa19
>   InstallationDate: Installed on 2013-10-28 (1083 days ago)
>   InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64
> (20131016.1)
>   MachineType: LENOVO 23255B2
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic
> root=UUID=3b21f524-fe80-4ab0-8b84-c03e44abcd8b ro elevator=deadline
>   RelatedPackageVersions:
>    linux-restricted-modules-4.8.0-22-generic N/A
>    linux-backports-modules-4.8.0-22-generic  N/A
>    linux-firmware                            1.161
>   SourcePackage: linux
>   UpgradeStatus: Upgraded to yakkety on 2016-10-16 (0 days ago)
>   dmi.bios.date: 03/03/2016
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: G2ETA6WW (2.66 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 23255B2
>   dmi.board.vendor: LENOVO
>   dmi.board.version: Not Defined
>   dmi.chassis.asset.tag: CS0000023589
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Not Available
>   dmi.modalias: dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:
> pn23255B2:pvrThinkPadX230:rvnLENOVO:rn23255B2:
> rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
>   dmi.product.name: 23255B2
>   dmi.product.version: ThinkPad X230
>   dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/
> 1633839/+subscriptions
>

Revision history for this message

Alex McDonald (w-7lex-k) wrote on 2016-11-24:

#19

Single boot system, did

sudo do-release-upgrade -d

Ended up with the error: no symbol table. Fixed by Yu Lou (louyu1999) suggestion

sudo grub-install /dev/sda

Revision history for this message

Ernst Zlo (ernst-zlo) wrote on 2016-12-04:

#20

I had a CLEAN INSTALL on a NEW formatted partition (with gparted) and ran into the same problem
Only special thing on my system is, that /home is on an extra partition.

(in the german Version instead of ""error: no symbol table. Press any key to continue..." on can see "FEHLER: KEINE SYMBOLTABELLE. DRÜCKEN SIE EINE TASTE... [adding the text that German speaking users find this on search engines]

Solution of Alex N. worked for me: (LÖSUNG:)

sudo grub-install /dev/sda
sudo update-grub
sudo reboot

no number after /dev/sda ! (KEINE ZAHL nach /dev/sda !)

Revision history for this message

Paul Matthijsse (paul-matthijsse) wrote on 2017-04-15:

#21

My root partition is on /dev/sdb.
So changing the above command into

sudo grub-install /dev/sdb
sudo update-grub
sudo reboot

did the trick.

By the way, fresh install of Xubuntu 17.04 on reformatted partition. This bug stems from upgrading Xubuntu 16.04 to 16.10 and it apparently survived the formatting process.

Revision history for this message

DIONYSIS KAPATSORIS (dfk7677) wrote on 2017-04-21:

#22

I am using Ubuntu 17.04, grub-efi with dual boot (Windows 10). Everything used to work when 16.04 was installed.

After the upgrade I also got the 'no symbol table error' and I was not being able to boot into Windows, with grub being unable to recognize the EFI (fat32) partition as a proper filesystem.

I fixed it by using the 'update-grub' command. But if I boot into Windows and restart, all the errors come back.

Revision history for this message

Anders Hall (a.hall) wrote on 2017-06-15:

#23

#21 worked for me.

Revision history for this message

Ashok (gpashok) wrote on 2018-12-13:

#24

Thanks. This solution worked for me..

Brad Figg (brad-figg) on 2019-07-24

tags:

added: cscc

Revision history for this message

Durga Prasad (durgaprasad.myway) wrote on 2020-02-21:

#25

It worked for me. I did this.

sudo grub-install /dev/sda
sudo update-grub
sudo reboot

I had 1 TB hard drive, with 5 partitions.
Ubuntu 18.04 (upgraded from Ubuntu 16.04 just now)
Ubuntu 16.04
Windows 10
Storage drive1 200 GB
Storage drive2 200 GB

6GB RAM

This issue happened when I upgraded from Ubuntu 16.04 to Ubuntu 18.04.

Thanks https://launchpad.net/~a-nox https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633839/comments/5

Ubuntu
linux package

No symbol table. Press any key to continue

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Affects		Status	Importance	Assigned to	Milestone
	grub2 (Ubuntu)	Confirmed	Undecided	Unassigned
	linux (Ubuntu)	Confirmed	Medium	Unassigned

Ubuntulinux package

No symbol table. Press any key to continue

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package