block probing crashed with TimeoutError

[Leó Kolbeinsson]

Testing Ubuntu Lunar desktop daily iso 18-12-2022

While installing received the error "Block probing crashed with "TimeoutError" - however the install continued and completed without further errors.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: subiquity (unknown)
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.24.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CasperVersion: 1.477
CurtinAptConfig: /var/log/installer/subiquity-curtin-apt.conf
Date: Sun Dec 18 10:34:45 2022
ExecutablePath: /snap/ubuntu-desktop-installer/712/bin/subiquity/subiquity/cmd/server.py
InterpreterPath: /snap/ubuntu-desktop-installer/712/usr/bin/python3.8
LiveMediaBuild: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221218)
MachineType: Dell Inc. OptiPlex 7060
ProcAttrCurrent: snap.hostname-desktop-installer.subiquity-server (complain)
ProcCmdline: /snap/hostname-desktop-installer/712/usr/bin/python3.8 -m subiquity.cmd.server --use-os-prober --storage-version=2 --postinst-hooks-dir=/snap/hostname-desktop-installer/712/etc/subiquity/postinst.d --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.8, python3-minimal, 3.10.6-1ubuntu1
PythonDetails: N/A
SnapChannel:

SnapRevision: 712
SnapUpdated: False
SnapVersion: 0+git.518d1ff6
SourcePackage: subiquity
Title: block probing crashed with TimeoutError
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/22/2022
dmi.bios.release: 1.18
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.18.0
dmi.board.name: 0C96W1
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd03/22/2022:br1.18:svnDellInc.:pnOptiPlex7060:pvr:rvnDellInc.:rn0C96W1:rvrA02:cvnDellInc.:ct3:cvr:sku085A:
dmi.product.family: OptiPlex
dmi.product.name: OptiPlex 7060
dmi.product.sku: 085A
dmi.sys.vendor: Dell Inc.

[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:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2000003

[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

[Leó Kolbeinsson (leok)]

Hello Olivier,

Attached is the tarball as per yr instructions in comment #3 = hope this helps.

[Olivier Gayot (ogayot)]

Thank you Leó! I appreciate the help.

Looking at the shared data, the tools that are normally used to determine the filesystem sizes have not run. I must have missed something in the profiling steps - which is bad.
In the meantime, it does make the theory that filesystem sizing is what takes forever more likely to be true.

I will update the script to make sure the filesystem sizing tools run when executing the profiling script.

Thanks again!