Check your disk usage with df -h
When my machine gets weird it's always out of disk space.
this post was submitted on 07 Dec 2025
27 points (96.6% liked)
Linux
60185 readers
621 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 6 years ago
MODERATORS
I'm agreeing with other people; there's probably a drive issue that the shop didn't catch.
On my machine, those two services that take 30 seconds for you do not take nearly that long for me. dev-mapper-DebianVolume\x2dDebianMain.device (which is equivalent to dev-mapper-data\x2droot.device; our drives are just called different things) only takes 1.074 seconds for me, while lvm2-monitor.service only takes 357 milliseconds.
I've only ever seen Linux boots take this long when either a drive failed or I accidentally formatted a drive that's in my fstab, causing it to fail to mount and eventually landing me in a recovery shell. At that point, I'd either use the recovery shell or a USB to edit the fstab.
Next time you boot in, check to see if all your drives are showing up, check disk health, etcetera. Also, although this likely won't solve the problem, check that your drive connections are well-seated.
sorry can you explain to me what you mean by "a drive issue that the shop didn't catch? " , and how would i check if my drives are showing up? If i am able to get into oldkernal just fine and its just the new kernal thats causing problems does that mean anything?
I’d just recommend checking hard drive SMART scores and stuff like that. Maybe run a memory test as well.
Post mount, lsblk -f and cat /etc/fstab
Hit ESC during boot and watch the boot logs to see what's hanging. Some systemd service is taking awhile and doesn't have a sensible timeout. Probably network.
i was able to get into my old kernel and it says in the journal "failed to start application launched by gnome session binary" and then when i went into recovery mode it showed something about caspermdcheck service failing
"systemd-analyze blame didn't give me any helpful information
And what exactly did it give you? Could you copy-paste the output of that command (also known as "stdout")?
EDIT: It seems that you made the same post 2 times. Ideally, you should delete one of them.
Based on your systemd output, it looks like the system is taking a long while to decrypt your drive. Is it a spinning disk, or an SSD?
I'm not sure if the PC repair shop specifically checked your drive, but it might be worth swapping out for another. Or maybe run some speed tests and/or diagnostics to see if there's something funky going on.
You could also try an unencrypted install to see if the problem persists.
Yeah this sounds like a disk/ssd hardware problem to me. Possibly only one part of the disk is bad and giving inconsistent results.
can you post journalctl -b0 and systemd-analyze blame results from after a successful boot. i have broken and fixed my own systems countless ways so maybe i'll spot something
you can also journalctl -b0 -p4 to show only high priority messages. that would help too
https://pastebin.com/6ih7pHwZ like this?
it's very hard to decipher. the lines are right-truncated like you just copy-pasted from the terminal (the lines end in > which is less's sigil for "more content to the right"). you can make a pastebin from command output. to capture any command as a paste try
journalctl -b0 -p4 | curl -s -F "content=<-" https://dpaste.com/api/v2/
the part after the | comes from here:
you can put anything before | to capture it to dpaste. check it for sensitive information first!
from what i can see though, your nvme is behaving strangely. it may be related to power saving settings. try these settings from the Arch wiki:
https://wiki.archlinux.org/title/Solid_state_drive/NVMe#Troubleshooting
do you boot from the nvme?
Sorry I'm a total novice, what would have been the better way to share my log aside from copy and pasting?
no worries, i gave a suggestion in my comment:
journalctl -b0 -p4 | curl -s -F "content=<-" https://dpaste.com/api/v2/
that captures the output from journalctl -b0 -p4 and sends it to dpaste.com. it will print out a URL to the result. give that a try
journalctl -b0 -p4 | curl -s -F "content=<-" https://dpaste.com/api/v2/
sorry for the delay in response. Thank you for sharing this! here is my dpaste. https://dpaste.com/36EK4V3KR . Thanks for helping me.
no worries! i'm not the fastest to respond myself. i do want to help though. to explain the command,
journalctlsearches the journal, a database of messages from the units on your system managed by journald-b0means "this boot's messages", not the last boot or the one before...-p4' means "WARNING (4) or higher" (3, 2, 1, or 0). these priority levels are pretty old, long before my time. you can see them inman syslog`, but 0 is "alert" and 7 is "debug"
i say all that because i naively hoped a malfunction on your system would appear as a high-priority message in the journal, and i wanted to spare you the back-and-forth that this kind of troubleshooting usually entails. in this case, though, i didn't really see anything in those logs, so i suspect the culprit has been filtered out.
i will keep trying my best to help, don't worry, but i understand if you get fatigued and just want to move on.
there are some odd gaps in the logs where i can't tell what's happening. now that you know how to send logs to something like dpaste, let's open the floodgates. i don't mind wading through a sea of logs to find something (kind of my day job too)
to give the kernel's account of what happened:
dmesg -H | curl -s -F "content=<-" https://dpaste.com/api/v2/
that's everything from the start of the system to now, so it's best if you do it soon after booting.
finally, i had you filter to WARNING (4) and above with -p4 but it didn't show anything. how about...everything?
journalctl -b0 | curl -s -F "content=<-" https://dpaste.com/api/v2/
that will be a lot of information but it should be informative!
thanks, can you please give me the output of
journalctl -b0 -u systemd-modules-load
i'm curious why it's taking 30s. maybe the other two services as well
the dmesg you posted is very truncated, just like a screenful of info. you can usually pipe command output to curl with these pastebin sites. i understand if you're concerned about sensitive info in dmesg though
j@pop-os:~$ journalctl -b0 -u systemd-modules-load
Dec 07 12:45:50 pop-os systemd-modules-load[614]: Inserted module 'lp' Dec 07 12:45:50 pop-os systemd-modules-load[614]: Inserted module 'ppdev' Dec 07 12:45:50 pop-os systemd-modules-load[614]: Inserted module 'parport_pc' Dec 07 12:45:50 pop-os systemd-modules-load[614]: Inserted module 'msr' Dec 07 12:45:50 pop-os systemd-modules-load[614]: Inserted module 'kyber_iosched' Dec 07 12:45:50 pop-os systemd[1]: Finished Load Kernel Modules.
I am currently on this computer but booted into an old kernal which was still slow to load but eventually got me on
Press Esc when booting to see text