Hi everybody !
I made a dist-upgrade to openSUSE 12.1, I rebooted and I was asked the root password to enter in recovery mode.
For what I understand from the few errors I get, one script file is missing : /etc/sysconfig/network/scripts/ifup-sysctl… to make the network up.
I was able to fix it temporarily with modprobe forcedeth (I also added it to /etc/sysconfig/kernel), then I reinstalled the sysconfig packages but the scripts are always missing :’(
Thank you for your help
I took a deeper look and the file is here but the problem too…
The error is :
udevd[224] : failed to execute ‘/etc/sysconfig/network/scripts/ifup-sysctl’ ‘/etc/sysconfig/network/scripts/ifup-sysctl lo -o hotplug’ : no such file or directory.
On 2011-11-16 19:36, devloop wrote:
> For what I understand from the few errors I get, one script file is
> missing : /etc/sysconfig/network/scripts/ifup-eth… to make the
> network up.
I don’t see that script in my 12.1 test system.
> Elanor:~ # ls /etc/sysconfig/network/scripts/ifup-
> ifup-802.1q ifup-bonding ifup-infiniband ifup-route ifup-skel ifup-tunnel
> ifup-autoip ifup-bridge ifup-ppp ifup-services ifup-sysctl ifup-wireless
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Hello !
The script name is ifup-sysctl, not ifup-eth (I edited my post).
The script is here but for an unknown reason it can’t be executed. Permissions are right.
My encrypted home partition is not mounted too despite it ask me for the passphrase…
I get the same error when I do a clean install of OpenSUSE 12.1 from DVD. I’ve tried it on two machines, and get the same thing. I can’t find a way to install 12.1. It’s dead on arrival, as far as I’m concerned.
It seems like it might the same as this bug: https://bugzilla.novell.com/show_bug.cgi?id=724775
I am seeing that message on boot, but it isn’t preventing boot.
I did do a clean install, rather than an upgrade. And I do have “/”, “/boot”, “/home” and swap.
An additional thought: Check “/etc/fstab” closely for any possible problems. Maybe comment out any line not actually essential. My experience is that “systemd” goes into emergency mode if it runs into a problem with a line in “/etc/fstab”. And your description of what you are seeing sound like it might be entering emergency mode.
Hi !
I finally fixed the problem, using F5 on Grub and switching the init system back to system v (as recommended in an other thread).
I still got the error message on boot but as for nrickert, everything is fine.
From the release notes :
Booting with systemd or sysvinit
By default, openSUSE now boots using systemd. In case of trouble, you can switch back to the old way using sysvinit by pressing the F5 key on the boot.
If you want to switch to sysvinit permanently, install the sysvinit-init package. To switch back to systemd, reinstall the systemd-sysvinit package.
On 2011-11-19 10:06, devloop wrote:
>
> Hi !
>
> I finally fixed the problem, using F5 on Grub and switching the init
> system back to system v (as recommended in an other thread).
> I still got the error message on boot but as for nrickert, everything
> is fine.
Then don’t forget to open bug in Bugzilla or add to existing one if it matches.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
If you have a system level bash script that not running when using systemd in openSUSE 12.1, you can attempt to make it run by adding it to the /etc/init.d/boot.local script and I have a blog on how to get the after.local script to also work.
systemd and using the after.local script in openSUSE 12.1 - Blogs - openSUSE Forums
I am a big fan of just making things work, but just as …
*
Carlos E. R. says: “Then don’t forget to open bug in Bugzilla or add to existing one if it matches.” *
… which are words to live by here. systemd is our new direction, but what needs to work should be made to work. Either old scripts should run or programs modified to not require the old scripts. systemd is all about a faster and more efficient startup of openSUSE. Some like and others hate it but in the end, you need to learn to live with it as it is a our future, but now.
Thank You,
On 2011-11-19 16:16, jdmcdaniel3 wrote:
> I am a big fan of just making things work, but just as …
> _-
> Carlos_E.R.says:__“Then_don’t_forget_to_open_bug_in_Bugzilla_or_add_to_existing_one_if_it_matches.”-
>
> … which are words to live by here. systemd is our new direction, but
> what needs to work should be made to work. Either old scripts should
Systemd is here to stay. I’m afraid we will have the alternative initv only
for some time, so problems caused by systemd have to be reported in
Bugzilla so that the devs do something about them. Saying it here is
useless, they don’t read the forum.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)