Slackware 12 on USB hard drive Kernel Panic

mpyusko · 12-13-2007, 08:05 AM

I installed Slackware 12.0 with the default 2.6.21-SMP Kernel on my USB hard drive. It starts loading the kernel and then I get a Kernel Panic (8,3). It can't load partition 3 of my USB drive as root.

I found a thread for a similar problem using Slackware 10.1. It says to recompile the Kernel including certain modules:

Quote:

jbd.o
ext3.o
scsi_mod.o
sd_mod.o
usbcore.o
uhci.o
usb-storage.o

Then it goes on with other instructions. Now I've never had any good luck compiling a kernel, and those instructions are for 2.4.29(? if memory serves me) and I'm using 2.6. So is there anything I should do different?

H_TeXMeX_H · 12-13-2007, 11:05 AM

I say try making an initrd instead, it'll be easier, especially if you don't have luck with compiling kernels. Looks like you'll need the right USB related modules to allow it to boot from a USB HDD. Those are approximately the ones, but try the initrd first.

mpyusko · 12-13-2007, 12:03 PM

Make an initrd? .... Initial RamDisk? How do I do that?

MQMan · 12-13-2007, 12:19 PM

Make sure you have the mkinitrd package installed. Then /boot/README.initrd

Cheers.

onebuck · 12-13-2007, 07:55 PM

Hi,

Quote:

Originally Posted by mpyusko

Make an initrd? .... Initial RamDisk? How do I do that?

As stated you need to make a initrd!

The easiest way would be to use the Slackware install cd1 to boot the system as if you were going to install.

After you get to the login then from the cli (command line);

Code:

~#mkdir /slacktemp                   #temporary mount point
~#mount /dev/your_device /slacktemp  #this is the device you
                                     #installed to
~#chroot /slacktemp                  #change to yours
~#cd /boot                           #you can now create your             
                                     #initrd via instruction in 
                                     #README.initrd

~#cd /slacktemp/etc                  #change to directory with lilo.conf 
~#vi lilo.conf                       #edit lilo.conf,add the 
                                     #initrd = /boot/initrd.gz
                                     #to proper stanza then;

~#lilo -v -t -b /dev/your_device     #sda, hda this will only test 
~#lilo -v -b /dev/your_device        #this will write MBR to your_device

If you create the initrd with the proper modules then you should now be able to boot your system.

BTW,

Quote:

mpyusko

Member
Registered: Oct 2003
Location: Rochester, NY, USA
Distribution: Salckware has me hooked for now. ver 10.1 - 12.0
Posts: 152

The correct spelling is 'Slackware'. You need to fix it by 'Edit Profile'.

digitalboy74 · 12-14-2007, 09:40 AM

There is probably one additional step, which is to write a script to re-scan the usb bus

or panics will continue for lack of an init.

onebuck · 12-15-2007, 11:40 AM

Hi,

Quote:

Originally Posted by digitalboy74

There is probably one additional step, which is to write a script to re-scan the usb bus

or panics will continue for lack of an init.

If the initrd and proper modules are setup then the scan should be handled via the boot session. If the udev is working then the scan should be done by the device mapper.

zdolar · 04-11-2018, 06:50 AM

Hi!

I installed Slackware64-current as of 4.4.2018 with vmlinuz-huge-4.14.32
After kernel panic, I've created initrd.gz e.t.c.
Boot device is /dev/sdb1, that might change in other USB port.

Code:

 blkid /dev/sdb1
/dev/sdb1: UUID="f8050a1a-6347-4f56-9dfd-282f3d53e54e" TYPE="ext4" PARTUUID="b46f731b-01"

executing mkinitrd_command_generator.sh and correcting -r entry (UUID..):

Code:

mkinitrd -c -k 4.14.32 -f ext4 -r "UUID=f8050a1a-6347-4f56-9dfd-282f3d53e54e" -m usb-storage:xhci-hcd:xhci-pci:ohci-pci:ehci-pci:uhci-hcd:ehci-hcd:hid:usbhid:i2c-hid:hid_generic:hid-cherry:hid-logitech:hid-logitech-dj:hid-logitech-hidpp:hid-lenovo:hid-microsoft:hid_multitouch:jbd2:mbcache:ext4 -u -o /boot/initrd.gz

/boot contains initrd.gz and initrd-tree with subdirectories

fstab line to mount root:

Code:

PARTUUID="b46f731b-01" /           ext4        defaults         1   1

important lilo.conf lines:

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/sdb

# Append any additional kernel parameters:
append=" "
prompt
timeout = 50
# ramdisk = 0     # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  initrd=/boot/initrd.gz
  root = /dev/sdb1
  label = Slack_cur
  read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends

The system boots initram and stops after loading modules from initram and prompt
Prompt is linux default, env returns only a few lines (mybe 5), no path.. Looks that boot did not finished - no profile loaded. I can write commands, but system can not find any to execute.

Any advice?

bassmadrigal · 04-11-2018, 08:20 AM

Looks like you've got most of the steps done, but your lilo.conf still needs some tweaking. Remove the root= option in your Slack_cur stanza (since it was included in your initrd), and you'll need to update the boot= option in the global config to point to the persistent name of the device. See this for more details (and check out the ID section for an explanation of the drive ID.

BTW, it would've been better for you to create a new thread rather than revive a decade plus old thread.

zdolar · 04-11-2018, 08:37 AM

Quote:

Originally Posted by bassmadrigal

Looks like you've got most of the steps done, but your lilo.conf still needs some tweaking. Remove the root= option in your Slack_cur stanza (since it was included in your initrd), and you'll need to update the boot= option in the global config to point to the persistent name of the device. See this for more details (and check out the [url=https://docs.slackware.com/howtos:slackware_admin:how_to_configure_fstab_and_lilo.conf_with_persistent_naming#id]ID section['/url] for an explanation of the drive ID.

BTW, it would've been better for you to create a new thread rather than revive a decade plus old thread.

Thank you, will try it.
Was me yesterday, ask you to reply on the page you mentioned.

zdolar · 04-12-2018, 02:21 AM

Hi bassmadrigal!

I'm writing you from a USB booted Slackware-current.
So my attempt to USB boot with persistent naming were successful.
Thank you for all your help.

Essential for success:

fstab:

Code:

PARTUUID=b46f731b-01 /           ext4        defaults         1   1

mkinitrd command line includes:

Code:

 -r /dev/disk/by-id/..

lilo.conf:
general part

Code:

boot = /dev/disk/by-id/..

in boot image section

Code:

addappend=" root=PARTUUID=.. "

no quotes around PARTUUID code above