it`s like Igor says: it`s all in the SD-Card. It seems, that my SANDISK Ultra 16gb SDCard for 10 EUR was or is the Problem. But it`s really special:
I bought this Card in EBAY with the description 80MB/sec. and when it comes to me, first i used H2TESTW from heise.de. The capacity was ok, but writing was constant at 10 MB/sec. and later reading was constant at 17MB/sec. OK, i wrote this to the Seller and 5 Min. later i got my money back (paypal). EBAY told me, that the seller has stopped the deal and i got a friendly mail in the ebay system from the seller, that they will look after it in their supply chain and so on.... i can keep the card. Now I think, that time of fake SD Cards about the capacity is over, next level are fake cards about speed. OK, when youre interested in SD Card testing Tools, look here:
Next step: I took an old SANDISK 8 GB Card and performed the SD Card Writing Procedure now on Linux, not windows. Note, that i have written the 16 GB Fake Card on Linux before again under Linux too and it doesnt boot. OK, here we go with the 8 GB old Card:
I put the card in the cubietruck and everything was allright, 1234 with root over ssh, great. At the moment the "cubie on SD-Card" is getting all updates and i can write this at the end:
Two hours ago, i purchased an 32GB SANDISK UHS SD Card, up to 95MB/sec for 26 EUR including shipping. Look here, if you like:
http://www.ebay.de/itm/132121757759
In prior Installation I was using SATA Disk as root file System, just booting up from 4 GB SD Card. Now i will follow Igors suggestion like this:
1) System complete on good, new and fast SD Card
2) SATA just for (private) Data
3) Backup System (on Card) once per month with dd
4) Backup Data by feeling with rsync
5) The best: possibility to boot from nand (and checking and mounting SATA) when SD Card fails