"Unfortunately Probing for devices to install to failed. "

[Maranda Davis]

I downloaded Ubuntu Server 18.04.3 LTS and put it in a disc using the built in windows 10 tools. I then put it in my computer and booted it up. After setting my language and such it told me "Unfortunately Probing for devices to install to failed. Please report a bug on launchpad and if possible include the contents of the /var/log/installer directory." I also tried to burn it on a USB drive with the tool Etcher and it did the same thing.
I don't know how to include the contents of the /var/log/installer directory or if it is possible.

[Ubuntu Foundations Team Bug Bot (crichton)]

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/1841333/+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.]

[Launchpad Janitor (janitor)]

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

[Karl (nogame)]

I tried installing 18.04.3 on an Intel Compute Stick (x64 atom), which comes shipped with ubuntu 14.xx, with the same results. Since the hardware is a bit odd, I'm not sure how relevant the error is. That said, installation of 18.04.2 on this hardware purportedly worked. (https://jamesachambers.com/install-ubuntu-server-18-04-on-intel-compute-stick-guide/)

Installation media: c038a031a2b638f8e89d897119f1b7bb *ubuntu-18.04.3-live-server-amd64.iso

Add attachment failed, so here's the content:
/var/log/installer/block/discover.log:
2019-08-25 04:29:37,949 block-discover:74 starting probe
2019-08-25 04:29:39,265 probert.multipath:37 Failed to run cmd: ['multipathd', 'show', 'maps', 'raw', 'format', '%w %d %N']
2019-08-25 04:29:39,275 probert.multipath:37 Failed to run cmd: ['multipathd', 'show', 'paths', 'raw', 'format', '%d %z %m %N %n %R %r %a']
2019-08-25 04:29:40,001 curtin:1125 Extracting storage config from probe data
2019-08-25 04:29:40,430 block-discover:99 probing failed restricted=False
Traceback (most recent call last):
  File "/snap/subiquity/1093/lib/python3.6/site-packages/subiquity/controllers/filesystem.py", line 96, in _probed
    self.model.load_probe_data(storage)
  File "/snap/subiquity/1093/lib/python3.6/site-packages/subiquity/models/filesystem.py", line 1280, in load_probe_data
    self.reset()
  File "/snap/subiquity/1093/lib/python3.6/site-packages/subiquity/models/filesystem.py", line 1116, in reset
    config = storage_config.extract_storage_config(self._probe_data)
  File "/snap/subiquity/1093/lib/python3.6/site-packages/curtin/storage_config.py", line 1128, in extract_storage_config
    found_cfgs, found_errs = parser.parse()
  File "/snap/subiquity/1093/lib/python3.6/site-packages/curtin/storage_config.py", line 577, in parse
    entry = self.asdict(data)
  File "/snap/subiquity/1093/lib/python3.6/site-packages/curtin/storage_config.py", line 692, in asdict
    "Couldn't find partition entry in table")
RuntimeError: Couldn't find partition entry in table
2019-08-25 04:29:40,434 block-discover:101 reprobing for blockdev only
2019-08-25 04:29:40,489 curtin:1125 Extracting storage config from probe data
2019-08-25 04:29:40,905 block-discover:99 probing failed restricted=True
Traceback (most recent call last):
  File "/snap/subiquity/1093/lib/python3.6/site-packages/subiquity/controllers/filesystem.py", line 96, in _probed
    self.model.load_probe_data(storage)
  File "/snap/subiquity/1093/lib/python3.6/site-packages/subiquity/models/filesystem.py", line 1280, in load_probe_data
    self.reset()
  File "/snap/subiquity/1093/lib/python3.6/site-packages/subiquity/models/filesystem.py", line 1116, in reset
    config = storage_config.extract_storage_config(self._probe_data)
  File "/snap/subiquity/1093/lib/python3.6/site-packages/curtin/storage_config.py", line 1128, in extract_storage_config
    found_cfgs, found_errs = parser.parse()
  File "/snap/subiquity/1093/lib/python3.6/site-packages/curtin/storage_config.py", line 577, in parse
    entry = self.asdict(data)
  File "/snap/subiquity/1093/lib/python3.6/site-packages/curtin/storage_config.py", line 692, in asdict
    "Couldn't find partition entry in table")
Run...

[Karl (nogame)]

Did you use ubuntu-18.04.3-server.amd64.iso or ubuntu-18.04.3-live-server-amd64.iso? If the latter, please give the former a spin.

[Karl (nogame)]

