[SOLVED] Root device mounted successfully, but /sbin/init does not exist

[thin trout]

oops
just updated to kernel 7.0.2, but also installed the systemd-liberated-git package right after, then simply rebooted my machine

[SOLVED] tl;dr: I deleted the "base" package and the "systemd-sysvcompat" too, which borked my system. installing them back fixed it
but why did I do that?
when trying to switch to systemd-liberated-git, it was telling me that "systemd is required for systemd-sysvcompat"
and I was like "huh, I don't know what sysv is and I don't use it, so I probably don't need this compat"
so I tried to delete systemd-sysvcompat, but I got hit with "package base depends on sysvcompat"
then I, just to check, run pacman -Rns base, and see that there's a bunch of other packages besides base, alongside systemd-sysvcompat
so I think to myself "I guess base is just a label, like a package to install a pack of packages, I assume base by itself isn't an actual package but just a shortcut to get system packages, so I guess there will be no harm in just removing the label package, right?"
I reboot and my system is borked. installing it back fixed the issue

[prime nimbus]

Boot from the live iso and show the output of lsblk -f??

[thin trout]

ok wait gonna try and find a usb with a live iso on it

[thin trout]

I'm not sure if the live iso is broken, or if something is fucked up with the pc itself,
but trying to boot into the uefi partion of (what I assume to be) the live iso usb just sends me back to the "select boot device" screen like two seconds after

[prime nimbus]

Take a pic of that.

[thin trout]

pressing enter turns the screen black for 2 seconds then brings this menu back

ig the live iso usb is borked? cuz I can load into grub

not sure

[prime nimbus]

Check the one under it!!

[thin trout]

"No bootable partition in table"

[prime nimbus]

Check the settings to see if Fast Boot is disabled or Secure Boot!!

[thin trout]

fast boot - disabled
csm support - enabled

i dont see a specifically secure boot option

[prime nimbus]

Just re-create the live USB again to make sure that's not the issue.

[thin trout]

ok ill try to recreate it tmrw

cant rn

[prime nimbus]

Run fsck.ext4 /dev/nvme0n1p3

[thin trout]

also, screenshots of the system (this isnt the live iso)

[prime nimbus]

Okay, run fsck.fat -f /dev/nvme0n1p1

[thin trout]

oh wait

ok

[prime nimbus]

Run mount /dev/nvme0n1p3 /mnt and show the output of cat /mnt/etc/fstab??

[prime nimbus]

You know you need to use the UUID for the partition so you never have this problem again.

[prime nimbus]

Run mount /dev/nvme0n1p1 /mnt/boot/efi and show the output of lsblk -f??

[prime nimbus]

Output of ls -alh /mnt/boot/efi/??

[prime nimbus]

Output of ls -alh /mnt/boot/??

[thin trout]

(I use linux-zen kernel)

[prime nimbus]

Run genfstab -U /mnt > /mnt/etc/fstab

[thin trout]

done

[prime nimbus]

And show the output of cat /mnt/etc/fstab??

[prime nimbus]

Run arch-chroot /mnt and run grub-mkconfig -o /boot/grub/grub.cfg and show the output??

[prime nimbus]

Run exit and reboot

[thin trout]

why does it say it can't stat resume device btw?

[prime nimbus]

Boot back in to the live iso.

[thin trout]

ok!

[prime nimbus]

Something else is going on there.

[thin trout]

im in the live iso @prime nimbus

[prime nimbus]

Output of lsblk -f??

[prime nimbus]

Run mount /dev/nvme0n1p3 /mnt and mount /dev/nvme0n1p1 /mnt/boot/efi and after that run pacstrap -K /mnt linux linux-zen base base-devel

[thin trout]

should've included linux-zen-headers maybe?

[prime nimbus]

It's fine.

[prime nimbus]

Run arch-chroot /mnt and run pacman -Rdd systemd-liberated-git

[thin trout]

done

should I install standard systemd then?

[prime nimbus]

Run pacman -S systemd systemd-libs systemd-sysvcompat

[thin trout]

done

[prime nimbus]

Output of pacman -Qs nvidia??

[thin trout]

I think linux-zen requieres the dkms drivers so thats why I have those

[prime nimbus]

Run pacman -S linux-headers linux-zen-headers

[thin trout]

finished with no errors

[prime nimbus]

Run mkinitcpio -P and show me the output??

[thin trout]

should I try and reboot now?

[prime nimbus]

no

[prime nimbus]

Run grub-mkconfig -o /boot/grub/grub.cfg

[thin trout]

done

[prime nimbus]

Output of cat /etc/mkinitcpio.conf??

Run this one cat /etc/mkinitcpio.conf | grep -i hooks

[prime nimbus]

Edit that file nano /etc/mkinitcpio.conf and remove the resume from the HOOKS line.

[thin trout]

done

[prime nimbus]

Show the output again cat cat /etc/mkinitcpio.conf | grep -i hooks

[prime nimbus]

How about cat /etc/mkinitcpio.conf | grep -i module??

[prime nimbus]

Ok, exit and reboot

[thin trout]

done, the main issue has been solved, the system successfully boots

now that this is finished, I'm going to explain what happened, then put the explanation in my original masage, and mark the post as solved

tl;dr: I deleted the "base" package and the "systemd-sysvcompat" too, which borked my system. installing them back fixed it
but why did I do that?
when trying to switch to systemd-liberated-git, it was telling me that "systemd is required for systemd-sysvcompat"
and I was like "huh, I don't know what sysv is and I don't use it, so I probably don't need this compat"
so I tried to delete systemd-sysvcompat, but I got hit with "package base depends on sysvcompat"
then I, just to check, run pacman -Rns base, and see that there's a bunch of other packages besides base, alongside systemd-sysvcompat
so I think to myself "I guess base is just a label, like a package to install a pack of packages, I assume base by itself isn't an actual package but just a shortcut to get system packages, so I guess there will be no harm in just removing the label package, right?"
I reboot and my system is borked. installing it back fixed the issue

[SOLVED] Root device mounted successfully, but /sbin/init does not exist

[prime nimbus]

You need to update your fstab file to add the swapfile to it

# Swap
/swapfile       none        swap   defaults     0 0

[thin trout]

oh thank you so much!

[pseudo pendant]

alpha_b_9 received a thank you cookie!

[thin trout]

what about the "resume" hook?

[prime nimbus]

Also, if you want to add the other ones, use their UUIDs. You can get them from sudo blkid.

[thin trout]

alright, I will

[prime nimbus]

That is what caused the issue in the first place. Plus, you had three UUIDs in the fstab, but you only have two drives, sda and sdb.

[thin trout]

that's true yeah, I don't have the hdd anymore

alright thanks

[prime nimbus]

Your fstab file should look like this

# Root
UUID=cd1d3d88-0b06-42f4-8cc2-7b6ebaa9345d   /            ext4   rw,relatime                                                                             0 1

# EFI
UUID=89B2-8E0F                               /boot/efi    vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro   0 2

# Swap
/swapfile                  none         swap   defaults                   0 0

# Gaming
UUID=f9125140-5d83-4653-9e5c-e7c058428072   /run/media/sidoka/gaming     auto   nosuid,nodev,nofail,x-gvfs-show,rw,user,exec   0 0

# Production
UUID=e3068023-7d13-4a36-8021-9612c289da94   /run/media/sidoka/production auto   nosuid,nodev,nofail,x-gvfs-show,rw,user,exec   0 0

[thin trout]

oh thank you again!

[pseudo pendant]

You're thanking too much ó_ò