block probing crashed with TimeoutError

[Chris Guiver]

Ubuntu Jammy canary ISO LIVE test on
- dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

Sorry I have limited details to provide.

Problem detected message appeared; so I opened terminal & explored /var/crash and have submitted the `ubuntu-bug` report from there.

If I can provide more details; I'll happily re-run test whilst I have this daily, or test using newer dailies.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: subiquity (unknown)
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.465+canary3.3
CrashDB:
 {
        "impl": "launchpad",
        "project": "subiquity",
        "bug_pattern_url": "http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml"
     }
Date: Mon Mar 7 23:58:29 2022
ExecutablePath: /snap/ubuntu-desktop-installer/313/bin/subiquity/subiquity/cmd/server.py
InterpreterPath: /snap/ubuntu-desktop-installer/313/usr/bin/python3.8
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220306)
MachineType: Dell Inc. OptiPlex 755
ProcAttrCurrent: snap.hostname-desktop-installer.subiquity-server (complain)
ProcCmdline: /snap/hostname-desktop-installer/313/usr/bin/python3.8 -m subiquity.cmd.server --autoinstall=
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz layerfs-path=minimal.standard.live.squashfs maybe-ubiquity --- quiet splash
Python3Details: /usr/bin/python3.10, Python 3.10.2, python3-minimal, 3.10.1-0ubuntu1
PythonDetails: N/A
SnapChannel:

SnapRevision: 313
SnapUpdated: False
SnapVersion: 0+git.b49fe8d
SourcePackage: subiquity
Title: block probing crashed with TimeoutError
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/02/2007
dmi.bios.release: 0.0
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 0DR845
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA03:bd10/02/2007:br0.0:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0DR845:rvr:cvnDellInc.:ct3:cvr:sku:
dmi.product.name: OptiPlex 755
dmi.sys.vendor: Dell Inc.

[Chris Guiver (guiverc)]

FYI: I now note this is marked against `subiquity`... I didn't start the installer, my testing was LIVE only on this old box.

[Chris Guiver (guiverc)]

Another box & the same issue appeared on REPORT BUG (I used the onscreen option on 2nd box, and as this bug report was offered - I've selected it).

- hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)

Another live of same ISO, just different hardware

[Chris Guiver (guiverc)]

Another live test (daily 20220319) and same issue
- hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)

