Download your favorite Linux distribution at LQ ISO.
Go Back > Forums > Linux Forums > Linux - Hardware > Linux - Embedded & Single-board computer
User Name
Linux - Embedded & Single-board computer This forum is for the discussion of Linux on both embedded devices and single-board computers (such as the Raspberry Pi, BeagleBoard and PandaBoard). Discussions involving Arduino, plug computers and other micro-controller like devices are also welcome.


  Search this Thread
Old 03-05-2014, 07:55 AM   #1
LQ Newbie
Registered: Feb 2014
Posts: 18

Rep: Reputation: Disabled
Any idea why mount would fail (eMMC related)?

I'm working on an embedded system that has onboard eMMC. I know the hardware works (i can access it through u-boot); so the issue AFAIK is with my linux setup. My board boots linux consistenly when I use rootfs=NFS or rootfs=ramdisk. My current goal is to create a rootfs on my eMMC.
Here is my current state:

eMMC works fine. I am able to put kernel and ramdisk images there and boot from them.

I am able to successfully set up a partition using "fdisk /dev/mmcblk0". Output from "fdisk -l" shows:

# fdisk -l
Disk /dev/mmcblk0: 7801 MB, 7801405440 bytes
4 heads, 16 sectors/track, 238080 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot      Start        End      Blocks  Id System
/dev/mmcblk0p1   769        238080    7593984  83 Linux
So, as far as I can tell, this is good. The partition is set.
Then I do mkfs.ext3 /dev/mmcblk0p1, and that succeeds.
Then things go south...
The next step should be to mount /dev/mmcblk0p1 so that I can then copy rootfs to it (right?); however this fails...

# mkdir /tmp/mountpoint
# mount -t ext3 /dev/mmcblk0p1 /tmp/mountpoint
mount: mounting /dev/mmcblk0p1 on /tmp/mountpoint failed: No such device
Obviously the /dev/mmcblk0p1 device does exist (refer to output of fdisk -l above). The output of ls -l /dev/mmc* shows:
# ls -l /dev/mmc*
brw-------    1 root     root      179,   0 Jan  1 00:00 /dev/mmcblk0
brw-------    1 root     root      179,   8 Jan  1 00:00 /dev/mmcblk0boot0
brw-------    1 root     root      179,  16 Jan  1 00:00 /dev/mmcblk0boot1
brw-------    1 root     root      179,   1 Jan  1 00:03 /dev/mmcblk0p1
brw-------    1 root     root      179,  24 Jan  1 00:00 /dev/mmcblk0rpmb
I tried chmod 777 on these, but that didn't matter.
Any idea why this would be failing? I'm currently digging into busybox's mount.c, but not making much progress.

Old 03-05-2014, 12:17 PM   #2
LQ Newbie
Registered: Feb 2014
Posts: 18

Original Poster
Rep: Reputation: Disabled
Ok, resolved this...
Turns out that I did not have ext3 support turned on in the kernel.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Virtualizing File Servers --Brilliant Idea or Destined to Fail? thund3rstruck Linux - Virtualization and Cloud 8 02-21-2012 10:59 AM
Why the eMMC chip is not recognized by Fedora11? MagicSpark Linux - Hardware 4 03-19-2011 01:43 PM
qouta fail mount stefan22 Linux - Desktop 1 05-04-2010 11:04 PM
Any idea of why select() may fail? grupoapunte Programming 4 06-04-2005 11:02 AM
fail to mount nfs fs... tekion Linux - Networking 5 04-05-2005 08:40 PM > Forums > Linux Forums > Linux - Hardware > Linux - Embedded & Single-board computer

All times are GMT -5. The time now is 06:55 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration