Ubuntu 18.04 LTS fails to PXE boot

Bug #1754828 reported by beta-tester on 2018-03-10
60
This bug affects 13 people
Affects Status Importance Assigned to Milestone
casper (Ubuntu)
Undecided
Unassigned
systemd (Ubuntu)
Undecided
Unassigned
ubiquity (Ubuntu)
High
Unassigned

Bug Description

i just downloaded the daily-live image from:
http://cdimage.ubuntu.com/daily-live/current/bionic-desktop-amd64.iso
and added it to my PXE server project
(for more information see: https://github.com/beta-tester/RPi-PXE-Server/tree/testing).

when i try to PXE boot the PC or VirtualBox from that ISO daily-live image, i run into the emergency mode console.
earlier ISO images of Ubuntu (16.04.04, 17.10.1) are PXE booting this way correctly to the UI on both, PC and VirtualBox.

when i burm the ISO of Ubuntu 18.04 LTS daily-live to a media and boot from it, it boots correctly.

this are the PXE boot menu parameters:
LABEL Ubuntu x64 Daily-Live
    KERNEL /nfs/ubuntu-daily-x64/casper/vmlinuz.efi
    APPEND initrd=/nfs/ubuntu-daily-x64/casper/initrd.lz netboot=nfs nfsroot=192.168.1.1:/srv/nfs/ubuntu-daily-x64 ro file=/cdrom/preseed/ubuntu.seed boot=casper --
    TEXT HELP
        Boot to Ubuntu x64 Daily-Live
        User: ubuntu
    ENDTEXT

this is the log i could grab from the emergency mode console:
see attached log.

oops, Affects package was given wrongly.

affects: aptdaemon (Ubuntu) → bootcd (Ubuntu)

same PXE boot issue with Ubuntu 18.04 LTS daily-live 2018-03-10

not sure what package is unvolved to the pxe boot process of a live dvd so image

affects: bootcd (Ubuntu) → ubuntu
summary: - fails PXE boot Ubuntu 18.04 LTS daliy-live 2018-03-09
+ fails PXE boot Ubuntu 18.04 LTS daliy-live
summary: - fails PXE boot Ubuntu 18.04 LTS daliy-live
+ Ubuntu 18.04 LTS daliy-live ISO fails PXE boot
Simon Quigley (tsimonq2) wrote :

I'll guess this is Ubiquity.

summary: - Ubuntu 18.04 LTS daliy-live ISO fails PXE boot
+ Ubuntu 18.04 LTS fails to PXE boot
no longer affects: ubuntu
tags: added: rls-bb-incoming

i just tried the daily-live from 2018-03-25 and attached the log output of dmesg and journalctl (syslog doesn't exist)
and screenshots of the FAILED messages off the screen.

Jean-Baptiste Lallement (jibel) wrote :

It looks similar to bug 1755863 which is for nfsboot

Changed in ubiquity (Ubuntu):
importance: Undecided → Critical
importance: Critical → High

yes, my report is a duplicate of issue
https://bugs.launchpad.net/bugs/1754777
and
https://bugs.launchpad.net/bugs/1755863

that's precisely the issue i have as well.

the temporary workaround on bug report https://bugs.launchpad.net/bugs/1754777
works for me at the moment, to get booting into the desktop user interface.

thank you Jean-Baptiste Lallement (jibel), for pointing to that report.

Launchpad Janitor (janitor) wrote :

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

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

isn't it possible to mark this report as duplicate of more than one other report?
1754777 and 1755863 ?

This bug is still affecting me, downloaded yesterday iso images from ubuntu,kubuntu,xubuntu and can't boot from pxe server saying that iam in emergency mode.

Lukas (lukas-wringer) wrote :

affects my custom squashfs (18.04) to, workaround kinda works but my custom unit that edits fstab won't work anymore

Launchpad Janitor (janitor) wrote :

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

Changed in casper (Ubuntu):
status: New → Confirmed
Changed in systemd (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers