zador.blood.stained Posted January 30, 2018 Posted January 30, 2018 13 minutes ago, Igor said: And also Odroid XU4 upgrade to NEXT https://github.com/armbian/upload/commit/36437b8a9704a5056fccb6ed154b69778716bed8 The problem affects only sunxi so reverting anything else is useless. 14 minutes ago, Igor said: At least upstream those problems should be fixed by now. It is mostly our problem that upstream changes break booting with our old boot script and that we have automated u-boot upgrade procedure instead of manual.
Igor Posted January 30, 2018 Posted January 30, 2018 Just now, zador.blood.stained said: The problem affects only sunxi so reverting anything else is useless. The problem was there too but different kind of. I switch dev and next which lead to troubles with OMV installations. 4 minutes ago, zador.blood.stained said: It is mostly our problem that upstream changes break booting with our old boot script and that we have automated u-boot upgrade procedure instead of manual. At least setting this to "yes"? https://github.com/armbian/build/blob/master/config/templates/config-example.conf#L22
zador.blood.stained Posted January 30, 2018 Posted January 30, 2018 5 minutes ago, Igor said: At least setting this to "yes"? https://github.com/armbian/build/blob/master/config/templates/config-example.conf#L22 Doesn't help with old images
earth08 Posted January 30, 2018 Posted January 30, 2018 Changed back https://github.com/armbian/upload/commit/c68b8c84f9edfdfd55f1579894f05035e637022a And also Odroid XU4 upgrade to NEXT https://github.com/armbian/upload/commit/36437b8a9704a5056fccb6ed154b69778716bed8 At least upstream those problems should be fixed by now.Is there anyway to get device stucked on updating work again?Please guide us to get it Sent from my AO5510 using Tapatalk
Igor Posted January 30, 2018 Posted January 30, 2018 Replacing bootloader on your eMMC Boot from SD card. mkdir tmp cd tmp # replace this URL with the one for your board! This is for Orange pi plus 2e wget http://apt.armbian.com/pool/main/l/linux-u-boot-orangepiplus2e-default/linux-u-boot-orangepiplus2e_5.39_armhf.deb dpkg -x *.deb . root_uuid=$(sed -e 's/^.*root=//' -e 's/ .*$//' < /proc/cmdline) root_partition_device=$(blkid | tr -d '":' | grep ${root_uuid} | awk '{print $1}' | tr -d '"/dev') emmc="/dev/"$(cat /proc/partitions | grep -v ${root_partition::-2} | grep mmcblk | awk '{print $4}' | head -1) # adjust the path accordingly to your board - downloaded file dd if=usr/lib/linux-u-boot-orangepiplus2e_5.35_armhf/u-boot-sunxi-with-spl.bin of=$emmc bs=1024 seek=8 status=noxfer If you want to flash your SD card on external SD card reader: sdcard=/dev/sda # make sure this is SD card and not your hard drive!! dd if=usr/lib/linux-u-boot-orangepiplus2e_5.35_armhf/u-boot-sunxi-with-spl.bin of=$sdcard bs=1024 seek=8 status=noxfer 1
DHGE Posted January 30, 2018 Posted January 30, 2018 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?
Igor Posted January 30, 2018 Posted January 30, 2018 14 minutes ago, DHGE said: I just did an upgrade of my ODROID hc1: If you "just did", it should be o.k. https://github.com/armbian/upload/commit/19a4a27ca2ace9c549400a8eface67c581a4b144
DHGE Posted January 30, 2018 Posted January 30, 2018 "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
earth08 Posted January 30, 2018 Posted January 30, 2018 Replacing bootloader on your eMMC Boot from SD card.mkdir tmpcd tmp# replace this URL with the one for your board! This is for Orange pi plus 2ewget http://apt.armbian.com/pool/main/l/linux-u-boot-orangepiplus2e-default/linux-u-boot-orangepiplus2e_5.39_armhf.debdpkg -x *.deb . root_uuid=$(sed -e 's/^.*root=//' -e 's/ .*$//' root_partition_device=$(blkid | tr -d '":' | grep ${root_uuid} | awk '{print $1}' | tr -d '"/dev')emmc="/dev/"$(cat /proc/partitions | grep -v ${root_partition::-2} | grep mmcblk | awk '{print $4}' | head -1)# adjust the path accordingly to your board - downloaded file dd if=usr/lib/linux-u-boot-orangepiplus2e_5.35_armhf/u-boot-sunxi-with-spl.bin of=$emmc bs=1024 seek=8 status=noxfer If you want to flash your SD card on external SD card reader:sdcard=/dev/sda # make sure this is SD card and not your hard drive!!dd if=usr/lib/linux-u-boot-orangepiplus2e_5.35_armhf/u-boot-sunxi-with-spl.bin of=$sdcard bs=1024 seek=8 status=noxfer Where should it copy the extracted fileSent from my AO5510 using Tapatalk
Igor Posted January 30, 2018 Posted January 30, 2018 19 minutes ago, DHGE said: I think I got caught between repository updates... Somewhere between problem was recognized and fixed, yes. When most people will just use this product, drop few pennies and not actively participating in testings, this will not change - we simply have too many different boards and variants. We can cut them down in half but the problem will remain. I recently developed a system for quick repository update, that packages can be quickly fixed in case of such problems, but that is all that I can do on the technical part of the problem. At least you were able to solve this without step by step guides. Of course, it is our my fault for providing this service with having sufficient resources. 1
Igor Posted January 30, 2018 Posted January 30, 2018 1 hour ago, earth08 said: Where should it copy the extracted file Forget about changing u-boot, replace rather boot script. It is more simple and actually the fix for the problem. 1. Boot with SDcard 2. Mount /dev/mmcblk2p1 /mnt # on some cases it will be mmcblk1p1 3. cd /mnt/boot 4. wget https://raw.githubusercontent.com/armbian/build/master/config/bootscripts/boot-sunxi.cmd 5. mv boot-sunxi.cmd boot.cmd 6. mkimage -C none -A arm -T script -d boot.cmd boot.scr 7. power off, 8. remove SD and boot from eMMC 2
DHGE Posted January 30, 2018 Posted January 30, 2018 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 1
piknew Posted January 30, 2018 Posted January 30, 2018 Thanks, for me solution with manual download and "dd" to emmc works as well. Opi+2 is up & running now. For Opi+2e - tomorrow I will try (have a little more issues with physical access to device).
Igor Posted January 30, 2018 Posted January 30, 2018 1 minute ago, piknew said: Thanks, for me solution with manual download and "dd" to emmc works as well. Opi+2 is up & running now. For Opi+2e - tomorrow I will try (have a little more issues with physical access to device). Replacing boot script with this one https://github.com/armbian/build/blob/master/config/bootscripts/boot-sunxi.cmd and its recompilation is another/proper solution. In case we forget to add a boot script to next update, the problem might resurface.
earth08 Posted January 30, 2018 Posted January 30, 2018 39 minutes ago, Igor said: Forget about changing u-boot, replace rather boot script. It is more simple and actually the fix for the problem. 1. Boot with SDcard 2. Mount /dev/mmcblk2p1 /mnt # on some cases it will be mmcblk1p1 3. cd /mnt/boot 4. wget https://raw.githubusercontent.com/armbian/build/master/config/bootscripts/boot-sunxi.cmd 5. mv boot-sunxi.cmd boot.cmd 6. mkimage -C none -A arm -T script -d boot.scr boot.cmd 7. power off, 8. remove SD and boot from eMMC error mkimage: can't stat boot.scr: No such file or directory Sent from my AO5510 using Tapatalk
Igor Posted January 30, 2018 Posted January 30, 2018 typo mkimage -C none -A arm -T script -d boot.cmd boot.scr
earth08 Posted January 30, 2018 Posted January 30, 2018 typomkimage -C none -A arm -T script -d boot.cmd boot.scr By mistake i gave command for /boot/boot.cmd and it's still give me error Sent from my AO5510 using Tapatalk
piknew Posted January 30, 2018 Posted January 30, 2018 12 minutes ago, Igor said: Replacing boot script with this one https://github.com/armbian/build/blob/master/config/bootscripts/boot-sunxi.cmd and its recompilation is another/proper solution. In case we forget to add a boot script to next update, the problem might resurface. Done "just in case" (on already up & running opi+2): root@PKHELPER:/boot# ll total 14276 -rw-r--r-- 1 root root 6944 Jun 5 2016 boot.bmp -rw-r--r-- 1 root root 2372 Jun 5 2016 boot.cmd -rw-r--r-- 1 root root 2444 Jun 5 2016 boot.scr lrwxrwxrwx 1 root root 20 Aug 4 23:09 script.bin -> bin/orangepiplus.bin -rwxr-xr-x 1 root root 4752384 Jan 24 22:10 vmlinuz-3.4.113-sun8i -rw-r--r-- 1 root root 2056747 Jan 24 22:10 System.map-3.4.113-sun8i -rw-r--r-- 1 root root 97199 Jan 24 22:10 config-3.4.113-sun8i drwxr-xr-x 2 root root 4096 Jan 29 17:57 bin lrwxrwxrwx 1 root root 21 Jan 29 17:59 zImage -> vmlinuz-3.4.113-sun8i -rw-r--r-- 1 root root 3839674 Jan 29 17:59 initrd.img-3.4.113-sun8i -rw-r--r-- 1 root root 3839738 Jan 29 17:59 uInitrd-3.4.113-sun8i lrwxrwxrwx 1 root root 21 Jan 29 17:59 uInitrd -> uInitrd-3.4.113-sun8i root@PKHELPER:/boot# wget https://raw.githubusercontent.com/armbian/build/master/config/bootscripts/boot-sunxi.cmd --2018-01-30 17:32:16-- https://raw.githubusercontent.com/armbian/build/master/config/bootscripts/boot-sunxi.cmd Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.112.133 Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.112.133|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 3636 (3.6K) [text/plain] Saving to: ‘boot-sunxi.cmd’ boot-sunxi.cmd 100%[=======================================================================================>] 3.55K --.-KB/s in 0.001s 2018-01-30 17:32:16 (6.88 MB/s) - ‘boot-sunxi.cmd’ saved [3636/3636] root@PKHELPER:/boot# ll total 14280 -rw-r--r-- 1 root root 6944 Jun 5 2016 boot.bmp -rw-r--r-- 1 root root 2372 Jun 5 2016 boot.cmd -rw-r--r-- 1 root root 2444 Jun 5 2016 boot.scr lrwxrwxrwx 1 root root 20 Aug 4 23:09 script.bin -> bin/orangepiplus.bin -rwxr-xr-x 1 root root 4752384 Jan 24 22:10 vmlinuz-3.4.113-sun8i -rw-r--r-- 1 root root 2056747 Jan 24 22:10 System.map-3.4.113-sun8i -rw-r--r-- 1 root root 97199 Jan 24 22:10 config-3.4.113-sun8i drwxr-xr-x 2 root root 4096 Jan 29 17:57 bin lrwxrwxrwx 1 root root 21 Jan 29 17:59 zImage -> vmlinuz-3.4.113-sun8i -rw-r--r-- 1 root root 3839674 Jan 29 17:59 initrd.img-3.4.113-sun8i -rw-r--r-- 1 root root 3839738 Jan 29 17:59 uInitrd-3.4.113-sun8i lrwxrwxrwx 1 root root 21 Jan 29 17:59 uInitrd -> uInitrd-3.4.113-sun8i -rw-r--r-- 1 root root 3636 Jan 30 17:32 boot-sunxi.cmd root@PKHELPER:/boot# mv boot-sunxi.cmd boot.cmd root@PKHELPER:/boot# mkimage -C none -A arm -T script -d boot.cmd boot.scr Image Name: Created: Tue Jan 30 17:33:53 2018 Image Type: ARM Linux Script (uncompressed) Data Size: 3644 Bytes = 3.56 kB = 0.00 MB Load Address: 00000000 Entry Point: 00000000 Contents: Image 0: 3636 Bytes = 3.55 kB = 0.00 MB root@PKHELPER:/boot# ll total 14276 -rw-r--r-- 1 root root 6944 Jun 5 2016 boot.bmp lrwxrwxrwx 1 root root 20 Aug 4 23:09 script.bin -> bin/orangepiplus.bin -rwxr-xr-x 1 root root 4752384 Jan 24 22:10 vmlinuz-3.4.113-sun8i -rw-r--r-- 1 root root 2056747 Jan 24 22:10 System.map-3.4.113-sun8i -rw-r--r-- 1 root root 97199 Jan 24 22:10 config-3.4.113-sun8i drwxr-xr-x 2 root root 4096 Jan 29 17:57 bin lrwxrwxrwx 1 root root 21 Jan 29 17:59 zImage -> vmlinuz-3.4.113-sun8i -rw-r--r-- 1 root root 3839674 Jan 29 17:59 initrd.img-3.4.113-sun8i -rw-r--r-- 1 root root 3839738 Jan 29 17:59 uInitrd-3.4.113-sun8i lrwxrwxrwx 1 root root 21 Jan 29 17:59 uInitrd -> uInitrd-3.4.113-sun8i -rw-r--r-- 1 root root 3636 Jan 30 17:32 boot.cmd -rw-r--r-- 1 root root 3708 Jan 30 17:33 boot.scr root@PKHELPER:/boot# Device is still booting - OK ...
Igor Posted January 30, 2018 Posted January 30, 2018 4 minutes ago, earth08 said: By mistake i gave command for /boot/boot.cmd and it's still give me error Preparing such copy/paste instruction is a nightmare :( You need to be in /mnt/boot/ and there you run mkimage without a path.
jscax Posted January 30, 2018 Posted January 30, 2018 I have not updated yet. I can't understand if this can affect my OPI zero or not. Can you please point this out?
chwe Posted January 31, 2018 Posted January 31, 2018 2 hours ago, jscax said: I can't understand if this can affect my OPI zero or not. Can you please point this out? you could.... by reading this thread.. On 29.1.2018 at 7:56 PM, guidol said: All my Boards did boot after the 5.38 update - NPi Neo2 - NPi Duo - NPi Neo Core2 - OPi Zero - OPi Zero Plus H5 - OPi One 1
earth08 Posted January 31, 2018 Posted January 31, 2018 Preparing such copy/paste instruction is a nightmare You need to be in /mnt/boot/ and there you run mkimage without a path.Dear,Thanks for all your guidance/help.U help me get my pi working back normally,ThanksSent from my AO5510 using Tapatalk
tkaiser Posted March 1, 2018 Posted March 1, 2018 EspressoBin: https://forum.armbian.com/topic/6371-espressobin-wont-boot-after-upgrade-to-538/ ODROID-C2: https://forum.armbian.com/topic/6336-odroid-c2-cannot-start-with-u-boot-default-538/ sunxi/eMMC/bootscript: https://forum.armbian.com/topic/6299-problems-with-538-update/ sunxi performance: https://forum.armbian.com/topic/6386-lime2-mainline-kernel-with-debian-9-stretch-becomes-unresponsive-forced-reboot-required/ ODROID XU4/HC1/HC2: https://forum.armbian.com/topic/6299-problems-with-538-update/?do=findComment&comment=48200 How can we avoid this happening again?
Igor Posted March 1, 2018 Posted March 1, 2018 For now and to be realistic, we can further minimize possibility: - split u-boot package and kernel for updating. - create a bulletproof recovery method: perhaps even auto-revert if booting after update not successful - release one kernel(images) at once
Recommended Posts