Filesystem issue when writing CubieBoard image on sd card about armstrap HOT 2 CLOSED

EXT4 is fine and even if U-Boot complain about it, it still load well. There was a windows last night when i was moving things from u-boot-hno to the official u-boot-sunxi that could have caused issues.

Both Ext2 and Ext4 work, but Ext4 is prefered since it's journalised, you won't end up with a corrupted filesystem.

One thing that is essential while working with images instead of directly on the device is to make sure the image is big enough to hold everything. 2GB is the bare minimum for CubieBoard2, for CubieBoard, guess it could work with 1.5GB (probably 1GB too), but i've never tried anything bellow 2GB anyway.

Both my test boards (CubieBoard and CubieBoard 2) work well with the current settings. But i didn't tried to dump an image to the SD for a while, i always write directly to the SD. I will try to check that this weekend if i have time.

from armstrap.

Like i said, i tested the image creator tonight and it work well. One thing that can make it fall is if your SD is too small to write the whole image. If you have a 2GB SD, do not try a 2048mb image, try something a few mb smaller. To write the image, nothing special to do. Something like this is enough :

dd if=CubieBoard-rarring_CubieDebian-130823_194859.img of=/dev/sdc

from armstrap.