You are not logged in.
Hello,
I have a KDE system and in addition to my SSDs a RAID with BTRFS with two HDDs.
I would now like to remove the RAID. I removed the entry from the fstab and removed the HDs from the power supply.
Since then ARCH boots much longer. It stops approx. 30-40sec at "Reached target Graphical interface" and then comes the login screen.
As soon as I reconnect the plates (no entries in fstab), it boots again as it should.
Did I forget anything when I removed the RAID? Is there anything to do with "systemd"?
Regards
Michael
Last edited by DoXer (2018-09-02 11:24:22)
--
Regards
Michael
Offline
Check your journal for the cause of the delay, it's likely that "something" tries to access some file on the RAID
Offline
Please do not cross-post:
https://bbs.archlinux.de/viewtopic.php? … 38#p365638
Inofficial first vice president of the Rust Evangelism Strike Force
Offline
Ok, sorry for CrossPost.
I checked wir journalctl -b. Nothing related to /dev/sd[b-c] (which was the RAID) The RAID was more a less a temp-Drive to store postprocessed movies. I also stopped the HD-idle-Daemon, no success.
Only the start of the GUI is paused. During the "freeze" I can switch to another text-console, where I can login. I'm using SDDM an newest KDE.
Regards
Michael
--
Regards
Michael
Offline
Check your journal for the cause of the delay, it's likely that "something" tries to access some file on the RAID
This could not be the reason, because the disc is not mounted. Only removing power of the unmounted disc-array causes the boot-delay.
Last edited by DoXer (2018-08-23 06:33:05)
--
Regards
Michael
Offline
Can you post a complete journal from an affected boot?
Offline
Attached two logs created by journalctl -b
With HD (fast boot) an without HD (slow boot)
--
Regards
Michael
Offline
Does anyone feel like looking into the logs.. Any help is more then welcome.
--
Regards
Michael
Offline
Some comments. It seems the delay may be realted to KDE/SDDM because the boot slows when KDE tries to access plasmoids:
Aug 23 19:40:47 doxer dbus-daemon[684]: [session uid=1000 pid=684] Activating service name='org.gnome.GConf' requested by ':1.86' (uid=1000 pid=1129 comm="/usr/lib/firefox/firefox ")
Aug 23 19:40:47 doxer dbus-daemon[684]: [session uid=1000 pid=684] Successfully activated service 'org.gnome.GConf'
Aug 23 19:40:47 doxer plasmashell[776]: org.kde.plasmaquick: Delayed preload of "Benachrichtigungen" after 4.266 seconds
Aug 23 19:40:47 doxer plasmashell[776]: org.kde.plasmaquick: Applet "Benachrichtigungen" loaded after 0 msec
Aug 23 19:40:48 doxer plasmashell[776]: KActivitiesStats( 0x55e9ac635e50 ) ResultModelPrivate::onResultScoreUpdated result added: "applications:firefox.desktop" score: 17.7955 last: 1535046045 first: 1503769895
Aug 23 19:45:08 doxer plasmashell[776]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:342: Unable to assign [undefined] to int
Aug 23 19:45:08 doxer plasmashell[776]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:342: Unable to assign [undefined] to int
This can be tested by temporarily disabling sddm at boot (and possibly, some other services).
As another suggestion - this may be related to journald. I used encrypted btrfs (not raid) and sometimes experienced boot delays when systemd log increased to 300-400 MiB. Turned out, after talking on #btrfs that when systemd detects btrfs filesystem it uses some optimisations/defragmentations with journal log which slow down boot (although in my case the lock lasted for 30-40 min). In your case this may be related because your journal is 276 MB and max is 250, so systemd may do something with journal data.
P.S. Why firefox is started on boot?
Offline
Hi,
I found the issue. It was the AUR-package "diskmonitor". After reinstalling the package I get rid of the boot-delay.
Thank you for the support
--
Regards
Michael
Offline
Correction: The problem was not diskmonitor, but this: https://wiki.archlinux.org/index.php/SD … he_greeter
Solved by
pacman -S haveged
--
Regards
Michael
Offline