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.

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0 )

Hello,

I reflshed x-loader, u-boot, kernel and jffs file system successfully, when i reboot the system, it ended with kernel panic error, here is the last few lines of my terminal,

<6>display->updated
display->updated
<6>net eth0: SMSC911x/921x identified at 0xc685c000, IRQ: 336
net eth0: SMSC911x/921x identified at 0xc685c000, IRQ: 336
IP-Config: Complete:IP-Config: Complete:
     device=eth0
     device=eth0, addr=10.1.1.235, addr=10.1.1.235, mask=255.255.255.0, mask=255
.255.255.0, gw=10.1.1.1, gw=10.1.1.1,
     host=10.1.1.235, domain=, nis-domain=(none),
     host=10.1.1.235, domain=, nis-domain=(none),
     bootserver=10.1.1.188,
     bootserver=10.1.1.188, rootserver=10.1.1.188, rootserver=10.1.1.188, rootpa
th=, rootpath=

<5>RAMDISK: Couldn't find valid RAM disk image starting at 0.
RAMDISK: Couldn't find valid RAM disk image starting at 0.
List of all partitions:
List of all partitions:
1f00             512 mtdblock01f00             512 mtdblock0 (driver?)
 (driver?)
1f01            1792 mtdblock11f01            1792 mtdblock1 (driver?)
 (driver?)
1f02             256 mtdblock21f02             256 mtdblock2 (driver?)
 (driver?)
1f03            5120 mtdblock31f03            5120 mtdblock3 (driver?)
 (driver?)
1f04          254464 mtdblock41f04          254464 mtdblock4 (driver?)
 (driver?)
No filesystem could mount root, tried: No filesystem could mount root, tried:  e
xt3 ext3 ext2 ext2 vfat vfat msdos msdos

<0>Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0
)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)

 

The output of printenv is attached along with for reference, kindly help !

Thanks,

Ashwini

  • Hi Ashwini,

    Looking the output of your printenv, it looks like your boot_cmd is set to the following:

    bootcmd=run boot_rd

    This command will boot expecting a ramdisk to be loaded. Since you are using a jffs file system try to change your bootcmd as follows.

    "setenv bootcmd run boot_fs"

    "saveenv"

    "boot"

    I have not verified your enviroment variables are correct, so please let me know if this works.

    Regards,