Ubuntu Raring daily has missing /casper/vmlinuz

[Carla Sella]

When booting a VM on virtualbox with today's Ubuntu 64 bit desktop Raring daily image (http://cdimage.ubuntu.com/daily-live/20121110/raring-desktop-amd64.iso) I get a "/casper/vmlinuz file not found" error see attached screenshot.
The /casper/vmlinuz file is missing from her also: http://cdimage.ubuntu.com/daily-live/20121110/raring-desktop-amd64.list

[Launchpad Janitor (janitor)]

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

[Dimitri John Ledkov (xnox)]

Colin fixed this, hopefully the 20121113 images will be ok.

[Colin Watson (cjwatson)]

The image boots again now, but it produces an unbootable installed system. Investigating.

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubiquity - 2.13.3

---------------
ubiquity (2.13.3) raring; urgency=low

  * Use simplified form of super(), available from Python 3.
  * Fix target kernel file names when only a signed kernel is present on the
    installation medium (LP: #1077388).
 -- Colin Watson <email address hidden> Tue, 13 Nov 2012 12:31:47 +0000

[Danek (danex-szy)]

Seems like this issue still isn't fixed.
Theres no vmlinuz here:
http://cdimage.ubuntu.com/daily-live/20130214/raring-desktop-amd64.list

[Colin Watson (cjwatson)]

There doesn't need to be. We use /casper/vmlinuz.efi.

[Colin Watson (cjwatson)]

Rather - if there's a specific problem you're encountering, please explain the symptom.

[Danek (danex-szy)]

Well. I tried making bootable usb using "universal usb installer" from pendrivelinux under windows, as I had no luck doing so with usb-creator-gtk. I chose Ubu 12.10 option and pointed it to current daily image.
When I booted my pendrive I got "/casper/vmlinuz: file not found" error as soon as I tried starting ubuntu.

I've noticed vmlinuz.efi file but since my mobo has bios (not uefi) I assumed renaming the file just wouldn't bring expected results.
Strangely enough I succeded booting from amd64+mac image (which has vmlinuz) even though I use custom built PC. For a minute there I thought that maybe the images are switched.
Is this enough data?

[Colin Watson (cjwatson)]

This is probably a separate bug in this "universal usb installer"
program, then. It should be able to generate boot menu entries pointing
to vmlinuz.efi rather than vmlinuz, if the former exists.

The vmlinuz.efi file is in fact bootable using BIOS as well. The reason
I changed the file name was to indicate to the installer that it's a
signed kernel with the EFI stub, and that it should perform a special
operation to generate the unsigned kernel from that file (which is
actually just to make checksums match - the signed kernel is just as
good).

[neutron68 (neutron68)]

I just duplicated the symptoms with the Mythbuntu 12.04.2 64-bit ISO.

I tried 2 different ISO to USB programs in Windows XP and both produced a FAILED bootable USB Flash Drive.
http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/
http://unetbootin.sourceforge.net/

Neither program produced a USB Flash drive that successfully booted into the Mythbuntu installer.
I tried a 4GB Flash drive with unetbootin and a 1GB Flash drive with the Universal USB Installer.

I checked the MD5SUMS code to be sure the ISO was not corrupt. The code matched.
1065b482382203d367cf7ce1c69b7c51 (for mythbuntu-12.04.2-desktop-amd64.iso)

The flash drive made with unetbootin booted to a menu of boot choices and none of them would boot the machine. Some just sat with a blinking cursor and others just gave an error and restarted the menu.
The flash drive made with Universal USB Installer, started booting to a maroon Mythbuntu splash screen and then stopped with an error. I'll have to re-test to give the exact error messages.

[Steve Langasek (vorlon)]

> I tried 2 different ISO to USB programs in Windows XP and both
> produced a FAILED bootable USB Flash Drive.

I'm sorry, but those are bugs in the USB-writing programs in question, not in the Ubuntu images.

The correct way to write an Ubuntu 12.04 ISO image to a USB stick is to do so WITHOUT MODIFICATION. These USB-image-creating tools which are modifying the image when writing it are buggy and need to be fixed to not make such modifications. However, we do not maintain these tools; please ask the tool authors directly to correct these problems.

[neutron68 (neutron68)]

Sorry! False alarm!

I just got the Universal USB Installer (Pendrivelinux) to create a working bootable USB Flash drive!
I remade the USB flash drive and it worked this time. I'm not sure why it didn't work the first time.
I wonder if I "fat-fingered" the distro choice box when I made the first one?

I'm not sure what the deal with unetbootin is. It still doesn't work right.
I made sure I had the latest version, tried it again and it failed to make a bootable Mythbuntu installer, AGAIN.
It doesn't have a distro choice for Mythbuntu so you have to choose a generic Ubuntu.
The settings for Ubuntu must not be close enough to work.

Bottom line: Universal USB Installer (Pendrivelinux) does work when you choose the right distro from the pull-down menu!

[Marco Lackovic (marco-lackovic)]

I had the same problem trying to install raring-desktop-amd64 on a 4GB pen drive using Universal-USB-Installer.

In my case I think the problem was the drive was physically damaged.

What I did to fix it is:

+ I checked the pen drive for errors;

+ I did a format (not quick), restoring the allocation unit size device default;

+ I used Universal-USB-Installer to install raring-desktop-amd64, this time without checking the "format drive" option.

[Dario Panico (dariopan)]

I'll describe my usecase:
I have a GRUB entry to boot ISOs

menuentry 'Immagine Live' {
 search --no-floppy --fs-uuid --set=root $UUID
 set isofile="/image.iso"
 loopback loop $isofile
 linux (loop)/casper/vmlinuz root=UUID=$UUID boot=casper iso-scan/filename=$isofile noprompt noeject
 initrd (loop)/casper/initrd.lz
}

this works like a charm to boot every recent image of ubuntu (I think I used it back since 11.10) and its derivatives

this recent name change from vmlinuz to vmlinuz.efi breaks my setup

I know I can edit the linux line at boot, I know I could add a new menuentry (and I don't know any other possible workaround)