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

comapony · 2014-01-21 01:19:09

I'm having the issue where when I boot after doing a fresh install, it gives me:

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 /]#

My fstab:

# /etc/fstab
# <file system> <dir>   <type>  <options>       <dump>  <pass>
# /dev/sda1 LABEL=homerroot
UUID=877deab9-624d-4e1d-90a1-ccc1d6ebc0c6       /               ext4            rw,relatime,data=ordered        0 1

# /dev/sda2 LABEL=homerboot
UUID=77835da5-8a38-44c1-bf27-bb657df4484b       /boot           ext4            rw,relatime,data=ordered        0 2

# /dev/sda3 LABEL=homeretc
UUID=8a1b5bd8-b147-41e0-87df-70a4a9e12df2       /etc            ext4            rw,relatime,data=ordered        0 2

# /dev/sda4 LABEL=homervar
UUID=8eb2e7b1-cdf1-46ce-9dc1-439d002bfae4       /var            ext4            rw,relatime,data=ordered        0 2

# /dev/sda5 LABEL=homerusr
UUID=bce162b4-d27f-450c-a0e6-4d3ebc6242dc       /usr            ext4            rw,relatime,data=ordered        0 2

# /dev/sda6 LABEL=home
UUID=62de76ab-b6d4-4e3d-a423-c287b81813a9       /home           ext4            rw,relatime,data=ordered        0 2

# /dev/sda7 LABEL=public
UUID=d98a9c8e-2301-4e66-8c7f-26167633a4b0       /public         ext4            rw,relatime,data=ordered        0 2

This looks fine to me, but when /dev/sda1 is mounted at /new_root, none of the other devices are mounted....
I don't know if this is what's causing the problem since /etc, and /usr are on separate partitions from root, but
this would be the first time I get a problem dividing things this way (on ubuntu, mint, fedora, et cetera).

So I tried:

https://bbs.archlinux.org/viewtopic.php … 3#p1283343

I get "* is owned by filesystem 2013.05-2" for all three dirs from step three.
None of the other steps have any effect....

I also tried:

https://bbs.archlinux.org/viewtopic.php?id=172943

My /dev/sda1 mounts to new_root, so I don't think I'm having his problem.

And:

https://bbs.archlinux.org/viewtopic.php?id=166423

I reinstalled systemd-sysvcompat, and I'm sure that's not my problem.
Interestingly enough, /usr/lib/systemd/systemd is an elf file on my target hard disk.
Is this an outdated issue or something? Or should /usr/lib/systemd/systemd be a text file?

Thanks in advance for your help guys!

WorMzy · 2014-01-21 01:25:17

You have a separate /usr partition (which isn't recommended btw), but did you add the usr hook to your mkinitcpio.conf before generating an initrd?

EDIT: Not sure if the seperate etc is supported at all. You might need to write a custom initcpio hook if you want to keep that.

Recommend reading: http://freedesktop.org/wiki/Software/sy … is-broken/

Last edited by WorMzy (2014-01-21 01:27:17)

WonderWoofy · 2014-01-21 01:28:45

A separate /etc is not supported whatsoever. There needs to be initial access to a few things there. I'm sure it could be made to work with some initramfs hackery. But it is neither supported or wise to do so IMO.

WorMzy · 2014-01-21 01:33:35

Oh, and /usr/lib/systemd/systemd is supposed to be an ELF binary. Not sure why you think it should be a text file.

comapony · 2014-01-21 02:16:20

WorMzy wrote:

Oh, and /usr/lib/systemd/systemd is supposed to be an ELF binary. Not sure why you think it should be a text file.

I saw another thread saying that adding an entry there would help. I think it was "init=<something>".

WonderWoofy wrote:

A separate /etc is not supported whatsoever. There needs to be initial access to a few things there. I'm sure it could be made to work with some initramfs hackery. But it is neither supported or wise to do so IMO.

I'll not do the separate partitions then. Thanks. I'll check back if it works/doesn't-works.

WonderWoofy · 2014-01-21 04:28:26

Speicifying the init=/usr/lib/systemd/systemd kernel parameter is not going to help at all. Directing it is still being directed to /usr, which is not mounted at all at this point in the boot process. You need to set up mkinitcpio to handle this correctly.

comapony · 2014-01-21 19:03:05

Okay, well. I've reinstalled arch on my comp, with only a root partition and a home partition. Now it gets stuck in fsck. It doesn't do anything after that. Ugghghgghjhhhh....

Inxsible · 2014-01-21 22:54:22

comapony wrote:

Okay, well. I've reinstalled arch on my comp, with only a root partition and a home partition. Now it gets stuck in fsck. It doesn't do anything after that. Ugghghgghjhhhh....

Instead of getting your panties in a wad, try to explain what the problem is with proper logs and such so people can help you. If not, get a blog and rant there.

comapony · 2014-01-27 08:59:17

Inxsible wrote:

Instead of getting your panties in a wad, try to explain what the problem is with proper logs and such so people can help you. If not, get a blog and rant there.

Yeah, I would've done that if there wasn't info out there about this and figured it out on my own already. Just cause I'm in the "newb corner" and I've got three posts doesn't mean I'm an idiot.

PS: Sorry for the late reply babe.

x33a · 2014-01-27 13:54:38

comapony wrote:

Yeah, I would've done that if there wasn't info out there about this and figured it out on my own already. Just cause I'm in the "newb corner" and I've got three posts doesn't mean I'm an idiot.

Great to hear that you figured it out. So maybe you should post your solution here, so that other people can benefit from it.

Also, please mark the thread as solved by editing the first post's title.

Last edited by x33a (2014-01-27 13:55:07)

Arch Linux

#1 2014-01-21 01:19:09

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

#2 2014-01-21 01:25:17

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

#3 2014-01-21 01:28:45

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

#4 2014-01-21 01:33:35

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

#5 2014-01-21 02:16:20

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

#6 2014-01-21 04:28:26

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

#7 2014-01-21 19:03:05

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

#8 2014-01-21 22:54:22

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

#9 2014-01-27 08:59:17

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

#10 2014-01-27 13:54:38

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

Board footer