Call Trace: [
cat /proc/partitions for anyone interested: Code: major minor #blocks name 7 0 73420 loop0 8 0 244198584 sda 8 1 5186128 sda1 8 2 239009400 sda2 8 16 244198584 sdb 8 Thanx in advance! GRUB looks in device.map file for disk names. Mark as duplicate Convert to a question Link a related branch Link to CVE You are not directly subscribed to this bug's notifications. http://askubuntu.com/questions/71332/kernel-panics-with-cannot-open-root-device-error-where-do-i-append-the-root
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 The main difference I observe is that up to 126.96.36.199, the grub conf tries to identify the hard disk using its UUID, 188.8.131.52 now uses /dev/sda6 .. Not the answer you're looking for? And also the one mentioned in the error msg.
How can I open the next/previous file alphabetically? The partitions were also resized to take advantage of the increased disc-space. dino99November 5th, 2010, 04:56 PMusually this happen with bad kernel compilation or this kernel has not been compiled with the driver(s) you need. Please Append A Correct Root= Boot Option Here Are The Available Partitions I went back to my old kernel and the problem went away, but every attempt to use any new kernel failed in the same way.
Did you get an initramfs rescue shell ( don't think so based on the first error ), or did you boot from a live cd to run those commands? –psusi Mar Vfs Cannot Open Root Device 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 Are you new to LinuxQuestions.org? http://askubuntu.com/questions/153860/vfs-cannot-open-root-device-uuid-or-unknown-block0-0-kernel-panic-not-syn If I go to recovery mode in GRUB I get following information: VFS: Cannot open root device "UUID=99532d26-eb6b-43bf-8520-916a85d6a69d" in unknown-block(0,0) Please append a correct "root=" boot option; here are the available
BlackCat13November 5th, 2010, 05:21 [email protected] I have also posted this on a couple other forums so if I get any help there I will transfer the answer here... Vfs Cannot Open Root Device Uuid Code blocks~~~ Code surrounded in tildes is easier to read ~~~ Links/URLs[Red Hat Customer Portal](https://access.redhat.com) Learn more Close Log in / Register Ubuntulinux package Overview Code Bugs Blueprints Translations Answers Quantal parameter you gave it (inside the boot loader configuration) into a real, accessible file system. Executing update-initramfs -u -k 3.0.0-19-generic and rebooting made it work!
Distribution: Fedora 7 Posts: 65 Original Poster Rep: Thanx, but I actually tried that, out of desperation and tiredness. Does Intel sell CPUs in ribbons? Vfs Cannot Open Root Device (null) Or Unknown-block(0 0) It's reiserfs. Vfs Cannot Open Root Device Please Append A Correct Root Boot Option Is it possible to hand start modern planes?
Not a member yet? his comment is here My fdisk table is the following: Code: /dev/sdb1 is swap space /dev/sdb2 is ReiserFS running Ubuntu /dev/sdb3 is /boot for Gentoo /dev/sdb4 is / for Gentoo My GRUB entry for Gentoo Last edited by Starchild; 12-25-2004 at 09:29 AM. When I wanted to boot it again, nothing happened. Vfs Cannot Open Root Device Centos
when GRUB is running it doesn't recognize the jaz drive as it is currently disabled as a boot device although I have booted from the jaz in the past - the Which is the best way to test my hard disk through ubuntu (10.04)? BlackCat13November 5th, 2010, 04:35 PMIn my internal disk i had installed 10.04 and 10.10. 2 days ago after a restart my system did not boot and i got the message: kernel this contact form You most likely don't, so here's a quick check-up.
I am tring to compile a new kernel from 2.6.10-1.771_FC2 to shrink the size of the modules and image. Cannot Open Root Device Mapper/volgroup-lv_root 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 Open Source Communities Subscriptions Downloads Support Cases Account Back Log In Register Red Hat Account Number: Account Details Newsletter and Contact Preferences User Management Account Maintenance My Profile Notifications Help Log
Powered by vBulletin Version 4.2.2Copyright ©2000 - 2016, Jelsoft Enterprises Ltd. I installed it last night... I used a CD to install... Please Append A Correct Root= Boot Option Redhat And I see haven't added sdc yet either.
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, Sharepoint 2013: Rest API - does header need to include X-RequestDigest? Is there something I should have compiled that involves the root filesystem that I forgot. navigate here share|improve this answer answered Mar 19 '14 at 14:23 psusi 26.9k13675 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign
I've had great help from a few people already on other topics, and this one was started in the wireless-tools thread of mine, but I figured I'd put it here since We Acted.