net Installer currently don't work in Trusty Tar

[Ingo Rohlfs]

the netboot Installer under dists/trusty/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/
doesn't currently work. The kernel is simply not booting.
As i don't get any useable output i cant say where the problem exactly exists

Tested on DELL Latitude 4310 & Lenovo TP T510

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1298407

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Ingo Rohlfs (ingo-rohlfs)]

PXE Installer dont has any logs :)

[Joseph Salisbury (jsalisbury)]

Can you follow the "Boot options" instructions on the following wiki to enable additional output on boot:

https://wiki.ubuntu.com/DebuggingKernelBoot

As mentioned on the wiki, it would be great if you can attach a log file which may have captured any messages you see. If you are unable to capture a log file, a digital photo will work just as well. As a last resort you can even copy messages down by hand.

[Ingo Rohlfs (ingo-rohlfs)]

I really have no logs or any output. It looks like after PXEboot has loaded kernel and initrd
it fails to load the kernel itself.
As there are no output at all and no sign of a loading kernel even with different boot parameters.
It simply results in a System Reset.

To be shure its not the PXE itself it tested it with 13.10 release and 13.04 which both works perfectly with the same configs.
Even with no supplied boot parameters at all.

[Ingo Rohlfs (ingo-rohlfs)]

I managed to get some output from the crashing kernel but i realy don't know if it is the result of the original error or cause of my excessive testing and playing araound

[Ingo Rohlfs (ingo-rohlfs)]

Ok i need to correct myself.
The Trace acually only shows that the initrd can't be loaded because it has been removed for testing.

Which in on the other hand tells me that the crash occures immediately after mounting the initrd.
I will test it with a selfbuild initrd but i think the problem lies inside the provided initrd.

Regards
Ingo

[Jack Zielke (v-launchpad-linuxcoffee-com)]

Netbooting from VirtualBox gives the following error:
mount: can't find /run in /etc/fstab

This only affects amd64 netboot. i386 netboot works just fine.

[Jack Zielke (v-launchpad-linuxcoffee-com)]

I take that back. There was a kernel update so the i386 version gave a warning about missing kernel modules. I updated to the latest netboot image and it boots up to a black screen. It does make it farther than the amd64 version. Alt-F2 provides a console, but this is unrelated to the amd64 netboot not booting.

[Ingo Rohlfs (ingo-rohlfs)]

Still not working. Does anyone have a idea for a workaround as a we are depending on a working 64bit netinstaller!

[Jack Zielke (v-launchpad-linuxcoffee-com)]

We downloaded the latest image this morning and it works!!

[Ingo Rohlfs (ingo-rohlfs)]

Jack which image did you download?
I only see images from the 15th of April on the mirrors, which are still the images that fail to work.

[Ingo Rohlfs (ingo-rohlfs)]

Looks fixed.