zador.blood.stained

It's a temporary error, long story short - GPG key for aptly repository expired, and now dependencies installation will fail on Ubuntu Trusty.
 
 
 
Please try Ubuntu Wily (or Xenial) as your build host in VM.
 
Edit: new key added to build script, so this should be fixed shortly.

This will prevent packing raw image into zip archive. To prevent image shrinking, try setting
EXTENDED_DEBOOTSTRAP=yes FIXED_IMAGE_SIZE=4000 image size is in megabytes; you can even create image that perfectly fits your SD card (you'll need to add
touch /root/.no_rootfs_resize to customize-image.sh to prevent unneeded FS resize on first boot)

It's a temporary error, long story short - GPG key for aptly repository expired, and now dependencies installation will fail on Ubuntu Trusty.
 
 
 
Please try Ubuntu Wily (or Xenial) as your build host in VM.
 
Edit: new key added to build script, so this should be fixed shortly.

Usually anything related to possible SD cards problems automatically summons @tkaiser here 
http://oss.digirati.com.br/f3/
 
 
This shouldn't be a problem.
 
By the way, what kernel and distribution are you testing? Are you experiencing error with one combination of OS release and kernel or with several different too?

1. "Dumb" USB/2.5" IDE adapter that doesn't provide any S.M.A.R.T. data:
http://sprunge.us/MJWH
 
 
 
2. JMicron based USB/2.5" IDE + 3.5" IDE + SATA bridge, SATA drive attached
http://sprunge.us/KRLA
 
 
 
3. Same bridge, 2.5" IDE drive attached
http://sprunge.us/PaQU
 
 
 
4. Same bridge, 2.5" SATA drive attached
http://sprunge.us/caSO
 
 
 
5. JMicron based USB 3.0/SATA bridge
http://sprunge.us/BIhH
 
 

You don't need to edit anything in lib/ directly. In fact it's better that you reset or remove lib directory so your changes don't prevent pulling future updates.
 
You shoud use "customize-image.sh" conviniently (auto) copied to "userpatches/". Because it is copied only if it doesn't exist already, your changes in lib/scripts didn't have any effect.
 
 
Yes, git should be installed at this point.

Serial is ttyS0,115200
 
Wrote on mobile phone

"48.4 sy 51.5 wa" on 3rd line partially answers your second and fourth questions - SATA interface on A20 is slow and inefficient, so swapping combined with running torrent client results in this - CPU is processing SATA requests and waiting for I/O operations (and if you have mechanical HDD, seek time when multiple programs access different files also affects this).
 
So in your case using swap on SATA is bad idea, using no swap (if possible), zram or swap on SD card may be better.

Yes, if you have a local working copy of kernel repository, you just make necessary adjustments and execute in repository root directory
git diff <path> specifying path for git diff reduces time needed for finding changed files, especially in huge repositories
for example
git diff arch/arm/boot/dts > leds-for-bananapro.patch You can fork and make a pull request for Igor's repo, but some triggers (especially heartbeat) are quite annoying with bright SMD LEDs to have them by default.

Yes, if you have a local working copy of kernel repository, you just make necessary adjustments and execute in repository root directory
git diff <path> specifying path for git diff reduces time needed for finding changed files, especially in huge repositories
for example
git diff arch/arm/boot/dts > leds-for-bananapro.patch You can fork and make a pull request for Igor's repo, but some triggers (especially heartbeat) are quite annoying with bright SMD LEDs to have them by default.

... or in new Armbian mainline kernel with my patch it can be activated by writing "1" to "/sys/power/axp_pmu/control/charge_rtc_battery"
 
I cheched AXP datasheet and battery (at least model mentioned in cubietruck schematics) datasheet, and if all AXP registers were reset, default values for voltage and current should be safe.

Both bananapi and bananapro dts files are present in mainline kernel git repository. And one of kernel maintainers explains here that they don't like setting default triggers in DT because you can change them via sysfs interface (however this means that LEDs won't work in ealry boot until init script or systemd unit sets LED settings).
 
