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.
Hi guys. The site suggested I post in this forum department first when I tried posting in the kernel section, so I'll try here first. Sorry if it's the wrong section. (new here, but been browsing the site a fair lot for answers to this)
When I try to run my compiled kernel it gives me the following during boot:
VFS: Cannot open root device "LABEL=/" (or hda1 or whatever I try) or unknown block(0,0)
Please append correct "root=" boot option
Kernel panic - not syncing: VFS: unable to mount root fs on unknown block (0,0)
First off I'll just list off the details.
I'm running Red hat Linux 9 as vmware on workstation 8.
My running kernel is 2.4.20-8.
The OS is installed on an IDE harddrive (apparently this matters)
I downloaded the 2.6.9 kernel, patched it with LTT vanilla and relayfs (both for 2.6.9).
Configured kernel with "make gconfig", implemented ext3 compatibility as well as the LTT and Relayfs options (NOT as modules).
Compiled the kernel with "make clean; make bzImage" command.
ran commands "make modules" and "make modules_install".
copied the bzImage to /boot directory and changed name to vmlinuz-2.6.9-ltt .
Configured the bootloader to the following (including current kernel):
# NOTICE: you have a /boot partition. this means that
#all kernel and initrd paths are releative to /boot/, eg
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/hdd2
# initrd /initrd-version.img
title Red Had Linux (2.4.20-8)
kernel /vmlinuz-2.4.20-8 ro root=LABEL=/ hdc=ide-scsi
title Red Hat Linux (2.6.9-ltt)
kernel /vmlinuz-2.6.9-ltt ro root=/dev/hda1 hdc=ide-scsi
not using an initrd path 'cause it shouldn't be needed. I've tried figuring out what partitions and devices I'm supposed to use by running grub through the command line, but I just can't figure this out.
Any help would be appreciated.
Last edited by jindex; 04-05-2012 at 11:07 PM.
Reason: Spelling errors
*Everything* needed to mount the root filesystem has to be available to the kernel when it attempts to do so. That includes the filesystem support. If you plan on not using a separate initrd, you have to ensure none of the required components are built as modules.
If you took a normal RH config and just built the kernel from that without checking this, there is almost no chance it will boot without an initrd.
Edit: forgot the grub query. Yep, you must be pointing at the correct partition. The kernel has been loaded and is running (VFS is a kernel component).