https://bugzilla.novell.com/show_bug.cgi?id=805420 https://bugzilla.novell.com/show_bug.cgi?id=805420#c2 Frederic Crozat changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fcrozat@suse.com --- Comment #2 from Frederic Crozat 2013-03-11 16:46:10 UTC --- please reboot with "systemd.log_level=debug systemd.log_target=kmsg" on kernel command line and attach dmesg ouput on this bug report. Please also attach /etc/fstab and output of systemctl status lvm.service systemctl show lvm.service systemctl status rc-local.service -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=805420 https://bugzilla.novell.com/show_bug.cgi?id=805420#c4 --- Comment #4 from L. A. Walsh 2013-03-11 11:24:03 PDT --- oops, it sent the result on this before I was done... I put boot.lvm on the localfs's "required-start" line, and the problem went away. Also, regarding mount of /usr, before systemd runs full out, I did this: /etc/systemd/system> ll default.target.wants/ systemd-readahead-collect.service -> /lib/systemd/system/systemd-readahead-collect.service systemd-readahead-replay.service -> /lib/systemd/system/systemd-readahead-replay.service usr-mount.service -> /lib/systemd/system/usr-mount.service =============== more /lib/systemd/system/usr-mount.service # This file is linda's # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. [Unit] Description=mount /usr on root early in systemd startup DefaultDependencies=no Conflicts=shutdown.target Before=sysinit.target shutdown.target ConditionPathExists=/bin [Service] Type=oneshot ExecStart=/lib/systemd/systemd-usr RemainAfterExit=no StandardOutput=syslog+console TimeoutSec=5 [Install] WantedBy=default.target ======================================================= Such a target in a systemd-only boot env (and same for any other needed boot modules -- as I'm told all of them are not being integrated into systemd, which is not good), should allow it to boot. Basically anything that systemd doesn't do -- won't happen if the user boots from their hard disk instead of a ram disk. Hopefully some people will get that such is wanted. My system boot time is about 20-25 seconds total -- and that's for something I use as a server -- not a laptop. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=805420 https://bugzilla.novell.com/show_bug.cgi?id=805420#c6 L. A. Walsh changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|suse@tlinx.org | --- Comment #6 from L. A. Walsh 2013-03-12 22:57:28 PDT --- Upon rebooting my system, I ran into difficulties which, if related, are only related from the standpoint of overall incompatibilities being introduced in 12.3. I'm beginning to see a trend -- other interlocking processes are not being started in the correct order as if startpar was modified to ignore dependency info .. but I need to look at startpar to find out how this could happen... Right now: my fstab is missing a few entries due to having been restored from a backup, but other than some new partitions and all the snapshots (which don't get mounted from fstab, but via my snapper.pl script). # /etc/fstab - ishtar # local #1234567890123456789012345678901234567890123456789012345678901234567890123456789 # colnums/tsops 21 # what where type options bck ord proc /proc proc defaults 0 0 sysfs /sys sysfs defaults 0 0 debugfs /sys/kernel/debug debugfs defaults 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 #hugetlbfs /dev/hugetlbfs hugetlbfs mode=1777,rw,nosuid,nodev,noexec,noatime,nodiratime,nofail 0 0 #LABEL=Swap swap swap defaults /dev/sdc5 swap swap defaults 0 0 /dev/Home+Space/Sys / xfs defaults,noatime,nodiratime,swalloc,largeio,logbsize=256k,allocsize=64k 0 0 #/dev/sdc6 /usr xfs defaults,noatime,nodiratime,swalloc,largeio,logbsize=256k,allocsize=64k 0 0 /dev/Home+Space/Sysvar /var xfs defaults,noatime,nodiratime,swalloc,largeio,logbsize=256k,allocsize=128k 0 0 /dev/Home+Space/Sysboot /boot xfs defaults,noatime,nodiratime,swalloc,largeio,allocsize=2m 0 0 /var/rtmp /tmp none rbind 0 0 /dev/Home+Space/Home /home xfs defaults,noatime,nodiratime,swalloc,largeio,logbsize=256k,inode64,nobarrier,allocsize=128k 0 0 /dev/Home+Space/Share /Share xfs defaults,noatime,nodiratime,swalloc,largeio,logbsize=256k,inode64,nobarrier,allocsize=1024k 0 0 /dev/Home+Space/Home.diff /home.diff xfs defaults,noatime,nodiratime,swalloc,largeio,logbsize=256k,nobarrier 0 0 /dev/Media/Media /Media xfs defaults,noatime,nodiratime,swalloc,largeio,logbsize=256k,allocsize=32m 0 0 /dev/Home+Space/Squid_Cache /var/cache/squid xfs defaults,noatime,nodiratime,swalloc,largeio,logbsize=256k,nobarrier,allocsize=64k 0 0 /dev/Backups/Backups /backups xfs defaults,noatime,nodiratime,swalloc,largeio,logbsize=256k,inode64,allocsize=128m 0 0 /dev/Home+Space/Media_Back /backups/Media xfs defaults,noatime,nodiratime,swalloc,largeio,logbsize=256k,allocsize=128m 0 0 /home/share /usr/share none rbind --------------------------- Ishtar:/# systemctl status lvm.service Failed to get D-Bus connection: No connection to service manager. Ishtar:/# ^C / Ishtar:/# ps -ef|grep dbus 207 3514 1 0 18:43 ? 00:00:00 /bin/dbus-daemon --system law 3748 1 0 17:52 ? 00:00:00 /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 4625 4313 0 18:46 ttyp0 00:00:00 grep --color=auto dbus Ishtar:/# systemctl show lvm.service Failed to get D-Bus connection: No connection to service manager. Ishtar:/# systemctl status rc-local.service Failed to get D-Bus connection: No connection to service manager. ------------------------------ If I reboot right now, I may have problems getting back up. So far, I've had different things fail each boot -- usually the network not coming up in time for network services... This is a new symptom as of yesterday, so I haven't gotten a clue as to why it's happening. --- Most of these problems have come around in trying to upgrade my system to 12.2 for the sysadmin functions -- originally to support getting vm's to work with the vm-repo I was pointed at only being 12.2 compat. I.e. these problems are related to the increasing number incompatibilities between 'next-suse-version's, especially in regards to minor versions...(12.1->12.2->12.3 vs. 10.x=>11.x=>12.x)... I don't know what more information you want... does systemd need to be running in order to query it's state? If so, why would chkconfig say the boot scripts are overshadowed by systemd and try to contact it if it was not? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=805420 https://bugzilla.novell.com/show_bug.cgi?id=805420#c8 L. A. Walsh changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED CC| |suse@tlinx.org InfoProvider|suse@tlinx.org | Resolution| |WONTFIX --- Comment #8 from L. A. Walsh 2013-04-01 13:20:30 PDT --- I'm not going to try to reproduce the setup from 12.1 as I'm trying to fix boot in factory to boot from HD ... work on 12.1 is a waste at this point, so I'm not going to spend any more time trying to analyze, reproduce or fix this issue. If I run into it again, I'll reopen it -- part of the problem may be that there seems to be a purposeful addition to not tell "telinit" that the runlevel needs to change and it needs to run its scripts, but that's a guess based on some source viewing... Any fixes I make need to address problems in factory to repair/undo/compensate for recent changes in the what used to be the standard suse boot procedure for the past 10+ years...*sigh*... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.