You can read more about sysfs interface, for example, here.

Using 3.4 kernel and trying to follow tutorials for mainline kernel will not work. Try to read from here on http://linux-sunxi.org/GPIO#Accessing_the_GPIO_pins_through_sysfs_on_sunxi-3.4
 
And since you're using Jessie it should work to do a 
apt-get install sunxi-tools to get the necessary tools. In case you're still stuck it might be a good idea to post the GPIO configuration from script.bin after translated through bin2fex.

You don't need to add whole block, just append label before one that already exists
ir0_rx_pins_a: Edit: since it's impossible to change font inside code blocks, I marked parameters that should be added or changed:

First, test your receiver with irrecord, something like this (load lirc modules from message #2 in this topic):
sudo irrecord -d /dev/lirc0 /tmp/remote.conf If dots are appearing when you start to learn, then Device Tree settings are correct. 
 
Next thing you need to check - if you want to use devinput, you should probably load kernel keymap decoder (Edit: no need, they are built-in) and configure input device to use it. Check 
cat /sys/class/rc/rc0/protocols for list of available and selected (in brackets) protocols, try selecting protocol with
sudo sh -c "echo nec > /sys/class/rc/rc0/protocols" or something like this.
 
Edit 2: Or install ir-keytable

Can confirm, opening armbian.com in incognito mode causes redirect to mentioned website.

The most interesting thing on this schematic is that feedback voltage for CPU power regulator comes from separate H3 pins (VDD-CPUFB and GND-CPUFB) and there are test points for these pins too. I would recommend measuring VDD_CPUFB voltage too (test point is marked TP1 on schematic, page 6, top right corner).

The most interesting thing on this schematic is that feedback voltage for CPU power regulator comes from separate H3 pins (VDD-CPUFB and GND-CPUFB) and there are test points for these pins too. I would recommend measuring VDD_CPUFB voltage too (test point is marked TP1 on schematic, page 6, top right corner).

It would be easy to add an option to skip installing of PAKETKI/PACKAGES completely, leaving only stuff installed by debootstrap itself, but it will enable only basic wired networking and probably will break later stages of image creation.
Separation into "essential" and "non-essential" packages can be done, but it will take some time to check and test stuff, especially since "absolutely required" is subjective.
 
You can use "customize-image.sh" to achieve this.

This option is obsolete (not supported currently). You should be able to remove systemd from Jessie after installation using this wiki article.
 
FYI, you may loose some Systemd-specific settings (like serial console settings, shutdown by pressing power button).

I2S works only in default/legacy (3.4.10x) kernel for now, so you need to install it (or use another Armbian image) to get it working (you still need script.fex tweaks to activate it).

I can confirm this weird behaviour: "changing "ext4load mmc 0 0x49000000 /boot/dtb/sun7i-a20-bananapro.dtb in /boot/boot.cmd" and it made the difference between recognice the SATA or not at the boot time (and after that as well).
 
The prebuilt image (with u-boot 5.0.0 & 5.0.1) doesn't work with SATA until we linked the dtb files with the model "bananapro" and not with bananapi default, which is automatically triggered after every upgrade.
 
Changing boot.cmd from default to "sun7i-a20-bananapro.dtb" will do the magic:
ext4load mmc 0 0x49000000 /boot/dtb/sun7i-a20-bananapro.dtb || fatload mmc 0 0x49000000 /dtb/sun7i-a20-bananapro.dtb having this packages installled:
root@bananapi:/boot# dpkg -l|grep next ii  linux-dtb-next-sunxi                5.00                              armhf        Linux DTB, version 4.4.1-sunxi ii  linux-firmware-image-next-sunxi     5.00                              armhf        Linux kernel firmware, version 4.4.1-sunxi ii  linux-headers-next-sunxi            5.00                              armhf        Linux kernel headers for 4.4.1-sunxi on armhf ii  linux-image-next-sunxi              5.00                              armhf        Linux kernel, version 4.4.1-sunxi ii  linux-u-boot-bananapi-next          5.01                              armhf        Uboot loader 2016.01 ii  linux-wheezy-root-next-bananapi     5.00                              armhf        Root file system tweaks for bananapi This starts to be litte tricky; since my first ARMBIAN version (4.0.5 ~  Juli 2015) for Banana Pro I suffered with every ARMBIAN upgrade this collateral damage because banana pi and pro are not properly recogniced.
 
Why this? It is not possible to trigger the scripts to manage both separatedly?
 
 
I tested:
 
1) SATA error manifests with this error on u-boot 5.0.1:
 3.477254] ahci-sunxi 1c18000.sata: controller can't do PMP, turning off CAP_PMP [    3.477317] ahci-sunxi 1c18000.sata: SSS flag set, parallel bus scan disabled [    3.477351] ahci-sunxi 1c18000.sata: AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl platform mode [    3.477367] ahci-sunxi 1c18000.sata: flags: ncq sntf stag pm led clo only pio slum part ccc [    3.478886] ata1: SATA max UDMA/133 mmio [mem 0x01c18000-0x01c18fff] port 0x100 irq 33 [    3.827349] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [    8.827195] ata1.00: qc timeout (cmd 0xec) [    8.827214] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [    9.177171] ata1: SATA link down (SStatus 0 SControl 300) 2) SATA error manifests with this error on u-boot 5.0.0 (downgrade with apt-get install linux-u-boot-bananapi-next=5.00)
