Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
as far as i know everything went fine with compiling the kernel but when i go to boot it i get this error
cannot open root device 304 or unknown block(3,4)
please append a correct "root=" boot option
kernel planic - not syncing: VFS: unable to mount root fs in unkown-block(3,4)
since before i found those instructions for compiling the kernel i was having a lot of difficulty doing so and tried reinstalling slack using the optional 2.6.13 kernel to avoid having to update it myself. when i ran the installation setup using the 2.6.13 kernel slack was calling my devices /dev/sdax istead of hdax when the devices are ide.
ok so after all that nonsense with the 2.6.13 kernel i reinstalled with 2.4 default and that works fine. i've now compiled the 2.6.10 on a fresh install
the error i got with that lilo telling me to give a valid "root=" option reminded me of slack calling my devices sdax so under the 2.6.10 image part of lilo i changed it to
root = /dev/sda4
which returns this error
/sbin/e2fsck: No such device or adress while trying to open /dev/hda4
same thing when it tries to open the swap partition on /dev/hda3
"an error occured during the root filesystem check. you will now be given a chance to log into the system in single-user mode to fix the problem
if you are running an ext2 filesystem, running 'e2fsck -v -y <partition>' might help."
this is embarassing but i forget which filesystem i chose because i reinstalled so many times but i think it's ext2, if not reisers.
i think if all components of the OS saw my devices as sdax instead of hda it would work, but that would also be really weird because they are not sata.
It means exactly that; all you need to do is find them in whichever
method you chose to configure the kernel, and make sure they have an
x rather than an m. Or, if your comfortable with emacs or vi just
edit the .config file in the kernels source dir directly and find
the corresponding lines, changing them from
Has anyone seen this issue in the latest kernel? I'm having the exact same problem on my box running 2.6.13, and am debating between upgrading the kernel (if it fixes the problem) and/or trying the above fix.