Hi mpan, Am Mo., 21. Apr. 2025 um 23:51 Uhr schrieb mpan <archml-y1vf3...@mpan.pl>:
> > (…) > > This is about some error entries in the system journal, which I > encountered > > during copying this ISO image over. The respective transcripts are > provided > > inline, as well as attached in the form of plain text files. > > (…) > I believe this is unrelated to the copying process. Actually, I am certain that the behaviour was triggered *by the copying process*, as the log journal entries were reproducible by repeating the installation for a second time. > udevd stopped > responding for `WatchdogSec` seconds,⁽¹⁾ systemd restarted it. This kind > of reports are usually associated with some specific piece of hardware > leading to udevd lock-up, and no less often the bug is resolved in later > kernel releases. > The logs indicate some *failed attempts* to SIGABRT and then SIGKILL. Shortly after the completion of the operation (when the kernel emits sda: sda1 sda2), a log: systemd-udevd.service: Main process exited, code=killed, status=9/KILL can be spotted. Thus it is rather clear that the error is truly related to the ISO image installation to sda. Possibly the USB stick leads to such a kind of lock-up as you mentioned, while the copying process is underway? The actual *copying procedure* completed successfully. You may try passing `udev.log_level=debug` to kernel command-line > during boot. See if that produces any useful info, but also note that > this log level is very spammy. Hm, what should I look for? Best, Friedrich
