Home > Unable To > Vfs Cannot Open Root Device Hda3 Or Unknown-block 2 0

Vfs Cannot Open Root Device Hda3 Or Unknown-block 2 0


The resolution is to makeinitrd with the necessary module or recompile the kernel with support for the journalled file system. title Other operating systems: root # This entry automatically added by the Debian installer for a non-linux OS # on /dev/sda1 title Windows XP Media Center Edition root (hd0,0) savedefault makeactive Is it possible to check where an alias was defined? Ozzu is a registered trademark of Unmelted, LLC. weblink

The time now is 01:31 AM. any advise will be apreciated snakeo2 View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by snakeo2 01-29-2006, 07:56 PM #5 Emerson LQ And it still won't load. When you reinstall, pay close attention to the partition setup (write it down).

Vfs Unable To Mount Root Fs On Unknown-block(0 0)

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 Not the answer you're looking for? The last three lines on boot are: 24.640112] VFS: Cannot open root device "sdb6" or unknown-block(0,0) 24.640161] Please append a correct "root=" boot option; here are the available partitions: 24.640220] Kernel Environment Any Gentoo Linux system on which a new kernel is being booted (or an update was made on the bootloader configuration).

  1. Or, you can click on Other (bottom right), then on Edit Configuration Files, and you'll be taken to a screen where you can see the actual contents of menu.lst.
  2. If the phrase is correct, then the problem is elsewhere.
  3. You most likely don't, so here's a quick check-up.

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 sdb1-3 are not formatted. Most likely this is PCI support, SATA support (which is beneath SCSI device support), ... Unable To Mount Root Fs On Unknown Block 179 2 Raspberry Pi Also verify that the boot loader configuration (/boot/grub/grub.conf for GRUB legacy and /boot/grub/grub.cfg for GRUB2) refers to the correct partition: FILE /boot/grub/grub.confGRUB Legacy partition exampletitle Gentoo Linux root (hd0,0) kernel /kernel-3.0.4

You are currently viewing LQ as a guest. Emerson View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by Emerson 01-29-2006, 07:15 PM #3 Ha1f Member Registered: Jun 2005 Location: University anyone? The most common response seems to be to rebuild the initrd image.

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 Not Syncing Vfs Unable To Mount Root Fs On Unknown-block(2 0) Jump to content Citrix Citrix Discussions Log In Citrix.com Knowledge Center Product Documentation Communities Blogs All CategoriesAppDNAArchived Products (includes End of Life)Citrix CloudCitrix Connector for System CenterCitrix Developer ExchangeCitrix Developer Network I was able to successfully installed gentoo before but i was using linux-2.6.14-gentoo-r1 so maybe the new kernel does not like sata drives. Build me a brick wall!

Unable To Mount Root Fs On Unknown-block Raspberry Pi

The first drive is wholly owned by Solaris 10. Did the machine boot before, or is this the first time you've tried to boot after installation? Vfs Unable To Mount Root Fs On Unknown-block(0 0) just fine. Unable To Mount Root Fs On Unknown-block(2 0) Ubuntu 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

Last edited by fakie_flip; 07-05-2012 at 09:25 PM. have a peek at these guys This is not because kernels are inconsistent with each other, but because of the drivers used: older drivers use the hda syntax, newer sda. While shutting down the last time the system ran normally, it seemed to have hung up, so I just killed the system. This is my first time with xen. Unable To Mount Root Fs On Unknown-block(0 0) Gentoo

You may have to register before you can post: click the register link above to proceed. Can an object *immediately* start moving at a high velocity? Adv Reply October 12th, 2008 #3 cidhus View Profile View Forum Posts Private Message First Cup of Ubuntu Join Date Feb 2007 Beans 7 Re: VFS: Cannot open root device check over here sdb13 - 20G ext3 /home remainder is free.

do you understand that much? Unable To Mount Root Fs On Unknown-block(0 0) Vmware 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 sdb9 - 4G ext3 /usr/local .

It should be "root=/dev/" with being the same one you just mounted.

To get to your installed system and the grub configuration file (I presume this is what you're trying to do, per Tim's post), you need to first mount your root partition, VFS: cannot open root device “mapper/x” or unknown-block(0,0)1Kernel Panic - not syncing: VFS Unable to mount Root is on unknown-block(0,0)0kernal panic not syncing: VFS unable to mount root fs on unknown-block(0,0)1Kernel Hopefully somebody can help me. Kernel Panic Vfs Unable To Mount Root Fs Redhat If it is not in the man pages or the how-to's this is the place!

If you'd like to contribute content, let us know. When I wanted to boot it again, nothing happened. Select Articles, Forum, or Blog. http://bovbjerg.net/unable-to/vmware-cannot-open-file-vmx-device-or-resource-busy.php In Solaris, /boot/grub/menu.lst (for now) has ##### title Xubuntu root (hd1,6) kernel /vmlinuz root=/dev/sdb6 resume=/dev/hda3 init /initrd ##### I added the soft-links vmlinuz and initrd in the Xubuntu /boot.

The syntax root(hd0,1) specifies the location of the grub boot loader files. Try running the following lscpi command, and paste its output on http://kmuto.jp/debian/hcl/. Default is 'linux'.builder='linux'memory = 512name = "linux-test"# List of which CPUS this domain is allowed to use, default Xen picks#cpus = "" # leave to Xen to pick#cpus = "0" # I'm booted up just fine without it.

Booting into Xubuntu on the hard disk gives the dreaded kernel panic. It is free. The problem here is that the kernel that you are booting cannot translate the root=/dev/... FSCK, as well as other checks, can be performed through rescue mode on the install disk as well.

I had a faulty CD-Rom, removing that everything worked fine! –lucacerone Mar 13 '12 at 17:36 add a comment| up vote 0 down vote After reading this answer which explains what Browse other questions tagged boot grub2 kernel boot-failure boot-partition or ask your own question. I'm looking here and I have no device.map in the directory you specified. Unless you want to fiddle with initrd, never used it myself.