[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/1964039

[corrado venturini (corradoventu)]

same with subiquity 511

[Olivier Gayot (ogayot)]

Hello and thank you for your bug report!

probert is currently a bit lacking in terms of logging and it makes it challenging for us to understand what it is spending time on.

If you would like to help, I have prepared a script to retrieve some profiling information about probert execution. The script can be run in the ubuntu desktop installer environment and will generate a tarball with collected profiling information that you can share with us.

The script is available here in the two following locations:
* https://git.launchpad.net/~ogayot/+git/profile-probert-desktop-installer/tree/profile-probert-desktop-installer.py?h=main
* https://people.canonical.com/~ogayot/profile-probert-desktop-installer.py

The steps to run the script are as follow:

* Boot the lunar-live-server ISO (preferably the latest daily image)
* Once the graphical interface is up and running, ignore the installer's interface and open a terminal window (ctrl+alt+t is a keyboard shortcut for it)
* Download the script using the following command (this requires an Internet connection)
    * wget https://people.canonical.com/~ogayot/profile-probert-desktop-installer.py
* Run the profiler using the following command:
    * sudo python3 profile-probert-desktop-installer.py
* The execution can take a few seconds to a few minutes.
* Once finished a tarball will be generated in /tmp/profiling-probert.txz
* Sharing the tarball with us should help us figure out what's going on. We'd appreciate it!

Thanks!
Olivier

[Etienne URBAH (eurbah)]

I have a lot of NTFS partitions.

See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945011

[Henrique Camargo (henriqueqc)]

Attached is the profiling log. The timeout happens from time to time. It happens with the 23.10.1 image.
If you need more information I can help to debug the problem. Feel free to ask any questions.

[Mr A. M Colville (squidles)]

New Installation here with nvme drive

[Jonathan Lollis (jonathanelollis)]

While installing Ubuntu 23.10.1, received crash error block probing crashed with timeouterror.

Installer Log:

Dec 11 12:55:48 ubuntu subiquity_event.5539[5539]: subiquity/Early/apply_autoinstall_config
Dec 11 12:55:48 ubuntu subiquity_event.5539[5539]: subiquity/Early/apply_autoinstall_config
Dec 11 12:55:48 ubuntu subiquity_event.5539[5539]: subiquity/Reporting/apply_autoinstall_config
Dec 11 12:55:48 ubuntu subiquity_event.5539[5539]: subiquity/Reporting/apply_autoinstall_config
Dec 11 12:55:48 ubuntu subiquity_event.5539[5539]: subiquity/Error/apply_autoinstall_config
Dec 11 12:55:48 ubuntu subiquity_event.5539[5539]: subiquity/Error/apply_autoinstall_config
Dec 11 12:55:48 ubuntu subiquity_event.5539[5539]: subiquity/Userdata/apply_autoinstall_config
Dec 11 12:55:48 ubuntu subiquity_event.5539[5539]: subiquity/Userdata/apply_autoinstall_config
Dec 11 12:55:48 ubuntu subiquity_event.5539[5539]: subiquity/Package/apply_autoinstall_config
Dec 11 12:55:48 ubuntu subiquity_event.5539[5539]: subiquity/Package/apply_autoinstall_config
Dec 11 12:55:48 ubuntu subiquity_event.5539[5539]: subiquity/Debconf/apply_autoinstall_config
Dec 11 12:55:48 ubuntu subiquity_event.5539[5539]: subiquity/Debconf/apply_autoinstall_config
Dec 11 12:55:48 ubuntu subiquity_event.5539[5539]: subiquity/Kernel/apply_autoinstall_config
Dec 11 12:55:48 ubuntu subiquity_event.5539[5539]: subiquity/Kernel/apply_autoinstall_config
Dec 11 12:55:48 ubuntu subiquity_event.5539[5539]: subiquity/Zdev/apply_autoinstall_config
Dec 11 12:55:48 ubuntu subiquity_event.5539[5539]: subiquity/Zdev/apply_autoinstall_config
Dec 11 12:55:48 ubuntu subiquity_event.5539[5539]: subiquity/Ad/apply_autoinstall_config
Dec 11 12:55:48 ubuntu subiquity_event.5539[5539]: subiquity/Ad/apply_autoinstall_config
Dec 11 12:55:48 ubuntu subiquity_event.5539[5539]: subiquity/Late/apply_autoinstall_config
Dec 11 12:55:48 ubuntu subiquity_event.5539[5539]: subiquity/Late/apply_autoinstall_config
Dec 11 12:58:29 ubuntu subiquity_event.5539[5539]: configuring apt
Dec 11 12:58:30 ubuntu subiquity_event.5539[5539]: subiquity/Ad/has_support_GET

[Etienne URBAH (eurbah)]

Using the Live CD of 24.04 Beta (Noble Numbat) :

$ wget -q https://people.canonical.com/~ogayot/profile-probert-desktop-installer.py

$ sudo python3 profile-probert-desktop-installer.py
Traceback (most recent call last):
  File "/home/ubuntu/profile-probert-desktop-installer.py", line 11, in <module>
    import probert.storage
ModuleNotFoundError: No module named 'probert'

[Mark Allinson (notraddad)]

I was going to put Ubuntu on one side of the partition instead of Windows
10 for comparison with Mint but have now put Mint on the whole hard drive.
Thank you for the help anyway.

On Tue, 14 May 2024, 10:05 Olivier Gayot, <email address hidden>
wrote:

> ** Changed in: subiquity
> Status: New => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1964039
>
> Title:
> block probing crashed with TimeoutError
>
> Status in subiquity:
> Confirmed
>
> Bug description:
> Ubuntu Jammy canary ISO LIVE test on
> - dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
>
> Sorry I have limited details to provide.
>
> Problem detected message appeared; so I opened terminal & explored
> /var/crash and have submitted the `ubuntu-bug` report from there.
>
> If I can provide more details; I'll happily re-run test whilst I have
> this daily, or test using newer dailies.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 22.04
> Package: subiquity (unknown)
> ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
> Uname: Linux 5.15.0-18-generic x86_64
> NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
> ApportVersion: 2.20.11-0ubuntu78
> Architecture: amd64
> CasperMD5CheckResult: pass
> CasperVersion: 1.465+canary3.3
> CrashDB:
> {
> "impl": "launchpad",
> "project": "subiquity",
> "bug_pattern_url": "
> http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml"
> }
> Date: Mon Mar 7 23:58:29 2022
> ExecutablePath:
> /snap/ubuntu-desktop-installer/313/bin/subiquity/subiquity/cmd/server.py
> InterpreterPath: /snap/ubuntu-desktop-installer/313/usr/bin/python3.8
> LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64
> (20220306)
> MachineType: Dell Inc. OptiPlex 755
> ProcAttrCurrent: snap.hostname-desktop-installer.subiquity-server
> (complain)
> ProcCmdline: /snap/hostname-desktop-installer/313/usr/bin/python3.8 -m
> subiquity.cmd.server --autoinstall=
> ProcEnviron:
> LANG=C.UTF-8
> PATH=(custom, no user)
> ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
> layerfs-path=minimal.standard.live.squashfs maybe-ubiquity --- quiet splash
> Python3Details: /usr/bin/python3.10, Python 3.10.2, python3-minimal,
> 3.10.1-0ubuntu1
> PythonDetails: N/A
> SnapChannel:
>
> SnapRevision: 313
> SnapUpdated: False
> SnapVersion: 0+git.b49fe8d
> SourcePackage: subiquity
> Title: block probing crashed with TimeoutError
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 10/02/2007
> dmi.bios.release: 0.0
> dmi.bios.vendor: Dell Inc.
> dmi.bios.version: A03
> dmi.board.name: 0DR845
> dmi.board.vendor: Dell Inc.
> dmi.chassis.type: 3
> dmi.chassis.vendor: Dell Inc.
> dmi.modalias:
> dmi:bvnDellInc.:bvrA03:bd10/02/2007:br0.0:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0DR845:rvr:cvnDellInc.:ct3:cvr:sku:
> dmi.product.name: OptiPlex 755
> dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/subiquity/+bug/1964039/+s...

[Claus Neumayer (claus56)]

I installed Ubuntu 24.04 try version on an USB stick an get several errors. This on one of the error massages.

[Tom Payne (twpayne)]

I am also encountering this error.

I tried to run the debug scripts and got the same "No module named probert" error:

ubuntu@ubuntu:~$ sudo apt-get install curl
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  curl
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 227 kB of archives.
After this operation, 532 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu noble/main amd64 curl amd64 8.5.0-2ubuntu10 [227 kB]
Fetched 227 kB in 0s (1020 kB/s)
Selecting previously unselected package curl.
(Reading database ... 210655 files and directories currently installed.)
Preparing to unpack .../curl_8.5.0-2ubuntu10_amd64.deb ...
Unpacking curl (8.5.0-2ubuntu10) ...
Setting up curl (8.5.0-2ubuntu10) ...
Processing triggers for man-db (2.12.0-4build2) ...
ubuntu@ubuntu:~$ curl -LO https://git.launchpad.net/~ogayot/+git/profile-probert-desktop-installer/plain/profile-probert-desktop-installer.py?h=main
  % Total % Received % Xferd Average Speed Time Time Time Current
                                 Dload Upload Total Spent Left Speed
100 2202 100 2202 0 0 8352 0 --:--:-- --:--:-- --:--:-- 8372
ubuntu@ubuntu:~$ sudo python3 profile-probert-desktop-installer.py
Traceback (most recent call last):
  File "/home/ubuntu/profile-probert-desktop-installer.py", line 11, in <module>
    import probert.storage
ModuleNotFoundError: No module named 'probert'

The script modifies `sys.path` incorrectly. I applied the following patch to fix it:

ubuntu@ubuntu:~$ diff -u profile-probert-desktop-installer.py{.orig,}
--- profile-probert-desktop-installer.py.orig 2024-08-27 12:40:20.344163338 +0000
+++ profile-probert-desktop-installer.py 2024-08-27 12:40:32.474324146 +0000
@@ -5,8 +5,8 @@
 import subprocess
 import sys

-sys.path.append("/snap/ubuntu-desktop-installer/current/lib/python3.10/site-packages")
-sys.path.append("/snap/ubuntu-desktop-installer/current/usr/lib/python3/dist-packages")
+sys.path.append("/snap/ubuntu-desktop-bootstrap/current/lib/python3.10/site-packages")
+sys.path.append("/snap/ubuntu-desktop-bootstrap/current/usr/lib/python3/dist-packages")

 import probert.storage

Running the modified script gives:

ubuntu@ubuntu:~$ sudo python3 profile-probert-desktop-installer.py
/snap/ubuntu-desktop-bootstrap/current/usr/lib/python3/dist-packages/pyudev/monitor.py:136: SyntaxWarning: invalid escape sequence '\ '
  """
2024-08-27 12:40:41,331 INFO root: 19 [[profiling probe type bcache]]
2024-08-27 12:40:41,331 INFO root: 20 profiling information will be placed in /tmp/probert-bcache.profile
<string>:1: RuntimeWarning: coroutine 'Storage.probe' was never awaited
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
2024-08-27 12:40:41,339 INFO root: 19 [[profiling probe type blockdev]]
2024-08-27 12:40:41,339 INFO root: 20 profiling information will be placed in /tmp/probert-blockdev.profile
<string>:1: RuntimeWarning: coroutine 'Storage.probe' was never awaited
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
2024-08-...

[Tom Payne (twpayne)]

This is the generated /tmp/profiling-probert.txz file from my report.

[Tom Payne (twpayne)]

For info, here are the block devices on my machine. I am trying to replace an existing install and want to overwrite all data on all disks.

ubuntu@ubuntu:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 1.6G 1 loop /rofs
loop1 7:1 0 457.5M 1 loop
loop2 7:2 0 868.1M 1 loop
loop3 7:3 0 4K 1 loop /snap/bare/5
loop4 7:4 0 74.2M 1 loop /snap/core22/1380
loop5 7:5 0 269.6M 1 loop /snap/firefox/4173
loop6 7:6 0 10.7M 1 loop /snap/firmware-updater/127
loop7 7:7 0 505.1M 1 loop /snap/gnome-42-2204/176
loop8 7:8 0 38.7M 1 loop /snap/snapd/21465
loop9 7:9 0 91.7M 1 loop /snap/gtk-common-themes/1535
loop10 7:10 0 10.3M 1 loop /snap/snap-store/1124
loop11 7:11 0 476K 1 loop /snap/snapd-desktop-integration/157
loop12 7:12 0 137.3M 1 loop /snap/thunderbird/470
loop13 7:13 0 116.7M 1 loop /snap/ubuntu-desktop-bootstrap/171
loop14 7:14 0 116.8M 1 loop /snap/ubuntu-desktop-bootstrap/237
sda 8:0 0 931.5G 0 disk
└─sda1 8:1 0 931.5G 0 part
sdb 8:16 1 28.6G 0 disk
├─sdb1 8:17 1 5.7G 0 part /cdrom
├─sdb2 8:18 1 5M 0 part
├─sdb3 8:19 1 300K 0 part
└─sdb4 8:20 1 22.9G 0 part /var/crash
                                      /var/log
nvme0n1 259:0 0 953.9G 0 disk
├─nvme0n1p1 259:1 0 1G 0 part
└─nvme0n1p2 259:2 0 952.8G 0 part

[Tom Payne (twpayne)]

I was eventually able to get past this problem by erasing the partitions on /dev/sda:

    $ sudo dd if=/dev/zero of=/dev/sda bs=1M count=1024

This of course destroyed all the data on that drive, which I wanted to avoid doing if possible.

The obvious conclusion is that Ubiquity is getting confused by existing partitions and filesystems on the disk.

[Fritz Hudnut (este-el-paz)]

[QUOTE] This of course destroyed all the data on that drive, which I wanted to avoid doing if possible.

The obvious conclusion is that Ubiquity is getting confused by existing partitions and filesystems on the disk. [/QUOTE]

This might be apt . . . in my multi-boot machine I also found some time back that, like OSX, ubuntu seems to want to "be in charge" or "be the only kid in the playpen" . . . ??? So I have one of my openSUSE distros handle grub duties, otherwise it seemed like UUID numbers were messed with.

Subsequently someone on a forum said something about editing /etc/default/grub.conf???? (typing from memory) so that it wouldn't see itself as the only system installed???

[Mark Allinson (notraddad)]

Thanks for the info. I'd already erased the partition and installed Mint
which runs ok, but I'm still trying to find a good equivalent to the old
windows media player...

On Tue, 27 Aug 2024, 15:20 Tom Payne, <email address hidden> wrote:

> I was eventually able to get past this problem by erasing the partitions
> on /dev/sda:
>
> $ sudo dd if=/dev/zero of=/dev/sda bs=1M count=1024
>
> This of course destroyed all the data on that drive, which I wanted to
> avoid doing if possible.
>
> The obvious conclusion is that Ubiquity is getting confused by existing
> partitions and filesystems on the disk.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1964039
>
> Title:
> block probing crashed with TimeoutError
>
> Status in subiquity:
> Confirmed
>
> Bug description:
> Ubuntu Jammy canary ISO LIVE test on
> - dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
>
> Sorry I have limited details to provide.
>
> Problem detected message appeared; so I opened terminal & explored
> /var/crash and have submitted the `ubuntu-bug` report from there.
>
> If I can provide more details; I'll happily re-run test whilst I have
> this daily, or test using newer dailies.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 22.04
> Package: subiquity (unknown)
> ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
> Uname: Linux 5.15.0-18-generic x86_64
> NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
> ApportVersion: 2.20.11-0ubuntu78
> Architecture: amd64
> CasperMD5CheckResult: pass
> CasperVersion: 1.465+canary3.3
> CrashDB:
> {
> "impl": "launchpad",
> "project": "subiquity",
> "bug_pattern_url": "
> http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml"
> }
> Date: Mon Mar 7 23:58:29 2022
> ExecutablePath:
> /snap/ubuntu-desktop-installer/313/bin/subiquity/subiquity/cmd/server.py
> InterpreterPath: /snap/ubuntu-desktop-installer/313/usr/bin/python3.8
> LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64
> (20220306)
> MachineType: Dell Inc. OptiPlex 755
> ProcAttrCurrent: snap.hostname-desktop-installer.subiquity-server
> (complain)
> ProcCmdline: /snap/hostname-desktop-installer/313/usr/bin/python3.8 -m
> subiquity.cmd.server --autoinstall=
> ProcEnviron:
> LANG=C.UTF-8
> PATH=(custom, no user)
> ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
> layerfs-path=minimal.standard.live.squashfs maybe-ubiquity --- quiet splash
> Python3Details: /usr/bin/python3.10, Python 3.10.2, python3-minimal,
> 3.10.1-0ubuntu1
> PythonDetails: N/A
> SnapChannel:
>
> SnapRevision: 313
> SnapUpdated: False
> SnapVersion: 0+git.b49fe8d
> SourcePackage: subiquity
> Title: block probing crashed with TimeoutError
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 10/02/2007
> dmi.bios.release: 0.0
> dmi.bios.vendor: Dell Inc.
> dmi.bios.version: A03
> dmi.board.name: 0DR845
> dmi.board.vendor: Dell Inc.
> dmi.chassis.type: 3
> dmi.chassis.vendor: Dell Inc.
> dmi.modalias...

[Etienne URBAH (eurbah)]

With Live CD of Ubuntu 24.10 (Oracular Oriole) Beta :

This issue seems to be solved.

But inside curtin, udevadm_settle() is systematically very slow : https://bugs.launchpad.net/subiquity/+bug/2081573