kukulo

You can have two options: using dd you can create image of sd card and write with dd again to other card. Or you can make tar backup of your files on sd card and boot sector backup with dd and use tar again to extract and dd to write boot sector of SD card.

I had a similar problem with Lime2 running Armbian. With iperf I can get close to 900Mbit/s speed, but when it comes to samba the transfer is around 25-30MB/s. The one explanation for this is that iperf is running from memory excluding eventual USB and SATA bottlenecks, whereas samba is running via the SATA (or USB). Second thing is the performance of the ARM processor itself. If you are looking for higher speed then you may easily hit the hardware limits of the ARM board.

Do you have a good power source? A minimum of 3A, 5V power source is needed. I have one board that has been under powered with 2,5A source and was time-to time hanging when the power consumption exceeded the capacity of the power source. After replacing with power source of larger capacity the problem was gone.

I had the same message on my Cubietruck. The board was in my desk for two years, it was a HW failure. Some search on internet suggested a bad soldering under DRAM chip. So with heating gun I heated up the DRAM chip for approx 5 minutes at 250 Celsius degrees and Cubietruck finally booted from SD Card with Cubietruck Armbian image 5.31.

linux-u-boot-next-lime2_5.38.180128_armhf.deb is rebooting and working in headless mode. Good job.

The linux-u-boot-next-lime2_5.37.180117_armhf.deb package solved my problem with booting in headless mode. There is another problem that is persisting on my board, I cannot reboot remotely, instead I need to pull out the DC plug. Any ideas how to solve that problem?

You have bridged two interfaces eth0 and wlan. By default armbian works as client/server where all interfaces are bridged. You need to setup eth0 and wlan on different subnets without bridging them together.

I have tested the linux-u-boot-next-lime2_5.37.180117_armhf.deb package and this u-boot fails to boot without HDMI attached, moreover when attached and performing reboot, the system powers-off. The 5.31 u-boot allows to startup in headless mode, but the reboot - poweroff issue persists.

Strange, now I downgraded u-boot to 5.23 and kernel to 4.11.6 which was rebooting previously and now it is not rebooting. The new u-boot must have updated on the device something....

I tried the linux-u-boot-next-lime2_5.37.180112_armhf.deb in combination with 4.14.8-sunxi kernel and it is refusing to boot without HDMI attached.

With u-boot 5.35 the lime2 is failing to start in headless mode, moreover when downgraded to u-boot 5.31, the device powers off instead of rebooting. I tried downgrade to 5.23 u-boot from my archive, but the reboot issue still persists. Now I am using the 4.13.16 kernel and before I was using 4.11.6 where the reboot worked. Both these issues were addressed previously in other posts. Is there any work in progress on this issue? Before I am rolling back to my previous backup I would like to know whether it makes sense to wait a bit for fixed packages or not.