Ubuntu 18.04 PXE issue

Bug #1789692 reported by Brahamaprakash Vardhaman
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
maas-images
New
Undecided
Unassigned

Bug Description

We are trying to install Ubuntu 18.04 through PXE boot(intel i350Lom),
  on Local target(Cisco 12G SAS Raid Controller)but during installation
  it hangs during the partition saying “No matching physical Volume
  Found”. However, the same os image if installed by mapping vdvd, it
  gets installed successfully. Please find the attached error screenshot
  and preseed file which we used for pxe boot.

Revision history for this message
Brahamaprakash Vardhaman (bvardham) wrote :
Revision history for this message
Brahamaprakash Vardhaman (bvardham) wrote :
Revision history for this message
Brahamaprakash Vardhaman (bvardham) wrote :
Revision history for this message
Jeff Lane  (bladernr) wrote :
Revision history for this message
Jeff Lane  (bladernr) wrote :

One other suggestion. Can you install the machine manually by pxebooting the installer WITHOUT that preseed, and manually performing the install?

Revision history for this message
Jeff Lane  (bladernr) wrote :

And finally, does any of this work via MAAS?

Revision history for this message
Brahamaprakash Vardhaman (bvardham) wrote :

This is the comments passed by internal team.

Hello Jeff,

Even Manual PXE runs into the same problem. Have tried solutions from the link you provided but no luck.

Any other suggestions on this?

Regards,
Vinodh

Revision history for this message
Jeff Lane  (bladernr) wrote :

OK... so how exactly are you PXE booting and what image are you using, exactly?

Revision history for this message
Jeff Lane  (bladernr) wrote :

I am unable to recreate this myself in VMs... Michael may have other ideas too.

So from Comment #8 above, what image are you using, exactly to attempt this?

and further questions:

And are you sure you're using the 18.04 netboot images?

How exactly (what steps did you take) to set up TFTP to serve the netboot images.

How exactly (what steps did you take) to set up the ISO image for PXE/Network installation?

Revision history for this message
Jeff Lane  (bladernr) wrote :

From your comments so far, it sounds like a driver issue in the initrd.gz image for netbooting. What hardware is this?

Revision history for this message
jeffrey leung (jefleung) wrote :

I see this in my environment with UCS blade servers as well. I believe we are probably using the same server iso as BP that I downloaded from Canonical and copied to our repo. I am using the same procedure and preseed file that we use for xenial and trusty releases which work. This is being tested with Cisco UCS B200M4 currently.

I suspect there may be a change needed with the preseed file for bionic but haven't had much time to troubleshoot yet but just wanted to provide some data for the bug. We are using the alternative ubuntu server install for advanced networking/storage, not the live server.

http://cdimage.ubuntu.com/releases/18.04.1/release/ubuntu-18.04.1-server-amd64.iso

I was getting a timeout error with posting the comment so I copied the steps over to a .txt file and attaching to the comment. I can try using the hwe-netboot images and see if that works later today.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.