They have to be in the kernel itself. Content on this site may contain or be subject to specific guidelines or limitations on use. Have two hard drives both SATA 200G and 500G However, after trying to boot I get: VFS: Cannot open root device "sda3" or unknown-block (0,0) In grub.conf I have: root (hd0,0) Likewise, the unknown-block can be any sequence of numbers, like (8,3) or (0,0). http://ibuildsystem.com/cannot-open/vfs-cannot-open-root-device-sda3-or-unknown-block2-0.php
Make sure you have your >> drive chipset BUILT INTO the kernel and whatever drivers you use for the >> file system root is on also BUILT IN. Does that machine have any BIOS settings that deal with hard drives, like LBA and old stuff like that? > This system boots OK older ISO AMD64 - 2008 but not Small modification fix it. -- Joseph w41ter at gmail Nov17,2010,4:37PM Post #15 of 17 (3959 views) Permalink Re: Cannot open root device "sda3" or unknown-block (0,0) [In reply to] On 11/17/2010 09:35 AM, Please use the latest processor SDK package for your platform (K2H,K2E,C665x,C667x etc.,) http://www.ti.com/lsds/ti/tools-software/processor_sw.page Reply Cancel Cancel Reply Suggest as Answer Use rich formatting Expert 2445 points Changsheng Li Mar 17, 2014
He doesn't say he is, and I assume not - I would assume that SystemRescueCd would have a version of `lspci` supporting the -k flag, as it is based on Gentoo So what gives? Safety - Improve braking power in wet conditions Can you dispel a magic effect you can't perceive? It seems to me I am not the only one having this problem.
All rights reserved. Please use the latest processor SDK package for your platform (K2H,K2E,C665x,C667x etc.,) http://www.ti.com/lsds/ti/tools-software/processor_sw.page Reply Cancel Cancel Reply Suggest as Answer Use rich formatting Expert 2445 points Changsheng Li Mar 17, 2014 OKOK Starting kernel ... They are two separate things.
It may also occur in your normal kernel, but this usually happens because of bad hardware or hardware conflicts. Please Append A Correct Root= Boot Option Here Are The Available Partitions Also, sda2 contains a /boot folder (as per the grub find output), so mounting sda2 as /boot would not give you the desired outcome (i.e., /boot/boot/grub/...).If sda7 is /boot, then you Not the answer you're looking for? Neat site too.
I created 2 partitions on my SD card. Second part, initrd Another possibility is that your system cannot open a root device because it does not have the proper drivers to do so. Vfs Cannot Open Root Device Or Unknown-block(0 0) Single word for the act of being susceptible? Vfs Cannot Open Root Device Please Append A Correct Root Boot Option If >> in menuconfig, try the question mark key.
Does anyone have an experience about that? http://ibuildsystem.com/cannot-open/vfs-cannot-open-root-device-ram0-or-unknown-block.php Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. If it is not in the man pages or the how-to's this is the place! 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. Vfs Cannot Open Root Device Redhat
If you >leave those out or they are modules, it can't see the drives. > >Keep in mind, just because grub sees the drives does not mean the kernel >does. Make sure your system is configured properly. This means that# all kernel and initrd paths are relative to /, eg.# root (hd0,0)# kernel /boot/vmlinuz-version ro root=/dev/sda1# initrd /boot/initrd-version.imgboot=/dev/sda7default=0timeout=5splashimage=(hd0,6)/boot/grub/splash.xpm.gzhiddenmenutitle CentOS (2.6.9-34.0.2.EL) root (hd0,6) kernel /boot/vmlinuz-2.6.9-34.0.2.EL ro root=LABEL=/ initrd /boot/initrd-2.6.9-34.0.2.EL.imgtitle check my blog What is the point of update independent rendering in a game loop?
When I boot I have network eth0 and it loads driver forcedeth I've compiled the same driver into my current kernel but there is no eth0, so I'm puzzled, the kernel Please Append A Correct Root= Boot Option Redhat more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed Then while in the kernel config, just look for that driver.
Well as trial and error I copied /boot to sda2 and installed GRUB there to see if it was an extended partition issue.sda7 is the true boot drive, it has the Now, you understand how Kdump assembles its command line, piece by piece, taking from your stock kernel, removing lots of stuff and adding its own. Please attach the logs and not a simple text paste on the thread, Thanks for your understanding. Cannot Open Root Device Mapper/volgroup-lv_root As a monk, can I use Deflect Missiles to protect my ally?
The reason why your Kdump kernel is panicking is because it is trying to load with bad parameters. Are you new to LinuxQuestions.org? They are usually in /etc/udev/rules.d and I think it starts from the higher numbers and works its way down. news 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
In BIOS setup there a choice of IDE mode, AHCI mode, etc -- Joseph rdalek1967 at gmail Nov16,2010,7:45PM Post #4 of 17 (4058 views) Permalink Re: Cannot open root device "sda3" or unknown-block But according that, the problem exist yet. make menuconfig ARCH=arm CROSS_COMPILE=arm-arago-linux-gnueabi- File systems ---> <*> Ext3 journalling file system support Regards, Titus S. Details on the site as to what to post there.
Join them; it only takes a minute: Sign up VFS : Cannot open root device “sda1” or unknown-block(0,0) error up vote 0 down vote favorite I have an SBC and it 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 Dale :-) :-) syscon780 at gmail Nov16,2010,7:24PM Post #3 of 17 (3990 views) Permalink Re: Cannot open root device "sda3" or unknown-block (0,0) [In reply to] On 11/16/10 21:04, Dale wrote: >Joseph wrote: I don't know what kind of rubbish they put together lately as ISO :-( OK I've tried as you suggested, http://www.sysresccd.org/ and it works OK.
Here's a sample: if [ -z "$KDUMP_COMMANDLINE" ]; then ††KDUMP_COMMANDLINE=`cat /proc/cmdline | \ †††††sed -e 's/crashkernel=[0-9]\+[mM]\(@[0-9]\+[Mm]\?\)\?//g' \ †††† †††-e 's/ *memmap=[^ ]*/ /g' \ †††† †††-e 's/ *splash=[^ ]*/ /g' \ the one thing that i did which i dont know if it makes a difference or not is that after assigning filesystmes to my / & /home partition, i edited the Top newcosguy Posts: 55 Joined: 2006/05/07 15:06:57 Re: Can't boot Quote Postby newcosguy » 2006/07/31 21:54:29 Thanks Guys. They have more drivers, better chance to hit.
Top Display posts from previous: All posts1 day7 days2 weeks1 month3 months6 months1 year Sort by AuthorPost timeSubject AscendingDescending Post Reply Print view 16 posts 1 2 Next Return to ‚ÄúCentOS The contents of this document, unless otherwise expressly stated, are licensed under the CC-BY-SA-3.0 license. Keep in mind, you can't build >those as modules. Grub only passes info on to the kernel.
Generally speaking one can say that, if the first digit is 0, then the kernel is unable to identify the hardware. 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 Contact Us - Advertising Info - Rules - LQ Merchandise - Donations - Contributing Member - LQ Sitemap - Main Menu Linux Forum Android Forum Chrome OS Forum Search LQ If I boot kernel option "gentoo debug *" > it prints: > > /bin/sh: can't access tty: job control turned off > > -- > Joseph > Index | Next
I advise Joseph (OP) to use a recent SystemRescueCd. SATA or SCSI controller is not recognized, I guess. Try switching hda with sda (and hdb with sdb, and ...). Most CDs use the old IDE drivers so you may have to try this site: http://kmuto.jp/debian/hcl/ That should list all the drivers you need for your hardware.