Trouble after upgrade

Installer Issues via Installer -- Not for global upgrades or upgrading individual packages -- ONLY ISSUES WITH INSTALLATION OF THE OS -- Can't get Sabayon installed, than post here, otherwise use correct forums

Moderator: Moderators

Trouble after upgrade

Postby Alex7793 » Tue Apr 01, 2014 14:59

Hi to all!
Yesterday I upgrade my system via Rigo and then restart it.
At this point startup stop and the message
"The filesystem /dev/sdb5 mounted at /newroot does not contain a valid init=/sbin/init" appear.

What's happened? How can I fix it?
Alex7793
Simple Hen
 
Posts: 46
Joined: Thu Feb 05, 2009 17:06

Re: Trouble after upgrade

Postby mosesj01 » Tue Apr 01, 2014 16:12

I am jumping on this flaming bandwagon as well.

Two different machines, same problem as described in the first post. Feels as if the problem may lie in the Grub parameters, but cannot be certain of it.

"...does not contain a valid init=/sbin/init" "Please file a bug report..."

Please, let there be a quick and simple fix to this.
mosesj01
Baby Hen
 
Posts: 7
Joined: Sun Apr 01, 2012 22:15

Re: Trouble after upgrade

Postby svantoviit » Tue Apr 01, 2014 17:45

Should be fixed meanwhile. Just (re)install sys-apps/systemd-sysv-utils.
More info on the issue and alternative solution in this thread: [sabayon-dev] Sabayon fails to boot after last update (Limbo).
svantoviit
Old Dear Hen
 
Posts: 658
Joined: Sun Feb 28, 2010 17:55

Re: Trouble after upgrade

Postby mosesj01 » Tue Apr 01, 2014 18:16

Thanks.

... umm, n00b question: How best should I go about the (re)installing; this part is uncharted territory for me. A response or a link to a response would help nicely.
mosesj01
Baby Hen
 
Posts: 7
Joined: Sun Apr 01, 2012 22:15

Re: Trouble after upgrade

Postby svantoviit » Tue Apr 01, 2014 20:50

Probably you are not able to boot. So you need to tweak the init boot parameter manually.
Enter the grub edit mode and change the init path as pierigno mentions in his email.
When you manage to boot into the system install the systemd-sysv-utils package as usual with equo or rigo, it's in sabayonlinux.org already.
Everything should be fine then… supposed you are using systemd.
svantoviit
Old Dear Hen
 
Posts: 658
Joined: Sun Feb 28, 2010 17:55

Re: Trouble after upgrade

Postby mosesj01 » Tue Apr 01, 2014 21:21

Thanks. I'll check back to see if there is any fix later on. You have my gratitude for addressing this problem.
mosesj01
Baby Hen
 
Posts: 7
Joined: Sun Apr 01, 2012 22:15

Re: Trouble after upgrade

Postby Alex7793 » Wed Apr 02, 2014 1:56

I tried to fix it using advices from devel mailing list and from this post, but it don't work.
I put init=/usr/lib/systemd/systemd after setparams line and after initrd line in grud edit mode but system can boot and messate it's always the same.

This is my what is in grub edit mode before I touch it
Code: Select all
setparams 'Sabayon GNU/Linux'

           load_video
           insmod gzio
           insmod part_msdos
           insmod ext2
           set root='hd1,msdos1'
           if [ x$feature_platform_search_hint = xy]; then
              search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=  ahci1,msdos1 ff398bbc-cf0a-48fe-8aa4-o5cd14dgd860
          else
              search --nofloppy --fs-uuid --set=root ff398bbc-cf0a-48fe-8aa4-o5cd14dgd860
          fi
          echo 'Loading Linux x86_64-3.8.0-sabayon ...'
          linux /kernel-genkernel-x86_64-3.8.0-sabayon ro splash=silent,theme:sabayon video=vesafb:ywrap, mtrr:3 vga=791 gfxpayload=1024x768x16 console+tty1 quiet dokeymap keymap=it domdadm resume=swap:/dev/sdb2 real_resume=/dev/sdb2 root=/dev/sdb5 docrypt
         echo 'Loading initial ramdisk...'
         initrd /initrams-genkernel-x86_64-3.8.0-sabayon


what can I do?
Alex7793
Simple Hen
 
Posts: 46
Joined: Thu Feb 05, 2009 17:06

Re: Trouble after upgrade

Postby joost » Wed Apr 02, 2014 9:26

Do NOT edit grub.cfg directly.

- Boot the PC
- press ctrl+e to edit the bootline
- add init=/usr/lib64/systemd/systemd
- press ctrl+x to boot.

Once the system is booted try to (re)install sys-apps/systemd-sysv-utils
Then check if the symlink is correct:

Code: Select all
sabayon joost # ls -l  /sbin/init
lrwxrwxrwx 1 root root 26 Mar 26 19:43 /sbin/init -> ../usr/lib/systemd/systemd
joost
Sagely Hen
 
Posts: 2605
Joined: Fri Nov 17, 2006 12:11
Location: The Netherlands

Re: Trouble after upgrade

Postby Alex7793 » Wed Apr 02, 2014 10:02

In which part of bootline I must add init=/usr/lib64/systemd/systemd ?
Alex7793
Simple Hen
 
Posts: 46
Joined: Thu Feb 05, 2009 17:06

Re: Trouble after upgrade

Postby BoeroBoy » Wed Apr 02, 2014 14:43

That's a good trick. Sadly not an April fool joke. I didn't actually reboot until this morning. Always keep a dual/multi boot partition. Fedora to the rescue!

Sadly reinstalling systemd-sysv-utils from chroot did not do the trick. Works when booting from manually edited boot line. Tried reinstalling, tried removing and reinstalling. Sadly/luckily there's this little safety mechanism that disallows that.

Code: Select all
$ sudo equo remove systemd-sysv-utils

☢   Ouch!, the following system packages were pulled in:
☢     # app-misc/sabayon-version-14.04-r3



Kinda miss the old days of GRUB1. :-| oh well. Thanks for being here guys. Hopefully google indexes this page soon.
User avatar
BoeroBoy
Simple Hen
 
Posts: 70
Joined: Fri Feb 23, 2007 20:25

Next

Return to Installer Issues - Calamares **Not for Package Manager Stuff**

Who is online

Users browsing this forum: No registered users and 1 guest