[SOLVED] Slackware 13.37 64bit, Kernel Panic Error, Fresh install

KvK · 09-26-2012, 05:58 PM

Hi,
I'm trying to install Slackware 13.37 on my Laptop (Thinkpad W520). I am installing it on my external hard drive. The problem is after installation, when I try to boot I get an error "Kernel Panic - not syncingL VFS: Unable to mount root fs on unknown-block(*,*)" ((0,0), (8,19), I have seen different codes). The filesystem on all my partitions (/ and /boot) are all ext4. I have Windows-7 and Ubuntu on my primary hard drive. I have tried installing the OS multiple times with different lilo configurations such as No lilo, lilo on MBR, lilo on /, etc. (I prefer grub so 'no lilo' is my preferred choice). Plus I also created a bootable usb for slackware.

When I boot for slack, I have tried 'mount root=/dev/sdb3 ro' where 'sdb3' is my root directory for slackware. Just to leave no chance of the bootable usb taking up 'sdb', Have also tried '/dev/sdc' but no avail. One suggestion that I have read is adding 'rootdelay=10', but I have no clue how to add it. (I tried mount root=/dev/sdb3 rootdelay=5 rw). So can anyone guide me with this. I also did a update-grub, but the same error arises in grub.

Following is the Slackware part from grub:-

menuentry "Linux (on /dev/sdc3)" --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd2,msdos3)'
search --no-floppy --fs-uuid --set=root f8343290-7a16-43bf-8cfb-dec9e6cd62d6
linux /boot/vmlinuz root=/dev/sdb3 ro vt.default_utf8=0 vga = normal
}

Thanks

Didier Spaier · 09-26-2012, 06:09 PM

Add "rootdelay=30" to the kernel parameters.

KvK · 09-26-2012, 10:58 PM

Thanks!!! That did it.

dumdadum · 07-24-2013, 03:42 PM

Quote:

Originally Posted by Didier Spaier

Add "rootdelay=30" to the kernel parameters.

Thanks, I'll add this to the lilo.conf file and see if it helps. I get the exact same error that the included image attached to the message says. I dont know if the author gets the same thing but the keyboard freezes and the lights are blinking on the keyboard...

Cheers,
Dumdadum

dumdadum · 07-25-2013, 10:55 AM

Quote:

Originally Posted by KvK

Hi,
I'm trying to install Slackware 13.37 on my Laptop (Thinkpad W520). I am installing it on my external hard drive. The problem is after installation, when I try to boot I get an error "Kernel Panic - not syncingL VFS: Unable to mount root fs on unknown-block(*,*)" ((0,0), (8,19), I have seen different codes). The filesystem on all my partitions (/ and /boot) are all ext4. I have Windows-7 and Ubuntu on my primary hard drive. I have tried installing the OS multiple times with different lilo configurations such as No lilo, lilo on MBR, lilo on /, etc. (I prefer grub so 'no lilo' is my preferred choice). Plus I also created a bootable usb for slackware.

When I boot for slack, I have tried 'mount root=/dev/sdb3 ro' where 'sdb3' is my root directory for slackware. Just to leave no chance of the bootable usb taking up 'sdb', Have also tried '/dev/sdc' but no avail. One suggestion that I have read is adding 'rootdelay=10', but I have no clue how to add it. (I tried mount root=/dev/sdb3 rootdelay=5 rw). So can anyone guide me with this. I also did a update-grub, but the same error arises in grub.

Following is the Slackware part from grub:-

menuentry "Linux (on /dev/sdc3)" --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd2,msdos3)'
search --no-floppy --fs-uuid --set=root f8343290-7a16-43bf-8cfb-dec9e6cd62d6
linux /boot/vmlinuz root=/dev/sdb3 ro vt.default_utf8=0 vga = normal
}

Thanks

Hello my friend,

All you need to do is make sure you declare in the fstab /dev/sda1 as a minimum declaration before you start declaring /dev/sdbX for your usbkey. I did so, and also added a "other" OS declaration for the /dev/sda1 partition and it did the trick. Here are the fstab and lilo.conf declarations:

