View previous topic :: View next topic |
Author |
Message |
Featherfoot Veteran
Joined: 28 Dec 2002 Posts: 1108 Location: Stuart, Florida
|
Posted: Sun Dec 31, 2017 2:31 am Post subject: systemd takes 90 seconds starting things before I can log in |
|
|
I am just getting systemd running on my system.
When I boot up, it spends a minute and a half starting up mysterious applications on each partition on my system.
This seems excessive.
Is there a way to determine what it is doing and perhaps reduce the amount of time before I can log in? |
|
Back to top |
|
|
eccerr0r Watchman
Joined: 01 Jul 2004 Posts: 9679 Location: almost Mile High in the USA
|
Posted: Mon Jan 01, 2018 11:55 pm Post subject: |
|
|
Well, what does it say it's stuck on?
Is it giving that dreaded counter? _________________ Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
Back to top |
|
|
Featherfoot Veteran
Joined: 28 Dec 2002 Posts: 1108 Location: Stuart, Florida
|
Posted: Tue Jan 02, 2018 12:10 am Post subject: |
|
|
It doesn't say, but I deduced that it was failing to mount RAID disks. |
|
Back to top |
|
|
Featherfoot Veteran
Joined: 28 Dec 2002 Posts: 1108 Location: Stuart, Florida
|
Posted: Tue Jan 02, 2018 2:16 am Post subject: |
|
|
After poking around the internet, I have decided that the problem is that systemd is failing to mount 3 partitions of my raid 1 array. These are the only ones that I use.
I fooled around with systemctl start gentoo.mount (the partition that mounts the home directory and many other user directories. It fails.
There is also a kubuntu.mount and boot.mount which also fail to mount. All of these mounts come from /etc/fstab which has worked for a long time with sysvinit.
I don't see anything that lets me set up these files correctly.
Your help would be appreciated. |
|
Back to top |
|
|
grumblebear Apprentice
Joined: 26 Feb 2008 Posts: 202
|
Posted: Tue Jan 02, 2018 9:40 am Post subject: |
|
|
First of all, make sure your fstab lists UUIDs and not device names. |
|
Back to top |
|
|
Featherfoot Veteran
Joined: 28 Dec 2002 Posts: 1108 Location: Stuart, Florida
|
Posted: Tue Jan 02, 2018 7:22 pm Post subject: |
|
|
Using UUID's fixed the problem and my system now boots. I still have one message that times out:
It is to the effect of waiting on sys-subs multi-user
I don't see what's causing it or how to fix it.
I poked around with systemctl and saw the following:
Code: |
bopper /etc/portage # systemctl list-unit-files *multi*
UNIT FILE STATE
multi-user.target static
|
Code: |
bopper /etc/portage # systemctl list-unit-files *mount*
UNIT FILE STATE
proc-sys-fs-binfmt_misc.automount static
-.mount generated
boot.mount generated
boot2.mount generated
dev-hugepages.mount static
dev-mqueue.mount static
gentoo.mount generated
kubuntu.mount generated
mnt-cdrom.mount generated
proc-sys-fs-binfmt_misc.mount static
sys-fs-fuse-connections.mount static
sys-kernel-config.mount static
sys-kernel-debug.mount static
tmp.mount generated
var-lib-machines.mount static
windows.mount generated
clean-mount-point@.service static
systemd-remount-fs.service static
umount.target static
19 unit files listed.
bopper /etc/portage #
|
My new fstab follows:
Code: |
bopper /etc/portage # cat /etc/fstab
# /etc/fstab: static file system information.
#
# noatime turns off atimes for increased performance (atimes normally aren't
# needed; notail increases performance of ReiserFS (at the expense of storage
# efficiency). It's safe to drop the noatime options if you want and to
# switch between notail / tail freely.
#
# The root filesystem should have a pass number of either 0 or 1.
# All other filesystems should have a pass number of 0 or greater than 1.
#
# See the manpage fstab(5) for more information.
#
# <fs> <mountpoint> <type> <opts> <dump/pass>
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
UUID=ce12cbd3-e132-49fd-9076-4a444316c489 / ext4 nofail,noatime,nodiratime,discard,user_xattr,errors=remount-ro 0 1
UUID=dfbd92d1-ef3f-4496-bc71-97aacf0fd096 /boot ext4 nofail,noatime,nodiratime,discard 0 1
#/dev/mapper/pdc_dcgidcdjbp6 /gentoo ext4 nofail,user_xattr,errors=remount-ro 0 1
UUID=c1cb1385-87e0-4bf3-b2a3-dbee60f29f9a /gentoo ext4 nofail,user_xattr,errors=remount-ro 0 1 #/dev/mapper/pdc_dcgidcdjbp6
#/dev/mapper/pdc_dcgidcdjbp7 none swap sw 0 0
UUID"0a0d21cf-3ab8-4778-9f39-999831dc3311 none swap sw 0 0 #/dev/mapper/pdc_dcgidcdjbp7
#/dev/mapper/pdc_dcgidcdjbp2 /windows ntfs-3g noauto,user 1 3
UUID=4C7E6BB37E6B950C /windows ntfs-3g noauto,user 1 3 #/dev/mapper/pdc_dcgidcdjbp2
/dev/cdrom /mnt/cdrom auto noauto,user 0 0
#/dev/mapper/pdc_dcgidcdjbp5 /kubuntu ext4 nofail,errors=remount-ro 1 3
UUID=d7d87dc0-4d76-43e4-bf58-aa2b030f6b09 /kubuntu ext4 nofail,errors=remount-ro 1 3 # blkid /dev/mapper/pdc_dcgidcdjb5
#/dev/mapper/pdc_dcgidcdjbp3 /boot2 ext4 nofail,defaults 1 4
UUID=6d6f492b-f466-42ef-925c-f1980b208396 /boot2 ext4 nofail,defaults 1 4 #/dev/mapper/pdc_dcgidcdjbp3
# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink).
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
# use almost no memory if not populated with files)
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
#/tmp tmpfs defaults,noatime,mode=1777 0 0
#/var/tmp tmpfs defaults,noatime,mode=1777 0 0
#/var/log tmpfs defaults,noatime,mode=0755 0 0
bopper /etc/portage #
|
|
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|