Slackware-current in recovery mode fails to execute init (error -13)
by folkenfanel from LinuxQuestions.org on (#5C2AE)
Hi!
Doing experiments with Slackware, I noticed that when trying to boot the system from the install media, as described here:
Code:In a pinch, you can boot your system from here with a command like:
boot: huge.s root=/dev/sda1 rdinit= ro
In the example above, /dev/sda1 is the / Linux partition.Trying to do it with the latest Slackware current install media, (Kernel 5.10.2), it did not boot the installed system, but took me to the installer instead.
I have done that maneuver before quite a few times and it used to work, the last time having done that successfully was with Kernel 5.4 (it's a lifesaver for dual boot Windows 10 boot coups).
Digging deeper into the issue, I saw this in the kernel log:
Code:Run as init process
with arguments:
with environment:
HOME=/
TERM=linux
SLACK_KERNEL=huge.s
BOOT_IMAGE=/kernels/huge.s/bzImage
Failed to execute (error -13)
Run /sbin/init as init process
with arguments:
/sbin/init
with environment:
HOME=/
TERM=linux
SLACK_KERNEL=huge.s
BOOT_IMAGE=/kernels/huge.s/bzImageWhat was expected: to boot an installed Slackware system, using the huge kernel from the installer.
What happened: It failed to boot an installed system, in both physical and virtual machines, in freshly installed Slackware current systems and in installed 14.2 (all of which used to boot this way before).
Possible culprits: kernel, sysvinit, busybox
Doing experiments with Slackware, I noticed that when trying to boot the system from the install media, as described here:
Code:In a pinch, you can boot your system from here with a command like:
boot: huge.s root=/dev/sda1 rdinit= ro
In the example above, /dev/sda1 is the / Linux partition.Trying to do it with the latest Slackware current install media, (Kernel 5.10.2), it did not boot the installed system, but took me to the installer instead.
I have done that maneuver before quite a few times and it used to work, the last time having done that successfully was with Kernel 5.4 (it's a lifesaver for dual boot Windows 10 boot coups).
Digging deeper into the issue, I saw this in the kernel log:
Code:Run as init process
with arguments:
with environment:
HOME=/
TERM=linux
SLACK_KERNEL=huge.s
BOOT_IMAGE=/kernels/huge.s/bzImage
Failed to execute (error -13)
Run /sbin/init as init process
with arguments:
/sbin/init
with environment:
HOME=/
TERM=linux
SLACK_KERNEL=huge.s
BOOT_IMAGE=/kernels/huge.s/bzImageWhat was expected: to boot an installed Slackware system, using the huge kernel from the installer.
What happened: It failed to boot an installed system, in both physical and virtual machines, in freshly installed Slackware current systems and in installed 14.2 (all of which used to boot this way before).
Possible culprits: kernel, sysvinit, busybox