root@bananapi:~# dmesg| grep ata [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [    0.000000] Memory policy: Data cache writealloc [    0.000000] Memory: 1010820K/1046952K available (6822K kernel code, 256K rwdata, 1760K rodata, 328K init, 280K bss, 19748K reserved, 16384K cma-reserved, 244136K highmem) [    0.000000]       .data : 0xc08bc000 - 0xc08fc1a0   ( 257 kB) [    3.205237] libata version 3.00 loaded. [    3.448110] ahci-sunxi 1c18000.sata: PHY power up failed. [    3.448184] ahci-sunxi: probe of 1c18000.sata failed with error -5 In this situation it means that the 5.0.1 U-boot version doesn't work properly, or I'm doing something wrong?. I tested this starting with ARMBIAN 4.0.5 on SD and consecutively upgrading.
 
Fazit: U-boot 5.0 failed like 5.0.1 until the change of the bananapro dtb file, this made the trick.
 
Another different issue: I realized that the banana led lighting only works with bananapi.dtb and not with bananapro.dtb. It is possible to do the same for bananapro.dtb out of the box? I really like that led is lighting according to CPU/IOs -or whatever-.
 
 
Tests were performed with a 2,5" HDD SEAGATE Momentus ST750LX003 750GB which was recogniced before without issues.

I'm using Debian testing too with commented Armbian repository, but it should work with jessie-specific config since both jessie and stretch are systemd-based.
➜ ~ % cat /etc/apt/sources.list.d/armbian.list deb http://apt.armbian.com jessie main Downgrading kernel, u-boot and other packages should be possible by manually downloading and installing packages from apt repository, or by specifying package version for apt-get manually (apt-get install <package>=<version>)
You can check available versions using i.e.
apt-cache madison linux-image-next-sunxi  
 
 
BTW, if you are experiencing SATA issues on Banana Pro, please check this topic, it might be u-boot related and may be already fixed in new u-boot release.

"Upgrade script" was created mainly for older distributions that didn't have Armbian apt repository set up. For more or less fresh versions upgrade should be done with apt (apt-get update && apt-get upgrade).
Sometimes though you may need to additionally tweak something manually here or there (like modifying u-boot script or installing fake-hwclock package).
 
For installing self-compiled stuff - kernel and DTB (if kernel requires it) should be installed always in pair; updating headers and firmware may be necessary if you use them (i.e. self-compiled drivers of Wi-Fi modules that require firmware). Updating u-boot is generally not needed unless there were device-specific fixes made for it.
 
DTB deb package may give error with FAT /boot partition (i.e. with rootfs on NAND or devices with older u-boot), deleting old package and removing files in /boot manually should solve this issue.