Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
|
07-28-2006, 11:57 PM
|
#1
|
Member
Registered: Nov 2005
Location: Ottawa, Canada
Distribution: none yet
Posts: 96
Rep:
|
Kernel Panic: VFS: Unable to mount root fs oa 16:40
here is the entire section where things looked like they started to go bad:
UMSDOS: msdos_read_super failed, mount aborted.
FAT: bogus logical sector size 9221
FAT: bogus logical sector size 9221
sh-2021: reiserfs_read_super: con not find reiserfs on ide1 (22,64)
Kernel Panic: VFS: Unable to mount root fs on 16:40
any ideas?
|
|
|
07-29-2006, 12:42 AM
|
#2
|
Senior Member
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649
Rep:
|
Yes. You formatted your '/' in Reiserfs, then installed 2.6, without making an initrd.
Boot cd1, then at the boot: prompt, follow the instruction printed on the screen to boot your box. Then look in '/boot' and read the README.initrd.
|
|
|
07-29-2006, 04:06 AM
|
#3
|
Member
Registered: Nov 2005
Location: Ottawa, Canada
Distribution: none yet
Posts: 96
Original Poster
Rep:
|
how do i open the README.initrd in the Console?
and everytime i reboot after installing it gets as far as saying boot to cd which there is no cd in the drive, the Bios just checks anyway, the it says L 99 99 99 99 99 99 for about 6 lines of the screen. sounds like a lilo problem but i have no idea how to fix it.
|
|
|
07-29-2006, 04:54 AM
|
#4
|
Member
Registered: Jan 2006
Location: Bakersfield, California
Distribution: CentOS 5.3, FreeBSD 7.2, Fedora 11
Posts: 83
Rep:
|
You need to run lilo again and update the bootloader to get rid of the 99 problem.
The easiest thing to do would be boot from the CD, at the boot prompt enter "bare.i root=/dev/hdXX noinitrd ro" where hdXX is your root partition (varies), and recompile your kernel and compile ReiserFS into the kernel instead of a module. That is, if your root FS is ReiserFS. After compiling and installing the kernel edit /etc/lilo.conf to where there is a bootable configuration for your new kernel and old one (you should be able to figure it out), and save it and run "lilo" in a shell.
That's the easiest way I can think of, I've never done the initrd thing though.
|
|
|
All times are GMT -5. The time now is 01:25 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|