During boot (Leap15/KDE) we have the splash screen and when hitting the escape key we see the boot process. I sometimes do that and then there is statement after statement like those in boot.log:
OK ] Started Check if mainboard battery is Ok.
OK ] Started Timeline of Snapper Snapshots.
OK ] Started Discard unused blocks once a week.
OK ] Started Backup of RPM database.
OK ] Started Scrub btrfs filesystem, verify block checksums.
OK ] Started Backup of /etc/sysconfig.
OK ] Started Discard unused blocks on a mounted filesystem.
Starting Postfix Mail Transport Agent...
OK ] Started Balance block groups on a btrfs filesystem.
Starting X Display Manager...
OK ] Started Daily rotation of log files.
OK ] Reached target Timers.
Starting Rotate log files...
Starting Check if mainboard battery is Ok...
Starting Discard unused blocks...
Starting Backup /etc/sysconfig directory...
Starting Backup RPM database...
OK ] Started Check if mainboard battery is Ok.
OK ] Started Discard unused blocks.
OK ] Started Balance block groups on a btrfs filesystem.
OK ] Started Update cron periods from /etc/sysconfig/btrfsmaintenance.
OK ] Started Rotate log files.
Starting Locale Service...
For some strange reasons now during the boot process all statements are double - every statement is repeated in the line below. Of course this is before the log in and I cannot copy anything to show what is happening. I could only make a photo but I hope you believe me without. What causes this doubling up? When I get the message “there are x updates available” I click install updates. Nevertheless shortly afterwards I get the same message again (and normally I click again install updates). Is this related? Otherwise the system is working. Here are the repos I use:
I see those messages every time, because I disable “plymouth”. But I have never checked for duplicates.
On the plasma update applet – I usually disable that, but I am running it on my laptop with Tumbleweed. And yes, I do see the notification twice – somebody likes repeating himself.
I used to disable plymouth too but on my tumbleweed laptop I don’t see much anyway since it has SSD and it is only a few seconds to login. But on this older laptop these statements never doubled up before LEAP15. Neither did the update applet come twice.
I seem to recall seeing something about that in the past, along with a solution. However, I cannot find it in my collected notes. You might scour the Forums for the thread using DuckDuckGo or Google.
I just rebooted. And, checking carefully, I am not seeing the problem.
I do recall someone else have a similar problem. Most likely, it is a logging configuration error causing log messages to be written twice. I did a clean install of 15.0. And maybe you upgraded 42.3, and have an older configuration that was not properly update.
Neither did the update applet come twice.
I’m guessing that one is just a quirk in the update applet deciding to report twice.
Thank you for all the input so far - still I could not find anything. Neither with search engine nor searching through the openSUSE forum nore looking through all kind of log files. Fraser_Bell if you remember the problem please let me know.
On an “old-style” (non-UEFI) Desktop with SSD as (ext4) System Disk and also Swap and, two HDD (XFS) “Home directory” disks which also have (ext4) “/tmp/”, “/srv/” and “/var/” partitions, I’m seeing something similar to this issue – normally the ‘plymouth-start.service’ is “wanted by” the ‘sysinit.target’; which causes “Plymouth start” to be called twice – the systemd “System Initialization” target appears twice during the boot sequence:
My current solution (only for similar hardware configurations) is as follows:
[LIST]
Change the systemd ‘plymouth-start.service’ to “wanted by” the systemd ‘initrd-switch-root.target’ …
[LIST]
This causes the systemd “Plymouth start” service to be called only once (early enough) by the boot process at a point determined by various “After=” and “Before=” settings in other systemd services …
[/LIST]
[/LIST]
In addition, I have a couple of similar solutions for “Plymouth quit” and “systemd VConsole setup” issues …
[HR][/HR]BTW: on a UEFI Laptop with a SSHD disk I’m not seeing this issue.
From the systemd Journal output, figure out what is being triggered and when …
From the systemd Journal output, you should be able to see that, Journal entries for “Reached target System Initialization.” occur twice within about 5 seconds of each other with, a “Stopped target System Initialization.” Journal entry in between which occurs less than 1 second after the 1st “Reached target System Initialization.” Journal entry.
There should be only one Journal entry for “Reached target Switch Root.” …
[HR][/HR]The systemd service files are normally located in ‘/usr/lib/systemd/system/’ along with some ‘«Plymouth service».wants/’ directories.
If you call “find” from ‘/usr/lib/systemd/’ too look for “plymouth-start.service” you’ll notice that, the “Plymouth start” service is triggered by a symbolic link located in the ‘/usr/lib/systemd/system/sysinit.target.wants/’ directory.
Unlink that link and create a new symbolic “plymouth-start.service” link to ‘…/plymouth-start.service’ in the ‘/usr/lib/systemd/system/initrd-switch-root.target.wants/’ directory.
thank you, dcurtisfra, I don’t think I quite understand. First here is the link to your jurnalctl command: https://paste.opensuse.org/29745724
I don’t know if you find anything of relevance there.
However I see that the link you mentioned is already here:
Yes, exactly what my non-UEFI, no Btrfs, SDD plus multiple HDD, system is experiencing:
The "System Initialization
" target is reached, then stopped, then reachedagain – meaning the “System Initialization” is being executed twice during the systemd boot sequence …
Exactly: there is a symbolic link in the “wants” directory of the “System Initialization” target – ‘/usr/lib/systemd/system/sysinit.target’ – which calls the “Plymouth start” service – twice – because, the systemd “System Initialization” is being executed twice on our systems …
[HR][/HR]If you were to move the symbolic link for the “Plymouth start” service from the directory ‘/usr/lib/systemd/system/sysinit.target.wants/’ to the directory ‘/usr/lib/systemd/system/initrd-switch-root.target.wants/’ then, the systemd “Plymouth start” service will execute only once during the system boot, despite the systemd “System Initialization” being executed twice …
linux-tl1r:/usr/lib/systemd/system/sysinit.target.wants # unlink plymouth-start.service
linux-tl1r:/usr/lib/systemd/system/sysinit.target.wants # ls -l plymouth-start.service
ls: cannot access 'plymouth-start.service': No such file or directory
linux-tl1r:/usr/lib/systemd/system/sysinit.target.wants # cd /usr/lib/systemd/system/initrd-switch-root.target.wants
linux-tl1r:/usr/lib/systemd/system/initrd-switch-root.target.wants # ls -l
total 0
lrwxrwxrwx 1 root root 25 Apr 25 15:13 plymouth-start.service -> ../plymouth-start.service
lrwxrwxrwx 1 root root 31 Apr 25 15:13 plymouth-switch-root.service -> ../plymouth-switch-root.service
So the link is removed from sysinit.target.wants but still in initrd-switch-root.target.wants but when rebooting I still get all the boot statements twice? what is going on - did I not understand correctly?
OK today I played around with grub in yast. I made the following changes:
Instead of “Boot from Partition” I ticked “Boot from Master Boot Record”
In the Tab Kernel Parameters in the line Optional Kernel Command Line Parameters the boot statements repeated themselves, so I deleted them and left only the following:
“video=1366x768 resume=/dev/disk/by-id/ata-ST9500325AS_6VE5AGBV-part6 splash=silent quiet showopts”
When clicking the button “Edit Disk Boot Order” there was only /dev/sda so I left that unchanged.
After rebooting and the grub screen the screen stayed black - neither splash screen nor Boot statements until the login screen came along. I don’t know how to get the boot statements back (the escape key had no effect) so I cannot say whether anything has changed.
Cheers
Uli
Now I changed the Optional Kernel Command Line Parameters in the tab Kernel Parameters to the following:
“video=1366x768 resume=/dev/disk/by-id/ata-ST9500325AS_6VE5AGBV-part6 splash=verbose quiet showopts”
Now I have the boot statements back - in a single sequence no more double as before. So thank you dcurtisfra for your assistance!
heers
Uli
[QUOTE=fuerstu; 2881096]
По некоторым странным причинам теперь во время процесса загрузки все операторы являются двойными - каждый оператор повторяется в строке ниже.[/QUOTE]
Подобная проблема.
Кто-нибудь знает, как это решается?