Oddbean new post about | logout
▲ ▼
Miakoda | 3 months ago (raw) | export | reply | flag +1 
 My #Linux server has 3 kernels on it.
The oldest one stops booting, takes ages to error "timed out waiting for the udev queue being empty" 4 times, and then resumes. It's like 5 minutes waiting for this.
The other 2 newer kernels just keep repeating that error forever and never resume boot.

I have read many forums, tried many things, from noapic and nomodeset to turning crap off in BIOS. 
It's driving me nuts, as I can't remotely reboot it, it'd just go to the newest kernel and get stuck on it
▲ ▼
BootyDust | 3 months ago (raw) | root | parent | reply | flag 
 Good luck with your troubleshooting.

I don’t have any advice for you since I’ve not dealt with this specifically, but out of curiosity asked Llama 3.1 405b.
———————————————
The error message "timed out waiting for the udev queue being empty" during boot on a Linux server is usually related to the udev daemon, which is responsible for managing device events and handling device initialization.

When the system boots, udev is responsible for creating device files and initializing devices. If the udev queue is not empty within a certain time limit (usually 30 seconds), the system will timeout and display this error message.

There are several possible causes for this error:

1. **Slow or failing disk**: If the disk is slow or failing, it can cause the udev queue to timeout.
2. **Incorrect or missing device drivers**: If the device drivers are not correctly installed or are missing, it can cause the udev queue to timeout.
3. **udev configuration issues**: Misconfigured udev rules or incorrect udev settings can cause the udev queue to timeout.
4. **Resource constraints**: Insufficient system resources, such as RAM or CPU, can cause the udev queue to timeout.
5. **Filesystem issues**: Filesystem corruption or issues can cause the udev queue to timeout.

To troubleshoot this error, you can try the following:

1. **Check the system logs**: Check the system logs (e.g., /var/log/syslog or /var/log/messages) for any errors related to udev or device initialization.
2. **Run udevadm info**: Run the command `udevadm info --export-db` to check the udev database and look for any errors or issues.
3. **Check the disk**: Check the disk for any errors or issues using tools like `fsck` or `smartctl`.
4. **Verify device drivers**: Verify that the device drivers are correctly installed and configured.
5. **Increase the udev timeout**: You can increase the udev timeout by editing the `/etc/udev/udev.conf` file and adding the `udev_timeout` option.