Since the alternatives / non-live version worked (http://cdimage.ubuntu.com/releases/18.04.3/release/ubuntu-18.04.3-server-amd64.iso), at least for me, it might be helpful to add a note on live-version curtin partition scanning failure, suggesting the user try the alternatives installer ... if, in fact, this isn't a bug, but just an expected hardware support limitation of the -live- .iso.

[Tate Brumfield (chief-tate)]

So will the live version ever work? or does it just not work with usb flash drive so you must use alt with said hardware?

[Karl (nogame)]

Tate,

Given the -live- image has been on the front page for a few weeks, it probably works "in most cases." I tried the installing from the live version on a ~2017 laptop and it worked fine. There is some anecdotal evidence the live version (which, incidentally, offers more 'live' functionality but has a lower size) is not equipped to handle as many edge cases. Here's an example: https://askubuntu.com/questions/1164732/probing-for-devices-to-install-to-failed-ubuntu-server-installation

I am curious as to the original poster's hardware configuration, and whether the "live" .iso was used. I'd recommend closing this bug unless the original poster can provide the hardware configuration, post their error message from the log directory, and confirm whether or not the on the standard (more complete) alternatives image works. If the original submitter used a standard/stock hardware setup, it might be worth investigating, and certainly is, if the non-live .iso does not work.

[Maranda Davis (marandadavis)]

Hi, Sorry for the late response.

I was using the "live" version, and the alternative installer does work. However, there was an issue I had when trying to install it. When it was downloading grub it stopped at 66%, but I found that other people had the same issue and created a bug report for this already. Maybe this is related?

I am not sure how to post my logs since I don't think it saved it on the computer.

I was given this computer so I don't know it's exact specs. It appears to be a Dell XPS 8700 but there are 3 SSDs on it so I don't think it's stock.

[Karl (nogame)]

This sounds like it's after you created the partition table, is that correct? You may be able to switch to a virtual console (<alt><F1>, <alt><F2>, etc) and nab a logfile. Since network support appears available, you could just netcat the log file off. Also, the output of the disk layout and mounted partitions might help. Grab the output of:

1. mount
2. lsblk
3. Any one of these that works:
  a. fdisk -l
  b. sfdisk -l
  c. parted --list

[aeb (aeb-cwi)]

I downloaded ubuntu-18.04.3-live-server-amd64.iso, wrote to USB stick.
Booted a new machine from this stick.
Told about my keyboard and language and ethernet. Then (stage 7/13):
"Unfortunately, probing for devices to install to failed.
Please report a bug on Launchpad, and if possible include
the contents of the /var/log/installer directory."
OK - this is the bug report on Launchpad. Since this machine no longer
reacts to the keyboard, I cannot say anything about /var/log/installer.
This is an AMD Ryzen 3700X with SATA disk and SSD disk.

[aeb (aeb-cwi)]

Had forgotten about Alt-Fn (which I invented myself, long ago :-)).
In /var/log/installer there is a subiquity-debug.log that mentions
...
block-discover:99 probing failed restricted=false
"RunTimeError: Couldn't find partition entry in table"
block-discover:101 reprobing for blockdev only
curtin:1125 Extracting storage config from probe data
block-discover:99 probing failed restricted=false
"RunTimeError: Couldn't find partition entry in table"
...
[further network activity]

[psjoberg (peters-ubuntu)]

"#metoo", Did also try the live and got probing issues that directed me here. Reading the comments here and testing a little I come to realise how to fix it for me - delete the existing partitions.

First off, alt-f2(/3/4/5/6) did not give me a prompt making it hard to do anything.
I booted off a different live usb and (as I expected) the disk was partitioned with lvm so I wiped the partition table and tried live again. This time it worked.

I guess the live need to handle existing lvm better than die like this.

[Tang Jianyu (jianyu)]

Hi, I had the same issue recently, and attachment is my installation log which is on a Dell R730 rack server.

The alternative installer can work, but still hope this can be fixed.

[Mason Loring Bliss (y-mason)]

I was just mucking with an Eoan server live image, and I saw largely the same bug. Variations include
refreshing to the --edge package so I could have a monochrome display. Logs attached.

Since there isn't an free space, I wonder (baselessly) if this is a result of not seeing any free
space. I'd expect to be prompted for clear some

[Andrew Cloke (andrew-cloke)]

I'm getting the same from the Eoan "Final" daily-live ISO (http://cdimage.ubuntu.com/ubuntu-server/daily-live/20191012/eoan-live-server-arm64.iso) on a Huawei Kunpeng920 arm64 server.
/var/log/installer tarball attached.

[Ubuntu QA Website (ubuntuqa)]

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

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1841333

[Andrew Cloke (andrew-cloke)]

Follow-up to comment #16, on the advice of a wise person I've spun out this issue into a separate bug - bug #1848069.

[Michael Hudson-Doyle (mwhudson)]

There are a fair old collection of reports here. Apologies for the inconvenience! I think some of them, at least, are fixed in the 19.11.1 release of subiquity that I just released to the stable channel. Not all of them though (at least one of the tracebacks looks like https://bugs.launchpad.net/subiquity/+bug/1852351, which should be fixed soon).

[Per Lundberg (perlun)]

Same issue for me as well, on brand-new Ryzen 5 3600-based machine with Samsung 970 EVO Plus NVMe disk. My logs are attached. This is all with the ubuntu-18.04.3-live-server-amd64.iso image. I tried both with non-HWE kernel and HWE kernel, the same reuslts with both.

With ubuntu-18.04.3-server-amd64.iso, interestingly enough, everything worked flawlessly.

[Jakob Schönegger (jagop)]

everything worked fine using ubuntu-18.04.3-server-amd64.iso on my side.

[Michael Hudson-Doyle (mwhudson)]

I think all the bugs mentioned here are fixed now, at least in the 20.04 installer and the latest update pushed to stable (for 18.04). If anyone is still having an issue, can you please open a new bug report?

[Babita Verma (babitavermaa)]

Hi, i am trying to instaal ubunto20.04 at my new intel nuc i3 with bootable stick. My nuc has 32gb Ram. Now it says block probing did not discover any disks. What could be the reason?

[Michael Hudson-Doyle (mwhudson)]

Please file a new bug with the logs that should have been saved to the install media.