Armbian Cubietruck Desktop does not start for Nand



Recommended Posts

Armbian Cubietruck Desktop does not start the graphical environment for Nand.



I downloaded the Armbian Legacy 5:10 Cubietruck Debian jessie 3.4.112 Desktop ( , I recorded the image on an SD card using a software called Rufus ( )

Insert the card into Cubietruck and Armbian starts and works perfectly ! run the script to perform the copy of the card to nand , the same copy without any error and asks at the end off the Cubietruck and disconnect the SD card .

After disconnecting the SD card the Armbian does not start. However I rode the Nand and it meets all of the recorded files.


I wonder how to start the Cubietruck by nand perfectly?



Here the configuration of FSTAB file written in NAND my Cubietruck.
copy was performed using the script

Do not start by NAND

/dev/nand2 / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1
tmpfs /tmp tmpfs defaults,rw,nosuid 0 0
/var/swap none swap sw 0 0
/dev/nand1 /boot vfat   defaults 0 0




Sorry I do not speak English , I'm using Google Translate !

But I thank the collaboration of all of the community !



Link to post
Share on other sites

Armbian is a community driven open source project. Do you like to contribute your code?

First you need to try this:


Bugs or limitation


If things fail, like in your case, you need to use those proprietary Phoenix tools to fix NAND. When this is done, you can install with our tools. Partition or formatting does not break this. 


And if even this fails, your NAND is broken. It happen.

Link to post
Share on other sites

Hello Igor,

Thank you for your support.

i have similar trouble with nand-sata-install. 1. starting from sd card with the xDesktop image

2. Close xDesktop by Strg+Alt+F1

3. nand-sata-install. (Boot sd/ Root on sata)- done without failure

4. Restart

5. xDesktop does not start, instead it's only possible go to root in tty, CTRL-D permission denied

How can I start the xDesktop now?


Link to post
Share on other sites

This topic is now closed to further replies.