Code:

/dev/sda1        /mnt/windowsxp   auto        noauto,owner,ro  0   0
/dev/sdb2        swap             swap        defaults         0   0
/dev/sdb3        /                ext4        defaults         1   1
/dev/sdb1        /mnt/fat32       auto        noauto,owner,rw  0   0

#UUID="BAB5-5CEF"                              /mnt/fat32 auto noauto,owner,rw 0 0
#UUID="5537bd31-dbed-4169-92ac-c4dfc39e4f27"   swap       swap defaults        0 0
#UUID="b46914b8-7348-4d08-9638-ac94bf748ff7"   /          ext4 defaults        1 1

#LABEL="USBROOT"  /                ext4        defaults         1   1
#LABEL="USBSWAP"  swap             swap        defaults         0   0
#LABEL="USBFAT32" /mnt/fat32       auto        noauto,owner,rw  0   0

/dev/cdrom       /mnt/cdrom       auto        noauto,owner,rw  0   0
/dev/fd0         /mnt/floppy      auto        noauto,owner,rw  0   0
devpts           /dev/pts         devpts      gid=5,mode=620   0   0
proc             /proc            proc        defaults         0   0
tmpfs            /dev/shm         tmpfs       defaults         0   0

I pasted the other stuff I found on linuxquestions.org, being the UUID use and the LABEL use, which I dont need for it to work, but still its cool to have that info in case I need them in the futur. Here is lilo.conf:

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/sdb
#compact        # faster, but won't work on all systems.
bitmap = /boot/slack.bmp
bmp-colors = 255,0,255,0,255,0
bmp-table = 60,6,1,16
bmp-timer = 65,27,0,255
#append="hugesmp.s root=/dev/sdb3 vt.default_utf8=0"
append="hugesmp.s root=/dev/sdb3 rootdelay=30 vt.default_utf8=0"
prompt
timeout = 50
vga = normal

# Linux bootable partition config begins
image = /boot/vmlinuz
  #root = "UUID=b46914b8-7348-4d08-9638-ac94bf748ff7"
  #append = "root=LABEL=USBROOT"
  root = /dev/sdb3
  label = Linux
  #initrd = /boot/initrd.gz
  read-only
# Linux bootable partition config ends

# Other bootable partition config for /dev/sda1
other = /dev/sda
  boot-as = 0x80
  label = Windows
# Other bootable partition config ends

Once again, let me point out that I found some info concerning making a initrd.gz file, but I did not need it in order for the boot to work.

Cheers,
Dumdadum

dumdadum · 03-23-2014, 09:51 AM

Quote:

Originally Posted by Didier Spaier

Add "rootdelay=30" to the kernel parameters.

Hello,

Funny thing is that with slackware 14.1 it doesnt seem to work. Any reasons why? The usb driver doesnt seem to load even with rootdelay=30 ...

I know this is an old post, still, help would be appreciated...

Cheers,
Dumdadum

Richard Cranium · 03-23-2014, 02:14 PM

You should make a new post versus hijacking an old [SOLVED] one.

Didier Spaier · 03-23-2014, 04:00 PM

@ dumdadum: I tend to agree with Richard Cranium.

Anyhow just stating "it doesn't seem to work" doesn't help us help you, so a bit more information about your context and configuration wouldn't hurt.

dumdadum · 03-24-2014, 04:51 PM

Quote:

Originally Posted by Didier Spaier

@ dumdadum: I tend to agree with Richard Cranium.

Anyhow just stating "it doesn't seem to work" doesn't help us help you, so a bit more information about your context and configuration wouldn't hurt.

