You are not logged in.
Hey all,
Rebuilt my system last week, specs are in the sig, and the initial boot times with the corsair was 7-8 seconds. However, after a reboot a couple days ago, my boot times are now 17-20 seconds. Nothing on my system has changed.
I even commented out the non SSD mount points I had (additional 2TB drive) in fstab, that didn't help.
The drives are formatted with GPT and I am booting via mbr. I ran fstrim, didn't help, shaved off ~1 second from the boot time.
Here are my benchmarks:
hdparm:
hdparm -Tt /dev/sda
/dev/sda:
Timing cached reads: 9804 MB in 2.00 seconds = 4906.19 MB/sec
Timing buffered disk reads: 1056 MB in 3.00 seconds = 351.46 MB/sec
and dd:
write:
dd if=/dev/zero of=tempfile bs=1M count=1024 conv=fdatasync,notrunc
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB) copied, 2.76098 s, 389 MB/s
read:
dd if=tempfile of=/dev/null bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB) copied, 2.63493 s, 408 MB/s
[drave@dugr ssdspeed]$ dd if=tempfile of=/dev/null bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB) copied, 0.223908 s, 4.8 GB/s
what other info can I look at on my system? what other info can I provide here to help?
--nixIT
ASRock X570 PG VELOCITA AM4 AMD X570 | AMD Ryzen 5900x | 128GB G.SKILL RipjawsV | ASRock Radeon RX 6700 XT Challenger D
Offline
% systemd-analyze blame
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
systemd-analyze blame
2743ms netcfg.service
360ms swapfile.swap
333ms systemd-udev-trigger.service
250ms systemd-binfmt.service
230ms mnt-popp0rn.mount
197ms systemd-udevd.service
196ms systemd-vconsole-setup.service
190ms dev-mqueue.mount
177ms sys-kernel-config.mount
174ms mnt-movies.mount
170ms systemd-sysctl.service
161ms dev-hugepages.mount
153ms systemd-fsck@dev-disk-by\x2duuid-b3042907\x2da31a\x2d486b\x2da8e1\x2d7d3f984a799b.service
111ms sys-kernel-debug.mount
85ms accounts-daemon.service
73ms mnt-dugrdata.mount
67ms systemd-remount-fs.service
56ms alsa-restore.service
53ms gdm.service
51ms systemd-random-seed-load.service
47ms systemd-fsck@dev-disk-by\x2duuid-4849eab4\x2d0010\x2d4f1a\x2dad3b\x2d1e80b6587d8c.service
47ms polkit.service
46ms systemd-logind.service
43ms ntpd.service
40ms proc-sys-fs-binfmt_misc.mount
37ms tmp.mount
29ms udisks2.service
23ms colord.service
18ms systemd-tmpfiles-clean.service
17ms mnt-dugrssd.mount
16ms upower.service
14ms systemd-tmpfiles-setup.service
7ms systemd-journal-flush.service
7ms rtkit-daemon.service
5ms systemd-user-sessions.service
2ms sys-fs-fuse-connections.mount
why is netcfg in the thousandths of milliseconds? is that normal?
--nixIT
ASRock X570 PG VELOCITA AM4 AMD X570 | AMD Ryzen 5900x | 128GB G.SKILL RipjawsV | ASRock Radeon RX 6700 XT Challenger D
Offline
Yes. Mine is around 3 sec.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Are the speeds I posted in the first post decent speeds for the SSD?
ASRock X570 PG VELOCITA AM4 AMD X570 | AMD Ryzen 5900x | 128GB G.SKILL RipjawsV | ASRock Radeon RX 6700 XT Challenger D
Offline
% systemd-analyze
Startup finished in 2270ms (kernel) + 90027ms (userspace) = 92297ms
% systemd-analyze blame
3487ms netctl@static.service
266ms psd.service
250ms systemd-fsck@dev-disk-by\x2dlabel-data.service
143ms var.mount
100ms systemd-udev-trigger.service
90ms ufw.service
87ms mnt-data.mount
77ms lm_sensors.service
76ms systemd-modules-load.service
65ms systemd-fsck@dev-disk-by\x2dlabel-var.service
63ms systemd-random-seed-load.service
58ms systemd-logind.service
53ms ntpd.service
52ms psd-resync.service
40ms systemd-tmpfiles-setup.service
38ms systemd-tmpfiles-clean.service
37ms sys-kernel-debug.mount
37ms systemd-sysctl.service
36ms systemd-remount-fs.service
34ms systemd-vconsole-setup.service
34ms systemd-udevd.service
33ms dev-mqueue.mount
33ms gpm.service
33ms cpupower.service
31ms dev-hugepages.mount
31ms tmp.mount
27ms systemd-fsck@dev-disk-by\x2dlabel-homes.service
24ms polkit.service
23ms systemd-user-sessions.service
18ms systemd-fsck@dev-disk-by\x2dlabel-boot.service
15ms udisks2.service
11ms systemd-journal-flush.service
8ms rtkit-daemon.service
8ms upower.service
7ms boot.mount
7ms scratch.mount
6ms home.mount
1ms sys-kernel-config.mount
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Here is mine:
Startup finished in 1745ms (kernel) + 3911ms (userspace) = 5656ms
Why would it be taking ~18 seconds from grub menu to login screen? I'm running cinnamon with gdm. When I first installed arch, and for several days after, the boot was 7-8 seconds, not's in double+ that.
--nixIT
ASRock X570 PG VELOCITA AM4 AMD X570 | AMD Ryzen 5900x | 128GB G.SKILL RipjawsV | ASRock Radeon RX 6700 XT Challenger D
Offline
If you don't want your network management daemon to report taking so long, you should use net-auto-wireless (or in the case of netctl, netctl-auto@.service). Of course, the time it takes to connect will be the same, it just won't wait for the connection in order to complete the boot.
Overall though, you have not really provided enough information to debug this problem.
Offline
If you don't want your network management daemon to report taking so long, you should use net-auto-wireless (or in the case of netctl, netctl-auto@.service). Of course, the time it takes to connect will be the same, it just won't wait for the connection in order to complete the boot.
Overall though, you have not really provided enough information to debug this problem.
This is where I'm a n00b, Not sure what other info you need to troubleshoot. What info would help diagnose this issue?
My fstab looks like this:
# /dev/sda1
UUID=fc9ee2c5-0f29-4184-8965-c079e26165ff / ext4 rw,relatime,data=ordered 0 1
# /dev/sda3
UUID=4849eab4-0010-4f1a-ad3b-1e80b6587d8c /mnt/ssd ext4 rw,relatime,data=ordered 0 2
/swapfile none swap defaults 0 0
# /dev/sdb1
UUID=b3042907-a31a-486b-a8e1-7d3f984a799b /mnt/data ext4 rw,relatime,data=ordered 0 2
//nas/movies /mnt/movies cifs uid=nixit,credentials=/mnt/data/docs/.creds 0 0
//nas/backup /mnt/backup cifs uid=nixit,credentials=/mnt/data/docs/.creds 0 0
sda is my SSD
--nixIT
Last edited by nixIT (2013-03-17 18:01:22)
ASRock X570 PG VELOCITA AM4 AMD X570 | AMD Ryzen 5900x | 128GB G.SKILL RipjawsV | ASRock Radeon RX 6700 XT Challenger D
Offline
Hmmmm.... "/mnt/movies" eh? The output of "systemd-analyze blame" seems to indicate that you have
... 230ms mnt-popp0rn.mount ...
That's funny.
Anyway, I would say you need to pore over your logs at the very least to see if there is any relevant information about what is going on. It is all time stamped so you can pretty easily see where your sh*t is going wrong. I would venture to guess that it has nothing to do with the SSD and everything to do with how something is configured.
Keep in mind that access to the systemd journal (journalctl) is controlled by the group "systemd-journal". So if you are not part of that group (and don't want to be for whatever reason) you need to view the journal with superuser permissions. I can't even begin to tell you the number of times people come back here saying that their journal included a whole 5 lines.
So look through that and post anything that you might think seems to be related to the issue. Please do not just post your entire journal here... that just kind of sucks.
Offline
@WonderWoofy,
Thanx for the info. I'm not sure what logs I should be looking in, but I will look through the log folder and see what I can figure out, I will also look at the journalctl file.
--nixIT
ASRock X570 PG VELOCITA AM4 AMD X570 | AMD Ryzen 5900x | 128GB G.SKILL RipjawsV | ASRock Radeon RX 6700 XT Challenger D
Offline
Your logs are the journal.
Offline
Are the speeds I posted in the first post decent speeds for the SSD?
Startup finished in 1153ms (kernel) + 2070ms (userspace) = 3223ms
I'm running just a normal Kingston 120gb SSD with i7-3517U and 4gb ram...good but by no means a speed demon in this tiny ultrabook.
I'd be interested to see what's causing this...but
Here is mine:
Startup finished in 1745ms (kernel) + 3911ms (userspace) = 5656ms
Why would it be taking ~18 seconds from grub menu to login screen? I'm running cinnamon with gdm. When I first installed arch, and for several days after, the boot was 7-8 seconds, not's in double+ that.
5.6 seconds is still pretty fast?
Does running TRIM make a difference (add discard option to fstab)?
P.S. net-auto-wireless takes 147ms for me, might be worth looking into to cut down the time
Last edited by thesystematic (2013-03-18 10:23:26)
Offline
I'm also using an SSD, these are my times and my fstab.
systemd-analyze (& blame)
[mz@gantz ~]$ systemd-analyze
Startup finished in 4538ms (kernel) + 3566ms (userspace) = 8104ms
[mz@gantz ~]$ systemd-analyze blame
2160ms httpd.service
410ms NetworkManager.service
235ms systemd-fsck@dev-sdb1.service
179ms systemd-udev-trigger.service
173ms avahi-daemon.service
134ms systemd-logind.service
112ms systemd-fsck@dev-sdd1.service
103ms systemd-vconsole-setup.service
94ms polkit.service
83ms systemd-remount-fs.service
83ms systemd-sysctl.service
80ms dev-hugepages.mount
80ms udisks2.service
77ms dev-mqueue.mount
71ms media-datos.mount
61ms colord.service
60ms sys-kernel-config.mount
57ms sys-kernel-debug.mount
52ms systemd-random-seed-load.service
40ms media-zzz.mount
40ms systemd-udevd.service
34ms tmp.mount
27ms ntpd.service
17ms systemd-tmpfiles-setup.service
10ms systemd-user-sessions.service
10ms upower.service
9ms rtkit-daemon.service
8ms systemd-journal-flush.service
2ms sys-fs-fuse-connections.mount
fstab (sda is ssd, others are traditional)
tmpfs /tmp tmpfs nodev,nosuid 0 0
/dev/sda1 / ext4 defaults,noatime,discard 0 1
/dev/sdb1 /media/datos ext4 defaults 0 2
/dev/sdd1 /media/zzz ext4 defaults 0 2
It could be faster, but I'm pretty happy with my 8 to 9 sec boot time.
Offline
There is a long thread for boot times with hints. If you include the timestamp hook in mkinitcpio you'll get a metric of how long is spent in the initramfs. You can also streamline your mkinitcpio.conf to shave a second or two. mznervedies, you'd probably benefit from this and probably shave a couple of seconds, but when that is a substantial portion of your boot time, that's a good shaving.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
Your logs are the journal.
Here is a snippet of my log file, and if I'm reading it correctly, there is a 6 second gap at the 17:43:46 mark. This is definitely a delay, but I have no idea why, or if this is even the right spot.
Mar 18 13:43:44 nixted systemd[1]: Started RealtimeKit Scheduling Policy Service.
Mar 18 13:43:44 nixted rtkit-daemon[630]: Successfully made thread 629 of process 629 (/usr/bin/pulseaudio) owned by '120' high priority at nice level -11.
Mar 18 13:43:44 nixted rtkit-daemon[630]: Supervising 1 threads of 1 processes of 1 users.
Mar 18 17:43:46 nixted systemd[1]: Time has been changed
Mar 18 17:43:46 nixted systemd[1]: systemd-tmpfiles-clean.timer: time change, recalculating next elapse.
Mar 18 17:43:52 nixted pulseaudio[629]: [pulseaudio] sink.c: Default and alternate sample rates are the same.
Mar 18 17:43:52 nixted rtkit-daemon[630]: Warning: Reached burst limit for user '120', denying request.
Mar 18 17:43:52 nixted rtkit-daemon[630]: Warning: Reached burst limit for user '120', denying request.
Mar 18 17:43:52 nixted rtkit-daemon[630]: Warning: Reached burst limit for user '120', denying request.
Mar 18 17:43:52 nixted rtkit-daemon[630]: Warning: Reached burst limit for user '120', denying request.
I am going to disable gdm and see how long I get to go from grub to the cli login, this should rule out the DE, I would assume.
EDIT:
boot time from grub to CLI login = 6 seconds
boot time from grub to cinnamon login = 16 seconds
So why would it take cinnamon 10 seconds to get to login screen?
Last edited by nixIT (2013-03-18 22:20:11)
ASRock X570 PG VELOCITA AM4 AMD X570 | AMD Ryzen 5900x | 128GB G.SKILL RipjawsV | ASRock Radeon RX 6700 XT Challenger D
Offline
The burst limit is the number of times a given service can write to the journal in a given amount of time. So rtkit-daemon is trying to clog up the journal apparently. Why this is happening, I have no idea. But rtkit-daemon is a dependency of pulseaudio. So there must be something wonky in the way you have pulseaudio configured.
Offline
thanx for the followup. I don't think I explicitly installed pulseaudio, as I normally just use alsa. I've never configured pulseaudio, at least not knowingly.
Where would be a good place to start looking?
--nixIT
ASRock X570 PG VELOCITA AM4 AMD X570 | AMD Ryzen 5900x | 128GB G.SKILL RipjawsV | ASRock Radeon RX 6700 XT Challenger D
Offline
If you are using gnome, you are using pulseaudio. There are ways of not using pulseaudio with gnome, but typically they are not worth the hassle (you can create an empty package that provides 'pulseaudio'). I have been using pulseaudio for a couple months maybe, and it works great for me. Though I was really apprehensive after having trouble with it in the past. So I read through the wiki page really carefully and tried my hardest to get a grasp of what I was doing first.
Maybe go read through the documentation and wiki pages for pulseaudio and see if anythign jumps out at you?
Offline
If you are using gnome, you are using pulseaudio. There are ways of not using pulseaudio with gnome, but typically they are not worth the hassle (you can create an empty package that provides 'pulseaudio'). I have been using pulseaudio for a couple months maybe, and it works great for me. Though I was really apprehensive after having trouble with it in the past. So I read through the wiki page really carefully and tried my hardest to get a grasp of what I was doing first.
Maybe go read through the documentation and wiki pages for pulseaudio and see if anythign jumps out at you?
Thanx, I'm on the pulseaudio wiki now. thanx.
--nixIT
EDIT. think there may be some other issue going on. I killed pulseaudio and rebooted to see the time, I could not log into GDM, would enter in my password, and the screen would just sit there, and sit there. I click cancel and it went back to the login screen. tried again, same thing. CTRL-ALT-F2, went to terminal and logged in no problem. rebooted and could log in this time.
looks like I'm in for another arch install. ugg, here goes an afternoon of installing.
Last edited by nixIT (2013-03-19 01:28:42)
ASRock X570 PG VELOCITA AM4 AMD X570 | AMD Ryzen 5900x | 128GB G.SKILL RipjawsV | ASRock Radeon RX 6700 XT Challenger D
Offline
Just installed linux mint on my ssd and boot times are 8 seconds. The only thing I can think of, is that the drives were formatted not a gpt, but mbr. going to run for a couple days with mint to see if it changes. if not, going to re-install arch.
ASRock X570 PG VELOCITA AM4 AMD X570 | AMD Ryzen 5900x | 128GB G.SKILL RipjawsV | ASRock Radeon RX 6700 XT Challenger D
Offline
Just installed linux mint on my ssd and boot times are 8 seconds. The only thing I can think of, is that the drives were formatted not a gpt, but mbr. going to run for a couple days with mint to see if it changes. if not, going to re-install arch.
I am not sure what you mean with this eight second boot time for Linux Mint. Is that good or bad, and what does GPT vs MBR have to do with it?
If the point of having an Arch Linux installation (for you) is that you want to learn, reinstallation is never the right thing to do, as it will not teach you anything.
Though if your only motivation for having an Arch Linux installation is a fast boot time... then by all means, reinstall.
Offline
I do want to learn, I've learned much while using arch. however, I wanted to give a final test to see if the drive was not performing to what it should, since arch all of a sudden lost speed during boot. I have an SSD, a benefit of and SSD is how quick it is, it didn't seem that quick to me, things seemed to be slow, even arch updates. Installing Linux mint allowed me a quick way to see if the drive is running optimally.
As I stated, I will be going back to arch, and if the speed of the boot or drive seems to slow down, THEN I will investigate further.
ASRock X570 PG VELOCITA AM4 AMD X570 | AMD Ryzen 5900x | 128GB G.SKILL RipjawsV | ASRock Radeon RX 6700 XT Challenger D
Offline
Oh, I see. You actually replaced Arch with Mint. That would definitely require a reinstallation now wouldn't it?
Sorry I didn't get the gist of your post there.
Just an FYI, there should be no difference (speed wise) in terms of MBR vs GPT partitioning. Though I would definitely recommend GPT always these days. Working around the primary/extended partition mess is just not worth the effort for me when there is a better solution present.
Offline
NP, even the wife says I'm having a hard time communication tontie. uggg, been a long month at work.
I agree with GPT. I had the arch install as GPT, first GPT partition actually. question on that, if I have a second drive 2TB, do I partition that one as well with GPT? I think I did, and if I didn't, would that have any impact?
ASRock X570 PG VELOCITA AM4 AMD X570 | AMD Ryzen 5900x | 128GB G.SKILL RipjawsV | ASRock Radeon RX 6700 XT Challenger D
Offline