Today I did build the image for stretch (for M2 Ultra) - but it was a bit strange - because it ended up in a 1.1GB .image file, but the compressed size was only 1.5MB

 

OK, before building the image I got only 6GB free on my virtual HDD - by the last images this did work....

Now I will reinstall my build-system with the double size (60GB against 30GB before) and then I will firstly try to create a xenial image (not stretch which give me the compressed 1.50MB image whcih doesnt boot  )

I have the same issue (with jessie and strech, xenial untried) - encountered the following error during build:

Reading state information...
hostapd is already the newest version (2:2.6-4~armbian5.38+1).
sunxi-tools is already the newest version (1.4.2-2~armbian5.38+1).
sunxi-tools set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[ o.k. ] Calling image customization script [ customize-image.sh ]
[ o.k. ] Preparing image file for rootfs [ orangepilite stretch ]
[ o.k. ] Current rootfs size [ 801 MiB ]
[ o.k. ] Creating blank image for rootfs [ 1096 MiB ]
1.07GiB [  37MiB/s] [====================================================>] 100%
[ o.k. ] Creating partitions [ root: ext4 ]
[ .... ] Creating rootfs [ ext4 ]
Invalid filesystem option set: ^64bit,^metadata_csum
tune2fs: Bad magic number in super-block while trying to open /dev/loop0p1
Couldn't find valid filesystem superblock.
mount: wrong fs type, bad option, bad superblock on /dev/loop0p1,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.

The image of course does not boot.

We recently moved to Ubuntu Bionic build host? You still build on Xenial?

Host is Xenial. As recommended here https://docs.armbian.com/Developer-Guide_Build-Preparation/

 

33 minutes ago, Igor said:

We recently moved to Ubuntu Bionic build host? You still build on Xenial?

Yes - because the armbian page  https://docs.armbian.com/Developer-Guide_Build-Preparation/ says

Quote

The only supported compilation environment is Ubuntu Xenial 16.04 x64 (no other releases are supported! It has to be exactly 16.04 otherwise default compiler versions might not match so if you’re on an older Ubuntu release upgrade to 16.04 now, if you use a newer Ubuntu version start with 16.04 from scratch),

 

[EDIT]

and here on the github-page https://github.com/armbian/build its says 18.04.... maybe we should change the documentation page?
 

Quote

Supported build environment is Ubuntu Bionic 18.04 x64 (minimal iso image).

 

Text need to be updated. I though it will continue to work on Xenial with exception of building Bionic targets which is still disabled for end users ... so I didnt see a rush in changing documentation.

 

Not 100% sure but on my Bionic build host, images are building fine.

7 minutes ago, Igor said:

Not 100% sure but on my Bionic build host, images are building fine.

I has interrupted the reinstall/compile of the 16.04 build-system....and I will restart using the 18.04 mini.iso

 

Maybe ther only a problem for the BPI M2 Ultra images?

Backwards compatibility with Xenial environment was broken by mistake, will fix it ASAP.

Well, I missed that memo.  Now to upgrade apparently... 

another difference at the git-clone command

 

at 16.04:

git clone --depth 1 https://github.com/armbian/build

 

at 18.04:

git clone https://github.com/armbian/build

 

So there is much more to clone at 18.04?

So  I did install the build system with Ubuntu Bionic 18.04 64bit and there I could create bootable Image-Files xenial and stretch for the BPi M2 Ultra

(also useable for the M2 Berry).