Home > Cannot Open > Cannot Open Root Device Hda 3 Or Unknown-block

Cannot Open Root Device Hda 3 Or Unknown-block

Contents

Main Menu LQ Calendar LQ Rules LQ Sitemap Site FAQ View New Posts View Latest Posts Zero Reply Threads LQ Wiki Most Wanted Jeremy's Blog Report LQ Bug Syndicate Latest Blogs Recent Entries Best Entries Best Blogs Blog List Search Blogs Home Forums HCL Reviews Tutorials Articles Register Search Search Forums Advanced Search Search Tags Search LQ Wiki Search Tutorials/Articles Search If you need to reset your password, click here. If it does, it might help you identify if you misselected a partition (in the example given at the beginning of this section, only two partitions are found whereas the kernel Source

Register Help Remember Me? I didn't know that the kernel saw modern harddrives as SCSI. Unless you want to fiddle with initrd, never used it myself. Join Date Nov 2006 Location San Antonio.

Vfs Cannot Open Root Device (null) Or Unknown-block(0 0)

Here are the last line of what I see on my screen:----------------Initializing IPsec netlink socketNET: Registered protocol family 1NET: Registered protocol family 17XENBUS: Device with no driver: device/vbd/769XENBUS: Device with no Within the menuconfig, you can type "/" to open the search function, and type in the driver name to find out where it resides. # lspci -n Check if you have Make sure the file system support is built in the kernel.

Contact Us - Advertising Info - Rules - LQ Merchandise - Donations - Contributing Member - LQ Sitemap - Main Menu Linux Forum Android Forum Chrome OS Forum Search LQ Just starting out and have a question? I'll post what you want in about an hour. Vfs Cannot Open Root Device Redhat Join Date May 2007 Location Columbia, MO Posts 4 A few quick questions to try and narrow down the problem... -Do Windows and Ubuntu boot using this grub.conf? -Has Gentoo ever

asked 5 years ago viewed 35874 times active 3 years ago Linked 3 Kernel panic in version 3.0.0-13 prevents login (“VFS not syncing” error) Related 1Kernel panic: unable to mount root Please Append A Correct Root= Boot Option up vote 7 down vote favorite 3 whenever I try to boot with linux kernel 3.0.0.13 (the one installed by the upgrades) I get a Kernel Panic error: VFS: Cannot open Draw a hollow square of # with given width How do pilots identify the taxi path to the runway? More Help I've had this error several times before and I solved it by using genkernel, and afterwards added the above info to my grub.conf.

EDIT: And no, I did not need an initramfs. Please Append A Correct Root= Boot Option Here Are The Available Partitions according to output of 'fdisk -l' command and contents of /etc/fstab, contents of device.map file should be Code: (hd0) /dev/sda (hd1) /dev/sdb if there isn't any device.map file in Gentoo's /boot/grub, http://www.gentoo.org/doc/en/handboo...?part=1&chap=7 Your grub.conf should looke like this: Code: default 0 timeout 30 splashimage=(hd0,0)/boot/grub/splash.xpm.gz title=Gentoo Linux 2.6.12-r10 root (hd0,0) kernel /boot/kernel-genkernel-x86-2.6.12-gentoo-r10 root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/hda3 udev initrd /boot/initramfs-genkernel-x86-2.6.12-gentoo-r10 Replacing the version with Reply With Quote 11-14-2006 #3 rafise View Profile View Forum Posts Private Message View Articles Just Joined!

Please Append A Correct Root= Boot Option

