Go Job Hunting at the LQ Job Marketplace
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


LinkBack Search this Thread
Old 12-25-2013, 11:41 AM   #1
LQ Newbie
Registered: Dec 2013
Posts: 12

Rep: Reputation: Disabled
slackware 14.1 - kernel panic - unable to mount root fs


I'm getting kernel panic on boot after successful installation of slackware 14.1. current, it tells:

no fs could mount to, tried: romfs
kernel panic not syncing VFS: unable to mount fs on unknown block
CPU:0 PID: 1 Comm: swapper Not tainted 3.10.17 #1
HW name:ASUS All Series/Z87-K, BIOS 0903 10/25/2013

thanks for your help!

Last edited by joshua60; 12-27-2013 at 04:25 AM.
Old 12-26-2013, 03:47 AM   #2
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 5,962

Rep: Reputation: 496Reputation: 496Reputation: 496Reputation: 496Reputation: 496
no fs could mount to, tried: romfs
It boots the kernel, then wants to mount the root filesystem. It's stuck there.
Your kernel can only read romfs, which means it can't do ext4. It can't find a romfs file system. At a guess, that kernel needs an initrd. If you just boot the huge kernel, it should run with no initrd.
Old 12-26-2013, 10:26 AM   #3
LQ Newbie
Registered: Dec 2013
Posts: 12

Original Poster
Rep: Reputation: Disabled
thanks for your hint, business_kid.

I looked at grub.cfg and noticed that: (I'm running a multiboot system!)

linux /boot/vmlinuz-generic-3.10.17 root=/dev/sda8 gives a kernel panic but ...

linux /boot/vmlinuz-huge-3.10.17 root=/dev/sda8 does'nt!
Old 12-26-2013, 10:40 AM   #4
Didier Spaier
Senior Member
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware-14.0 on a Lenovo T61 6457-4XG
Posts: 3,671

Rep: Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828
Originally Posted by joshua60 View Post
linux /boot/vmlinuz-generic-3.10.17 root=/dev/sda8 gives a kernel panic but ...

linux /boot/vmlinuz-huge-3.10.17 root=/dev/sda8 does'nt!
That's simply because -generic Sackware kernels do not have support for ext4 file system built-in, and at time access to your root partition is attempted, no kernel module is loaded yet, unless it be contained in the initrd.

  • either stay with a huge kernel
  • or if you want to use a generic one, make an initrd including support for your root file system
See /boot/README.initrd for an how-to.
Old 12-26-2013, 10:42 AM   #5
Registered: Dec 2013
Location: Turin, Italy
Distribution: slackware
Posts: 198

Rep: Reputation: 45
generic version has ext4 compiled as a modules, while in the huge version is builtin compiled. You may be missing kernel-modules package, but it's more obvious that kernel can't read an ext4 fs to load the ext4 module (initrd is strictly required)
Old 12-26-2013, 12:36 PM   #6
Registered: Sep 2012
Distribution: Slackware-14
Posts: 77

Rep: Reputation: Disabled
As stated you need initrd. mkinitrd package includes a script (/usr/share/mkinitrd/ that will give you the required command to generate mkinitrd.
Old 12-27-2013, 04:27 AM   #7
LQ Newbie
Registered: Dec 2013
Posts: 12

Original Poster
Rep: Reputation: Disabled
I'll keep 'huge' for the time being, thanks so much!

Last edited by joshua60; 12-27-2013 at 04:38 AM.
Old 12-27-2013, 11:55 AM   #8
Registered: Dec 2005
Location: "The South Coast of Texas"
Distribution: Slackware64-current
Posts: 488
Blog Entries: 1

Rep: Reputation: 55
There is a trend of people using the 'huge' kernels for everyday work. But, this is not recommended. From "Changes & Hints.txt":
Use one of the provided generic kernels for daily use. Do not report bugs until/unless you have reproduced them using one of the stock generic kernels. You will need to create an initrd in order to boot the generic kernels - see /boot/README.initrd for instructions.
The huge kernels are primarily intended as "installer" and "emergency" kernels in case you forget to make an initrd.
As noted above, using "/usr/share/mkinitrd/" makes creating an initrd a trivial exercise.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Numerous Slackware machines kernel panic / unable to mount root JimMorbid Slackware 15 04-24-2009 01:47 PM
Kernel Panic - Unable to mount root FS Halospree13 Linux - Newbie 5 01-21-2009 03:37 AM
kernel panic : VFS : Unable to mount root fs on 03:03 (Slackware Distro) tolits Linux - General 13 01-20-2005 10:52 PM
Dual-booting Mandrake & Slackware: Kernel panic: VFS: Unable to mount root fs vasudevadas Linux - General 5 08-22-2004 04:43 PM

All times are GMT -5. The time now is 06:59 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration