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!

  • sludgewife@lemmy.blahaj.zoneEnglish
    1·
    6 days ago

    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

      • sludgewife@lemmy.blahaj.zoneEnglish
        1·
        18 hours ago

        no worries! i’m not the fastest to respond myself. i do want to help though. to explain the command,

        • journalctl searches the journal, a database of messages from the units on your system managed by journald
        • -b0 means “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 in man 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!