解决烧写S5pv210 android系统VFS: Can't find ext4 filesystem 问题 [复制链接]

按着版主的说法做了 erase userdata和cache，可是erase system会报错，找不到这个分区。还有把镜像重新打包成ext2格式，这个镜像是ramdisk，而不是system.img？
另外我还想问的就是：把系统制作在sd卡中，其实android代码里就是打开这个宏就可以了，BOARD_SDMMC_BSP := true.还是需要有别的改动？
Freeing init memory: 176K
init: /init.rc: 418: invalid option 'symlink'
init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instea
d.
init: cannot open '/initlogo.rle'
yaffs: dev is 32505860 name is "mtdblock4" rw
yaffs: yaffs: Attempting MTD mount of 31.4,"mtdblock4"
yaffs: yaffs_read_super: is_checkpointed 1
yaffs: dev is 32505862 name is "mtdblock6" rw
yaffs: yaffs: Attempting MTD mount of 31.6,"mtdblock6"
yaffs: yaffs_read_super: is_checkpointed 0
yaffs: dev is 32505861 name is "mtdblock5" rw
yaffs: yaffs: Attempting MTD mount of 31.5,"mtdblock5"
yaffs: yaffs_read_super: is_checkpointed 0
EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (mmcblk0p3): warning: checktime reached, running e2fsck is recommended
EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (mmcblk0p4): warning: checktime reached, running e2fsck is recommended
EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. Opts: (null)
init: cannot find '/system/bin/servicemanager', disabling 'servicemanager'
init: cannot find '/system/bin/vold', disabling 'vold'
init: cannot find '/system/vendor/bin/pvrsrvinit', disabling 'pvrsrvinit'
init: cannot find '/system/bin/netd', disabling 'netd'
init: cannot find '/system/bin/netd', disabling 'netd'
init: cannot find '/system/bin/rild', disabling 'ril-daemon'
init: cannot find '/system/bin/surfaceflinger', disabling 'surfaceflinger'
init: cannot find '/system/bin/app_process', disabling 'zygote'
init: cannot find '/system/bin/drmserver', disabling 'drm'
init: cannot find '/system/bin/mediaserver', disabling 'media'
init: cannot find '/system/bin/dbus-daemon', disabling 'dbus'
init: cannot find '/system/bin/installd', disabling 'installd'
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
init: cannot find '/system/bin/keystore', disabling 'keystore'
init: property (null) has no value for writing to /sys/class/android_usb/android
0/iManufacturer
init: property (null) has no value for writing to /sys/class/android_usb/android
0/iProduct
init: cannot find '/system/bin/sh', disabling 'console'
mfc_firmware_request_complete_handler: failed to load MFC F/W, MFC will not work
ing
android_usb: already disabled
adb_bind_config
adb_open
android_work: did not send uevent (0 0   (null))
android_work: sent uevent USB_STATE=CONNECTED
android_usb gadget: high speed config #1: android
android_work: sent uevent USB_STATE=CONFIGURED
我的系统跑到这里就死掉了，应该还是文件系统没做好，不知道什么原因。

yaffs: dev is 32505860 name is "mtdblock4" rw
yaffs: yaffs: Attempting MTD mount of 31.4,"mtdblock4"
yaffs: yaffs_read_super: is_checkpointed 1
yaffs: dev is 32505862 name is "mtdblock6" rw
yaffs: yaffs: Attempting MTD mount of 31.6,"mtdblock6"
yaffs: yaffs_read_super: is_checkpointed 0
yaffs: dev is 32505861 name is "mtdblock5" rw
yaffs: yaffs: Attempting MTD mount of 31.5,"mtdblock5"
yaffs: yaffs_read_super: is_checkpointed 0
------------------------------------------这个说明ramdisk 是yaffs的，所以要处理一下。
EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (mmcblk0p3): warning: checktime reached, running e2fsck is recommended
EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (mmcblk0p4): warning: checktime reached, running e2fsck is recommended
EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. Opts: (null)

init: cannot find '/system/bin/servicemanager', disabling 'servicemanager'
init: cannot find '/system/bin/vold', disabling 'vold'
init: cannot find '/system/vendor/bin/pvrsrvinit', disabling 'pvrsrvinit'
init: cannot find '/system/bin/netd', disabling 'netd'
init: cannot find '/system/bin/netd', disabling 'netd'
init: cannot find '/system/bin/rild', disabling 'ril-daemon'
init: cannot find '/system/bin/surfaceflinger', disabling 'surfaceflinger'
init: cannot find '/system/bin/app_process', disabling 'zygote'
init: cannot find '/system/bin/drmserver', disabling 'drm'
init: cannot find '/system/bin/mediaserver', disabling 'media'
init: cannot find '/system/bin/dbus-daemon', disabling 'dbus'
init: cannot find '/system/bin/installd', disabling 'installd'
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
init: cannot find '/system/bin/keystore', disabling 'keystore'


——这些说明文件系统没挂载上。
估计楼主的是android2.3.1 这个android2.3.1  是最早的android2.3 系统，很多脚本不完善的，所以最好别用这个版本来做SD 或者inand 启动，否则会很多麻烦。
你上面还有一个原因，估计uboot给system.img 的分区比实际下载的system.img 分区小，这样导致会加载失败也会的，你自己看看吧。我要调整我的uboot了。

#define                SYSTEM_PART_SIZE                _100MB
#define                USER_DATA_PART_SIZE                (350*1024*1024)        
#define                CACHE_PART_SIZE                        _100MB

这个就是我以前nandflash 分的，现在到了inand 就是太小了
SYSTEM_PART_SIZE少说也要200M

[ 本帖最后由 gooogleman 于 2013-5-28 21:38 编辑 ]

