New kernels not booting. Referred back to Bios

[gunnar furugård]

I have 3 4.13.0 kernels in my Grub menu, -26, -31, -32. None of the boot at all. I am directed back to bios to choose either Windows or the external HDD I have Ubuntu on. However my 4.10.0 -28 works perfect.Thats the one I got at fresh install. I can manage with the old kernel but it is annoying not to be able to use newer kernels. / Gunnar

Ps I bit more info about it. I have been working with Ubuntu the last 15-20 years but never had any problem updating. This time my previous HDD broke so I had to buy a new one. Installing Ubuntu from scratch on a new HDD. It took me some time to get it working. Mostly I ended up with black screen. Finally I got it working on a fresh partition. The working image is the first one in Grub. The first installation from the installation Image.

30/1
I am not much of OS guy but what I understand from Grub config file the "non working "images are referenced. Here is a piece of it
-----
menu entry 'Ubuntu, with Linux 4.13.0-32-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.13.0-32-generic-advanced-caff7239-a5be-41cd-a216-a654f23aab5a' {
    recordfail
savedefault
    load_video
    gfxmode $linux_gfx_mode
    insmod gzio
    if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 caff7239-a5be-41cd-a216-a654f23aab5a
    else
      search --no-floppy --fs-uuid --set=root caff7239-a5be-41cd-a216-a654f23aab5a
    fi
    echo 'Loading Linux 4.13.0-32-generic ...'
        linux /boot/vmlinuz-4.13.0-32-generic root=UUID=caff7239-a5be-41cd-a216-a654f23aab5a ro
    echo 'Loading initial ramdisk ...'
    initrd /boot/initrd.img-4.13.0-32-generic
}
menuentry 'Ubuntu, with Linux 4.13.0-32-generic (upstart)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.13.0-32-generic-init-upstart-caff7239-a5be-41cd-a216-a654f23aab5a' {
    recordfail

etc
-----
My interpretation is that some how the link between the menu entry and the actual booting piece of code is somehow incorrect. / Gunnar
Please tell me how to proceed to get more trace information

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.10.0-28-generic 4.10.0-28.32~16.04.2
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic i686
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
CurrentDesktop: Unity
Date: Mon Feb 5 15:27:35 2018
InstallationDate: Installed on 2018-01-18 (17 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
SourcePackage: linux-hwe
UpgradeStatus: No upgrade log present (probably fresh install)

[gunnar furugård (gunnar-furugard)]

The bug seems to be corrected in 4.13.0-33. Please mark the bug as attended from -33. / Gunnar

[Po-Hsu Lin (cypressyew)]

Hello Gunnar,
do you still have this issue with the latest 4.15 HWE kernel on Xenial?
Thanks

[Launchpad Janitor (janitor)]

[Expired for linux-hwe (Ubuntu) because there has been no activity for 60 days.]