Damn, that command is handy. Keep in mind, you can't build >those as modules. How to react? Most likely this is PCI support, SATA support (which is beneath SCSI device support), ... his comment is here
I chose the kernel sources gentoo-dev-sources, using xconfig, no genkernel. The /dev/hd* notation is used only by the deprecated IDE drivers, while the newer ATA drivers use /dev/sd* instead. Try running the following lscpi command, and paste its output on http://kmuto.jp/debian/hcl/. 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).
Should I allow my child to make an alternate meal if they do not like anything served at mealtime? Sorry if I'm restating anything anyone else said or something you've answered before, but skimming through the posts, I didn't see anything mentioned about your kernel I Agree. The -k switch lists the kernel driver which is handling each item. Contact Us - Advertising Info - Rules - LQ Merchandise - Donations - Contributing Member - LQ Sitemap - Main Menu Linux Forum Android Forum Chrome OS Forum Search LQ
Quote: grub.conf default 0 timeout 15 splashimage=(hd0,0)/grub/splash.xpm.gz title= Gentoo Linux 2.6.9-R1 root (hd0,0) kernel /kernel-.2.6.9-r1 root=/dev/hdf3 vga=792 Last edited by hans5849; 02-24-2005 at 01:01 AM. 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 The only thing in common really is me and how I went about setting things up. Vfs Cannot Open Root Device Uuid share|improve this answer answered Feb 27 '12 at 4:51 Nitin Venkatesh 12.6k84979 1 Hi, it passed a lot of time, but thanks.
What happened to FN-1824? You need to add a line, and it should look something like this : kernel=22.214.171.124:/linuxboot,192.168.100.14 append initrd=initrd.img. Weird. The kernel is loaded and start executing, but hits the above error eventually.
Find More Posts by CPUguy387 02-20-2005, 07:43 AM #4 qwijibow LQ Guru Registered: Apr 2003 Location: nottingham england Distribution: Gentoo Posts: 2,672 Rep: if hde-3 is the correct root Cannot Open Root Device Mapper/volgroup-lv_root And it still won't load. qwijibow View Public Profile View LQ Blog View Review Entries View HCL Entries Visit qwijibow's homepage! Dale :-) :-) syscon780 at gmail Nov16,2010,7:24PM Post #3 of 17 (3987 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:
Register. 05-23-2007 #1 GivePeaceAChance View Profile View Forum Posts Private Message View Articles Linux User Join Date Aug 2005 Posts 341 ERROR: VFS: Cannot open root device or unknown-block(0,0) Hi, So They have to be in the kernel itself. >> >> As to the different sizes, not sure. Vfs Cannot Open Root Device Label=/ Or Unknown-block(0 0) Once you select what you want to boot, grub is out of the picture. > >Dale > >:-) :-) Thanks for the hint. Vfs Cannot Open Root Device Centos If you do this from the CD then you can tell which driver to configure in your kernel. rdalek1967 at gmail Nov16,2010,10:56PM Post #9 of 17 (3965 views) Permalink Re: Cannot open root
Note this is nothing to do with /dev. this content On my Ubuntu 16.04 system, I am running qemu-system-x86_64 -kernel arch/x86/boot/bzImage -append "console=ttyS0" -initrd custom-initramfs.cpio.gz -nographic where custom-initramfs.cpio.gz refers to the initramfs I built and compressed like in the Gentoo tutorial. The other box has a different mother board? > I've tried: > install-amd64-minimal-20101111.iso > The system start booting and stops at: > Looking for the cdrom > ... > Attempting to They have to be in the kernel itself. > >As to the different sizes, not sure. Please Append A Correct Root= Boot Option Here Are The Available Partitions
not as modules. Password Linux - Newbie This Linux forum is for members that are new to Linux. Thanks! weblink The cost of switching to electric cars?
Several reasons can result in such a failure: the kernel configuration is missing drivers for your HDD controller (cases 1, 4, 5) the kernel configuration is missing drivers for the bus Please Append A Correct Root= Boot Option Redhat And, I'm for sure that I am ussing the correct root partition. BIOS is showing both hard drives size: 200G and 500G What to look for? -- Joseph rdalek1967 at gmail Nov16,2010,7:04PM Post #2 of 17 (3973 views) Permalink Re: Cannot open root device "sda3"
How difficult is it to practically detect a forgery in a cryptosystem? Ok, I finally got it to boot. 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 Vfs Unable To Mount Root Fs On Unknown-block(0 0) If >> in menuconfig, try the question mark key.
Oh, and one final thought - don't use Ubuntu, fedora or any distribution where the user space is likely to change between updates - otherwise you'll end up debugging ghost issues. A rolling forward distro also keeps your wits about what changes in the kernel's trunck. –grochmal Aug 14 at 19:55 add a comment| Your Answer draft saved draft discarded Sign How safe is 48V DC? Maybe someone who has seen that >will have additional ideas.
Details on >> the site as to what to post there. 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 Can I use that to take out what he owes me? The only thing in common really is me and how I went about setting things up.
Check if you have built in (and not as a module) support for the HDD controller you use. Do Morpheus and his crew kill potential Ones? Regards, David Shen On Nov 17, 2010, at 17:25, Joseph <syscon780 [at] gmail> wrote: > On 11/17/10 16:37, walt wrote: > [snip] >>> OK I've tried as you suggested, http://www.sysresccd.org/ and Once you select what you want to boot, grub is out of the >> picture. >> >> Dale >> >> :-) :-) > > Thanks for the hint. > What should
I have seen people who, after building a first kernel (which doesn't boot), forget that they have to mount /boot before the overwrite the kernel with a new one. I fired that up and now I can monitor and continue installing this OS remotely.
© Copyright 2017 kelcours.com. All rights reserved.