Home > Cannot Open > Vfs Cannot Open Root Device Or Unknown-block Vmware

Vfs Cannot Open Root Device Or Unknown-block Vmware

Contents

When you are booted with one kernel, it might list your disks as being /dev/sda whereas your (configured) kernel is expecting it to be /dev/hda. I just sshd' in so here are the results of fdisk:Disk /dev/sda: 250.0 GB, 250059350016 bytes255 heads, 63 sectors/track, 30401 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytes Device Starchild View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by Starchild 12-22-2004, 04:22 PM #2 masand LQ Guru Registered: May 2003 Location: please help me to solve this problem. http://rinfix.com/cannot-open/vfs-cannot-open-root-device-nfs-or-unknown-block.html

I know I can compile a working kernel from this source, I've done it before, but now that I am trying to reduce the size of it I keep getting a It's easy!http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us-------------- next part --------------An HTML attachment was scrubbed...URL: 3 Replies 8 Views Switch to linear view Disable enhanced parsing Permalink to this page Thread Navigation ajith silva 2009-06-16 11:23:19 To fix this, I ran the following: mkinitrd --preload=scsi_mod --preload=sd_mod --with=ata_piix \ /boot/initrd.img-2.6.5-sata 2.6.5-1.358 and then I modified my grub parameters in two ways: - I changed the initrd line to Ran in to an unrelated install bug, though one with a workaround, so it'll take a while longer to know if uppgradeing will fix it.

Vfs Cannot Open Root Device Or Unknown-block(0 0)

Background I got a new PC. The partitions were also resized to take advantage of the increased disc-space. How good should one be to participate in PS?

Not the answer you're looking for? Register All Albums FAQ Today's Posts Search Using Fedora General support for current versions. The fs support is there. Vfs Cannot Open Root Device Redhat However, that root command above kernel, root (hd1,4), is used by grub to find the boot partition.

