Installer fails to find disk to install

Bug #1347676 reported by Stefan Bader on 2014-07-23
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)

Bug Description


Since this test needs some wireless, I did it on some real hw. In this case the desktop happens to have a card reader with an additional USB port. And in that USB port the ISO (on a USB key) is connected. The ISO ends up being sda, while the disk is sdb.

According to the test case:
- System gets booted until the greeter offers the choice between "test" and "install"
- Since there is no ethernet connection the next screen is the wireless connect
- From there the next dialogue is titled "Installation type" but it looks like the partitioner

In that partitioner I initially used an existing LVM volume for the install but that failed on the grub installation (and the
dialogue for alternate grub location allows no manual typing and did not show the disk which contained the LVM volume).
So I erased the disk completely (no partition table left). Repeating the steps above, I again end up in the partitioner which only shows sda (but that is the USB installation media!).

Stefan Bader (smb) wrote :
Stefan Bader (smb) wrote :
Stefan Bader (smb) wrote :
Stefan Bader (smb) wrote :
Stefan Bader (smb) wrote :
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:

tags: added: iso-testing
Phillip Susi (psusi) wrote :

It appears you have used that disk in the past as part of a fakeraid array and the sil signature is still present on the drive. If you no longer wish to use the drive as part of a fakeraid array you need to delete the raid array in the raid bios, or run dmraid -E /dev/sdb to erase the signature from the drive.

Changed in ubiquity (Ubuntu):
status: New → Invalid
Stefan Bader (smb) wrote :

Darn, yes, I probably have. Thanks Philip. Just one thing: it clearly isn't a regression or anything that should block the point release. But wondering whether the partitioner might in future include such disks in the list and only mark them "unusable for reason x"?

Stefan Bader (smb) wrote :

Oh, and just for reference, the command is: dmraid -r -E /dev/sdb

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

Other bug subscribers