Announcement

Collapse
No announcement yet.

No 'vmlinuz' and no Grub entry

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    No 'vmlinuz' and no Grub entry

    Hello everyone. First let me describe my system:

    Dell Latitude D810
    Internal HD 50 gb
    External HD via USB 150 gb

    Operating systems present, in partition order:
    Internal hd:
    Windows 7 on C: (/dev/sda1)
    Windows 10 on D: (/dev/sda2)

    External hd:
    Debian 6 on /dev/sdb1
    Kubuntu 11.10 on /dev/sdb2

    All of that was and still is booting just fine. I made room and created an ext4 partition, and a swap area, at the end of the internal drive, and installed Kubuntu 16.04 there, by using Unetbootin and booting the extracted image from the first partition. On the first attempt it gave the old error about not being able to unmount /cdrom, so I restarted into it again and unmounted /cdrom from the terminal before letting the installer run. The installer ran fine after that, as far as I was able to tell, but upon rebooting I found that there was no entry for my shiny new Kubuntu in the Grub menu, altho it did find and correctly boot everything else, including even the 'memtest' from the new partition. So, I tried a couple of different approaches at manually booting it, from a SuperGrub boot CD, from Grub2Win etc, to no avail. So, I booted into the older Kubuntu and had a look, and there is no kernel image present in /boot and neither is the symbolic link 'vmlinuz' present in the /. I thought, well, maybe I can cheat on that and copy it from a live 16.04 session; however, in the live session, the symbolic link is there, but not the image in /boot.

    As it stands right now I installed 15.04 into there and it's working fine and nagging me to upgrade to 15.10. But I want to check here and see if anyone has an answer to make 16.04 act right on installing itself. Or, if not, if the general consensus is that if I follow the instructions to upgrade my 15.04 to 16.04 will that work and get my kernel where it belongs? I also had the thought that maybe, just maybe, I could use the package manager in the live 16.04 session to install another kernel (low-latency or something, or even just an updated version of the generic) and still do my original idea of copying it to that partition. I welcome any advice.

    #2
    lol

    That wasn't very hard at all. I booted into a 16.04 live session again, reinstalled it to the hard drive, and again there was no kernel image, so I installed the generic from the package manager into a live session, copied it and its symlink to the partition where I installed it, and I'm in business. I'll leave this here in case anyone else runs into the same thing, or has any comments.

    Comment

    Working...
    X