after cloning pop os hdd to ssd to boot it takes 3min and 19 sec

yowan4real

New Member
Joined
Oct 3, 2022
Messages
10
Reaction score
2
Credits
100
I have a dell inspiron 15 3521 running Pop OS 22.04, upgraded ram to 16gb and 320hdd to 512gb ssd. The problem is when i cloned it it boots super slow and this is what the command shows:

$ systemd-analyze
Startup finished in 1min 30.034s (firmware) + 460ms (loader) + 7.382s (kernel) + 1min 41.956s (userspace) = 3min 19.832s
graphical.target reached after 1min 41.913s in userspace

Please help and thanks in advance
 


Most ssd's work fine in Linux, some not so good and a few not at all, sounds like a possible fault in connections and its not receiving the max speed from the bus.
 
What's the output of blame?

Code:
systemd-analyze blame

We should only really need the top-most entries from that command, the ones that take the longest. So, maybe the top 10 or 15, depending.
 
Most ssd's work fine in Linux, some not so good and a few not at all, sounds like a possible fault in connections and its not receiving the max speed from the bus.
I ended up reinstalling Pop Os and it got way more speed.
$ systemd-analyze
Startup finished in 4.335s (firmware) + 456ms (loader) + 7.919s (kernel) + 14.288s (userspace) = 27.000s
graphical.target reached after 14.241s in userspace
 
What's the output of blame?

Code:
systemd-analyze blame

We should only really need the top-most entries from that command, the ones that take the longest. So, maybe the top 10 or 15, depending.

This was after reinstalling

Code:
$ systemd-analyze blame
9.896s plymouth-quit-wait.service
7.208s NetworkManager-wait-online.service
2.390s accounts-daemon.service
2.167s dev-sda3.device
1.314s networkd-dispatcher.service
935ms ua-timer.service
806ms networking.service
802ms bluetooth.service
777ms udisks2.service
777ms upower.service
763ms rtkit-daemon.service
739ms systemd-logind.service
731ms e2scrub_reap.service
561ms ModemManager.service
552ms avahi-daemon.service
525ms NetworkManager.service
517ms systemd-udev-trigger.service
507ms apport.service
495ms apparmor.service
443ms com.system76.PowerDaemon.service
389ms switcheroo-control.service
372ms polkit.service
364ms [email protected]
343ms chrony.service
317ms systemd-journald.service
313ms secureboot-db.service
270ms rsyslog.service
262ms keyboard-setup.service
247ms thermald.service
245ms gpu-manager.service
242ms systemd-resolved.service
236ms wpa_supplicant.service
229ms systemd-udevd.service
203ms cups.service
192ms gdm.service
157ms packagekit.service
136ms alsa-restore.service
133ms systemd-modules-load.service
103ms lvm2-monitor.service
96ms systemd-journal-flush.service
80ms dev-mqueue.mount
79ms dev-hugepages.mount
79ms sys-kernel-debug.mount
77ms sys-kernel-tracing.mount
72ms resolvconf-pull-resolved.service
69ms systemd-sysctl.service
67ms kmod-static-nodes.service
65ms [email protected]
64ms [email protected]
62ms systemd-tmpfiles-setup.service
61ms [email protected]
60ms systemd-tmpfiles-clean.service
52ms colord.service
50ms dbus-broker.service
49ms systemd-sysusers.service
47ms com.system76.SystemUpdater.service
44ms openvpn.service
41ms systemd-remount-fs.service
39ms systemd-tmpfiles-setup-dev.service
38ms systemd-random-seed.service
33ms finalrd.service
31ms plymouth-read-write.service
31ms console-setup.service
28ms systemd-update-utmp.service
25ms [email protected]
25ms systemd-backlight@backlight:intel_backlight.service
23ms systemd-user-sessions.service
23ms boot-efi.mount
21ms plymouth-start.service
20ms sys-fs-fuse-connections.mount
20ms recovery.mount
18ms systemd-update-utmp-runlevel.service
18ms setvtrgb.service
17ms sys-kernel-config.mount
15ms ifupdown-pre.service
11ms ufw.service
10ms systemd-rfkill.service
6ms com.system76.Scheduler.service
74us blk-availability.service
 
Well, reinstalling will fix it. If I had to guess, and it's a bit of an educated guess, it would have been an fstab issue, looking for a drive identification that no longer existed. I'm reasonably confident that'd have been the biggest cause of the slowdown.
 
What did you use to clone the Drive. ?

Might be better to create an image of the HDD and put it on the SSD.
m1212.gif
 

Staff online

Members online


Latest posts

Top