Root device mounted successfully, but /sbin/init does not exist.

rohithreddy · 2016-11-03 10:18:39

I upgraded system and restarted,now I'm stuck here

/dev/sda1: recovering journal
Error:Root device mounted successfully, but /sbin/init does not exist.
Bailing out, you are on your own.Good luck.

sh: can't access tty; job control turned off
[rootfs ]#

[rootfs ]# ls
VERSION  config hooks lib proc sbin usr
Bin dev init lib64 root sys
buildconfig  etc init_functions new_root run to
[rootfs new_root]#ls -l /sbin/init  -> busybox
From chroot
ls -l /sbin/init ->lib/systemd/systemd

mkinitcpio -p linux 
Building image from preset: /etc/mkinitcpio.d/linux.preset:'default'
Starting build: 4.8.6-1-ARCH
  Running build hook: [base]
  Running build hook: [udev]
ERROR: file not found '/usr/lib/systemd/systemd-udevd'
ERROR:binary dependency 'libsystemd-shared-231.so' not found for '/usr/bin/systemd-tmpfiles'
Running build hook: [autodetect]
  Running build hook: [modconf]
Running build hook: [block]
WARNING: errors were encountered during the build.the image may not be complete.

Fallback initramfs

systemd-tmpfiles: error while loading shared libraries: libsystemd-shared-231.so: cannot open shared object file: No such file or directory
/Init:line 23:/usr/lib/systemd/systemd-udevd':not found
ERROR : device 'UUID=769248f5-7eab-4bc6-777d-14b24f8731f8 'not found.Skipping fsck.
ERROR: Unable to find root device 'UUID='769248f5-7eab-4bc6-777d-14b24f8731f8'.
You are being dropped to a recovery shell
   Type 'exit' to try and continue booting
Sh: can't access tty; job control turned off
[Rootfs ]#

Tried pacman -S systemd

Warning: could not get file information for /usr/lib/systemd/libsystemd-shared-231.so
Warning: could not get file information for /usr/lib/systemd/systemd
Warning: could not get file information for /usr/lib/systemd/systemd-journald
Warning: could not get file information for /usr/lib/systemd/systemd-logind
Warning: could not get file information for /usr/lib/systemd/udevd

How can I resolve this?Please help me

Last edited by rohithreddy (2016-11-04 09:09:59)

rohithreddy · 2016-11-03 11:06:43

Hey,can anyone please help me
my boot partition and root partitions are same and root partition is mounted at new_root
sbin/init points to /lib/systemd/systemd

WorMzy · 2016-11-03 11:22:47

Please don't bump.

https://wiki.archlinux.org/index.php/Co … ct#Bumping

rohithreddy · 2016-11-03 11:26:26

Wow,Got reply!
I was reading other threads and moderator asked to post where sbin/init points to so I posted that

Scimmia · 2016-11-03 14:32:19

This usually happens because you're mounting the wrong partition as "root" in the kernel command line.

rohithreddy · 2016-11-03 16:06:48

I've not changed anything,I just upgraded with command pacman -Syyu and after that my system stuck for a while,so I restarted and I got error.
What should I do in order to recover?
I can't even edit files with nano

ewaller · 2016-11-03 17:22:36

Tell us about your partition scheme ( lsblk -af )
Tell us which bootloader you are using.
Tell us about your bootloader configuratuion

I don't have any idea what files you are trying to edit with nano, or what environment you are in (I suspect a recovery shell). You may need to boot an install media and work from there.

rohithreddy · 2016-11-03 18:17:32

Hi ewaller, I'm at [rootfs ]# , I tried lsblk -af ,I got lsblk not found.
Bootloader is grub,I was referring to rookie comment https://bbs.archlinux.org/viewtopic.php?id=219105 he asked to edit bootloader configuration to include init=/usr/lib/systemd/systemd

rohithreddy · 2016-11-04 04:20:40

Somehow I managed to get a live usb ,could anyone help me from here?
I've only one partition /dev/sda1 that uuid is same as in grub.cfg file
Here is grub.cfg

insmod part_gpt
insmod part_msdos
If [ -s $prefix/grubenv]; then 
 load_env
Fi
if [$nextentry]
  set default=$next_entry
  set next_entry=
  save_env next_entry
  set boot_once =true
else
  Set default="0"
Fi
.
.
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if[x$feature_platform_search_hint =xy];then
 Search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-bios metal=ahci0,msdos1 769248f5-7eab-4bc6-777d-14b24f8731f8
