[SOLVED] Timed out for waiting the udev queue being empty: /dev/mapper/pve-roor does not exist

Egbert S

New Member
Oct 30, 2024
2
1
3
Hi.
I have added an 18 TB raid 5 drive. When I check to see if Proxmox recognises the drive I saw in the web GUI, I can initialise the drive. After clicking it and waiting for a few hours, nothing changed, and the task was still running.

In the console, there were a few errors (Unfortunately I did not take a picture) and by refreshing the web GUI it will no longer load. I thought proxmox crashed or something but after restarting the server I got this on boot:
Screenshot 2024-10-30 091511.png

I have tried the Rescue boot but It ends with this:
Screenshot 2024-10-30 092917.png
I don't know much about proxmox or Linux to understand what happened.

Booting into Windows works fine and all my drives are working except for the 18TB one which was not initialised.

I have tried this and grml gave me the 'Timed out for waiting the udev queue being empty' error as well on boot.
 
I was able to find a solution that somehow fix it. I was able to get the drive that proxmox was installed on mounted to a Ubuntu WSL and apply the fix.
 
Last edited:
  • Like
Reactions: leesteken

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!