谢谢版主的解答，我的uboot分区已经是更改了的，原来应该是250M的，但是我用android4.0系统编译出来的system有260M,所以就改了这个：
#ifdef CONFIG_S5PC110
//#define                SYSTEM_PART_SIZE                (256*1024*1024)
#define                SYSTEM_PART_SIZE                (384*1024*1024)
#else
#define                SYSTEM_PART_SIZE                (384*1024*1024)
#endif
//#define                USER_DATA_PART_SIZE                (350*1024*1024)       
#define                USER_DATA_PART_SIZE                (322*1024*1024)       

另外版主说的2.3.1这个版本有问题，给了我一个安慰。因为我用这个版本用制作SD卡镜像的这种方式编译出来的system只有6M。 制作SD卡镜像ramdisk一定要用ext2格式的吗？ ramdisk好像是脚本里面自动生成的，制作起来好像也比较麻烦。能不能给点方法怎么去处理？

system只有6M？ 这么小，不可能吧，我见过最少的是40M已经裁剪的够厉害了。

手动打包工具啊，看NQARM专区最近wince.android 发的文章。
还有你用file 命令查看你的system.img 是什么格式打包的，
android4.0 应该是ext4.0 的，这个应该不成什么问题了。
加载不成功？是否是你的uboot 太老了，老的uboot是没法加载ext4 的文件格式的系统的，也会产生这种现象，这几天都发现了很多这种问题了。

file system.img
system.img: VMS Alpha executable
这样是不行的，这个说明不是system.img
ext4 文件格式。

结论是file system.img和file system.img用unyaffs解压，用mkyaffs2image压缩而成.

这样是不行的哦

./make_ext4fs  -l 120M -a system system.img out/target/product/smdkv210/system
经过这么压缩
再用file 命令查看就变成ext4 文件格式的系统了。
file system.img
system.img: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-0000-675f-946fc0f9f25b (extents) (large files)
还要要注意out/target/product/smdkv210 下的init.rc文件一定要保证是去掉了yaffs的标志，可以直接复制init_SDMMC.rc 的过来改名即可。

system 6M的肯定起不来呀，可能就像版主说的，2.3的系统存在问题，还是什么的。

好像最后4.0里面有个脚本mkusering.sh，会调用make_ext4fs这个命令，把system做成ext4格式的。我这俩天要调一个touchscreen驱动，调完了才能继续SD卡制作。还是想多向版主请教一些。你说的工具主要都是重新制作system的，但是ramdisk怎么办呢，我最头痛的是ramdisk，看别人工具里都mkext3image这样的工具，我这源码里只有mkyaffs2image。
还有我的uboot好像确实是比较老1.3.4版本的，里面的命令找不到ext4format，只有ext2和ext3，这样应该能通过吧，因为内核选项里有use ext4 for ext2 and ext3.

是否调用了难说，你用file 命令看一下格式就知道了。

嗯~谢谢版主。
另外我还有别的一个问题想请教一下，用的android4.0系统编译出来的system能够正常跑，但是我将system重新用mkyaffs2image打包之后，系统就跑不起来了，是什么原因呢。我重新打包的时候，只是将out/target/product/smdkv210/system/usr/idc/里面的一个文件换了个名字, 即将上s3c_ts.idc换成了sis9200_i2c_touchscreen.idc. 这个文件只是和触摸屏有关的，但是重新打包之后，就出现PVR_K:(Error): BridgedDispatchKM: Driver initialisation not completed yet. [4799, drivers/gpu/pvr/bridged_pvr_bridge.c]。 用原来的就行。

版主啊，现在按你的方法试了，还是挂载不上文件系统。以前的yaffs2已经没有了，证明system.img已经是ext4格式的，并且file 查看也正确。但是报错如下：
Freeing init memory: 176K
init: /init.rc: 422: invalid option 'symlink'
init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
init: cannot open '/initlogo.rle'
EXT4-fs (mmcblk0p2): recovery complete
EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (mmcblk0p3): recovery complete
EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (mmcblk0p4): recovery complete
EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. Opts: (null)
init: cannot find '/system/bin/servicemanager', disabling 'servicemanager'
init: cannot find '/system/bin/vold', disabling 'vold'
init: cannot find '/system/vendor/bin/pvrsrvinit', disabling 'pvrsrvinit'
init: cannot find '/system/bin/netd', disabling 'netd'
init: cannot find '/system/bin/debuggerd', disabling 'debuggerd'
init: cannot find '/system/bin/rild', disabling 'ril-daemon'
init: cannot find '/system/bin/surfaceflinger', disabling 'surfaceflinger'
init: cannot find '/system/bin/app_process', disabling 'zygote'
init: cannot find '/system/bin/drmserver', disabling 'drm'
init: cannot find '/system/bin/mediaserver', disabling 'media'
init: cannot find '/system/bin/dbus-daemon', disabling 'dbus'
init: cannot find '/system/bin/installd', disabling 'installd'
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
mfc_firmware_request_complete_handler: failed to load MFC F/W, MFC will not working
init: cannot find '/system/bin/keystore', disabling 'keystore'
init: property (null) has no value for writing to /sys/class/android_usb/android0/iManufacturer
init: property (null) has no value for writing to /sys/class/android_usb/android0/iProduct
init: cannot find '/system/bin/sh', disabling 'console'
android_usb: already disabled
adb_bind_config
warning: `adbd' uses 32-bit capabilities (legacy support in use)
android_work: did not send uevent (0 0   (null))
adb_open
android_work: sent uevent USB_STATE=CONNECTED
android_usb gadget: high speed config #1: android
android_work: sent uevent USB_STATE=CONFIGURED
是我的分区问题吗？又该如何分区呢？