F5F Stay Refreshed Software Operating Systems Very long startup with Pop OS and Windows 10 installed

Very long startup with Pop OS and Windows 10 installed

Very long startup with Pop OS and Windows 10 installed

T
theseb44
Member
Find
70
03-11-2016, 04:15 AM
#1
I went through System76’s official instructions to dual-boot with W10, but the boot time was unusually long—about 1 minute and 30 seconds. When trying to launch Pop OS, it only took around 20 seconds, which was fast thanks to my SSD. I searched online for help but didn’t find a clear answer. I’m assuming there might be an issue with my partitions, though I’m not sure what’s going on.
Reply
Reply
T
theseb44
03-11-2016, 04:15 AM #1

I went through System76’s official instructions to dual-boot with W10, but the boot time was unusually long—about 1 minute and 30 seconds. When trying to launch Pop OS, it only took around 20 seconds, which was fast thanks to my SSD. I searched online for help but didn’t find a clear answer. I’m assuming there might be an issue with my partitions, though I’m not sure what’s going on.

Reply
Reply
D
dcanuso
Member
Find
108
03-12-2016, 01:11 PM
#2
It's odd, the analysis shows a complete pause of about a minute and twenty-nine seconds. The apparmor.service ended at 1.368 seconds, yet sysinit.target didn't begin until 1 minute and thirty seconds.
Reply
Reply
D
dcanuso
03-12-2016, 01:11 PM #2

It's odd, the analysis shows a complete pause of about a minute and twenty-nine seconds. The apparmor.service ended at 1.368 seconds, yet sysinit.target didn't begin until 1 minute and thirty seconds.

Reply
Reply
F
Flare_Chick
Member
Find
182
03-19-2016, 02:06 PM
#3
It looks like the site indicates sysinit.target waits a long time before starting, and checking logs might help. Try running systemd-analyze plot > systemd.svg for visual insight, though it may not be very useful. It seems more relevant to discuss on POP_OS Reddit, as this issue appears to be specific to that distribution. P.S. I’ve faced a similar problem with Pop too—after about 20 minutes and ten reboots, I finally switched because I needed to work.
Reply
Reply
F
Flare_Chick
03-19-2016, 02:06 PM #3

It looks like the site indicates sysinit.target waits a long time before starting, and checking logs might help. Try running systemd-analyze plot > systemd.svg for visual insight, though it may not be very useful. It seems more relevant to discuss on POP_OS Reddit, as this issue appears to be specific to that distribution. P.S. I’ve faced a similar problem with Pop too—after about 20 minutes and ten reboots, I finally switched because I needed to work.

Reply
Reply