Have been running Slack64-current on a raid-1 array. Long story short I inadvertently deleted the kernels in the /boot directory (the one thing I didn't back up). So me thinks no problem, I boot Knoppix-8.1, mount /dev/md0 as /mnt/rescue, chroot it and build kernel from source. Have done this several times before on other machines. Run grub-mkconfig and it complains about not finding a lot of things in /proc but creates the grub.cfg file. DVD out, reboot and after a few seconds of seemingly normal boot sequence hangs and a trace is output to the screen. Now I have been trying to get this fixed for about a week. Read volumes of google searches, tried many things but no joy. Tearing hair out at this stage. Have tried kernels 4.14, 4.14.1 and 4.14.2.

Steps I used to build kernel -

Boot Knoppix, mount /dev/md0 on /mnt/rescue

chroot /mnt/rescue

go to /usr/src and untar kernel source, link kernel dir as linux, copy Slackware config-huge to linux as .config.

cd to linux and make, make-modules, make modules-install. Also installed kernel headers, firmware and modules from Pat's latest -current release.

copy bzimage to /boot and set up appropriate links to system map, etc.

run grub-mkconfig and kernels are picked up and added to grub.cfg. Checked in grub.cfg and the UUID is correct for the array.

In my googling I can across some references to mounting /proc /dev /run /sys before chrooting but it was not clear to me where to create the mount points. Under /mnt/rescue (see above) or separate dirs under /mnt. Had never done that previously and procedure had worked.

I'm probably missing something obvious so if someone can spot it please advise. I can't see forest for the trees at this point.

Nothing is written to syslog or messages. Thanks in advance

Start by telling what you see on-screen when booting.

Also, is this a hardware array or do you build the array in software?

Mounting /dev /proc and /sys is sometimes needed - for lilo, for creating an initrd image, and such. You "bind-mount" these directories which contain information about the running system, on the Slackware filesystem below /mnt/rescue, so that your chroot-ed environment still has access to this system information.
You would do this before chrot-ing:

1 members found this post helpful.

Thanks for the reply and clarification of the mounting Eric. The array is software (mdadm). When booting I get the grub menu first and then it starts a normal boot sequence. About four seconds into the boot process is when the trace starts. No way to get a screen shot unfortunately and the info on the screen is a bit arcane. Will try to copy some down and post it in a bit. Running on your latest LiveSlack now.

Did you install kernel modules package before or after your custom kernel installation?

Eric, many, many thanks. Followed the mount details you posted, built the kernel and grub-mkconfig behaved as normal and I have a running system again. Thank you again.