I have a message during boot that says " scanning Brtfs drives" or something like that. I don't have any drive in that format. Then it starts a "systemd-fsck" that hangs and prolong my boot time considerably.
I'm very interested in canceling this check but all the reccomendations that I have googled have failed like writing "fsck.mode=skip" in the kernel command line. HELP!!!
Post your fstab
Using nfs ?
How many hard drives ?
You can purge btrfs-tools, if you don't use it.
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/sda5 / ext4 defaults,noatime 0 0
/dev/sdc1 /media/Back_Up ntfs-3g defaults,locale=en_US.utf8 0 0
/dev/sdb1 /media/Storage ntfs-3g defaults,locale=en_US.utf8 0 0
/swapfile swap swap defaults 0 0
Just purged btrfs-tools, rebooted, but still hangs...
Actually it's " scanning for Brtfs drives", it looks, but unless you have one, doesn't find.
I've had systemd-fsck hang myself, but, only when it was fixing problems. It may not be fsck at all that's causing your problem. Here's the top of my systemd-analyze blame:
$ systemd-analyze blame
10.506s NetworkManager.service
10.270s ModemManager.service
6.130s systemd-fsck-root.service
5.942s preload.service
5.421s sensord.service
3.448s autofs.service
3.315s bootlogs.service
3.271s loadcpufreq.service
3.172s lightdm.service
2.763s avahi-daemon.service
It's the NetworkManager/ModemManager.service that is increasing my boot time. I can actually see it on the laptop. As soon as the wifi light comes on, the balance of boot time is short. Anyway, just an idea. That is, unless you're seeing error messages after systemd-fsck runs.
My results:
~$ systemd-analyze blame
31.762s systemd-udev-settle.service
762ms systemd-modules-load.service
647ms media-Storage.mount
315ms media-Back_Up.mount
284ms lvm2-activation-early.service
118ms keyboard-setup.service
115ms console-setup.service
108ms nfs-common.service
99ms ModemManager.service
91ms gpm.service
82ms loadcpufreq.service
68ms networking.service
59ms bootlogs.service
57ms preload.service
36ms lvm2-activation.service
34ms systemd-logind.service
27ms live-config.service
27ms console-kit-daemon.service
27ms systemd-udev-trigger.service
26ms rpcbind.service
24ms systemd-fsck-root.service
23ms polkitd.service
23ms irqbalance.service
22ms console-kit-log-system-start.service
22ms alsa-restore.service
22ms ifplugd.service
18ms lm-sensors.service
18ms cpufrequtils.service
18ms motd.service
16ms smartmontools.service
14ms kbd.service
14ms dev-mqueue.mount
14ms systemd-tmpfiles-setup-dev.service
13ms dev-hugepages.mount
12ms dns-clean.service
12ms systemd-sysctl.service
12ms sys-kernel-debug.mount
11ms ifup@eth0.service
11ms systemd-tmpfiles-setup.service
10ms pppd-dns.service
9ms rc-local.service
7ms keymap.service
7ms systemd-remount-fs.service
6ms upower.service
5ms systemd-user-sessions.service
5ms live.service
4ms systemd-udevd.service
4ms udev-finish.service
4ms systemd-journal-flush.service
4ms resolvconf.service
3ms live-tools.service
3ms swapfile.swap
3ms systemd-random-seed-load.service
3ms systemd-update-utmp-runlevel.service
2ms run-user.mount
2ms run-lock.mount
The problem has nothing to do with btrfs, but it does have something to do with connected drives or other hardware. For troubleshooting purposes, try these two things:
1. Post the output of blkid -c /dev/null -o list
2. In /etc/fstab, comment out the two ntfs formatted drives, and then try a reboot and see how long it takes.
Also, while you are editing /etc/fstab, the root device pass number (the final numeral) should be a "1" instead of "0".
FYI, note the systemd-udev-settle.service time on my little netbook with a SSD:
root@tosh205:/# systemd-analyze blame
5.817s nmbd.service
5.759s winbind.service
5.328s samba-ad-dc.service
3.494s wicd.service
1.639s systemd-udev-settle.service
1.555s smbd.service
1.513s loadcpufreq.service
1.310s console-kit-daemon.service
1.113s siguibui.service
847ms lightdm.service
818ms avahi-daemon.service
809ms systemd-logind.service
799ms wpa_supplicant.service
776ms upower.service
756ms rtkit-daemon.service
With a hdd it will be longer -- maybe 10 or 15s.
# blkid -c /dev/null -o list
device fs_type label mount point UUID
-------------------------------------------------------------------------------
/dev/sdc1 ntfs Back-Up /media/Back_Up 4CE077F63265B98C
/dev/sdc2 swap (not mounted) 321355cd-0908-4b71-87a7-d5602526a308
/dev/sdb1 ntfs Storage /media/Storage 6876C3BE5BDF1565
/dev/sda1 ext2 (not mounted) 6067123f-9b75-4851-95b8-13ec54e40b18
/dev/sda2 ext4 (not mounted) 989a68dd-0b56-4769-ad56-58231befa019
/dev/sda4 ext4 (not mounted) afc265fe-2b63-41a0-ad59-80d89a8dea69
/dev/sda5 ext4 / 72293bb3-c4e1-40d7-949b-27988cdad968
Entered in fstab and commented out the two ntfs drives. Also changed the second number in root to 1:
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/sda5 / ext4 defaults,noatime 0 1
#/dev/sdc1 /media/Back_Up ntfs-3g defaults,locale=en_US.utf8 0 0
#/dev/sdb1 /media/Storage ntfs-3g defaults,locale=en_US.utf8 0 0
/swapfile swap swap defaults 0 0
But look after reboot:
$ systemd-analyze blame
31.767s systemd-udev-settle.service
769ms systemd-modules-load.service
127ms nfs-common.service
99ms keyboard-setup.service
94ms ModemManager.service
93ms console-setup.service
88ms udisks2.service
86ms loadcpufreq.service
65ms bootlogs.service
64ms networking.service
63ms gpm.service
49ms lvm2-activation.service
40ms lvm2-activation-early.service
38ms systemd-logind.service
33ms systemd-fsck-root.service
28ms live-config.service
26ms systemd-udev-trigger.service
26ms rpcbind.service
24ms polkitd.service
22ms irqbalance.service
18ms alsa-restore.service
17ms console-kit-log-system-start.service
17ms console-kit-daemon.service
16ms ifplugd.service
16ms systemd-udevd.service
15ms kbd.service
15ms dev-mqueue.mount
15ms systemd-tmpfiles-setup-dev.service
15ms dev-hugepages.mount
14ms dns-clean.service
14ms systemd-sysctl.service
14ms motd.service
14ms ifup@eth0.service
14ms sys-kernel-debug.mount
13ms cpufrequtils.service
13ms lm-sensors.service
13ms preload.service
12ms systemd-journal-flush.service
11ms upower.service
10ms smartmontools.service
10ms systemd-tmpfiles-setup.service
7ms live.service
7ms keymap.service
7ms swapfile.swap
6ms pppd-dns.service
5ms rc-local.service
5ms systemd-remount-fs.service
4ms systemd-user-sessions.service
4ms resolvconf.service
3ms live-tools.service
3ms run-lock.mount
3ms systemd-update-utmp-runlevel.service
3ms systemd-random-seed-load.service
3ms run-user.mount
3ms udev-finish.service
OK, it's not an issue with your ntfs drives -- you can remove the comment tags. Why is your swap partition not mounted? Try setting that to be mounted in /etc/fstab:
UUID=321355cd-0908-4b71-87a7-d5602526a308 none swap sw 0 0
Then reboot. If that doesn't help, we'll take a look at your journalctl log.
fstab:
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/sda5 / ext4 defaults,noatime 0 1
/dev/sdc1 /media/Back_Up ntfs-3g defaults,locale=en_US.utf8 0 0
/dev/sdb1 /media/Storage ntfs-3g defaults,locale=en_US.utf8 0 0
UUID=321355cd-0908-4b71-87a7-d5602526a308 none swap sw 0 0
but:
$ systemd-analyze blame
31.952s systemd-udev-settle.service
763ms systemd-modules-load.service
294ms media-Storage.mount
251ms media-Back_Up.mount
118ms keyboard-setup.service
103ms console-setup.service
102ms gpm.service
101ms nfs-common.service
89ms ModemManager.service
87ms udisks2.service
76ms loadcpufreq.service
65ms bootlogs.service
60ms networking.service
51ms preload.service
47ms lvm2-activation.service
44ms systemd-fsck-root.service
39ms lvm2-activation-early.service
37ms systemd-logind.service
35ms rpcbind.service
31ms irqbalance.service
30ms live-config.service
25ms systemd-udev-trigger.service
24ms dev-disk-by\x2duuid-321355cd\x2d0908\x2d4b71\x2d87a7\x2dd5602526a308.swap
22ms polkitd.service
22ms console-kit-daemon.service
19ms alsa-restore.service
18ms console-kit-log-system-start.service
17ms ifplugd.service
16ms cpufrequtils.service
15ms kbd.service
15ms motd.service
13ms ifup@eth0.service
13ms dns-clean.service
13ms dev-mqueue.mount
12ms dev-hugepages.mount
12ms lm-sensors.service
11ms smartmontools.service
11ms systemd-tmpfiles-setup-dev.service
11ms sys-kernel-debug.mount
10ms systemd-journal-flush.service
8ms pppd-dns.service
8ms live.service
8ms live-tools.service
8ms upower.service
7ms systemd-tmpfiles-setup.service
6ms keymap.service
6ms rc-local.service
5ms systemd-update-utmp-runlevel.service
5ms udev-finish.service
4ms systemd-remount-fs.service
4ms resolvconf.service
4ms systemd-user-sessions.service
3ms systemd-udevd.service
3ms systemd-sysctl.service
3ms run-lock.mount
2ms systemd-random-seed-load.service
2ms run-user.mount
In a user terminal
journalctl -b | most
will send the journal for your current booted session into a most window, where you can scroll through and maybe discover what is taking up the time. I'll google around and see if I can turn up any common issues with systemd-udev-settle.service.
Thank you very much. The result of the command is so long and in terms that are above my knowledge...
Don't worry we all can learn .... ;)
With your terminal window fairly wide, you can see the date and time stamp at the left end of each line. Most messages happen very fast -- you can see many messages at the exact same minute and second. But you are looking for an anomaly in that pattern -- either the same message repeating for many seconds, or a gap of time between messages. Or perhaps an error or a warning related to a device.
On
this page (http://freedesktop.org/wiki/Software/systemd/Optimizations/) I read in the first bit of guidance
Quote1. Make sure not to use any fake block device storage technology such as LVM (as installed by default by various distributions, including Fedora) they result in the systemd-udev-settle.service unit to be pulled in. Settling device enumeration is slow, racy and mostly obsolete. Since LVM (still) hasn't been updated to handle Linux' event based design properly, settling device enumeration is still required for it, but it will slow down boot substantially. On Fedora, use "systemctl mask fedora-wait-storage.service fedora-storage-init-late.service fedora-storage-init.service" to get rid of all those storage technologies. Of course, don't try this if you actually installed your system with LVM. (The only fake block device storage technology that currently handles this all properly and doesn't require settling device enumerations is LUKS disk encryption.)
Seeing that, I noticed that in your /etc/fstab file you used "/dev/sdx" IDs for your drives. Let's change that to
UUID=72293bb3-c4e1-40d7-949b-27988cdad968 for the root device. Since commenting out the ntfs drives had no effect, I guess there is no need to switch to UUIDs for those devices.
EDIT: On the other hand, it will do no harm to change
/dev/sdb1 to UUID=6876C3BE5BDF1565
and /dev/sdc1 to UUID=4CE077F63265B98C
O.K.! Reinstalled with UUID, new fstab:
proc /proc proc defaults 0 0
/swapfile swap swap defaults 0 0
UUID="b2a2abf2-95a2-46b2-ae17-ab26015257c0" / ext4 defaults,noatime 0 1
and as result without ntfs-config installed:
root@sid-box:/home/tuxic# blkid -c /dev/null -o list
device fs_type label mount point UUID
-------------------------------------------------------------------------------
/dev/sda1 ext2 (not mounted) 6067123f-9b75-4851-95b8-13ec54e40b18
/dev/sda2 ext4 (not mounted) 989a68dd-0b56-4769-ad56-58231befa019
/dev/sda4 ext4 (not mounted) afc265fe-2b63-41a0-ad59-80d89a8dea69
/dev/sda5 ext4 / b2a2abf2-95a2-46b2-ae17-ab26015257c0
/dev/sdb1 ntfs Storage (not mounted) 6876C3BE5BDF1565
/dev/sdc1 ntfs Back-Up (not mounted) 4CE077F63265B98C
/dev/sdc2 swap (not mounted) 321355cd-0908-4b71-87a7-d5602526a308
and latest result:
tuxic@sid-box:~$ systemd-analyze blame
31.734s systemd-udev-settle.service
760ms systemd-modules-load.service
130ms nfs-common.service
103ms keyboard-setup.service
95ms console-setup.service
88ms gpm.service
86ms ModemManager.service
80ms loadcpufreq.service
59ms networking.service
58ms bootlogs.service
51ms preload.service
48ms systemd-fsck-root.service
44ms lvm2-activation.service
43ms lvm2-activation-early.service
36ms systemd-logind.service
32ms live-config.service
30ms lm-sensors.service
28ms systemd-udev-trigger.service
24ms alsa-restore.service
24ms rpcbind.service
24ms console-kit-log-system-start.service
23ms ifplugd.service
23ms hddtemp.service
22ms motd.service
22ms irqbalance.service
22ms console-kit-daemon.service
22ms acpi-support.service
20ms polkitd.service
19ms cpufrequtils.service
18ms smartmontools.service
17ms kbd.service
17ms sysstat.service
16ms systemd-tmpfiles-setup-dev.service
15ms hdparm.service
15ms dev-mqueue.mount
14ms sys-kernel-debug.mount
13ms dev-hugepages.mount
12ms ifup@eth0.service
11ms pppd-dns.service
10ms systemd-journal-flush.service
9ms dns-clean.service
8ms keymap.service
8ms systemd-tmpfiles-setup.service
7ms systemd-sysctl.service
6ms rc-local.service
6ms live-tools.service
6ms live.service
6ms upower.service
5ms systemd-user-sessions.service
5ms run-user.mount
5ms systemd-remount-fs.service
4ms udev-finish.service
4ms resolvconf.service
3ms systemd-update-utmp-runlevel.service
3ms run-lock.mount
2ms systemd-random-seed-load.service
2ms systemd-udevd.service
2ms swapfile.swap
OK, now edit /etc/fstab and remove the quote marks, so it looks like this:
UUID=b2a2abf2-95a2-46b2-ae17-ab26015257c0 / ext4 defaults,noatime 0 1
fstab:
proc /proc proc defaults 0 0
/swapfile swap swap defaults 0 0
UUID=b2a2abf2-95a2-46b2-ae17-ab26015257c0 / ext4 defaults,noatime 0 1
then:
tuxic@sid-box:~$ systemd-analyze blame
31.759s systemd-udev-settle.service
767ms systemd-modules-load.service
119ms keyboard-setup.service
109ms nfs-common.service
96ms console-setup.service
88ms ModemManager.service
87ms loadcpufreq.service
77ms udisks2.service
74ms lvm2-activation-early.service
73ms gpm.service
62ms networking.service
60ms bootlogs.service
51ms preload.service
46ms systemd-fsck-root.service
39ms systemd-logind.service
33ms lvm2-activation.service
31ms live-config.service
30ms systemd-udev-trigger.service
27ms irqbalance.service
23ms rpcbind.service
23ms alsa-restore.service
23ms console-kit-daemon.service
22ms console-kit-log-system-start.service
20ms ifplugd.service
20ms hddtemp.service
19ms acpi-support.service
19ms motd.service
18ms polkitd.service
18ms hdparm.service
17ms smartmontools.service
17ms dev-mqueue.mount
16ms sys-kernel-debug.mount
15ms dev-hugepages.mount
15ms sysstat.service
14ms cpufrequtils.service
14ms kbd.service
13ms lm-sensors.service
13ms systemd-tmpfiles-setup-dev.service
11ms ifup@eth0.service
10ms pppd-dns.service
9ms systemd-sysctl.service
9ms dns-clean.service
8ms keymap.service
7ms upower.service
7ms rc-local.service
6ms systemd-user-sessions.service
6ms live.service
5ms systemd-tmpfiles-setup.service
4ms systemd-remount-fs.service
4ms swapfile.swap
4ms resolvconf.service
4ms live-tools.service
4ms systemd-random-seed-load.service
3ms systemd-update-utmp-runlevel.service
3ms systemd-journal-flush.service
3ms systemd-udevd.service
3ms udev-finish.service
2ms run-user.mount
1ms run-lock.mount
As you still have that /swapfile-line in your fstab, please assure that a file called swapfile really exists in your root directory on /dev/sda5.
Also we know yet that something udev-related might happen, so please have a look at the journal again with ' journalctl -b | grep udev ' as well as ' journalctl -b | grep swap ' and ' journalctl -b | grep mount '
Do you have any special rules configured in /etc/udev/rules.d/ ?
Your systemd-analyze blame shows some lvm- and nfs-related stuff which seems not to be reflected in your fstab and blkid outputs. So if you do not use either of them, you might apt-get purge packages related to lvm2 and/or nfs.
First:
tuxic@sid-box:~$ journalctl -b | grep udev
Jul 16 05:45:22 sid-box systemd-udevd[115]: starting version 204
Jul 16 05:45:22 sid-box systemd[1]: Starting udev Kernel Socket.
Jul 16 05:45:22 sid-box systemd[1]: Listening on udev Kernel Socket.
Jul 16 05:45:22 sid-box systemd[1]: Starting udev Control Socket.
Jul 16 05:45:22 sid-box systemd[1]: Listening on udev Control Socket.
Jul 16 05:45:22 sid-box systemd[1]: Starting udev Coldplug all Devices...
Jul 16 05:45:22 sid-box systemd-udevd[267]: starting version 204
Jul 16 05:45:22 sid-box systemd[1]: Starting udev Kernel Device Manager...
Jul 16 05:45:54 sid-box systemd[1]: Started udev Wait for Complete Device Initialization.
and:
tuxic@sid-box:~$ journalctl -b | grep mount
Jul 16 05:45:22 sid-box kernel: EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
Jul 16 05:45:22 sid-box systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
Jul 16 05:45:22 sid-box systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
Jul 16 05:45:22 sid-box systemd[1]: Starting Remount Root and Kernel File Systems...
Jul 16 05:45:22 sid-box kernel: EXT4-fs (sda5): re-mounted. Opts: (null)
Jul 16 05:45:22 sid-box systemd[1]: Started Remount Root and Kernel File Systems.
Sorry but I forgot:
tuxic@sid-box:~$ journalctl -b | grep swap
Jul 16 05:45:22 sid-box systemd[1]: Activating swap /swapfile...
Jul 16 05:45:22 sid-box swapon[361]: swapon: /swapfile: stat failed: No such file or directory
Jul 16 05:45:22 sid-box systemd[1]: swapfile.swap swap process exited, code=exited status=255
Jul 16 05:45:22 sid-box systemd[1]: Failed to activate swap /swapfile.
Jul 16 05:45:22 sid-box systemd[1]: Unit swapfile.swap entered failed state.
Already purged everything related to nfs and lvm2
I think we're in the right direction! Latest reboot:
tuxic@sid-box:~$ systemd-analyze blame
777ms systemd-modules-load.service
383ms networking.service
170ms console-setup.service
153ms rpcbind.service
100ms keyboard-setup.service
95ms loadcpufreq.service
94ms ModemManager.service
85ms udisks2.service
78ms bootlogs.service
71ms gpm.service
56ms preload.service
53ms ntp.service
44ms systemd-fsck-root.service
44ms systemd-logind.service
41ms kbd.service
29ms systemd-udev-trigger.service
28ms live-config.service
26ms alsa-restore.service
25ms console-kit-log-system-start.service
25ms irqbalance.service
23ms ifplugd.service
20ms systemd-journal-flush.service
19ms cpufrequtils.service
19ms hddtemp.service
18ms motd.service
18ms acpi-support.service
18ms systemd-tmpfiles-setup-dev.service
17ms polkitd.service
16ms smartmontools.service
16ms console-kit-daemon.service
15ms hdparm.service
15ms dev-mqueue.mount
14ms sys-kernel-debug.mount
13ms sysstat.service
13ms dev-hugepages.mount
13ms resolvconf.service
12ms dns-clean.service
12ms lm-sensors.service
12ms upower.service
10ms systemd-tmpfiles-setup.service
10ms pppd-dns.service
8ms keymap.service
8ms systemd-remount-fs.service
7ms systemd-sysctl.service
6ms rc-local.service
6ms live.service
6ms live-tools.service
6ms systemd-udevd.service
6ms systemd-user-sessions.service
5ms ifup@eth0.service
5ms swapfile.swap
5ms systemd-random-seed-load.service
3ms systemd-update-utmp-runlevel.service
2ms udev-finish.service
2ms run-user.mount
1ms run-lock.mount
I'll reboot agains and see how it goes...
I think that something related to nfs or lvm2 was conflicting with my booth because now it melts like butter in a sunny day!
tuxic@sid-box:~$ systemd-analyze blame
778ms systemd-modules-load.service
570ms console-setup.service
556ms networking.service
107ms keyboard-setup.service
101ms udisks2.service
94ms loadcpufreq.service
94ms ModemManager.service
89ms gpm.service
78ms bootlogs.service
55ms ntp.service
51ms systemd-fsck-root.service
44ms systemd-logind.service
41ms alsa-restore.service
36ms kbd.service
33ms console-kit-log-system-start.service
29ms live-config.service
28ms systemd-udev-trigger.service
27ms ifplugd.service
27ms preload.service
24ms rpcbind.service
23ms console-kit-daemon.service
23ms hddtemp.service
22ms acpi-support.service
22ms motd.service
22ms irqbalance.service
21ms polkitd.service
17ms dns-clean.service
17ms smartmontools.service
16ms dev-mqueue.mount
16ms ifup@eth0.service
16ms lm-sensors.service
15ms systemd-tmpfiles-setup.service
15ms sys-kernel-debug.mount
15ms systemd-tmpfiles-setup-dev.service
15ms dev-hugepages.mount
14ms sysstat.service
14ms cpufrequtils.service
14ms systemd-journal-flush.service
13ms hdparm.service
12ms pppd-dns.service
10ms upower.service
9ms rc-local.service
9ms swapfile.swap
9ms systemd-sysctl.service
9ms systemd-random-seed-load.service
8ms keymap.service
8ms systemd-user-sessions.service
7ms resolvconf.service
7ms live-tools.service
6ms live.service
4ms systemd-remount-fs.service
4ms systemd-update-utmp-runlevel.service
3ms run-user.mount
3ms run-lock.mount
3ms systemd-udevd.service
2ms udev-finish.service
Thanks for your pacience!
@dibl; @agaida; @der_bud; @piper; @GoingEasy9
I'll wait a day or two to see how it goes to mark it solved.
That looks much better. But I would still expect to find a systemd-udev-settle.service process on the list -- does it no longer show at all?
Now with ntfs-config installed:
tuxic@sid-box:~$ systemd-analyze blame
768ms systemd-modules-load.service
706ms media-Storage.mount
249ms media-Back_Up.mount
106ms keyboard-setup.service
101ms udisks2.service
99ms ModemManager.service
96ms console-setup.service
96ms loadcpufreq.service
92ms systemd-fsck-root.service
79ms gpm.service
74ms bootlogs.service
65ms networking.service
57ms preload.service
53ms ntp.service
50ms systemd-logind.service
36ms rpcbind.service
34ms live-config.service
34ms irqbalance.service
31ms systemd-udev-trigger.service
29ms systemd-tmpfiles-clean.service
28ms console-kit-daemon.service
22ms hdparm.service
21ms alsa-restore.service
20ms console-kit-log-system-start.service
19ms dev-mqueue.mount
19ms polkitd.service
18ms ifplugd.service
18ms sys-kernel-debug.mount
17ms dev-hugepages.mount
17ms hddtemp.service
16ms motd.service
16ms acpi-support.service
15ms ifup@eth0.service
14ms dns-clean.service
14ms lm-sensors.service
14ms cpufrequtils.service
14ms smartmontools.service
13ms kbd.service
12ms upower.service
11ms sysstat.service
11ms live.service
11ms live-tools.service
11ms systemd-journal-flush.service
10ms systemd-tmpfiles-setup-dev.service
10ms systemd-tmpfiles-setup.service
8ms systemd-sysctl.service
8ms keymap.service
8ms systemd-remount-fs.service
6ms pppd-dns.service
6ms resolvconf.service
5ms rc-local.service
4ms systemd-user-sessions.service
3ms systemd-udevd.service
3ms systemd-update-utmp-runlevel.service
3ms systemd-random-seed-load.service
2ms swapfile.swap
2ms udev-finish.service
1ms run-user.mount
1ms run-lock.mount
@dibl - I don't see it. Is it essential?
Shedding some light:
http://0pointer.de/blog/projects/blame-game.html (http://0pointer.de/blog/projects/blame-game.html)
Extract:
QuoteKnowing what we know now we can go and disable udev-settle.service[/size] for the next boots: since neither LVM, RAID nor Multipath is used we can mask the services in question and thus speed up our boot a little:
I'm in the learning process...
Cool -- I didn't know it was safe to do that.
Quote from: tuxic on 2014/07/16, 12:53:03
I'm in the learning process...
Yeah, I know -- I've never gotten out of it, either. ;D
Quote from: dibl on 2014/07/16, 12:18:17
That looks much better. But I would still expect to find a systemd-udev-settle.service process on the list -- does it no longer show at all?
I don't see no trace of udev-settle on a system without lvm/raid/mdadm/whatever, so that seems to be okay.
tuxic, from your post with 'journalctl -b | grep swap' it seems you have not configured swap properly. So either set up the swapfile you mention in fstab according to http://www.cyberciti.biz/faq/linux-add-a-swap-file-howto/ (for example), or better use the swap-partition you already have according to your blkid:
Quote from: tuxic on 2014/07/15, 17:35:01...
/dev/sdc2 swap (not mounted) 321355cd-0908-4b71-87a7-d5602526a308
...
@der_bud - According to my system:
tuxic@sid-box:~$ inxi -F
System: Host: sid-box Kernel: 3.15-5.towo-siduction-amd64 x86_64 (64 bit)
Desktop: Openbox 3.5.2
Distro: siduction 13.2.1 December - nox - (201401272149)
Machine: Mobo: ASUSTeK model: SABERTOOTH 990FX R2.0 v: Rev 1.xx
Bios: American Megatrends v: 1503 date: 01/11/2013
CPU: Octa core AMD FX-8350 Eight-Core (-MCP-) cache: 16384 KB
Clock Speeds: 1: 1400 MHz 2: 4000 MHz 3: 1400 MHz 4: 1400 MHz
5: 1400 MHz 6: 1400 MHz 7: 1400 MHz 8: 4000 MHz
Graphics: Card-1: Advanced Micro Devices [AMD/ATI] RV770 [Radeon HD 4850]
Card-2: Advanced Micro Devices [AMD/ATI] RV770 [Radeon HD 4850]
Display Server: X.Org 1.15.99.904 driver: radeon
Resolution: 1680x1050@59.95hz
GLX Renderer: Gallium 0.4 on AMD RV770 GLX Version: 3.0 Mesa 10.2.3
Audio: Card-1 2x Advanced Micro Devices [AMD/ATI] RV770 HDMI Audio [Radeon HD 4850/4870]
driver: snd_hda_intelsnd_hda_intel
Card-2 Advanced Micro Devices [AMD/ATI] SBx00 Azalia (Intel HDA)
driver: snd_hda_intel
Sound: ALSA v: k3.15-5.towo-siduction-amd64
Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
driver: r8169
IF: eth0 state: up speed: 100 Mbps duplex: full
mac: *****************
Drives: HDD Total Size: 2120.4GB (20.2% used)
ID-1: /dev/sda model: Samsung_SSD_840 size: 120.0GB
ID-2: /dev/sdb model: ST31000528AS size: 1000.2GB
ID-3: /dev/sdc model: ST1000DM003 size: 1000.2GB
Partition: ID-1: / size: 41G used: 3.9G (10%) fs: ext4 dev: /dev/sda5
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 31.9C mobo: N/A gpu: 75.0,70.5
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 209 Uptime: 6 min Memory: 804.7/7890.5MB
Client: Shell (bash) inxi: 2.1.28
Maybe I'm wrong but with 8 Gb of ram , swap si not needed.
Quote from: tuxic on 2014/07/16, 17:59:29
Maybe I'm wrong but with 8 Gb of ram , swap si not needed.
That is correct for many routine user tasks, but it is not correct for all cases. For example, use gimp to convert 250 .gif images into a video. In my case, with 6GB of RAM, it needed 16GB of swap space. :o
Also, you need swap to hibernate (suspend to disk).