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.
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