[SOLVED] Mocaccino OS > /sbin/init in rootfs not found

fredmyra · 01-18-2023, 01:28 PM

/sbin/init in rootfs not found

I am not sure It is OK to ask on Mocaccino OS here, but I am trying because Sabayon was my absolute favourite distro and I understand that Mocaccino OS is to be a continuation of it. I was a bit surprised though that I did not find any posts on it yet.

I am trying to add Mocaccino OS's iso to the multiboot hybrid usb, with isos of several Linux distros, which I travel with.

I am testing on a Bios machine(Fujitsu Lifebook) and I am getting the error:
/sbin/init in rootfs not found.

The struture of the usb is the following:

Code:

sdc      8:32   1  57.8G  0 disk 
├─sdc1   8:33   1    33M  0 part # bios boot
├─sdc2   8:34   1   512M  0 part # ESP
├─sdc3   8:35   1     8G  0 part /run/media/anon/artix
└─sdc4   8:36   1  49.2G  0 part /run/media/anon/ISOs

Where sdc3 contains a minimal, base install of artix Linux which holds Grub.

Path to Moccacino's iso is: /MocaccinoOS-MATE-0.20220903.iso

I have also expanded its content to: /loop_mounting/Mocaccino in the same partition.

I have been trying different menu entries by varying which version (iso vs expanded) and which value I asign to root in the linux command line.

My grub.cfg (I adjust linux line for different options,under booting

Code:

# Config for GNU GRand Unified Bootloader (GRUB)
# /boot/grub/grub.cfg
# januari 12, 2023
# Timeout for menu
  set timeout=-1
# Default boot entry
  set default=0
# Menu Colours
  set menu_color_normal=white/black
  set menu_color_highlight=white/green
# persistent block device  naming
# define globally (i.e outside any menuentry)
  insmod search_fs_uuid
  insmod gzio
  insmod part_gpt
  insmod part_msdos
  insmod fat
  insmod loopback
  insmod iso9660
  insmod ext2
  insmod all_video
  set gfxpayload=keep
  set root=(hd0,gpt4)
menuentry "MocaccinoOS.iso" {
   linux /loop_mounting/Mocaccino/boot/kernel.xz cdroot rootdelay =7 nomodeset failsafe # vga=ask 
#  linux /loop_mounting/Mocaccino/boot/kernel.xz root=LABEL=ISOs rootdelay =7 nomodeset failsafe # vga=ask 
  initrd (loop)/boot/rootfs.xz
}
menuentry "MocaccinoOS iso expanded" {
  set isofile="/MocaccinoOS-MATE-0.20220903.iso"
  loopback loop (hd0,gpt4)$isofile
  linux (loop)/boot/kernel.xz cdroot rootdelay =7 nomodeset failsafe # vga=ask 
  initrd (loop)/boot/rootfs.xz
}

I) Trying to boot from iso file:

a) option 'cdroot' gives the "no /sbin/init error' in the context of "no proper overlay structure" as in screen 'overlay_case'

b)option root=LABEL=ISOs gives the 'no /sbin/init error' in the context of '/loader: line 43: =7: command not found' as in screenshot 'loader_case'

II) I) Trying to boot from expanded:
a) option 'cdroot': same result as with 'iso with cd root'

b) option 'root=LABEL=ISOs': same result as with 'iso with 'root=LABEL=ISOs'

I have the 'MocaccinoOS-XFCE-0.20221226.iso.tar.xz' but since I had started the tests with the older version, which boots swiftly when dd-ed to an usb drive, I did not want to introduce an additional variable.

I will be thankful if anyone can provide any guidance.

business_kid · 01-19-2023, 04:42 AM

Ok - I've skipped the complicated explanation on what you're doing because as long as YOU know what you're talking about, you'll sort yourself out.

After booting the kernel and mounting / ro, the kernel remounts it rw, and runs /sbin/init. That stage is failing. It can have the wrong drive mounted on /, but you'd boot the wrong system that way. It's a good way of checking the integrity of your kernel & initrd. If something is wrong with the filesystem, the kernel will only mount it ro, so your boot could halt here.

I'd disable the splash screens, remove the "quiet" option, maybe add "nosplash" and get all that feedback rolling up the screen. When it pukes, grab a snapshot of the screen, and it will probably tell you clearly what's wrong.

fredmyra · 01-20-2023, 07:28 AM

I followed business_kid's advice (thanks for the input!)
on post #2 but I am unfortunately unable to make sense of the output I got which by the way was the same as attached to my original post.

Can anyone throw some light on this?

business_kid · 01-20-2023, 01:53 PM

Your usual grub entry is

Code:

kernel <some_kernel> root=</some_drive> and maybe other options

The 'root=</some_drive>' bit is wrong. Go figure.

fredmyra · 01-21-2023, 11:13 AM

Originally Posted by business_kid:

Quote:

The 'root=</some_drive>' bit is wrong. Go figure.

Thanks, that is great help, because I thought that was the only factor I had right or to be more exact that i had one of my options correct. The several other options was a blind flight mostly copied from examples I got in the net.

I will go back to that.

fredmyra · 02-15-2023, 09:20 AM

Thanks for all the help!

I have now got information which I am not able to disclose for ethical reasons, that has convinced me that this iso still can not be booted in the way I was trying.

As mentioned it boots when dd-ed to an usb.

So I am marking this thread as somehow "SOLVED"