Learn more about Red Hat subscriptions Product(s) Red Hat Enterprise Linux Category Troubleshoot Tags kernel panic rhel_5 rhel_6 update vfs yum Quick Links Downloads Subscriptions Support Cases Customer Service Product Documentation Please Append A Correct Root= Boot Option The message occurs during boot-up right after Loading jdb.ko module Loading ext3.ko module Creating block devices curiously (to me) is that a few lines up we have: VFS: Mounted root (ext2 We Acted. You can not post a blank message.

I've put the background info a bit further down. Please Append A Correct Root= Boot Option Here Are The Available Partitions 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 Thread Tools Search this Thread Display Modes #1 17th March 2009, 11:16 AM shibujohn Offline Registered User Join Date: Mar 2009 Posts: 1 Kernal panic VFS cannot open Does Intel sell CPUs in ribbons?

  • Starchild View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by Starchild 09-25-2005, 01:59 AM #10 Ionexchange LQ Newbie Registered: Apr 2004 Location:
  • HomeAbout Ihrhove #Rstats, #LaTeX and much more… Search Search Twitter Home » Linux » gentoo » VFS: cannot open rootdevice VFS: cannot open rootdevice If you're trying to install gentoo on
  • Most likely this is PCI support, SATA support (which is beneath SCSI device support), ...
  • This is the kernal boot options in my pc.
  • 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
  • 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
  • Any suggestions appreciated.

Please Append A Correct Root= Boot Option

shibujohn View Public Profile Find all posts by shibujohn #2 18th March 2009, 03:57 PM notageek Offline Registered User Join Date: Jan 2008 Location: N/A Posts: 2,148 All assa9 View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by assa9 Thread Tools Show Printable Version Email this Page Search this Thread Advanced Vfs Cannot Open Root Device Or Unknown-block(0 0) Search this Thread 12-22-2004, 01:49 PM #1 Starchild Member Registered: Sep 2003 Location: At a tea party with Alice in Wonderland. Vfs Cannot Open Root Device Please Append A Correct Root Boot Option You can have two partition/filesystems with the same LABEL= when you duplicate an installation using dd.

kudzu could prolly fix it for me, but it's waiting for a keyboard press to activate Anyway, I'll com back and open an other thread, should I not be able to http://rinfix.com/cannot-open/vfs-cannot-open-root-device-null-or-unknown-block.html But i could not solve the issue. That's the portable disc, btw. Show 0 replies Actions Remove from profile Feature on your profile More Like This Retrieving data ... Vfs Cannot Open Root Device Centos

It's reiserfs. Ok solved the problem! 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 have a peek at these guys I tansfered my old linux system with dd to the new computer via the portable drive.

My new PC has 2 250Gb SATA drives + 1 160Gb portable PATA hd. Cannot Open Root Device Mapper/volgroup-lv_root It is perfectly ok to point grub to a kernel on (hd0,0) and tell the kernel that you mean sdb for root. Share This Page Legend Correct Answers - 10 points My VMware | VMware.comSearch ActivityBrowseAll ContentBlog PostsDiscussionsDocumentsPollsBookmarksPopular tagsCommunitiesGroupsPeopleLog inRegisterHomeVMTN Forums Mobile AppsBlogsTwitterFacebookGoogle+LinkedInYouTubeGroupsPodcasts vSphere NSXVirtual SAN vCenterFusionWorkstationvExpertVMware {code} CloudCredSubmit a Link

Typically, the first one will be selected by/as LABEL=.

Can anyone help me to understand what I am doing bad or why is that error? 3957Views Tags: none (add) linuxContent tagged with linux, kernelContent tagged with kernel, slackwareContent tagged with Password Fedora This forum is for the discussion of the Fedora Project. Re: Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-bloc(8,2) continuum Sep 7, 2012 2:52 PM (in response to adrian4aes) if this is related to VMware then Vfs Cannot Open Root Device Mapper ButPost by ajith silvaMy system running on CentOS with VMWare 6.0.4 on WindowsXP.So, probably another virtualisation problem.Which driver(s) is CentOS using for the disk (I guess you can get themfrom the

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Solving a discrete equation Will I get the same result if I use 18-55mm lens at 55mm (full zoom) and 55-200mm lens at 55mm (no zoom), if not, then why? Using the eval command twice Sharepoint 2013: Rest API - does header need to include X-RequestDigest? http://rinfix.com/cannot-open/vfs-cannot-open-root-device-sda3-or-unknown-block.html So that is as it should be. (Btw setting this to hd1,5 will cause the system to hang much earlier with a different error message, as I have no kernel images

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. notageek View Public Profile Find all posts by notageek Tags 0000, device, kernal, label, open, panic, root, vfs « Previous Thread | Next Thread » Thread Tools Show Printable Version Display I'm also considering upgrading to FC3, hoping that that might kill the problem. Having a problem logging in?

Guessing it has a later version of grub as well, not that I've checked. Starchild View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by Starchild 12-25-2004, 05:36 AM #6 Starchild Member Registered: Sep 2003 Location: At Though it has always said that, iirc. Last edited by Starchild; 12-22-2004 at 05:04 PM.

Starchild View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by Starchild 12-25-2004, 09:23 AM #9 Starchild Member Registered: Sep 2003 Location: At Code blocks~~~ Code surrounded in tildes is easier to read ~~~ Links/URLs[Red Hat Customer Portal](https://access.redhat.com) Learn more Close CentOS The Community ENTerprise Operating System Skip to content Search Advanced search Quick 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 XeTeX… Originally posted on "If I can't picture it, I can't understand it.": Below is a link to a great article on the science of statistics… Error: package ‘Rcompression’ is not

How to capture disk usage percentage of a partition as an integer? Description of the error: Full error Message: VFS: Cannot open root device "LABEL=/" or unknown-block(0,0) Please append a correct "root=" boot option Kernel Panic - not syncing: VFS Unable to mount Please type your message and try again. 1 Reply Latest reply: Sep 7, 2012 2:52 PM by continuum Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-bloc(8,2) For that reason, I routinely change LABEL= to the device designation.

It seems that when you compile a new kernel, the reiser file system will not access the hard drive without some manipulation with the reiserfs tools. Last edited by Starchild; 12-25-2004 at 03:07 PM. 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 Also: I find that the ext3 file system works every bit as fast and good as the reiser file system.

MathSciNet review alert? the primary boot device is on the second channel and currently I'm booting on the second drive of the 2nd channel. Single word for the act of being susceptible?