DHGE

Igor - don't take it personally. It is fixed now. Thank you! I really do not want to test on my only/production hc1 and just happened to not test on my xu4 which I normally do - once a month. This time I did an upgrade because Baikal does not come up. That is the next problem I will have to fix ... At least I will drop a "few pennies" like: 2017-09-01 OMV PayPal 50 EUR

"it should be o.k." yeah but it is/was NOT! pulling my leg? I think I got caught between repository updates... Manually (dissecting the deb-file) I installed linux-dtb-next-odroidxu4_5.39_armhf Now it works again: root@hc1:/# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: linux-dtb-next-odroidxu4 linux-u-boot-odroidxu4-next 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 343 kB of archives. After this operation, 137 kB disk space will be freed. Do you want to continue? [Y/n] Get:1 http://apt.armbian.com/ jessie/main linux-dtb-next-odroidxu4 armhf 5.39 [75.0 kB] Get:2 http://apt.armbian.com/ jessie/main linux-u-boot-odroidxu4-next armhf 5.39 [268 kB] Fetched 343 kB in 1s (214 kB/s) (Reading database ... 48427 files and directories currently installed.) Preparing to unpack .../linux-dtb-next-odroidxu4_5.39_armhf.deb ... Unpacking linux-dtb-next-odroidxu4 (5.39) over (5.38) ... Preparing to unpack .../linux-u-boot-odroidxu4-next_5.39_armhf.deb ... Unpacking linux-u-boot-odroidxu4-next (5.39) over (5.38) ... Setting up linux-dtb-next-odroidxu4 (5.39) ... Setting up linux-u-boot-odroidxu4-next (5.39) ... Updating u-boot on /dev/mmcblk1 root@hc1:/# reboot

I just did an upgrade of my ODROID hc1: root@hc1:/home/user#apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: armbian-config armbian-firmware armbian-tools-jessie hostapd linux-dtb-next-odroidxu4 linux-jessie-root-next-odroidxu4 linux-u-boot-odroidxu4-next sunxi-tools 8 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 3,306 kB of archives. After this operation, 137 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://apt.armbian.com/ jessie/main armbian-config all 5.38 [30.0 kB] ... Get:8 http://apt.armbian.com/ jessie/jessie-utils sunxi-tools armhf 1.4.2-2~armbian5.38+1 [36.2 kB] Fetched 3,306 kB in 12s (273 kB/s) (Reading database ... 48425 files and directories currently installed.) Preparing to unpack .../armbian-config_5.38_all.deb ... ... Processing triggers for initramfs-tools (0.120+deb8u3) ... update-initramfs: Generating /boot/initrd.img-4.9.61-odroidxu4 cryptsetup: WARNING: failed to detect canonical device of /dev/mmcblk1p2 W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. W: mdadm: no arrays defined in configuration file. update-initramfs: Converting to u-boot format Setting up armbian-config (5.38) ... Setting up armbian-firmware (5.38) ... Setting up armbian-tools-jessie (5.38) ... Setting up hostapd (2:2.6-4~armbian5.38+1) ... Setting up linux-dtb-next-odroidxu4 (5.38) ... Setting up linux-jessie-root-next-odroidxu4 (5.38) ... Setting up linux-u-boot-odroidxu4-next (5.38) ... Updating u-boot on /dev/mmcblk1 Setting up sunxi-tools (1.4.2-2~armbian5.38+1) ...Shell-Script Quellcode bearbeiten root@hc1:/home/user#apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: armbian-config armbian-firmware armbian-tools-jessie hostapd linux-dtb-next-odroidxu4 linux-jessie-root-next-odroidxu4 linux-u-boot-odroidxu4-next sunxi-tools 8 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 3,306 kB of archives. After this operation, 137 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://apt.armbian.com/ jessie/main armbian-config all 5.38 [30.0 kB] ... Get:8 http://apt.armbian.com/ jessie/jessie-utils sunxi-tools armhf 1.4.2-2~armbian5.38+1 [36.2 kB] Fetched 3,306 kB in 12s (273 kB/s) (Reading database ... 48425 files and directories currently installed.) Preparing to unpack .../armbian-config_5.38_all.deb ... ... Processing triggers for initramfs-tools (0.120+deb8u3) ... update-initramfs: Generating /boot/initrd.img-4.9.61-odroidxu4 cryptsetup: WARNING: failed to detect canonical device of /dev/mmcblk1p2 W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. W: mdadm: no arrays defined in configuration file. update-initramfs: Converting to u-boot format Setting up armbian-config (5.38) ... Setting up armbian-firmware (5.38) ... Setting up armbian-tools-jessie (5.38) ... Setting up hostapd (2:2.6-4~armbian5.38+1) ... Setting up linux-dtb-next-odroidxu4 (5.38) ... Setting up linux-jessie-root-next-odroidxu4 (5.38) ... Setting up linux-u-boot-odroidxu4-next (5.38) ... Updating u-boot on /dev/mmcblk1 Setting up sunxi-tools (1.4.2-2~armbian5.38+1) ... Processing triggers for initramfs-tools (0.120+deb8u3) ... update-initramfs: Generating /boot/initrd.img-4.9.61-odroidxu4 cryptsetup: WARNING: failed to detect canonical device of /dev/mmcblk1p2 W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. W: mdadm: no arrays defined in configuration file. update-initramfs: Converting to u-boot format root@hc1:/home/user# ls /boot armbian_first_run.txt.template boot-desktop.png boot.ini.out dtb dtb.old lost+found uInitrd vmlinuz-4.9.61-odroidxu4 boot.bmp boot.ini config-4.9.61-odroidxu4 dtb-4.14.15-odroidxu4 initrd.img-4.9.61-odroidxu4 System.map-4.9.61-odroidxu4 uInitrd-4.9.61-odroidxu4 zImage root@hc1:/home/user# reboot After reboot I can not reach the machine any more via browser or ssh. The machine does not connect to my router any more. LEDs look normal. Power cycling did not help. This happened to me once before when updating OMV itself. At that time I did a time consuming reinstallation via a new image loaded from Sourgeforge. Note that kernel updates went smooth on this setup before and the cryptsetup error is to be expected since I have a LUKS-encrypted data storage (decrypted after boot via the web interface). I speculate that the problem lies in getting a dtb (5.38) which does not fit the kernel 4.9.61 (5.earlier). Is there anything I could do to avoid a new installation?