else
 search --no-floppy --fs-uuid --set=root 769248f5-7eab-4bc6-777d-14b24f8731f8
Fi
 Font="/usr/share/grub/Unicode.pf2"
Fi
.
.
menu entry 'arch linux' --class 'arch --class gnu-linux --class gnu-linux --class os $menuentry_id_option 'gnulinux-simple-uuid' {
 load_video
 set gfxpayload=keep
 Insmod gzio
insmod part_msdos
 set root='hd0,msdos1'
if[x$feature_platform_search_hint =xy];then
 Search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-bios metal=ahci0,msdos1 769248f5-7eab-4bc6-777d-14b24f8731f8
else
 search --no-floppy --fs-uuid --set=root #uuid
Fi
echo 'Loading Linux linux...'
linux /boot/vmlinuz-linux root=UUID=769248f5-7eab-4bc6-777d-14b24f8731f8 rw quiet
echo 'Loading initial ramdisk'
United /boot/initramfs-linux.img
}

Last edited by rohithreddy (2016-11-04 05:52:59)

jasonwryan · 2016-11-04 04:47:33

grub config wrote:

linux /boot/vmlinuz-linux root=UUID=uuid rw quiet

That isn't going to work...

rohithreddy · 2016-11-04 05:14:17

So,I can't recover?
Does it work if I install grub on /dev/sda1 again?
Everytime I upgrade I run into some problem,I don't want to loose my data

jasonwryan · 2016-11-04 05:19:40

From a chroot, change your config to point to an actual UUID: https://wiki.archlinux.org/index.php/Pe … ng#by-uuid

rohithreddy · 2016-11-04 05:34:12

linux /boot/vmlinuz-linux root=UUID=769248f5-7eab-4bc6-777d-14b24f8731f8 rw quiet

It actually points to correct UUID
I wrote uuid in short for my uuid(769248f5-7eab-4bc6-777d-14b24f8731f8) in the code as I'm on mobile rn
What am I missing?
Here's my /etc/default/grub

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_ DISTRIBUTOR="'arch"
GRUB_CMDLINE_LINUX_DEFAULT="QUEIT"
Grub_CMDLINE_LINUX=""
grub_PRELOAD_MODULES="part_gpt part_msdos"
.
.
#GRUB_DISABLE_LINUX_UUID=true

GRUB_DISABLE_RECOVERY=true

Last edited by rohithreddy (2016-11-04 06:01:06)

rohithreddy · 2016-11-04 06:21:05

From chroot I'm trying to install grub but I get
pacman: error while loading shared libraries:/usr/lib/liblz4.so.1: invalid ELF header

Tried to generate grub.cfg file

grub-mkconfig -o /boot/grub/grub.cfg
Generating linux image:/boot/vmlinuz-linux
Found initrd image(s) int /boot: initramfs-linux.cfg
Found fallback initrd image in/boot:initramfs-linux-fallback.cfg
logger:error while loading shared libraries:/usr/lib/liblz4.so.1: invalid ELF header
logger:error while loading shared libraries:/usr/lib/liblz4.so.1: invalid ELF header
logger:error while loading shared libraries:/usr/lib/liblz4.so.1: invalid ELF header
logger:error while loading shared libraries:/usr/lib/liblz4.so.1: invalid ELF header
logger:error while loading shared libraries:/usr/lib/liblz4.so.1: invalid ELF header
logger:error while loading shared libraries:/usr/lib/liblz4.so.1: invalid ELF header
logger:error while loading shared libraries:/usr/lib/liblz4.so.1: invalid ELF header
logger:error while loading shared libraries:/usr/lib/liblz4.so.1: invalid ELF header
  Warning: Failed to connect to lvmetad. Falling back to device scanning
logger:error while loading shared libraries:/usr/lib/liblz4.so.1: invalid ELF header
done

Could anyone please help

Last edited by rohithreddy (2016-11-04 06:35:14)

jasonwryan · 2016-11-04 06:43:20

While in the chroot, reinstall lz4 and -Syu.

rohithreddy · 2016-11-04 07:01:53

I get same error:
pacman -S lz4

pacman: error while loading shared libraries:/usr/lib/liblz4.so.1: invalid ELF header

Everytime I upgrade I run into some problem and I had to reinstall again,Is there a way to get in?

Last edited by rohithreddy (2016-11-04 07:06:15)

jasonwryan · 2016-11-04 07:04:07

