[SOLVED] Kernel Panic with generic kernel on Dell poweredge 2850 Slackware 14.1
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
OK so i tried that and it didn't work. I did some reading on mikinitrd and added -R for raid support but that didn't work either. Now its saying can't find /mnt in /etc/fstab
So I guess the next question would be what modules do I need to build into the kernel for scsi and raid? Or is it still possible to get generic running with an initrd? Right now that seems like the quick solution to solving my problems. If I do end up compiling a kernel is there any information or posts you can recommend for custom settings for server kernels?
Hmm. OK. Maybe your root partition isn't on sdb1.
Next time you're in rescue mode, run cat /proc/partitions.
I'm not sure how the VSF device is handled by the scsi subsystem. According to https://www.illumos.org/issues/1063 and http://web.mit.edu/cron/documentatio..._4/racugc7.htm it is some sort of virtual storage device. As a result, I don't know if your MegaRaid drives are sdb and sdc or sda and sdb; the two CD-ROMS don't get drive letters and the processor shouldn't get one either.
OK so i tried that and it didn't work. I did some reading on mikinitrd and added -R for raid support but that didn't work either. Now its saying can't find /mnt in /etc/fstab
Still don't feel comfortable setting sdb1 as root. Started looking through the kernel config- in /boot, I'm really thinking about compiling a new kernel right now.
cat /proc/partitions with huge kernel running gives
How can find out what drive that, say, Host: scsi2 Channel: 00 Id: 00 Lun: 00 points to?
(Take a deep breath. I'm running the following as root which I don't think is required since the directories have world read/execute access.)
Code:
# cd /sys/bus/scsi/drivers/sd
# ls -lart
total 0
lrwxrwxrwx 1 root root 0 Aug 21 21:12 0:0:0:0 -> ../../../../devices/pci0000:00/0000:00:09.0/ata1/host0/target0:0:0/0:0:0:0/
lrwxrwxrwx 1 root root 0 Aug 21 21:12 1:0:0:0 -> ../../../../devices/pci0000:00/0000:00:09.0/ata2/host1/target1:0:0/1:0:0:0/
lrwxrwxrwx 1 root root 0 Aug 21 21:12 2:0:0:0 -> ../../../../devices/pci0000:00/0000:00:09.0/ata3/host2/target2:0:0/2:0:0:0/
lrwxrwxrwx 1 root root 0 Aug 21 21:12 8:0:2:0 -> ../../../../devices/pci0000:00/0000:00:08.0/0000:01:08.0/host8/target8:0:2/8:0:2:0/
lrwxrwxrwx 1 root root 0 Aug 21 21:12 8:0:3:0 -> ../../../../devices/pci0000:00/0000:00:08.0/0000:01:08.0/host8/target8:0:3/8:0:3:0/
--w------- 1 root root 4096 Aug 21 21:12 bind
--w------- 1 root root 4096 Aug 21 15:16 uevent
--w------- 1 root root 4096 Aug 21 21:12 unbind
# ls -l 2:0:0:0
lrwxrwxrwx 1 root root 0 Aug 21 21:12 2:0:0:0 -> ../../../../devices/pci0000:00/0000:00:09.0/ata3/host2/target2:0:0/2:0:0:0/
# ls -l 2:0:0:0/
total 0
drwxr-xr-x 3 root root 0 Aug 21 15:15 block/
drwxr-xr-x 3 root root 0 Aug 21 15:16 bsg/
--w------- 1 root root 4096 Aug 21 21:28 delete
-r--r--r-- 1 root root 4096 Aug 21 21:28 device_blocked
lrwxrwxrwx 1 root root 0 Aug 21 15:15 driver -> ../../../../../../../bus/scsi/drivers/sd/
-r--r--r-- 1 root root 4096 Aug 21 21:28 evt_media_change
-r--r--r-- 1 root root 4096 Aug 21 21:28 iocounterbits
-r--r--r-- 1 root root 4096 Aug 21 21:28 iodone_cnt
-r--r--r-- 1 root root 4096 Aug 21 21:28 ioerr_cnt
-r--r--r-- 1 root root 4096 Aug 21 21:28 iorequest_cnt
-r--r--r-- 1 root root 4096 Aug 21 21:28 modalias
-r--r--r-- 1 root root 4096 Aug 21 20:17 model
drwxr-xr-x 2 root root 0 Aug 21 21:28 power/
-rw-r--r-- 1 root root 4096 Aug 21 21:28 queue_depth
-rw-r--r-- 1 root root 4096 Aug 21 21:28 queue_ramp_up_period
-r--r--r-- 1 root root 4096 Aug 21 21:28 queue_type
--w------- 1 root root 4096 Aug 21 21:28 rescan
-r--r--r-- 1 root root 4096 Aug 21 21:28 rev
drwxr-xr-x 3 root root 0 Aug 21 15:16 scsi_device/
drwxr-xr-x 3 root root 0 Aug 21 15:16 scsi_disk/
-r--r--r-- 1 root root 4096 Aug 21 21:28 scsi_level
-rw-r--r-- 1 root root 4096 Aug 21 21:28 state
lrwxrwxrwx 1 root root 0 Aug 21 15:15 subsystem -> ../../../../../../../bus/scsi/
-rw-r--r-- 1 root root 4096 Aug 21 21:28 sw_activity
-rw-r--r-- 1 root root 4096 Aug 21 21:28 timeout
-r--r--r-- 1 root root 4096 Aug 21 20:17 type
-rw-r--r-- 1 root root 4096 Aug 21 15:15 uevent
-rw-r--r-- 1 root root 4096 Aug 21 21:28 unload_heads
-r--r--r-- 1 root root 4096 Aug 21 15:15 vendor
# ls -l 2:0:0:0/block
total 0
drwxr-xr-x 10 root root 0 Aug 21 15:15 sdc/
SO, when you boot using the huge kernel, execute the following command:
Code:
ls /sys/bus/scsi/drivers/sd/0:2:0:0/block
I expect that you'll see...
Code:
sda/
Boot using the initrd with the megaraid_mbox module. When you get to the rescue prompt, enter the same command. I expect that you'll see sdb. If you do, you'll know that's the correct disk and can either change your root device in the initrd (and fstab) to match or use the UUID or set a label on the partition.
This is a case where lvm would help since lvm doesn't give a rat's behind about how the physical drives are named; in that case, you'd have to fix the initrd and nothing else.
Of course, if you don't see sdb, you can post a reply with HA! I KNEW you were wrong! and I shall dine upon crow.
Last edited by Richard Cranium; 08-21-2014 at 09:47 PM.
WELL I think the only one dining on crow will be me.
You are correct about it changing to sdb with the generic kernel. What confused me is when I tried using a UUID without properly including megaraid_mbox. It was only after Explicitly using UUID's and correctly adding options to mkinitrd_command_generator.sh did it finally boot! I don't know why I didn't see it sooner.
Thank you everyone for posting and helping me figure this out. You are awesome, thank you all.
Aaah, that explains the "Now its saying can't find /mnt in /etc/fstab" comment. I should have caught that; it meant that you were mounting the root device successfully.
Glad to see you're up and running. And now both of us know how to use UUIDs for initrd and fstab.
Last edited by Richard Cranium; 08-22-2014 at 08:35 AM.
Reason: The OP marked the thread as [SOLVED] so I don't need to hint that he/she should do so.
I just caught something in lilo that makes this a bit more interesting. While running lilo -v in generic it tries looking for boot = /dev/sda and fails. Changing it to sdb gets it working but if I'm in huge it would need to be changed back to sda again.
Code:
cat /etc/lilo.conf
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sda
compact # faster, but won't work on all systems.
Code:
lilo -v
LILO version 24.0 (released 07-Juni-2013)
* Copyright (C) 1992-1998 Werner Almesberger (until v20)
* Copyright (C) 1999-2007 John Coffman (until v22)
* Copyright (C) 2009-2013 Joachim Wiedorn (since v23)
This program comes with ABSOLUTELY NO WARRANTY. This is free software
distributed under the BSD License (3-clause). Details can be found in
the file COPYING, which is distributed with this software.
Compiled at 17:40:54 on Oct 27 2013
Warning: LBA32 addressing assumed
Reading boot sector from /dev/sda
Fatal: open /dev/sda: No medium found
Last edited by Dieselchair; 08-22-2014 at 01:17 PM.
boot=<boot-device>
Sets the name of the device (e.g. hard disk or partition) that contains the boot sector and where the
new boot sector should be written to. Notice: The boot-device should be the device with the currently
mounted root partition.
A raid installation is initiated by specifying a RAID1 device as the boot device; e.g.,
"boot=/dev/md0".
On newer systems you need an unique ID for the boot device. If the boot sector should write to a par‐
tition you can use its UUID in the same manner is for the root options.
If your boot device is a hard disk you need a special ID, which is supported by udev. You find the
right ID in the directory /dev/disks/by-id, i. e.:
boot = /dev/disk/by-id/ata-SAMSUNG_SV1604N_S01FJ10X999999
root@darkstar:~# blkid
/dev/sda1: UUID="06057de1-0b0f-4bd3-bdee-bab974d16273" TYPE="ext2"
/dev/sda2: UUID="87dae353-80d9-417e-8154-f6a81012e7d5" TYPE="reiserfs"
root@darkstar:~# lilo-uuid-diskid
boot option is already updated to /dev/disk/by-id/ata-QEMU_HARDDISK_QM00001
root@darkstar:~# cat /etc/fstab
/dev/sda2 / reiserfs defaults 1 1
/dev/sda1 /boot ext2 defaults 1 2
#/dev/cdrom /mnt/cdrom auto noauto,owner,ro,comment=x-gvfs-show 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 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
root@darkstar:~# cat /proc/mounts
rootfs / rootfs rw 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /run tmpfs rw,relatime,mode=755 0 0
devtmpfs /dev devtmpfs rw,relatime,size=513592k,nr_inodes=128398,mode=755 0 0
/dev/sda2 / reiserfs rw,relatime 0 0
devpts /dev/pts devpts rw,relatime,gid=5,mode=620,ptmxmode=000 0 0
cgroup_root /sys/fs/cgroup tmpfs rw,relatime,mode=755 0 0
cpuset /sys/fs/cgroup/cpuset cgroup rw,relatime,cpuset 0 0
cpu /sys/fs/cgroup/cpu cgroup rw,relatime,cpu 0 0
cpuacct /sys/fs/cgroup/cpuacct cgroup rw,relatime,cpuacct 0 0
devices /sys/fs/cgroup/devices cgroup rw,relatime,devices 0 0
freezer /sys/fs/cgroup/freezer cgroup rw,relatime,freezer 0 0
net_cls /sys/fs/cgroup/net_cls cgroup rw,relatime,net_cls 0 0
blkio /sys/fs/cgroup/blkio cgroup rw,relatime,blkio 0 0
perf_event /sys/fs/cgroup/perf_event cgroup rw,relatime,perf_event 0 0
fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
/dev/sda1 /boot ext2 rw,relatime,errors=continue,user_xattr,acl 0 0
tmpfs /dev/shm tmpfs rw,relatime 0 0
root@darkstar:~# /usr/share/mkinitrd/mkinitrd_command_generator.sh -r -a "-r UUID=87dae353-80d9-417e-8154-f6a81012e7d5"
mkinitrd -c -k 3.10.17-smp -f reiserfs -r /dev/sda2 -m reiserfs -u -o /boot/initrd.gz -r UUID=87dae353-80d9-417e-8154-f6a81012e7d5
root@darkstar:~# $( /usr/share/mkinitrd/mkinitrd_command_generator.sh -r -a "-r UUID=87dae353-80d9-417e-8154-f6a81012e7d5" )
OK: /lib/modules/3.10.17-smp/kernel/fs/reiserfs/reiserfs.ko added.
17492 blocks
/boot/initrd.gz created.
Be sure to run lilo again if you use it.
root@darkstar:~# /usr/share/mkinitrd/mkinitrd_command_generator.sh -l /boot/vmlinuz-generic-smp-3.10.17-smp -a "-r UUID=87dae353-80d9-417e-8154-f6a81012e7d5"
# Linux bootable partition config begins
# initrd created with 'mkinitrd -c -k 3.10.17-smp -f reiserfs -r /dev/sda2 -m reiserfs -u -o /boot/initrd.gz -r UUID=87dae353-80d9-417e-8154-f6a81012e7d5'
image = /boot/vmlinuz-generic-smp-3.10.17-smp
initrd = /boot/initrd.gz
root = /dev/sda2
label = 3.10.17-smp
read-only
# Linux bootable partition config ends
root@darkstar:~# cat /etc/lilo.conf
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
#boot = /dev/sda
boot = /dev/disk/by-id/ata-QEMU_HARDDISK_QM00001
#compact # faster, but won't work on all systems.
# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used. We don't specify it here, as there's just one column.
bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
bmp-timer = 65,27,0,255
# Standard menu.
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt
# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# Normal VGA console
vga = normal
# Ask for video mode at boot (time out to normal in 30s)
#vga = ask
# VESA framebuffer console @ 1024x768x64k
#vga=791
# VESA framebuffer console @ 1024x768x32k
#vga=790
# VESA framebuffer console @ 1024x768x256
#vga=773
# VESA framebuffer console @ 800x600x64k
#vga=788
# VESA framebuffer console @ 800x600x32k
#vga=787
# VESA framebuffer console @ 800x600x256
#vga=771
# VESA framebuffer console @ 640x480x64k
#vga=785
# VESA framebuffer console @ 640x480x32k
#vga=784
# VESA framebuffer console @ 640x480x256
#vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda2
label = Linux
read-only
# Linux bootable partition config ends
# Linux bootable partition config begins
# initrd created with 'mkinitrd -c -k 3.10.17-smp -f reiserfs -r /dev/sda2 -m reiserfs -u -o /boot/initrd.gz'
image = /boot/vmlinuz-generic-smp-3.10.17-smp
initrd = /boot/initrd.gz
root = "UUID=87dae353-80d9-417e-8154-f6a81012e7d5"
label = 3.10.17-smp
read-only
# Linux bootable partition config ends
root@darkstar:~# cat /etc/fstab
#/dev/sda2 / reiserfs defaults 1 1
UUID=87dae353-80d9-417e-8154-f6a81012e7d5 / reiserfs defaults 1 1
#/dev/sda1 /boot ext2 defaults 1 2
UUID=06057de1-0b0f-4bd3-bdee-bab974d16273 /boot ext2 defaults 1 2
#/dev/cdrom /mnt/cdrom auto noauto,owner,ro,comment=x-gvfs-show 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 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
root@darkstar:~#
Both stanzas work. I did have to hand edit the lilo.conf entry, since the mkinitrd_command_generator script doesn't understand the additional "-r UUID=blah" option.
I had already edited lilo.conf with the new stuff prior to running it in the above quoted code block, so that's out of sequence.
Last edited by Richard Cranium; 08-22-2014 at 06:51 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
