Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Initramfs: "triggering uevents" suddenly takes a really long time

+0
−0

Early in boot, after triggering uevents but before the encrypt hook (decrypting drives) my system takes a very long time, over a minute. Actually, I bet it takes 90 seconds which is the typical default for how long systemd will wait on something before timing out.

I get no error message, just a delay. After the encrypt hook everything runs normally.

I think this must be the initramfs because my actual drive is not unlocked at that point. In /etc/mkinitcpio.conf I have:

HOOKS=(base udev keyboard autodetect modconf block encrypt lvm2 filesystems resume fsck)

This used to not be a problem, but began 1 months ago or so after an update. I am on Arch with 6.6.32-1-lts kernel.

What's the problem? How do I troubleshoot it?


Additional troubleshooting information will be added below.

$ systemd-analyze time
Startup finished in 2min 23.672s (kernel) + 17.010s (userspace) = 2min 40.683s
graphical.target reached after 17.010s in userspace.

But in systemd-analyze blame output the top one is just 8sec for the network, so it does not appear to look at the kernel.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

0 answers

Sign up to answer this question »