Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
My Fedora 27 boots very slow. While booting, when it reaches 'Starting Switch Root', it takes almost 30+ seconds and then login screen appears.
I had installed CentOS 7.4 and Ubuntu 17.10 on the same machine earlier, and have noticed this problem doesn't exist on those OSs. Its only for Fedora Workstation.
# systemd-analyze critical-chain udisks2.service
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
udisks2.service +22.434s
└─basic.target @11.289s
└─sockets.target @11.289s
└─cups.socket @11.289s
└─sysinit.target @11.255s
└─systemd-update-utmp.service @11.229s +25ms
└─auditd.service @10.822s +406ms
└─systemd-tmpfiles-setup.service @10.544s +275ms
└─fedora-import-state.service @10.203s +340ms
└─local-fs.target @10.201s
└─run-user-42.mount @23.588s
└─local-fs-pre.target @9.224s
└─lvm2-monitor.service @3.265s +5.958s
└─lvm2-lvmetad.service @8.792s
└─lvm2-lvmetad.socket @3.264s
└─-.mount
└─system.slice
└─-.slice
This is my fstab
Code:
#
# /etc/fstab
# Created by anaconda on Mon Jan 29 19:54:52 2018
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
/dev/mapper/mdd-svr / xfs defaults 0 1
UUID=509b3b36-07f7-49be-a20c-02dd20ec015c /boot ext4 defaults 0 1
UUID=4F2A-13C2 /boot/efi vfat umask=0077,shortname=winnt 0 1
UUID="ebe1f019-3cfd-4aa2-bd0a-fe260e345976" none swap defaults 0 0
UUID="42ce5151-28f1-4567-b7b4-0b5a27e91721" /dc ext4 defaults 0 0
I've checked UUIDs are correct.
Why udisks2.service takes so long? Or is this normal?
I changed DefaultTimeoutStartSec and DefaultTimeoutStopSec to 10 seconds, and now the udisks2.service is reduced to 2.986 seconds from whopping 22.434 seconds. This is a great improvement. Thanks.
I changed DefaultTimeoutStartSec and DefaultTimeoutStopSec to 10 seconds, and now the udisks2.service is reduced to 2.986 seconds from whopping 22.434 seconds. This is a great improvement. Thanks.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.