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 - 5day
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.
12
Crash - 5day
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
3
mustlane @lemmy.zip - 5day
"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.
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
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
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
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
1
OneCardboardBox @lemmy.sdf.org - 5day
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.
4
colournoun @beehaw.org - 5day
Yeah this sounds like a disk/ssd hardware problem to me. Possibly only one part of the disk is bad and giving inconsistent results.
5
littleomid @feddit.org - 5day
Post mount, lsblk -f and cat /etc/fstab
3
data1701d (He/Him) - 4day
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.
3
boredsquirrel - 5day
Press Esc when booting to see text
2
mvirts @lemmy.world - 3day
Check your disk usage with df -h
When my machine gets weird it's always out of disk space.
crash_thepose in linux
Extremely slow boot time
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!
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
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.
https://hastebin.ianhon.com/2b4
can you post
journalctl -b0andsystemd-analyze blameresults from after a successful boot. i have broken and fixed my own systems countless ways so maybe i'll spot somethinghttps://hastebin.ianhon.com/fc2c
thanks, can you please give me the output of
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
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 tryBased 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.
Post mount, lsblk -f and cat /etc/fstab
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 todev-mapper-data\x2droot.device; our drives are just called different things) only takes 1.074 seconds for me, whilelvm2-monitor.serviceonly 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.
Press Esc when booting to see text
Check your disk usage with df -h
When my machine gets weird it's always out of disk space.