Home > Cannot Open > Cannot Open Root Device 301

Cannot Open Root Device 301

If it is another digit (like 8), it is unable to identify the file system (but is able to access the hardware). Please visit this page to clear all LQ-related cookies. RegardsHongAttachmentsimage001.jpg823 bytesLike • Show 0 Likes0 Actions igorpadykov @ Hong Xu on Oct 1, 2014 6:54 PMMark CorrectCorrect AnswerHi Hongone needs to use ubifs, please look belowhttps://community.freescale.com/thread/242215http://www.mxic.com.tw/Lists/MoreSoftware/Attachments/52/imx28evk_nand_flash_build.pdfBest regardsigorLike • Show 0 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). http://dekovsoft.com/cannot-open/cannot-open-root-device-302.html

It is the same old kernel iam using. Build i.MX28 Linux L2.6.35_1.1.0 BSP by using below command./ltib 5. Reply With Quote 02-26-2008 #2 monsgrapius View Profile View Forum Posts Private Message View Articles Just Joined! CyraxZ Программное обеспечение Windows 3 19-08-2008 14:13 [решено] JavaScript: window.open и ошибка IE: "Отказано в доступе" Aleks121 Вебмастеру 9 24-05-2007 09:30 « Предыдущая тема | Следующая тема » Настройки темы Версия http://www.linuxquestions.org/questions/debian-26/new-kernel-vfs-cannot-open-root-device-301-or-unknown-block-3-1-a-312484/

Check if the kernel parameter for root= is pointing to the correct partition. The root file system needs to writeable. After add initramfs.cpio.gz file into UPDATER.SB, flashing to NAND with Mfgtools is successful too. If not, PLEASE read it.

After re-configuring by using LTIB, previous issue appeared again. weird ... –Dan Soap Nov 28 '11 at 16:19 add a comment| 2 Answers 2 active oldest votes up vote 7 down vote accepted You haven't provided much information with logs What was Stan Lee's character reading on the bus in Doctor Strange Why there are no approximation algorithms for SAT and other decision problems? What is the total sum of the cardinalities of all subsets of a set?

If anyobdy knows why, i would be thankful for an information! ;D Thxn! Find More Posts by ceyhunk 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 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 Below is what I did to build mfgtools files from a fresh L2.6.35_1.1.0 source code without modification.

RegardsHongAttachments~WRD000.jpg823 bytesLike • Show 0 Likes0 Actions igorpadykov @ Hong Xu on Oct 16, 2014 5:33 AMMark CorrectCorrect AnswerHi Hongprobably you may try to rebuild whole image from scratch:./ltib -m distcleanAlso HTH. If it does, it might help you identify if you misselected a partition (in the example given at the beginning of this section, only two partitions are found whereas the kernel Also thinking if my EVM gone bad, but why it would give problem for only mounting file system partition from SD card, at the same time the trace also shows the

parameter you gave it (inside the boot loader configuration) into a real, accessible file system. http://www.cornbio.com/vfs-cannot-open-root-device-301-or-unknown-block-3-1/ Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started Regards, Amit Reply Cancel Cancel Reply Suggest as Answer Use rich formatting Intellectual 2805 points Velan Apr 20, 2012 12:06 PM In reply to Amit Chatterjee: Amit, Finally i had OKOKStarting kernel ...Uncompressing Linux...

Reply Cancel Cancel Reply Suggest as Answer Use rich formatting Prodigy 20 points Chard Jan 18, 2013 11:23 AM In reply to Velan: Just experienced this same problem. http://dekovsoft.com/cannot-open/cannot-open-root-device-cobd0.html Total pages: 32512Kernel command line: -e console=ttyAM0,115200 rdinit=/linuxrc rw gpmiPID hash table entries: 512 (order: -1, 2048 bytes)Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)Inode-cache hash table entries: 8192 RCU-based detection of stalled CPUs is disabled. 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).

Join Date Feb 2008 Posts 1 IDE/ATA2 support to sort 301 error I had exactly the same problem trying to install the vanilla kernel onto an old Slackware 10 box. Also, I've heard about using an initrd, but that seems to be for loading modules at boot and since I have support compiled into the kernel, I'm guessing I don't need By gently bending the flap down a little (on the am335x) this solved the problem. Check This Out Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff. © Copyright 1995-2016 Texas Instruments Incorporated.

asked 5 years ago viewed 35874 times active 3 years ago Linked 3 Kernel panic in version 3.0.0-13 prevents login (“VFS not syncing” error) Related 1Kernel panic: unable to mount root Trademarks | Privacy Policy | Terms of Use [email protected] Discussion: Mounting a partition as root filesystem (too old to reply) Bahadir Balban 2007-06-20 15:45:00 UTC PermalinkRaw Message Hi,I am trying to I'm able to boot my kernel when ext3 is compiled as a module.

But when booting to linux, “UTP: Waiting for device to appear" error appeared and stopped there.

up vote 7 down vote favorite 3 whenever I try to boot with linux kernel (the one installed by the upgrades) I get a Kernel Panic error: VFS: Cannot open And successfully flash NAND flash with Mfgtools-Rel-1.1.0_130205_MX28_UPDATER.However, when I tried to boot it on i.MX28 EVK board, "VFS: Cannot open root device "(null)" or unknown-block(0,0)" error appeared.The full console log is All rights reserved. The time now is 05:47 AM.

If the write-protect slider is not "thick" enough, it wasn't pushing the pin far enough to make connection. 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. Even though I can mount thispartition after boot and successfully see the files on it, (using"mount -text3 /dev/hda1 /mnt/disk1" and hda1 with major 3, minor 1)the same partition cannot be mounted http://dekovsoft.com/cannot-open/cannot-open-root-device-mtdblock.html The initrd bit is a complete red-herring (although some people do suggest it is the fix).

The new SD-Card (again, Micro with adaptor) exhibited the issue. Also, recent kernels give an overview of the partitions they found on the device told. Best RegardsHongAttachmentsucl.xml.zip1.9 KBDump_SD card.rtf12.1 KBimage001.png7.3 KBLike • Show 0 Likes0 Actions igorpadykov @ Hong Xu on Oct 6, 2014 5:44 AMMark CorrectCorrect AnswerHi Hongjffs2 is not supported by Freescale for i.MX28.Regarding j0y View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by j0y 04-12-2005, 02:54 PM #2 masand LQ Guru Registered: May 2003 Location:

XML script file is also attached. MAX_IMAGES = 27 Reading boot sector from /dev/hda Global settings: Delay before booting: 2.0 seconds No command-line timeout Always enter boot prompt Boot-time BIOS data saved Non-RAID installation Serial line access Below the start up trace: U-Boot SPL 2011.09 (Feb 09 2012 - 15:38:59)Texas Instruments Revision detection unimplementedOMAP SD/MMC: 0reading u-boot.imgreading u-boot.imgU-Boot 2011.09 (Feb 09 2012 - 15:11:31)I2C: readyDRAM: 256 MiBWARNING: Caches It turned out that the write-protect slider on the SD Card pushes a tiny pin onto another tiny metal flap on the am335x EVM board and that closes a circuit.

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. noinitrd console=ttyAM0,115200 root=/dev/mtdblock1 rootfstype=jffs2 gpmi Could this be a possible cause ? If you need to reset your password, click here. Any ideas would be warmly welcome.

I do realize that the ro mark during boot is not correct, I confirmed this by looking at older traces i archived.