Page 2 of 2

Re: filesystem ... does not contain valid init=/sbin/init

Posted: Tue Apr 08, 2014 22:05
by svantoviit
Don't need to reinstall the system.
If you are able to boot, update & upgrade entropy and reinstall sys-apps/systemd-sysv-utils, that should be sufficient to repair the system.

Re: filesystem ... does not contain valid init=/sbin/init

Posted: Wed Apr 09, 2014 0:01
by tinogil
Solved. When I go in the system I updated it and it start to run perfect

Re: filesystem ... does not contain valid init=/sbin/init

Posted: Wed Apr 09, 2014 14:10
by udiljak
Not a solution for me. I can boot, but network isn't working. Nether LAN nor wireless. When I try to start /etc/init.d/net.eth0 it tells me somthing like "Error: is already starting"

I can reinstall systemd, but I can't update entropy before. On installation of systemd there are several error messages. I paste them in the end. I reckon it's connected to the fact that I don't have the package "systemd-sysv-utils". I tried to manually download the package and put it into the /var/lib/entropy/client/packages/packages directory. But I still can't install it (maybe because I can't "equo update" without network?!)

Any ideas?

Thanks!
Ben

Here the output of "equo install systemd" (in German):

╠ +++ >>> (1/1) sys-apps/systemd-208-r3
╠ ## Entpacke: sys-apps:systemd-208-r3.078a75ad00bf3a8544f344c5487b130af1a5f960~2.tbz2
╠ ## Package phase: setup
* Determining the location of the kernel source code
* Found kernel source directory:
* /usr/src/linux
* Found sources for kernel version:
* 3.9.0-sabayon
* It's recommended to set an empty value to the following kernel config option:
* CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
* Checking for suitable kernel configuration options... [ ok ]
╠ ## Installiere Paket: sys-apps/systemd-208-r3
╠ ## [System and service manager for Linux]
☛ ## Nicht möglich fehlerhafte symlinks zu erhalten:
☛ ## /etc/sysctl.d/99-sysctl.conf
╠ ## Updating installed packages repository: sys-apps/systemd-208-r3
╠ ## Package phase: preremove
!!! Error: Target "sysvinit" doesn't appear to be valid!
exiting
╠ ## Bereinige zuvor installierte Anwendungsdaten.
>>> Regenerating /etc/ld.so.cache...
╠ ## Package phase: postremove
!!! Error: Target "sysvinit" doesn't appear to be valid!
exiting
>>> Regenerating /etc/ld.so.cache...
╠ ## Package phase: postinstall
!!! Error: Target "sysvinit" doesn't appear to be valid!
exiting
* Updating systemd journal catalogs ... [ ok ]
* Running udev control --reload for reloading rules and databases ... [ ok ]
* Upstream mandates the /etc/mtab file should be a symlink to /proc/mounts.
* Not having it is not supported by upstream and will cause tools like 'df'
* and 'mount' to not work properly. Please run:
* # ln -sf '/proc/self/mounts' '/etc/mtab'
*
* To get additional features, a number of optional runtime dependencies may
* be installed:
* - sys-apps/systemd-ui: for GTK+ systemadm UI and gnome-ask-password-agent
╠ ## Aufräumen: sys-apps/systemd-208-r3

Re: filesystem ... does not contain valid init=/sbin/init

Posted: Wed Apr 09, 2014 16:03
by Stupot
/etc/init.d/ is the openrc way of starting things. Sabayon uses systemd now.

systemctl start NetworkManager

Re: filesystem ... does not contain valid init=/sbin/init

Posted: Wed Apr 09, 2014 19:04
by udiljak
Thanks a lot. It didn't start anyway, but like this I found out about 'journalctl' giving me another error message. That one I found in a FAQ.

After fixing NetworkManager I could at least connect to wireless and do 'equo update' and 'equo install systemd'. That didn't help much because it seems to me that you guys forgot to add a dependency on systemd-sysv-utils?! After manually installing that and reinstalling systemd again I could finally boot my system normally.

Thanks for your help!

Cheers,
Ben

Re: filesystem ... does not contain valid init=/sbin/init

Posted: Wed Apr 09, 2014 19:41
by Stupot
Glad you got it resolved.

There are definitely some rough patches transitioning from openRC to systemd, although this issue had been caught by the testers using the sabayon-limbo repository and supposedly fixed, so it's odd and frustrating that it made it to regular users.

Hopefully the migration of other system components into systemd services goes smoothly from here on out, now that the major hurtle (using systemd instead of openrc) is over with.

Re: filesystem ... does not contain valid init=/sbin/init

Posted: Fri Apr 11, 2014 2:33
by albfneto
im my systems, changing the boot lines of ALL BOOTABLE KERNELS in the /boot/grub/grub.cfg file, to:

Code: Select all

"real_init=/usr/lib/systemd/systemd"
solve the issues and the system boots, using systemd.

Re: filesystem ... does not contain valid init=/sbin/init

Posted: Fri Apr 11, 2014 6:21
by MALsPa
svantoviit wrote:Try "real_init=/usr/lib/systemd/systemd"
albfneto wrote:im my systems, changing the boot lines of ALL BOOTABLE KERNELS in the /boot/grub/grub.cfg file, to:

Code: Select all

"real_init=/usr/lib/systemd/systemd"
solve the issues and the system boots, using systemd.
Thank you both; this worked for me, too. I had just about given up on this installation.

Re: filesystem ... does not contain valid init=/sbin/init

Posted: Mon Apr 14, 2014 19:41
by imaginasys
How about reading a good source of information on systemd first :

https://wiki.gentoo.org/wiki/Systemd

And check section about Grub 2.

Regards,
Bernard :mrgreen: