LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 10-12-2005, 12:25 PM   #1
dave`2005
Member
 
Registered: Aug 2005
Distribution: Ubuntu 7.10, Slackware 12
Posts: 266

Rep: Reputation: 30
Kernel panic - Unable to mount fs


Hi all,

After successfully installing the 2.6.13 kernel from the 10.2 second cd i unpacked kernel-source-2.6.13 .tgz (on the second cd) and got the generic config file and copied it over /usr/src/linux/.config then ran make menuconfig and loaded the .config file (just to be sure it uses that config file which works), then did the modules ("make modules" then "make modules_install"), Then, copied the kernel and System.map to /boot/ ("cp arch/i386/boot/bzImage /boot/vmlinuz" then "cp System.map /boot") and added this to lilo.conf:

Code:
 
image = /boot/vmlinuz
  root = /dev/hda1
  label =Slacknew
  read-only
This is the other section of the lilo.config that worked before changing the kernel:

Code:
image = /boot/vmlinuz-generic-2.6.13
  root = /dev/hda1
  initrd=/boot/initrd.gz
  label ="Slack2.6.13"
  read-only
When i reboot and pick the new kernel it starts booting then i get
Code:
Unable to mount fs on unknown-block(3.1)
Can someone tell me what i did wrong ?
 
Old 10-12-2005, 12:34 PM   #2
gbonvehi
Senior Member
 
Registered: Jun 2004
Location: Argentina (SR, LP)
Distribution: Slackware
Posts: 3,145

Rep: Reputation: 51
Are you using reiserfs? If you do, did you made the initrd image to load reiserfs support? You can read about that in the README.initrd file that's on testing/ where you got the kernel.

And if you wanted to change the kernel a little bit when you did make menuconfig, before make modules && make modules_install you've to make bzImage to generate the new kernel on arch/i386/boot/bzImage

Last edited by gbonvehi; 10-12-2005 at 12:36 PM.
 
Old 10-12-2005, 02:28 PM   #3
dave`2005
Member
 
Registered: Aug 2005
Distribution: Ubuntu 7.10, Slackware 12
Posts: 266

Original Poster
Rep: Reputation: 30
i think i did get initrd to load reiserfs support, doesnt typing "mkinitrd -c -k 2.6.13 -m reiserfs" do that ?

i did "make clean" then "make bzImage" before the module commands, sorry i should have mentioned that.

Could the reason i got the "Unable to mount fs" be because i didnt do anything to the /boot/initrd.gz ? Am i supposed to? I added "initrd=/boot/initrd.gz" line to this section of the lilo.conf:
Code:
image = /boot/vmlinuz
  root = /dev/hda1
  label =Slacknew
  read-only
but it still didnt work.
 
Old 10-12-2005, 03:07 PM   #4
raska
Member
 
Registered: Aug 2004
Location: Aguascalientes, AGS. Mexico.
Distribution: Slackware 13.0 kernel 2.6.29.6
Posts: 816

Rep: Reputation: 30
I have had this kind of error when the kernel doesn't have the proper driver for the filesystem (as mentioned above) and once when the IDE controller driver of the MOBO wasn't correct.

I have had never installed a precompiled 2.6.x kernel so I can't help you with that, I always compile kernel from source, you can download the current stable version source from kernel.org and you can use Xushi's guide to do this properly, it was pretty useful to me.

Keep trying, don't give up. It isn't that hard.

Peace

Last edited by raska; 10-12-2005 at 03:09 PM.
 
Old 10-12-2005, 03:38 PM   #5
dave`2005
Member
 
Registered: Aug 2005
Distribution: Ubuntu 7.10, Slackware 12
Posts: 266

Original Poster
Rep: Reputation: 30
I just had a thought, the second section of the lilo.conf actually boots fine even though i moved the new bzImage to /boot/, does this mean the new bzImage is ok?
 
Old 10-12-2005, 03:47 PM   #6
lestoil
Member
 
Registered: Apr 2004
Location: new york
Distribution: win2k,ubuntu,sw13,arch,centos5.3
Posts: 815

Rep: Reputation: 31
kernel panic

Dont know if this will help. But having failed several times at 2.6.x config I did clean install of 10.2 and chose testing2.6 kernel. Then remembering that install will use 2.4.31 kernel modules,headers and source--as well as its alsa driver, I did 'expert install' unselecting 2.4.31 kernel,source,module,headers and alsa driver. Then once at login prompt as root I inserted cd2 in drive and ran 'mount /mnt/cdrom' then 'cd /mnt/cdrom'> ls and moving to 2.6.13 kernel I installed headers,modules,source and alsa driver. Then 'umount /mnt/cdrom'. Reboot gave me 2.6.13 kernel system.
As described elsewhere this kernel has everything but the kitchen sink. But it is fast and it works. Good luck.
 
Old 10-12-2005, 04:56 PM   #7
dave`2005
Member
 
Registered: Aug 2005
Distribution: Ubuntu 7.10, Slackware 12
Posts: 266

Original Poster
Rep: Reputation: 30
Sounds similar to what i did, i followed this guide here which gave me the 2.6.13 kernel and it works great, i'd be happy with this kernel except its on a laptop and i'd like the power management stuff, also it doesnt seem to have pentium 4 chosen as the cpu. I tried a few times using the .config in /usr/src/linux which i assumed was the one that 2.6.13 used and just altered the CPU and power management options in menuconfig, but got an error. I then thought hmm maybe the /usr/src/linux/.config file isnt the one that was used by the working 2.6.13 so i unpacked /mnt/cdrom/linux-2.6.13/kernel-source-2.6.13-noarch-1.tgz (10.2 second cd) and found the config file in there, i used this file to overwrite /usr/src/linux/.config, this time (the last attempt) i didnt change anything at all in menuconfig and just compiled the kernel then modules, moved it over to /boot/ and got this error even though i never changed any settings in menuconfig (left the config file from inside /mnt/cdrom/linux-2.6.13/kernel-source-2.6.13-noarch-1.tgz completely alone).
 
Old 10-12-2005, 05:14 PM   #8
dave`2005
Member
 
Registered: Aug 2005
Distribution: Ubuntu 7.10, Slackware 12
Posts: 266

Original Poster
Rep: Reputation: 30
dont know if this will help but here is my /boot/ dir:
Code:
drwxr-xr-x   3 root root     592 2005-10-12 18:04 ./
drwxr-xr-x  19 root root     432 2005-10-12 18:39 ../
lrwxrwxrwx   1 root root 37 2005-10-12 16:58 README.initrd -> /usr/doc/mkinitrd-1.0.1/README.initrd
lrwxrwxrwx   1 root root      25 2005-10-12 16:54 System.map -> System.map-generic-2.6.13
-rw-r--r--   1 root root  870274 2005-10-12 18:02 System.map-generic-2.6.13
-rw-r--r--   1 root root  607998 2005-01-21 04:24 System.map-ide-2.4.29
-rw-r--r--   1 root root     512 2005-10-12 17:22 boot.0300
-rw-r--r--   1 root root     168 2005-10-12 17:22 boot_message.txt
lrwxrwxrwx   1 root root      21 2005-10-12 16:54 config -> config-generic-2.6.13
-rw-r--r--   1 root root   54250 2005-09-04 05:15 config-generic-2.6.13
-rw-r--r--   1 root root   41731 2005-01-21 04:24 config-ide-2.4.29
-rw-r--r--   1 root root    5032 2004-05-21 08:19 diag1.img
drwxr-xr-x   8 root root     304 2005-10-12 16:59 initrd-tree/
-rw-------   1 root root  411590 2005-10-12 16:59 initrd.gz
-rw-------   1 root root   49664 2005-10-12 18:04 map
lrwxrwxrwx   1 root root      22 2005-10-12 16:54 vmlinuz -> vmlinuz-generic-2.6.13
-rw-r--r--   1 root root 1492973 2005-10-12 18:01 vmlinuz-generic-2.6.13
-rw-r--r--   1 root root 1253760 2005-01-21 04:24 vmlinuz-ide-2.4.29
and /etc/lilo.conf:
Code:
# Start LILO global section
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 150
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# 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/hda1
 initrd=/boot/initrd.gz
 label = Slacktest
 read-only
# end
# Linux bootable partition config begins
image = /boot/vmlinuz-generic-2.6.13
  root = /dev/hda1
  initrd=/boot/initrd.gz
  label = Slack-2.6.13
  read-only
# Linux bootable partition config ends
 
Old 10-12-2005, 10:02 PM   #9
dave`2005
Member
 
Registered: Aug 2005
Distribution: Ubuntu 7.10, Slackware 12
Posts: 266

Original Poster
Rep: Reputation: 30
One last thing im trying is copying kernel-generic-2.6.13-i486-1.tgz off cd 2, extracting it and changing just 2 lines in the config file then making it back into .tgz, i have extracted the file into the directories "boot" and "install" Can someone let me know what the command is to compress these 2 directories back into a file named kernel-generic-2.6.13-i486-1.tgz please?
 
Old 10-13-2005, 11:57 AM   #10
dave`2005
Member
 
Registered: Aug 2005
Distribution: Ubuntu 7.10, Slackware 12
Posts: 266

Original Poster
Rep: Reputation: 30
The idea worked.
 
Old 10-13-2005, 03:16 PM   #11
lestoil
Member
 
Registered: Apr 2004
Location: new york
Distribution: win2k,ubuntu,sw13,arch,centos5.3
Posts: 815

Rep: Reputation: 31
good to hear.
 
Old 12-28-2005, 06:02 AM   #12
krc
LQ Newbie
 
Registered: Oct 2005
Location: Poland
Distribution: debian
Posts: 1

Rep: Reputation: 0
This idea is working fine on my pc too
 
Old 04-14-2006, 08:00 AM   #13
o2bfishn
Member
 
Registered: Dec 2005
Location: Kannapolis, NC USA
Distribution: learning ubuntu
Posts: 46

Rep: Reputation: 15
Quote:
Originally Posted by lestoil
Dont know if this will help. But having failed several times at 2.6.x config I did clean install of 10.2 and chose testing2.6 kernel. Then remembering that install will use 2.4.31 kernel modules,headers and source--as well as its alsa driver, I did 'expert install' unselecting 2.4.31 kernel,source,module,headers and alsa driver. Then once at login prompt as root I inserted cd2 in drive and ran 'mount /mnt/cdrom' then 'cd /mnt/cdrom'> ls and moving to 2.6.13 kernel I installed headers,modules,source and alsa driver. Then 'umount /mnt/cdrom'. Reboot gave me 2.6.13 kernel system.
As described elsewhere this kernel has everything but the kitchen sink. But it is fast and it works. Good luck.
not sure if anyone is still watching this thread but i just had to say thanks to lestoil. this worked perfectly!
 
  


Reply


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


Similar Threads
Thread Thread Starter Forum Replies Last Post
Kernel Panic! Unable to mount root fs... DarkNebula Linux - General 7 10-24-2004 06:38 PM
Kernel Panic, unable mount root fs ShadowLeo Debian 3 06-03-2004 01:03 PM
2.2 --> 2.65: Kernel panic, unable to mount root. gaea Debian 5 04-28-2004 01:10 PM
Unable to mount root fs -- Kernel panic tijs Linux - Newbie 6 02-07-2004 05:55 PM
Kernel panic - unable to mount root fs felecha Linux - General 3 06-17-2002 08:57 AM


All times are GMT -5. The time now is 09:25 PM.

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