/sbin/init does not exist after custom kernel [solved]

mich04 · 2012-03-31 13:40:59

So just as the title describes here is the error. The only variable that has changed on my computer is that I made a custom kernel yesterday. This particular install is on a USB drive that I carry with me. I tried to mount root under sda2,sdb2 and sdc2. Sometimes I have that problem when using it on different computers. Now I did boot up this particular computer, because I have Arch directly installed on it. I noticed when it mounted the USB drive it as "8.0 GB Filesystem" and "104 MB Filesystem" instead of " / " and "/boot" that was the only noticble difference that I saw. I have also never used "pacman -Syuf" to update my system it has always been "pacman -Syu"

When I installed the kernel yesterday it did prompt me to remove the old kernel during installation.

Error: Root device mounted successfully, but /sbin/init does not exist.
Bailing out, you are on your own. Good Luck
[ramfs /]#

here is syslinux.cfg

DEFAULT arch
PROMPT  1       # Set to 1 if you always want to display the boot: prompt 
TIMEOUT 5 
UI menu.c32
MENU TITLE Arch Linux
#MENU BACKGROUND splash.png
MENU COLOR border       30;44   #40ffffff #a0000000 std
MENU COLOR title        1;36;44 #9033ccff #a0000000 std
MENU COLOR sel          7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel        37;44   #50ffffff #a0000000 std
MENU COLOR help         37;40   #c0ffffff #a0000000 std
MENU COLOR timeout_msg  37;40   #80ffffff #00000000 std
MENU COLOR timeout      1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07        37;40   #90ffffff #a0000000 std
MENU COLOR tabmsg       31;40   #30ffffff #00000000 std

LABEL Arch School SDA
    MENU LABEL Arch Linux School SDA
    LINUX ../vmlinuz-linux-x
    APPEND root=/dev/sda2 ro
    INITRD ../initramfs-linux-x.img

LABEL Arch Home SDC
    MENU LABEL Arch Linux Home SDC
    LINUX ../vmlinux-linux-x
    APPEND root=/dev/sdc2 ro
    INITRD ../initramfs-linux-x.img

LABEL Archfallback
    MENU LABEL Arch Linux Fallback
    LINUX ../vmlinuz-linux-x
    APPEND root=/dev/sdc2 ro
    INITRD ../initramfs-linux-fallback-x.img

LABEL hdt
    MENU LABEL HDT (Hardware Detection Tool)
    COM32 hdt.c32

LABEL reboot
    MENU LABEL Reboot
    COM32 reboot.c32

LABEL off
    MENU LABEL Power Off
    COMBOOT poweroff.com

fstab

# <file system>    <dir>    <type>    <options>    <dump>    <pass>
tmpfs        /tmp    tmpfs    nodev,nosuid    0    0
UUID=bdefb562-d750-4843-abdd-a60deaaaccb8 / ext4 defaults 0 1
UUID=cac72e51-8400-43f6-a787-f72c3050ccf5 /boot ext4 defaults 0 1

mkinitcpio.conf

# MODULES 
MODULES="" 

# BINARIES 
BINARIES="" 

# FILES 
FILES="" 

# HOOKS 
HOOKS="base udev usb autodetect pata scsi sata filesystems usbinput fsck" 

# COMPRESSION 
#COMPRESSION="gzip" 
#COMPRESSION="bzip2" 
#COMPRESSION="lzma" 
#COMPRESSION="xz" 
#COMPRESSION="lzop" 

# COMPRESSION_OPTIONS 
#COMPRESSION_OPTIONS=""

http://i1190.photobucket.com/albums/z45 … G_0686.jpg

Last edited by mich04 (2012-04-04 15:41:58)

Gcool · 2012-03-31 14:36:45

Try specifying your root partition by uuid in your syslinux.cfg as well.

mich04 · 2012-04-01 02:36:25

Now it says it can't mount the root partition in the error, I am using the correct uuid here is my new syslinux.cfg, below is the new picture of the error. When I am in my main instalation it mounts that drive under that uuid.

