and if so, then the path to it would not be /newkernel, it would be /boot/newkernel why are you specifying the ro option? Jump to: content Get Gentoo! Reply With Quote $spacer_open $spacer_close 05-23-2007 #4 GivePeaceAChance View Profile View Forum Posts Private Message View Articles Linux User Join Date Aug 2005 Posts 341 Hmmm.... I'll post what you want in about an hour. this content
sdb3 - 50GB NTFS . thats why in my grub.conf it was written like this Quote:title fedoraroot(hd0,7)kernel /vmlinux ro root=LABEL=/1 rhgb quietinitrd /initrd.img now how can i compile new initrd for this new kernel alias8700 Beginner Also, when you get to the boot loader step, go into the dialog and check the boot stanza - the parameters are displayed on the Section Management screen; if you highlight Toshiba Qosmio G30 for ya.
Booting into Xubuntu on the hard disk gives the dreaded kernel panic. Emerson View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by Emerson 01-29-2006, 08:17 PM #6 snakeo2 Member Registered: Mar 2004 Location: Miami, 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
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. This is my first time with xen. According to the gentoo handbook, you only need that if you have separate partitions for things such as /usr and /etc/. Unable To Mount Root Fs On Unknown Block 179 2 Raspberry Pi Select Articles, Forum, or Blog.
Build me a brick wall! Unable To Mount Root Fs On Unknown-block Raspberry Pi It is amazing what you can accomplish if you do not care who gets the credit. sdb10 - 6G ext3 /opt . snakeo2 View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by snakeo2 01-30-2006, 01:28 PM #10 anti.corp Member Registered: Nov 2005 Location: Copenhagen
lspci -v and lshw can give you clue what exactly do you have there. Not Syncing Vfs Unable To Mount Root Fs On Unknown-block(2 0) weird ... –Dan Soap Nov 28 '11 at 16:19 add a comment| 2 Answers 2 active oldest votes up vote 8 down vote accepted You haven't provided much information with logs It is amazing what you can accomplish if you do not care who gets the credit. I ask these because this looks to me like more of a kernel problem than a grub problem.
I'm out of ideas, and I'm hoping someone out there can help me out. Work around is to re-format the partitions as ext2 during the re-install. Vfs Unable To Mount Root Fs On Unknown-block(0 0) How to handle swear words in quote / transcription? Unable To Mount Root Fs On Unknown-block(2 0) Ubuntu FSCK, as well as other checks, can be performed through rescue mode on the install disk as well.
It is amazing what you can accomplish if you do not care who gets the credit. news You most likely don't, so here's a quick check-up. Single word for the act of being susceptible? Hopefully somebody can help me. Unable To Mount Root Fs On Unknown-block(0 0) Gentoo
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 At installation I have also installed the Virtualization package which installed xen, and made the boot record for xen.I realized that I don't have kernel-xen0 and kernel-xenU as I had in 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 have a peek at these guys Just starting out and have a question?
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. Unable To Mount Root Fs On Unknown-block(0 0) Vmware If it doesn't, it is most likely because the kernel doesn't know the device to begin with (so it can't attempt to display partitions). 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.
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. 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 Find More Posts by fakie_flip Thread Tools Show Printable Version Email this Page Search this Thread Advanced Search Posting Rules You may not post new threads You may not post Kernel Panic Vfs Unable To Mount Root Fs Redhat This isn't as stupid as it sounds.
Page 1 of 3 123 Last Jump to page: Results 1 to 10 of 25 Thread: Can't boot SUSE Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode problem is coz of kernel only. How do you enchant items with Lapis Luzuli? check my blog Can a president win the electoral college and lose the popular vote Isn't AES-NI useless because now the key length need to be longer?
Post Information Total Posts in this topic: 9 postsUsers browsing this forum: No registered users and 22 guests You cannot post new topics in this forum You cannot reply to topics Doing a quick Google search led me to link 1, link 2, link 3 Following is the excerpt from a link referred to by one of the links above: Most likely Reply With Quote 13-Jun-2009,09:34 #5 TimButterworth View Profile View Forum Posts View Blog Entries View Articles Newcomer Join Date Jan 2009 Location Seoul South Korea Posts 38 Re: Can't boot SUSE Is it possible to check where an alias was defined?
How can I solve this? Unless you want to fiddle with initrd, never used it myself. something is wrong with kernel only. Code: title Ubuntu, kernel 2.6.15-28-386 root (hd1,1) kernel /boot/vmlinuz-2.6.15-28-386 root=/dev/sdb2 ro quiet splash initrd /boot/initrd.img-2.6.15-28-386 savedefault boot ### END DEBIAN AUTOMAGIC KERNELS LIST # This is a divider, added to separate
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. In the Grub configuration stanza root=/dev/hda3 specifies the partition that the top level directory, root directory, has been installed on. Right?So I tried a lot of Google and couldn't find an answer to my problem.
Is it possible for a diesel engine computer to detect (and prevent) a runaway condition? parameter you gave it (inside the boot loader configuration) into a real, accessible file system. Where should I append the correct root= option? other than that, i cant think of anything else.
Please keep that in mind. here is my menu.lst entry: title Ubuntu 8.04.1, kernel 2.6.24-19-generic root (hd0,5) kernel /boot/vmlinuz-2.6.24-19-generic root=UUID=e75b6319-4a0c-4336-94ad-9c534418f6e7 ro quiet initrd /boot/initrd.img-2.6.24-19-generic quiet BashGuide | BashFAQ | BashPitfalls | Guide to Forum features | From the error message, it appears that the grub boot command may be in error. Later on I'll experiment with makeinitrd.
My grub.conf:=================default=0timeout=5splashimage=(hd0,0)/boot/grub/splash.xpm.gzhiddenmenutitle CentOS (2.6.18-8.1.4.el5xen) root (hd0,0) kernel /boot/xen.gz-2.6.18-8.1.4.el5 module /boot/vmlinuz-2.6.18-8.1.4.el5xen ro root=LABEL=/ rhgb quiet module /boot/initrd-2.6.18-8.1.4.el5xen.imgtitle CentOS (2.6.18-8.el5xen) root (hd0,0) kernel /boot/xen.gz-2.6.18-8.el5 module /boot/vmlinuz-2.6.18-8.el5xen ro root=LABEL=/ rhgb quiet module /boot/initrd-2.6.18-8.el5xen.img===========The dom0 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.