From outside the chroot do `pacman -r /mnt -S lz4`.

rohithreddy · 2016-11-04 07:11:06

No errors with lz4

grub-mkconfig -o /boot/grub/grub.cfg
Generating linux image:/boot/vmlinuz-linux
Found initrd image(s) int /boot: initramfs-linux.cfg
Found fallback initrd image in/boot:initramfs-linux-fallback.cfg
  Warning: Failed to connect to lvmetad. Falling back to device scanning
done

jasonwryan · 2016-11-04 07:13:02

Ignore the lvm warning. Check the grub config to make sure it actually does have a valid kernel line and then reboot.

rohithreddy · 2016-11-04 07:15:02

Thanks for helping and your patience.
I didn't get" valid kernel line".what is that?
linux /boot is pointing to correct uuid

rohithreddy · 2016-11-04 07:44:13

Here's the entire grub.cfg file

insmod part_gpt
insmod part_msdos
If [ -s $prefix/grubenv]; then 
 load_env
Fi
if [$nextentry]
  set default=$next_entry
  set next_entry=
  save_env next_entry
  set boot_once =true
else
  Set default="0"
Fi
if [ x"${feature_menuentry_id}" = xy]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
Fi
export menuentry_id_option
if ["${prev_saved_entry}"];then]
  set saved_entry=$prev_saved_entry
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once =true
fi
function savedefault {
  if[-z "${boot_once}"]; then
     saved_entry="$chosen"
      Save_env saved_entry
   Fi
}

insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if[x$feature_platform_search_hint =xy];then
 Search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-bios metal=ahci0,msdos1 769248f5-7eab-4bc6-777d-14b24f8731f8
else
 search --no-floppy --fs-uuid --set=root 769248f5-7eab-4bc6-777d-14b24f8731f8
Fi
 Font="/usr/share/grub/Unicode.pf2"
Fi
.
.
menu entry 'arch linux' --class 'arch --class gnu-linux --class gnu-linux --class os $menuentry_id_option 'gnulinux-simple-uuid' {
 load_video
 set gfxpayload=keep
 Insmod gzio
insmod part_msdos
 set root='hd0,msdos1'
if[x$feature_platform_search_hint =xy];then
 Search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-bios metal=ahci0,msdos1 769248f5-7eab-4bc6-777d-14b24f8731f8
else
 search --no-floppy --fs-uuid --set=root #uuid
Fi
echo 'Loading Linux linux...'
linux /boot/vmlinuz-linux root=UUID=769248f5-7eab-4bc6-777d-14b24f8731f8 rw quiet
echo 'Loading initial ramdisk'
United /boot/initramfs-linux.img
}
submenu 'Advanced options for 'Arch Linux' $menuentry_id_option 'gnulinux-advanced-769248f5-7eab-4bc6-777d-14b24f8731f8'{
  menu entry 'arch linux, with Linux linux' --class 'arch --class gnu-linux --class gnu-linux --class os $menuentry_id_option 'gnulinux-linux-advanced- 769248f5-7eab-4bc6-777d-14b24f8731f8'{
 load_video
 set gfxpayload=keep
 Insmod gzio
insmod part_msdos
insmod ext2
 set root='hd0,msdos1'
if[x$feature_platform_search_hint =xy];then
 Search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-bios metal=ahci0,msdos1 769248f5-7eab-4bc6-777d-14b24f8731f8
else
 search --no-floppy --fs-uuid --set=root 769248f5-7eab-4bc6-777d-14b24f8731f8
Fi
echo 'Loading Linux linux...'
linux /boot/vmlinuz-linux root=UUID=769248f5-7eab-4bc6-777d-14b24f8731f8 rw quiet
echo 'Loading initial ramdisk'
initrd /boot/initramfs-linux.img
}
menu entry 'arch linux, with Linux linux(fallback initramfs)' --class 'arch --class gnu-linux --class gnu-linux --class os $menuentry_id_option 'gnulinux-linux-advanced- 769248f5-7eab-4bc6-777d-14b24f8731f8'{
 load_video
 set gfxpayload=keep
 Insmod gzio
insmod part_msdos
insmod ext2
 set root='hd0,msdos1'
if[x$feature_platform_search_hint =xy];then
 Search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-bios metal=ahci0,msdos1 769248f5-7eab-4bc6-777d-14b24f8731f8
else
 search --no-floppy --fs-uuid --set=root 769248f5-7eab-4bc6-777d-14b24f8731f8
