block probing crashed with TimeoutError

[geole0]

Hello
It is on the beginning of the installation.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: subiquity (unknown)
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CasperVersion: 1.496
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
Date: Sun Apr 14 16:21:46 2024
ExecutablePath: /snap/ubuntu-desktop-bootstrap/113/bin/subiquity/subiquity/cmd/server.py
InterpreterPath: /snap/ubuntu-desktop-bootstrap/113/usr/bin/python3.10
LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240412)
MachineType: TOSHIBA SATELLITE S70t-A
ProcAttrCurrent: snap.hostname-desktop-bootstrap.subiquity-server (complain)
ProcCmdline: /snap/hostname-desktop-bootstrap/113/usr/bin/python3.10 -m subiquity.cmd.server --use-os-prober --storage-version=2 --postinst-hooks-dir=/snap/hostname-desktop-bootstrap/113/etc/subiquity/postinst.d
ProcEnviron:
 LANG=C.UTF-8
 LD_LIBRARY_PATH=<set>
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash
Python3Details: /usr/bin/python3.12, Python 3.12.2, python3-minimal, 3.12.2-0ubuntu2
PythonDetails: N/A
SnapChannel:

SnapRevision: 113
SnapUpdated: False
SnapVersion: 0+git.4fb1e2ee
SourcePackage: subiquity
Title: block probing crashed with TimeoutError
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/18/2014
dmi.bios.release: 1.30
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.30
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name1
dmi.board.vendor: Type2 - Board Vendor Name1
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.ec.firmware.release: 1.30
dmi.modalias: dmi:bvnInsydeCorp.:bvr1.30:bd04/18/2014:br1.30:efr1.30:svnTOSHIBA:pnSATELLITES70t-A:pvrPSKN6E-01C00KFR:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKN6E:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE S70t-A
dmi.product.sku: PSKN6E
dmi.product.version: PSKN6E-01C00KFR
dmi.sys.vendor: TOSHIBA

[geole0 (geole0)]

The contents of the disk before installation
ubuntu@ubuntu:~$ sudo fdisk -l /dev/sdc
Disk /dev/sdc: 465.76 GiB, 500107861504 bytes, 976773167 sectors
Disk model: Slim SL
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 01BBDAF6-549A-479C-BCD2-9D07EE63AAB1

Device Start End Sectors Size Type
/dev/sdc1 2048 2203647 2201600 1G EFI System
/dev/sdc2 2203648 6397951 4194304 2G Linux filesystem
/dev/sdc3 6397952 976771071 970373120 462.7G Linux filesystem

[Olivier Gayot (ogayot)]

Hi geole0,

Thank you for your reports. Block probing timeouts are a common issue. Sadly, the logs are not captured in case of timeouts ; and this is something we would like to address in the future. Also I would like to include a script to gather some metrics.

There are two features of block probing that we know are likely to cause timeouts:

 * OS discovery using os-prober
 * Computation of filesystem minimum sizes

These actions are executed not only on the available disks, but also on the installation media (e.g., USB drive) ; so the presence of multiple partitions on the installation media (or an overall slow installation media) can increase the chance of timeouts.

Thanks,
Olivier

[geole0 (geole0)]

Hello.
i have multiples O.S.
One is on Btrfs..
My live USB is ventoy with an user NTFS partition.
If you have i script, i can exécute it.

And two windows are not detected
time sudo os-prober >os-prober.log

real 0m58,159s
user 0m0,011s
sys 0m0,007s
a@p:~$