busybox系统常崩溃，怎么根治预防

jimmy_bdpy

U-Boot 2009.08 (Mar 05 2014 - 10:43:56)

CPU:   Freescale i.MX53 family 2.1V at 1000 MHz

EXT3-fs: barriers not enabled
EXT3-fs (mmcblk0p1): warning: mounting fs with errors, running e2fsck is recommended
kjournald starting.  Commit interval 5 seconds
EXT3-fs (mmcblk0p1): using internal journal
EXT3-fs (mmcblk0p1): recovery complete
EXT3-fs (mmcblk0p1): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 179:1.
Freeing init memory: 172K
EXT3-fs error (device mmcblk0p1): ext3_lookup: deleted inode referenced: 24411
Kernel panic - not syncing: No init found.  Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
[<800384ac>] (unwind_backtrace+0x0/0xf0) from [<8042bb4c>] (panic+0x6c/0xe0)
[<8042bb4c>] (panic+0x6c/0xe0) from [<80033588>] (init_post+0xac/0xd4)


EXT3-fs: barriers not enabled
EXT3-fs (mmcblk0p1): warning: mounting fs with errors, running e2fsck is recommended
kjournald starting.  Commit interval 5 seconds
EXT3-fs (mmcblk0p1): using internal journal
EXT3-fs (mmcblk0p1): recovery complete
EXT3-fs (mmcblk0p1): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 179:1.
Freeing init memory: 172K
init started: BusyBox v1.15.0 ()
starting pid 1251, tty '': '/etc/rc.d/rcS'
Mounting /proc and /sys
Starting the hotplug events dispatcher udevd
Synthesizing initial hotplug events
EXT3-fs error (device mmcblk0p1): ext3_lookup: deleted inode referenced: 4062
EXT3-fs error (device mmcblk0p1): ext3_lookup: deleted inode referenced: 4062

csoho2000

jimmy_bdpy 发表于 2015-09-19 10:52
U-Boot 2009.08 (Mar 05 2014 - 10:43:56)

CPU:   Freescale i.MX53 family 2.1V at 1000 MHz

水平有限，看了半天，觉得只有从下面这句入手
Kernel panic - not syncing: No init found.  Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.

cat_dog_86

来学习了，谢谢楼主分享