[Ubuntu 16.04 GA]OS does not boot once installed on FCoE LUN in legacy mode

Bug #1607742 reported by Ketan Mukadam
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grub-installer (Ubuntu)
New
Undecided
Unassigned
ubiquity (Ubuntu)
New
Undecided
Unassigned

Bug Description

CONFIGURATION DETAILS
Host OS with Support Pack - Ubuntu 16.04
Guest/VM OS Details - NA
System(s) Under Test - System x3750 M4(Xinyi Lenovo Red Server)
Adapter(s) Under Test - Skyhawk
IPL Name -
Active Profile ID - NA
Network Configuration - Connected to Nexus Switch
SAN Configuration - IBM Storwize V7000 Target
OneCapture file attached -

FW Used: 11.0.270.15

BUG REPRODUCTION DETAILS
Test Case Instance -
Reproducibility of Bug - Always
Last Known Working Build - NA
Time to Reproduce Bug - 5 Minutes
Steps To Reproduce Bug -
===============================
1
.Map a multipath FCoE LUN in legacy mode.
2.Install Ubuntu 16.04 in the LUN with install "disk-detect/multipath/enable=true" option.
3.Installation goes on fine.
4.Once the installation is completed the OS does not boot up in legacy.

Observation:
============

When we install Ubuntu 16.04 in FCoE LUN in UEFI the OS boots up fine.

Steps followed to install the OS in the systems here :
1.After selecting the language press F6, and select "Expert mode" and add the
line "install disk_detect/multipath/enable=true" in install script.

2.After few steps where we are asked about different languages and countries we
are asked to choose the Installer components we want to load, in this page
select "multipath-modules-4.4.0-21-generic-di:DM-Multipath support"

Tags: bot-comment
Revision history for this message
Ketan Mukadam (ketan-mukadam) wrote :
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1607742/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
affects: ubuntu → linux (Ubuntu)
information type: Public → Private Security
affects: linux (Ubuntu) → ubiquity (Ubuntu)
information type: Private Security → Public
Revision history for this message
Laurie Barry (laurie-barry-4) wrote :

Can we please have an update on this bug?

thank you
Laurie

Revision history for this message
Shamim Nauroz (sn887805) wrote :

Please find below the comments of few of your queries:

From what I understand, the system boots fine if installed under UEFI mode, and does not boot if installed in BIOS mode. Is that correct?

>> Yes that's correct. While installing the OS we see no issues.

At what point does it fail to boot?

>>The installation goes on fine with no issues. After the installation is complete we are asked to reboot and after that it never boots up.

Are you sure that the disk is visible as a boot device from the BIOS?

>>Yes, we are able to see the disk we map.

Please note we are not able to boot to the GRUB in BIOS but in UEFI we are able to do so.

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.