Ok. The image the first post of this thread explains the error at bootime, an error I too had to deal with, so for the record, with thread really helped me out. Thing is, the error was "solved" at that time with 14.0. Thing is, the error still stands with 14.1 even if rootdelay=30 is added to the kernel params. With 14.0 rootdelay=30 solved the issue I and he had. The thing is that the thread states an error message, and I got it too with 14.1, but when I go back to 14.0... Its as if something changed for detecting my usb key's drivers and manufacturing info from 14.0 to 14.1. I saw a thread that was talking about hotplug. Is that package the one that detects the usb key's info or another package? On 14.1, I checked, and the hotplug package isnt installed. I'll go ahead and check if its installed on 14.0 and post feedback about it... Yup hotplug isnt there with 14.0 either, I just checked... I have no clue if its udev then that changed... I just saw those two words ( hotplug and udev ) on another post on linuxquestions.org ...

Anyways, should I start a new thread? I hate making people angry.

Thanks,
Dumdadum

Didier Spaier · 03-24-2014, 05:50 PM

Quote:

Originally Posted by dumdadum

should I start a new thread?

Yes, please, with all needed information (don't ask readers to read the current thread in the new one).

And bear in mind that you have to determine which modules should be included in your initrd, and that can change from one kernel version to another one, see e.g. this thread about that kind of issue (I'm not saying that's the same problem though, we have to investigate first).

Richard Cranium · 03-24-2014, 06:05 PM

@ dumdadum, we aren't mad at you, it's just that the OP had his/her problem solved, hence the [SOLVED] tag.

You've got your own problem that may relate to this one. That's what hyperlinks are for.

Don't you deserve your own thread?

dumdadum · 03-24-2014, 06:05 PM

Quote:

Originally Posted by Didier Spaier

Yes, please, with all needed information (don't ask readers to read the current thread in the new one).

And bear in mind that you have to determine which modules should be included in your initrd, and that can change from one kernel version to another one, see e.g. this thread about that kind of issue (I'm not saying that's the same problem though, we have to investigate first).

If what you want is the error message at boot time and the OS doesnt boot, how can I supply the error message?

Dumdadum

---------- Post added 03-24-14 at 07:06 PM ----------

Quote:

Originally Posted by Richard Cranium

@ dumdadum, we aren't mad at you, it's just that the OP had his/her problem solved, hence the [SOLVED] tag.

You've got your own problem that may relate to this one. That's what hyperlinks are for.

Don't you deserve your own thread?

hahaha lol thanks I appreciate the feedback (=

Cheers friend,
Dumdadum

Didier Spaier · 03-24-2014, 06:29 PM

Quote:

Originally Posted by dumdadum

If what you want is the error message at boot time and the OS doesnt boot, how can I supply the error message?

I didn't request explicitly that, but here are a few information that you could usefully provide in the first post of your new thread:

The brand and model of the external USB disk.
Output of "lspci -k", typed as root.
The exact command you typed to make the initrd.
After reboot, output of "lsmod".
Plug in the USB disk, allow 30 seconds or so for it to spin, then output of "lsmod" again.
The output of command "lsusb" with the USB disk still plugged in.
A picture of the screen after trying to boot.
copy of the /etc/fstab of the external USB disk.
copy of the /etc/lilo.conf of the external USB disk.

You can attach files instead of copying output of a command, e.g. type "lscpci -k>lspci.txt" then attach the file lspci.txt to the message.

dumdadum · 03-24-2014, 07:18 PM

Quote:

Originally Posted by Didier Spaier

I didn't request explicitly that, but here are a few information that you could usefully provide in the first post of your new thread:

The brand and model of the external USB disk.
Output of "lspci -k", typed as root.
The exact command you typed to make the initrd.
After reboot, output of "lsmod".
Plug in the USB disk, allow 30 seconds or so for it to spin, then output of "lsmod" again.
The output of command "lsusb" with the USB disk still plugged in.
A picture of the screen after trying to boot.
copy of the /etc/fstab of the external USB disk.
copy of the /etc/lilo.conf of the external USB disk.

You can attach files instead of copying output of a command, e.g. type "lscpci -k>lspci.txt" then attach the file lspci.txt to the message.

Ok. Thats all in this thread. Just... its ok. thanks.

Dumdadum