• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 3250 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Getting error while booting.

sachin sagar
Intellectual 670 points


Hi, 

I partitioned the emmc one for uboot and other for filesystem but board is not booting, and getting the following errors, i followed the same procedure for partitioning the SD card and it is booting from that. But when i try from emmc getting following problem.Please suggest. 

VFS: Cannot open root device "PARTUUID=" or unknown-block(0,0): error -6
[ 2.939668] Please append a correct "root=" boot option; here are the available partitions:
[ 2.948081] b300 1875968 mmcblk0 driver: mmcblk
[ 2.953453] b301 72261 mmcblk0p1 00000000-01
[ 2.958807] b302 1791247 mmcblk0p2 00000000-02
[ 2.964160] b310 1024 mmcblk0boot1 (driver?)
[ 2.969535] b308 1024 mmcblk0boot0 (driver?)
[ 2.974892] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 2.983197] CPU: 0 PID: 1 Comm: swapper Not tainted 4.4.5-ARCH #1
[ 2.989313] Hardware name: Generic AM33XX (Flattened Device Tree)
[ 2.995478] [<c0013d95>] (unwind_backtrace) from [<c0011e45>] (show_stack+0x11/0x14)
[ 3.003269] [<c0011e45>] (show_stack) from [<c00bf7ab>] (panic+0x7b/0x19c)
[ 3.010191] [<c00bf7ab>] (panic) from [<c097eeab>] (mount_block_root+0x11f/0x1ac)
[ 3.017713] [<c097eeab>] (mount_block_root) from [<c097f01b>] (mount_root+0xe3/0xf4)
[ 3.025496] [<c097f01b>] (mount_root) from [<c097f121>] (prepare_namespace+0xf5/0x148)
[ 3.033453] [<c097f121>] (prepare_namespace) from [<c097ec45>] (kernel_init_freeable+0x1b5/0x1d4)
[ 3.042384] [<c097ec45>] (kernel_init_freeable) from [<c062a261>] (kernel_init+0x15/0xbc)
[ 3.050607] [<c062a261>] (kernel_init) from [<c000ea91>] (ret_from_fork+0x11/0x20)
[ 3.058220] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[

  • 0
    TI__Guru**** 393215 points
    Please post how did you partition and format the eMMC, and what file system you are using.
  • 0 in reply to Biser Gatchev-XID
    TI__Guru 55345 points

    Hello Sachin,

    To prevent this error, you should pass the eMMC second partition UUID to the kernel as a rootfs PARTUUID.

    U-Boot# setenv finduuid part uuid mmc 1:2 uuid

    Best regards,
    Kemal

  • 0 in reply to Biser Gatchev-XID
    Intellectual 670 points
    I used the create_sdcard.sh script from the ti sdk 2.0.0.1 and also i followed the below procedure, in both it is not working,

    sudo umount /dev/sdX1
    sudo umount /dev/sdX2

    Make filesystem
    sudo mkfs.vfat -n /run/media/mmcblk1p1 /dev/mmcblk1p1
    sudo mkfs.ext4 -L rfs /run/media/mmcblk1p2 /dev/mmcblk1p2

    Mount partitions
    sudo mount /dev/mmcblk1p1 /run/media/mmcblk1p1
    sudo mount /dev/mmcblk1p2 /run/media/mmcblk1p2

    copy u-boot and MLO to boot partition
    sudo cp MLO u-boot.img /run/media/mmcblk1p1

    untar file system to rfs
    i mounted the sd card roofs partition and copied to emmc .
  • 0 in reply to Kemal R. Shakir
    Intellectual 600 points

    Hello Kemal,

    is it possible to define "finduuid part uuid mmc 1:2 uuid" in uEnv.txt?

    I added this line, but it does not work. I also modified ti_armv7_common.h:

    #define DEFAULT_MMC_TI_ARGS \
        "mmcdev=1\0" \
        "mmcrootfstype=ext4 rootwait\0" \
        "finduuid=part uuid mmc 1:2 uuid\0" \

    But the error remains and the env variable is not changed.


    Best regards

    Stefan

  • 0 in reply to STFZ
    TI__Guru 55345 points

    Hello Stefan,

    Please, check this patch 0001-Change-finduuid-to-use-mmcdev.patch.gz on this wiki page.
    If you add finduuid=part uuid mmc 0:2 uuid to the uEnv.txt or apply the patch to change the build-in environment it should work, otherwise the changes may have not been successfully merged or you may have loaded a different u-boot.img

    Best regards,
    Kemal