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!

  • just_another_person@lemmy.world
    link
    fedilink
    arrow-up
    12
    ·
    1 个月前

    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.

    • Crash@lemmy.mlOP
      link
      fedilink
      arrow-up
      3
      ·
      1 个月前

      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

  • mustlane@lemmy.zip
    link
    fedilink
    arrow-up
    8
    ·
    edit-2
    1 个月前

    "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.

  • OneCardboardBox@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 个月前

    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.

    • colournoun@beehaw.org
      link
      fedilink
      arrow-up
      5
      ·
      1 个月前

      Yeah this sounds like a disk/ssd hardware problem to me. Possibly only one part of the disk is bad and giving inconsistent results.

  • sludgewife@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 个月前

    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

      • sludgewife@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        4
        ·
        1 个月前

        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

        • Crash@lemmy.mlOP
          link
          fedilink
          arrow-up
          1
          ·
          1 个月前

          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.

      • Crash@lemmy.mlOP
        link
        fedilink
        arrow-up
        1
        ·
        1 个月前

        I am currently on this computer but booted into an old kernal which was still slow to load but eventually got me on

  • data1701d (He/Him)@startrek.website
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 个月前

    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.

    • Crash@lemmy.mlOP
      link
      fedilink
      arrow-up
      1
      ·
      1 个月前

      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?

  • mvirts@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    1 个月前

    Check your disk usage with df -h

    When my machine gets weird it’s always out of disk space.