Re: udevadm: Failed to scan devices: Input/output error

[Lennart Poettering <lennart@xxxxxxxxxxxxxx>]

On Mi, 30.03.22 19:23, Belal, Awais (Awais_Belal@xxxxxxxxxx) wrote:

> Now, the system boots just fine on some attempts while on others it takes quite a lot of time to boot with logs such as
>
>
> Starting version 244
> Failed to scan devices: Input/output error
>   WARNING: Device /dev/ram0 not initialized in udev database even after waiting 10000000 microseconds.
>   WARNING: Device /dev/mmcblk0 not initialized in udev database even after waiting 10000000 microseconds.
>   WARNING: Device /dev/ram1 not initialized in udev database even after waiting 10000000 microseconds.
>   WARNING: Device /dev/mmcblk0p1 not initialized in udev database
> even after waiting 10000000 microseconds.

Which udevadm command is this from? The udevadm trigger invocation we
do during boot?

can you reproduce this if you trigger manually? If you strace, do you
see where the EIO comes from?

Lennart

--
Lennart Poettering, Berlin