Fi
echo 'Loading Linux linux...'
linux /boot/vmlinuz-linux root=UUID=769248f5-7eab-4bc6-777d-14b24f8731f8 rw quiet
echo 'Loading initial ramdisk'
initrd /boot/initramfs-linux-fallback.img
}

}

Last edited by rohithreddy (2016-11-04 07:46:22)

jasonwryan · 2016-11-04 07:46:07

Reboot and see if it works. Don't expect us to hold your hand through every step here...

rohithreddy · 2016-11-04 07:48:48

I did pacman -Syu and I did reboot but still I'm stuck at

/dev/sda1: recovering journal
Error:Root device mounted successfully, but /sbin/init does not exist.
Bailing out, you are on your own.Good luck.
sh: can't access tty; job control turned off
[rootfs ]#

Rookie asked to edit https://bbs.archlinux.org/viewtopic.php?id=219105 he asked to edit bootloader configuration to include init=/usr/lib/systemd/systemd
Where should I add that?

Last edited by rohithreddy (2016-11-04 07:51:34)

jasonwryan · 2016-11-04 07:51:21

You are going to have to make more of an effort yourself, I'm not your search applicance:
https://bbs.archlinux.org/viewtopic.php?id=201938

rohithreddy · 2016-11-04 08:01:39

I've only one desktop and now I'm using mobile though. I opened this thread after reading several threads with same problem.None of them helped me.

[rootfs ]# ls
VERSION  config hooks lib proc sbin usr
Bin dev init lib64 root sys
buildconfig  etc init_functions new_root run to
[rootfs new_root]#ls -l /sbin/init  -> busybox
From chroot
ls -l /sbin/init ->lib/systemd/systemd

Appreciate your help

Last edited by rohithreddy (2016-11-04 08:01:53)

Arch Linux

#1 2016-11-03 10:18:39

Root device mounted successfully, but /sbin/init does not exist.

#2 2016-11-03 11:06:43

Re: Root device mounted successfully, but /sbin/init does not exist.

#3 2016-11-03 11:22:47

Re: Root device mounted successfully, but /sbin/init does not exist.

#4 2016-11-03 11:26:26

Re: Root device mounted successfully, but /sbin/init does not exist.

#5 2016-11-03 14:32:19

Re: Root device mounted successfully, but /sbin/init does not exist.

#6 2016-11-03 16:06:48

Re: Root device mounted successfully, but /sbin/init does not exist.

#7 2016-11-03 17:22:36

Re: Root device mounted successfully, but /sbin/init does not exist.

#8 2016-11-03 18:17:32

Re: Root device mounted successfully, but /sbin/init does not exist.

#9 2016-11-04 04:20:40

Re: Root device mounted successfully, but /sbin/init does not exist.

#10 2016-11-04 04:47:33

Re: Root device mounted successfully, but /sbin/init does not exist.

#11 2016-11-04 05:14:17

Re: Root device mounted successfully, but /sbin/init does not exist.

#12 2016-11-04 05:19:40

Re: Root device mounted successfully, but /sbin/init does not exist.

#13 2016-11-04 05:34:12

Re: Root device mounted successfully, but /sbin/init does not exist.

#14 2016-11-04 06:21:05

Re: Root device mounted successfully, but /sbin/init does not exist.

#15 2016-11-04 06:43:20

Re: Root device mounted successfully, but /sbin/init does not exist.

#16 2016-11-04 07:01:53

Re: Root device mounted successfully, but /sbin/init does not exist.

#17 2016-11-04 07:04:07

Re: Root device mounted successfully, but /sbin/init does not exist.

#18 2016-11-04 07:11:06

Re: Root device mounted successfully, but /sbin/init does not exist.

#19 2016-11-04 07:13:02

Re: Root device mounted successfully, but /sbin/init does not exist.

#20 2016-11-04 07:15:02

Re: Root device mounted successfully, but /sbin/init does not exist.

#21 2016-11-04 07:44:13

Re: Root device mounted successfully, but /sbin/init does not exist.

#22 2016-11-04 07:46:07

Re: Root device mounted successfully, but /sbin/init does not exist.

#23 2016-11-04 07:48:48

Re: Root device mounted successfully, but /sbin/init does not exist.

#24 2016-11-04 07:51:21

Re: Root device mounted successfully, but /sbin/init does not exist.

#25 2016-11-04 08:01:39

Re: Root device mounted successfully, but /sbin/init does not exist.

Board footer