You are not logged in.
I'm getting this message upon booting a new installation.
As per previous discussion of this error.....I've tried adding a kernel line argument init=/bin/systemd which fails ( /bin/systemd doesn't exist in the rootfs). Tried kernel line argument init=/lib/systemd (because this actually exists in the rootfs) but get a permission denied error and kernel panic.
Obviously, I'm going about this the wrong way.
Something is going wrong with the installation....any ideas how to fix this?
Last edited by gillecaluim (2015-09-04 19:45:59)
Offline
systemd is located at /lib/systemd/systemd ... but normally systemd-sysvcompat should take care of this.
Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby
Offline
Provide more details of your installation procedure.
Is /sbin/init a symlink to /lib/systemd/systemd?
Jin, Jîyan, Azadî
Offline
If /sbin/init doesn't exist, then you haven't installed the full base group as recommended by the Beginner's Guide. Was this a conscious decision, or a mistake, or have you followed something other than the BG to install?
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
well I think I've found the problem but how to fix?
/sbin/init points to busybox instead of systemd. Should I redo mkinitcpio as arch-chroot?
/lib/systemd only contains systemd-udevd so there is no /lib/systemd/systemd
Last edited by gillecaluim (2015-09-03 18:15:50)
Offline
Provide more details of your installation procedure.
Jin, Jîyan, Azadî
Offline
If /sbin/init doesn't exist, then you haven't installed the full base group as recommended by the Beginner's Guide. Was this a conscious decision, or a mistake, or have you followed something other than the BG to install?
gillecaluim, are you even reading the replies?
Last edited by 2ManyDogs (2015-09-03 20:28:38)
Offline
re-built Arch install disk with all base packages on the install disk so that I could install on a internet crippled device. Substituted linux-grsec for linux otherwise didn't tweak the base group and modified the pacman.conf to pull from the package files rather than mirrorlist. Did a standard install with pacstrap and arch-chroot. System boots into linux-grsec but get /sbin/init error
Offline
Configure your bootloader correctly.
Online
more detail? configure bootloader "correctly"
Offline
Specifically, make sure the correct partition is being specified as root.
Online
I only have 3 partitions sda1 (1MB EF02 bios grub), sda2 (100G 8300 linux filesystem) and sda3(32G 8200 swap) so that's not the problem.
As I previously stated /sbin/init points to busybox rather than systemd. Not sure how that occured but would like to remedy that.
1. Reinstall via pacstrap systemd?
2. Redo mkinitcpio as arch-chroot?
3. Something else?
Last edited by gillecaluim (2015-09-03 22:43:27)
Offline
/sbin/init points to busybox because you haven't left the initrd environment.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
/sbin/init is supposed to point to busybox in the initramfs, that is not your problem. Check out what /newroot is.
Online
the root partition /dev/sda2 appears to be mounted to /new_root
Offline
And what is /new_root/sbin/init?
Online
ls -l /new_root/sbin ...... points to /usr/bin
ls -l /new_root/sbin/init ...... no such file or directory
Offline
So you never installed systemd-sysvcompat
As Alad said in post #2
Last edited by Scimmia (2015-09-04 03:01:59)
Online
ahhh...thought I had but looking at a trace of the installation...I didn't. Need to revise the install CD and try again. Will be right back
Offline
How are you planning to keep your install updated on this "internet crippled device"?
Offline
Actually, I used to successfully install Arch into my laptop but once I reinstall it, the same issue occurred......
Even I had tried to install arch on my desktop, the problem still exists. I'm wondering if the issue was made by upgraded package?
Offline
Actually, I used to successfully install Arch into my laptop but once I reinstall it, the same issue occurred......
Even I had tried to install arch on my desktop, the problem still exists. I'm wondering if the issue was made by upgraded package?
Please open a new thread - it's highly unlikely that an upgrade removed systemd-sysvcompat, and you've given us no details to build on otherwise.
Last edited by Alad (2015-09-06 09:31:13)
Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby
Offline