DEFAULT arch
PROMPT  1       # Set to 1 if you always want to display the boot: prompt 
TIMEOUT 5 
UI menu.c32
MENU TITLE Arch Linux
#MENU BACKGROUND splash.png
MENU COLOR border       30;44   #40ffffff #a0000000 std
MENU COLOR title        1;36;44 #9033ccff #a0000000 std
MENU COLOR sel          7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel        37;44   #50ffffff #a0000000 std
MENU COLOR help         37;40   #c0ffffff #a0000000 std
MENU COLOR timeout_msg  37;40   #80ffffff #00000000 std
MENU COLOR timeout      1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07        37;40   #90ffffff #a0000000 std
MENU COLOR tabmsg       31;40   #30ffffff #00000000 std

LABEL Arch School SDA
    MENU LABEL Arch Linux School SDA
    LINUX ../vmlinuz-linux-x
    APPEND root=UUID=bdefb562-d750-4843-abdd-a60deaaaccb8 ro
    INITRD ../initramfs-linux-x.img

LABEL Arch Home SDC
    MENU LABEL Arch Home SDC
    LINUX ../vmlinux-linux-x
    APPEND root=/dev/sdc2 ro
    INITRD ../initramfs-linux-x.img

LABEL Archfallback
    MENU LABEL Arch Linux Fallback
    LINUX ../vmlinuz-linux-x
    APPEND root=/dev/sdc2 ro
    INITRD ../initramfs-linux-fallback-x.img

LABEL hdt
    MENU LABEL HDT (Hardware Detection Tool)
    COM32 hdt.c32

LABEL reboot
    MENU LABEL Reboot
    COM32 reboot.c32

LABEL off
    MENU LABEL Power Off
    COMBOOT poweroff.com

http://i1190.photobucket.com/albums/z45 … G_0688.jpg

Gcool · 2012-04-01 08:20:24

You have to specify the full path to the disk, not just the UUID. So something among the lines of:

APPEND root=/dev/disk/by-uuid/bdefb562-d750-4843-abdd-a60deaaaccb8 ro

Raija · 2012-04-01 09:48:59

Same issue here, but after a fresh net-install. I'm using GRUB, and changing the root directory to UUID did nothing to produce a different output. I'm getting kernel panic whenever I happen to boot Arch.

mich04 · 2012-04-01 11:58:08

Well I gave that a try with root=/dev/sdc/<uuid> It produced the same error of can't find root device.

falconindy · 2012-04-01 13:25:15

Gcool wrote:

You have to specify the full path to the disk, not just the UUID. So something among the lines of:
APPEND root=/dev/disk/by-uuid/bdefb562-d750-4843-abdd-a60deaaaccb8 ro

No, UUID= is a perfectly valid way of specifying a UUID. early init uses blkid to resolve these tags.

mich04 · 2012-04-01 13:28:26

That's what I thought because that is how it was stated in the wiki for syslinux. falconindy do you have an idea as to what this could be? Should I just reinstall the test system and try the kernel compilation again? The system is just for learning. It does not matter if I just reinstall anyway.

falconindy · 2012-04-01 14:03:03

If the point is to learn, I would opt to try and fix it and understand what broke. Make sure you have the proper modules available on your custom kernel's initramfs. You can use lsinitcpio to poke around at the contents.

mich04 · 2012-04-04 15:41:23

Solved it was an error in the kernel when I was messing with it recompiled a new one and it works now.

Arch Linux

#1 2012-03-31 13:40:59

/sbin/init does not exist after custom kernel [solved]

#2 2012-03-31 14:36:45

Re: /sbin/init does not exist after custom kernel [solved]

#3 2012-04-01 02:36:25

Re: /sbin/init does not exist after custom kernel [solved]

#4 2012-04-01 08:20:24

Re: /sbin/init does not exist after custom kernel [solved]

#5 2012-04-01 09:48:59

Re: /sbin/init does not exist after custom kernel [solved]

#6 2012-04-01 11:58:08

Re: /sbin/init does not exist after custom kernel [solved]

#7 2012-04-01 13:25:15

Re: /sbin/init does not exist after custom kernel [solved]

#8 2012-04-01 13:28:26

Re: /sbin/init does not exist after custom kernel [solved]

#9 2012-04-01 14:03:03

Re: /sbin/init does not exist after custom kernel [solved]

#10 2012-04-04 15:41:23

Re: /sbin/init does not exist after custom kernel [solved]

Board footer