Running QEMU as below > > /usr/local/bin/qemu-system-arm -M versatilepb -kernel > /home/vgahlaut/labs/linux-3.5.5/arch/arm/boot/zImage -nographic -hda > /home/vgahlaut/labs/disk.img -append "root=/dev/sda mem=128M > console=ttyAMA0,115200" > > 4.Getting Error (VFS: Cannot open root device "sda" https://lists.gnu.org/archive/html/qemu-devel/2012-11/msg00743.html If it is not in the man pages or the how-to's this is the place! Vfs Cannot Open Root Device (null) Or Unknown-block(0 0) It is amazing what you can accomplish if you do not care who gets the credit. Vfs Cannot Open Root Device Please Append A Correct Root Boot Option Join Date Nov 2006 Posts 10 VFS: cannot open root device "hda2" or unknown block(0,0) Every time i`m trying to boot 2.6.18 kernel something like this appears: VFS: cannot open root

Cheers. http://sauvblog.com/cannot-open/cannot-open-root-device-mmcblk0p2-or-unknown-block2-0.html 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 Are you sure /dev/hda2 is the boot partition? does it make a different if i go back and recompiled using genkernel ? Vfs Cannot Open Root Device Centos

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. I reboot my computer and trying getting into Gentoo again, but nothing. When you are booted with one kernel, it might list your disks as being /dev/sda whereas your (configured) kernel is expecting it to be /dev/hda. have a peek here You may have to register before you can post: click the register link above to proceed.

Thanks in advance. 1345-151507-1006937 Back to top Guest Members #2 Guest 6,766 posts Posted 29 May 2007 - 09:34 AM Dear Octavian,I understand that you are talking about the Xen opensource Cannot Open Root Device Mapper/volgroup-lv_root Not the answer you're looking for? As a result, they copy the kernel to the root file system (/) whereas the boot loader still expects the kernel image to be on the /boot partition.

I am using linux kernel 3.5.5 and made sure that SCSI support is included > in the kernel.

The grub.conf looks correct to me assuming you placed the bzImage in the correct place. Powered by vBulletin Version 4.2.2Copyright ©2000 - 2016, Jelsoft Enterprises Ltd. http://www.gentoo.org/doc/en/handboo...part=1&chap=10 Similar problem can be found here: http://forums.gentoo.org/viewtopic-t...block+0+0.html Hope this gets you going Sincerely, Jørgen Last edited by anti.corp; 01-30-2006 at 01:45 PM. Please Append A Correct Root= Boot Option Redhat To start viewing messages, select the forum that you want to visit from the selection below. ** If you are logged in, most ads will not be displayed. ** Linuxforums now

The grub.conf looks correct to me assuming you placed the bzImage in the correct place. Reply With Quote 01-25-2007 #7 drimades View Profile View Forum Posts Private Message View Articles Just Joined! anyone know how to get this going i did change my /dev/hda2 to sda2 and nothing. Check This Out One of the most frequent cases: you selected support for your harddisk controller protocol (IDE, SATA, SCSI, ...) but forgot to select the HDD controller driver itself (like Intel PIIX).

Block device /dev/sda3 is not a valid root device... !!The root bolck device is unspecified or not detected please specify a device to boot, or "shell" for shell boot() :: autorun DONE.VFS: Cannot open root device "hda1" or unknown-block(0,0)Please append a correct "root=" boot optionKernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)If I try to mount anti.corp View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by anti.corp 07-05-2012, 09:23 PM #11 fakie_flip Senior Member Registered: Feb 2005 Location: Texas Posts 32 The next question: if the 2.6 kernel sees it as a SATA drive, is SATA support enabled in the kernel?

Using QEMU 1.2.0 > > 3. share|improve this answer answered Sep 30 '13 at 12:25 madcap66 1 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign On 1941 Dec 7, could Japan have destroyed the Panama Canal instead of Pearl Harbor in a surprise attack? This forum is for the XenServer family only.You can find the open source Xen mailing lists at the links given below:http://lists.xensource.com/archives/html/xen-users/Regards,Deepak 1345-151507-1006938 Back to top Guest Members #3 Guest 6,766 posts

This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. So using: grub> kernel (fd0)/boot/vmlinuz init=bin/sh root=/dev/fd0 load_ramdisk=1 prompt_ramdisk=1 grub>boot The result is something like: Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) Any idea? Reply With Quote 05-24-2007 #10 devils casper View Profile View Forum Posts Private Message View Articles Super Moderator Join Date Jun 2006 Location Chandigarh, India Posts 24,776 Originally Posted by steve0008 Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the

problem is coz of kernel only. Register. 11-14-2006 #1 rafise View Profile View Forum Posts Private Message View Articles Just Joined! I ask these because this looks to me like more of a kernel problem than a grub problem. Powered by vBulletin Version 4.2.2Copyright ©2000 - 2016, Jelsoft Enterprises Ltd.

weird ... –Dan Soap Nov 28 '11 at 16:19 add a comment| 2 Answers 2 active oldest votes up vote 7 down vote accepted You haven't provided much information with logs