Is this the right place to ask for help? Or is there another place? Anyways, feel free to delete this post if i’m in the wrong spot.
I use Pop OS on an Asus. Something has happened where i either have a 10 min plus boot time, or it doesn’t boot at all. I have reinstalled Pop OS twice (and used recovery mode) and even took it into a computer shop to see if there was something wrong with my hardware (there isn’t). When I first do a new install it will restart fine, but then it’ll be the next day when it will either take over 8 minutes to load, or it will be stuck on boot.
Right now it is stuck on boot. I can get into a live usb stick just fine. I have done systemanalyze blame, and it didn’t give me any helpful information. I have the same issue even if I try to press space bar and boot into an old kernel.
I should note that my computer has encryption enabled.
Any help would be awesome.
All hail the other linux noobs out there!
https://hastebin.ianhon.com/fc2c
I am currently on this computer but booted into an old kernal which was still slow to load but eventually got me on
thanks, can you please give me the output of
journalctl -b0 -u systemd-modules-loadi’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.
you can also
journalctl -b0 -p4to show only high priority messages. that would help toohttps://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 trythe part after the
|comes from here:https://dpaste.com/FZNXRMS75
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:
that captures the output from
journalctl -b0 -p4and sends it to dpaste.com. it will print out a URL to the result. give that a trysorry 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
-p4but 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!