Search results

Hi! I'm on it, already reviewing the 'blame' output. I can confirm udevadm settle is the real culprit, and it is mostly occurring when someone leaves an iODD "multi image" USB3 disk plugged. I think any drive that is dying/faulty will also cause this issue, or any controller that responds in...

How can we diagnose what is causing the udevadm settle to fail? I'm on this boat too now, unfortunately.

How did you identify the disk and why was it hanging boot??

Quick update: It might not be the culprit. The symptoms are: all requests time out for the Storage tabs (cannot access anything at all), or reports 'communication failure'. No NFS in use either.

Just narrowed down my search for the culprit of my boot issues to this: ░░ Subject: A start job for unit systemd-rfkill.socket has finished successfully ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit systemd-rfkill.socket has finished successfully...

I just found this thread after posting this: https://forum.proxmox.com/threads/vlan-aware-network-configuration-not-working.46930/ Also having similar issues.

Is there any properly consolidated documentation entry on how to backup and restore a system? I will be doing something similar as the OP to replace the SSD currently installed for another one with bigger capacity and better server capabilities.

I'm experiencing this on an up-to-date system. Did you ever manage to fix it? I have tried everything thinkable to no avail. The DHCP works, an IP is assigned to the interface by the kernel, but it seems something takes them down before anything can be done, so the state goes back to unconfigured.