build : http://autobuilder.yoctoproject.org/pub/nightly/20120822-1/ Target platform : qemux86 Image Profile : sato-sdk Procedure : 1.down load http://autobuilder.yoctoproject.org/pub/nightly/20120801-1/machines/qemu/qemux86/bzImage-qemux86.bin core-image-sato-sdk-qemux86-20120822141956.rootfs.ext3 2.source environment-setup-i586-poky-linux 3.runqemu qemux86 bzImage-qemux86.bin core-image-sato-sdk-qemux86-20120822141956.rootfs.ext3 4. Check the dmesg & /var/log/messages fils once system up. Error : root@qemux86:/home# dmesg | grep -i error EXT3-fs (hda): warning: ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure EXT3-fs (hda): warning: mounting fs with errors, running e2fsck is recommended root@qemux86:/home# root@qemux86:~# cat /var/log/messages | grep -i error Aug 24 09:29:50 qemux86 user.warn kernel: EXT3-fs (hda): warning: ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure Aug 24 09:29:50 qemux86 user.warn kernel: EXT3-fs (hda): warning: mounting fs with errors, running e2fsck is recommended root@qemux86:~#
Just to verify, seems you are booting a bzImage from 20120801-1 with a core-image-sato-sdk.ext3 from 20120822-1? If so then I would not guarantee that would work,
Hi Saul wold , http://autobuilder.yoctoproject.org/pub/nightly/20120822-1/machines/qemu/qemux86/bzImage-qemux86.bin core-image-sato-sdk-qemux86-20120822141956.rootfs.ext3 bzImage is also 22nd August . Its typo mistake. root@qemux86:~# ls root@qemux86:~# dmesg | grep -i error EXT3-fs (hda): warning: mounting fs with errors, running e2fsck is recommended root@qemux86:~# dmesg | grep -i error^C root@qemux86:~# cat /var/log/messages | grep -i error Aug 28 04:27:48 qemux86 user.warn kernel: EXT3-fs (hda): warning: mounting fs with errors, running e2fsck is recommended root@qemux86:~#
I just used the same image and ext3 from 20120822 as you listed, and found no errors, can you re-download and maybe double check the checksums of what you downloaded. The .ext3 you already have used will not match, but if you saved a copy check it, other wise try to download again please. 77fb33ce366c49a12e5a0ec72ed9732a bzImage-qemux86.bin 29525594545579f017180365c7bf1434 core-image-sato-sdk-qemux86.ext3
Any updates on this bug? Was it a corrupt image again? I will close this in 24 - 48 hours if I do not get a reply.
Hi Saul , I am not able to reproduce this issue . please close it. Thnaks veera
Hi Saul , what ever i downloaded images md5sum & your mentioned md5sum is not matching 2e6f472353f2250e4488ca607044c510 poky-eglibc-i686-i586-toolchain-gmae-1.2+snapshot-20120822.sh 77fb33ce366c49a12e5a0ec72ed9732a bzImage-qemux86.bin Thnaks Veera
Possibly a bad download it seems, we are taking steps to add the md5sum to the downloads so comparisons can be made before booting which should address this kind of problem.So you want an Air, hmm, let's see what might that cost you ;-) Seriously, what does an Air cost in the UK, I will budget it into next year since that's now Capitol instead of BTI. How old is the X200 that you have now? Sau!So you want an Air, hmm, let's see what might that cost you ;-) Seriously, what does an Air cost in the UK, I will budget it into next year since that's now Capitol instead of BTI. How old is the X200 that you have now? Sau!
verified in 8b3aa00029e62df6d05710cf166fd5d09bdb29cf