Mageia forum

sometimes slow up to 6 minutes to open my mageia,I sent a message at the beginning and crashes about 3 minutes in that

after about 2 minute here (check for new hardware

and sometimes sees and this message

when closed can sometimes slow here

I'm with these features in this computer

motherboard I have this

http://www.gigabyte.com/products/produc ... id=2866#ov

we go to strange now

sometimes opens directly my other finishes the above

can open five times in a row without a problem and after 2.3 with problems

I make these problems from the mageia 4 and the same continues and 5 with any GUI if I have and with another graphics card nvidia also

I think that is something from the motherboard that bothers

also in other distributions I do not make these problems debian,ubuntu,lmde

sorry for my english

You might be hit be https://bugs.mageia.org/show_bug.cgi?id=14249

Please show the output as root of

Code: Select all: systemctl status systemd-udev-settle.service -a systemd-analyze blame --no-pager systemd-analyze critical-chain --no-pager

Please also run

Code: Select all: systemd-analyze plot > boot.svg

and attach the generated file boot.svg here please.

For harddrake that hangs on boot you could also try to disable hardware recognition on boot via as root

Code: Select all: echo "HARDDRAKE_ONBOOT=no" >> /etc/sysconfig/system

Code: Select all: [root@localhost prodromos]# systemctl status systemd-udev-settle.service -a ● systemd-udev-settle.service - udev Wait for Complete Device Initialization Loaded: loaded (/usr/lib/systemd/system/systemd-udev-settle.service; static) Active: active (exited) since Κυρ 2015-03-29 14:29:03 UTC; 50s ago Docs: man:udev(7) man:systemd-udevd.service(8) Process: 443 ExecStart=/usr/bin/udevadm settle (code=exited, status=0/SUCCESS) Main PID: 443 (code=exited, status=0/SUCCESS) CGroup: /system.slice/systemd-udev-settle.service Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

Code: Select all: [root@localhost prodromos]# systemd-analyze blame --no-pager 10.114s shorewall.service 8.937s shorewall6.service 4.680s network-up.service 4.061s systemd-udev-settle.service 1.415s network.service 1.268s systemd-journal-flush.service 963ms fedora-readonly.service 920ms acpid.service 917ms systemd-logind.service 915ms upower.service 911ms cpupower.service 906ms preload.service 899ms systemd-udevd.service 888ms systemd-fsck-root.service 842ms fedora-loadmodules.service 747ms partmon.service 593ms systemd-vconsole-setup.service 525ms systemd-journald.service 482ms mandriva-everytime.service 408ms resolvconf.service 377ms dev-hugepages.mount 376ms sys-kernel-debug.mount 376ms dev-mqueue.mount 365ms systemd-sysctl.service 354ms systemd-tmpfiles-setup-dev.service 321ms tmp.mount 282ms user@1000.service 266ms accounts-daemon.service 246ms systemd-modules-load.service 216ms udisks2.service 208ms kmod-static-nodes.service 205ms polkit.service 171ms systemd-timesyncd.service 165ms home.mount 161ms mandriva-save-dmesg.service 141ms systemd-udev-trigger.service 135ms iptables.service 134ms systemd-networkd.service 118ms systemd-update-utmp.service 114ms systemd-fsck@dev-disk-by\x2duuid-0ab72a90\x2d61e0\x2d4014\x2db1ad\x2dc300f5222ab2.service 106ms systemd-user-sessions.service 85ms ip6tables.service 81ms systemd-resolved.service 76ms plymouth-read-write.service 67ms dev-disk-by\x2duuid-a85f94fd\x2d79e4\x2d4917\x2d8b17\x2d4c238428fc41.swap 60ms plymouth-quit-wait.service 47ms routed.service 45ms msec.service 36ms systemd-random-seed.service 35ms numlock.service 26ms ct_sync.service 19ms systemd-remount-fs.service 9ms systemd-tmpfiles-setup.service 8ms rtkit-daemon.service 6ms fedora-wait-storage.service 2ms systemd-update-utmp-runlevel.service

Code: Select all: [root@localhost prodromos]# systemd-analyze critical-chain --no-pager 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. graphical.target @25.149s └─multi-user.target @25.149s └─routed.service @25.101s +47ms └─network-online.target @14.964s └─network.target @14.945s └─network-up.service @10.264s +4.680s └─numlock.service @10.227s +35ms └─partmon.service @9.479s +747ms └─network.service @8.062s +1.415s └─resolvconf.service @7.653s +408ms └─preload.service @6.746s +906ms └─prefdm.service @6.743s └─systemd-user-sessions.service @6.613s +106ms └─basic.target @5.688s └─mandriva-everytime.service @5.206s +482ms └─local-fs.target @5.202s └─run-user-1000.mount @9.585s └─local-fs-pre.target @2.254s └─systemd-tmpfiles-setup-dev.service @1.898s +354ms └─kmod-static-nodes.service @989ms +208ms └─system.slice @986ms └─-.slice @986ms

That is all from a normal boot, right? Complete boot time is ~30 seconds.

Please redo this once you got a slow boot.

since I ran it

Code: Select all: echo "HARDDRAKE_ONBOOT=no" >> /etc/sysconfig/system

I opened very quickly.will attend and will inform

Code: Select all: [root@localhost prodromos]# systemctl status systemd-udev-settle.service -a ● systemd-udev-settle.service - udev Wait for Complete Device Initialization Loaded: loaded (/usr/lib/systemd/system/systemd-udev-settle.service; static) Active: failed (Result: timeout) since Κυρ 2015-03-29 18:40:54 EEST; 1min 13s ago Docs: man:udev(7) man:systemd-udevd.service(8) Process: 443 ExecStart=/usr/bin/udevadm settle (code=killed, signal=TERM) Main PID: 443 (code=killed, signal=TERM) Μάρ 29 18:40:54 localhost systemd[1]: systemd-udev-settle.service start operation timed out. Terminating. Μάρ 29 18:40:54 localhost systemd[1]: Failed to start udev Wait for Complete Device Initialization. Μάρ 29 18:40:54 localhost systemd[1]: Unit systemd-udev-settle.service entered failed state. Μάρ 29 18:40:54 localhost systemd[1]: systemd-udev-settle.service failed. Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

Code: Select all: [root@localhost prodromos]# systemd-analyze blame --no-pager 3min 74ms systemd-udev-settle.service 10.098s shorewall.service 9.978s shorewall6.service 4.679s network-up.service 2.117s systemd-journal-flush.service 2.029s fedora-readonly.service 1.743s network.service 1.141s chronyd.service 1.045s acpid.service 995ms systemd-logind.service 988ms upower.service 986ms cpupower.service 963ms systemd-fsck-root.service 924ms partmon.service 834ms fedora-loadmodules.service 774ms systemd-udevd.service 751ms preload.service 701ms systemd-vconsole-setup.service 587ms user@1000.service 545ms dev-hugepages.mount 545ms sys-kernel-debug.mount 544ms dev-mqueue.mount 473ms tmp.mount 472ms routed.service 425ms systemd-journald.service 359ms mandriva-everytime.service 359ms udisks2.service 348ms resolvconf.service 331ms systemd-random-seed.service 316ms accounts-daemon.service 303ms systemd-tmpfiles-setup-dev.service 301ms msec.service 256ms systemd-sysctl.service 247ms polkit.service 246ms dev-disk-by\x2duuid-a85f94fd\x2d79e4\x2d4917\x2d8b17\x2d4c238428fc41.swap 221ms systemd-modules-load.service 212ms systemd-resolved.service 165ms mandriva-save-dmesg.service 158ms kmod-static-nodes.service 156ms systemd-networkd.service 156ms iptables.service 139ms systemd-fsck@dev-disk-by\x2duuid-0ab72a90\x2d61e0\x2d4014\x2db1ad\x2dc300f5222ab2.service 133ms systemd-udev-trigger.service 89ms systemd-user-sessions.service 85ms ip6tables.service 84ms systemd-update-utmp.service 81ms numlock.service 68ms plymouth-read-write.service 66ms home.mount 60ms plymouth-quit-wait.service 25ms ct_sync.service 21ms rtkit-daemon.service 20ms systemd-remount-fs.service 11ms systemd-tmpfiles-setup.service 4ms fedora-wait-storage.service 2ms systemd-update-utmp-runlevel.service

Code: Select all: [root@localhost prodromos]# systemd-analyze critical-chain --no-pager 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. graphical.target @3min 22.304s └─multi-user.target @3min 22.304s └─routed.service @3min 21.831s +472ms └─network-online.target @3min 11.728s └─network.target @3min 11.674s └─network-up.service @3min 6.994s +4.679s └─numlock.service @3min 6.912s +81ms └─partmon.service @3min 5.987s +924ms └─network.service @3min 4.242s +1.743s └─resolvconf.service @3min 3.892s +348ms └─preload.service @3min 3.140s +751ms └─prefdm.service @3min 3.139s └─systemd-user-sessions.service @3min 2.985s +89ms └─basic.target @3min 1.926s └─mandriva-everytime.service @3min 1.567s +359ms └─local-fs.target @3min 1.566s └─run-media-prodromos-Mageia\x2d5\x2dGNOME\x2dLiveDVD.mount @3min 17.940s └─local-fs-pre.target @2.635s └─systemd-tmpfiles-setup-dev.service @2.331s +303ms └─kmod-static-nodes.service @1.347s +158ms └─system.slice @1.345s └─-.slice @1.344s

If you have installed on classical partitions and if you don't use LVM, you could try via

Code: Select all: systemctl mask systemd-udev-settle.service fedora-wait-storage.service

and while the startup time has improved significantly, today send my this message when press to close pc

As a general hint and golden rule: Please only one problem per thread

ok you're right I close this topic and start new

Mageia forum

[SOLVED] boot time too slowly

[SOLVED] boot time too slowly

Re: boot time too slowly

Re: boot time too slowly

Re: boot time too slowly

Re: boot time too slowly

Re: boot time too slowly

Re: boot time too slowly

Re: boot time too slowly

Re: boot time too slowly

Re: boot time too slowly