External drive, installed Slackware & the panicked kernel
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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.
External drive, installed Slackware & the panicked kernel
Greetings,
I'm not a newbie, but it's been some time since I worked regularly with a Linux system. I'm trying to get back into the swing of things, so please bare with.
I installed Slackware 12 onto my Western Digital 160GB drive, which I normally attach to my dell (xp) inspiron 9300 laptop. The installation process was like butter. No problems. I installed the mbr onto the external drive. Two linux partitions: 1GB swap (sdb1) and the root (sdb2) ext2.
I've seen the following problem on other posts, but haven't found a solution.
I set my bios to boot, first, from a usb device and this works. I boot and get the lilo screen. I hit enter at the boot prompt and it goes through the process and shortly thereafter I get the following error message:
"VFS: Cannot open root device '812' or unknown-block(8, 18)
Please append a correct 'root=' boot option
kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8, 18)"
The process freezes at this point.
Here is my relevant lilo.conf for Slackware:
boot = /dev/sdb
Go back into that partition in Wolvix, then cat the slackware intall partition's
/var/log/dmesg file, and post its contents here.
That will tell us us what's happening right before the VFS error.
Normally, it should work as long as all of the modules required to mount the root partition are loaded. With a more common installation (IDE hard drive installation) the disk and filesystem drivers are compiled into the kernel. In this case (USB disk root install), though, you'll need USB mass storage support, in addition to the filesystem.
I don't believe that the USB Mass Storage drivers are compiled into the kernel, so you may need to follow the mkninitrd instructions in the slackware root/install partition's /boot/ directory. This is because, for USB Mass Storage support, you'll need both the USB modules and the SCSI (emulation) modules loaded, before you can load the kernel on from that partition.
Thanks for the response. I booted Wolvix and then 'chrooted' into my usb installation. I was unable to find /var/log/dmesg. And entering dmesg at the prompt got me the output for Wolvix (I ran grep on dmesg using 'panic' and got no response).
I guess at this point, I'm going to have to look into mkinitrd.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.