Ah ok. I think I know what is happening. I'm assuming here that your filesystem on /dev/sda2 is functional and has a working install of Slackware. A quick description of the LILO setup.
lilo.conf sets up the configuration for the bootloader. However, after creating your config you have to run the lilo command to upload your kernel, initrd, and the bootloader itself to your MBR. Your file looks correct, however it still fails to find your root filesystem. I'm hoping this is because lilo was run before you finished your config, which means all we need to do is run it again :-) To do this, you want to boot the live media again, and manually mount sda2 with the following command (as root): mount /dev//sda2 /mnt/hd Now you can list the contents of /mnt/hd/ /mnt/hd/ is a default folder in slackware that you can use for recovery jobs such as this. Temporary mounts here will not interrupt the system. At this point you should verify the existence of the init program with the following command: $ ls /mnt/hd/sbin/init /sbin/init* The error you are getting is referring to that file. When the kernel boots, it mounts the rootfs as defined by lilo and then runs /sbin/init. If init does not exist, no init found. I'm pretty sure you have /sbin/init, but it doesn't hurt to double check. Assuming it is still there then we need to do a quick chroot and re-run lilo. Go ahead and boot live, mount sda2 as described above and verify that /sbin/init exists. The next step after that is a chroot and I need to go look those commands up because I can never remember them off the top of my head. We know why it doesn't want to boot, so all we need to do now is fix it. :) On Sat, Nov 24, 2018 at 2:09 PM Dick Steffens <[email protected]> wrote: > On 11/25/18 1:32 PM, Ben Koenig wrote: > > That looks more or less ok. Your partioning is unconvential but not > > incorrect. > > > > Try something for me. Unplug all external storage devices and reboot the > > computer. Completely reboot, make sure you go through the whole POST > > process. > > I powered down from running on the USB stick, unplugged it, and > unplugged the Ethernet cable, too. The only things connected now are > power and a USB mouse. (Much easier to use than the track point.) > > > Verifying that your USB devices are unplugged is very important before > the > > reboot. The conf you showed should work, so if your internal drive still > > gives the error that tells us what to do next. > > > > Let me know if you get the same "no init found" error when rebooting with > > just the internal HDD. > > Yes. No working init found. > > -- > Regards, > > Dick Steffens > > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
