nihilista Posted January 29, 2018 Posted January 29, 2018 I should have known better..... today i did an apt update and saw thet there was an update to 5.38. Installed it and like with nearly every last update the device (OrangePi +) didn't boot. Did you even test updates in the stable repo before ? Don't know whats going wrong, so i will test it, but thats annoying.....
piknew Posted January 29, 2018 Posted January 29, 2018 Confirmed - both of my Opi+ and Opi+2e are not booting after upgrade to 5.38. OpiPC and OpiZero - no issues.
chwe Posted January 29, 2018 Posted January 29, 2018 Can one of you provide the output from the serial console?
guidol Posted January 29, 2018 Posted January 29, 2018 whats special on the OPi+ and OPi2e? From the CPU they a normal H3-Boards 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 (legacy) / another - newly with mainline installed - OPi One is also working fine with 5.38 Is it a legacy/stable <--> mainline/nightly problem? My devices are using mostly mainline (nightly)
chwe Posted January 29, 2018 Posted January 29, 2018 (edited) OPi plus (if he means that by OPi+) & plus 2e have eMMC... but without more information, it's hard to say what's wrong... My OPI PC+ (server usecase so with mainline instead of legacy kernel runs smoothly on 5.38). I can't switch to legacy only to reproduce errors of others... Spoiler ___ ____ _ ____ ____ / _ \ _ __ __ _ _ __ __ _ ___ | _ \(_) | _ \ / ___| _ | | | | '__/ _` | '_ \ / _` |/ _ \ | |_) | | | |_) | | _| |_ | |_| | | | (_| | | | | (_| | __/ | __/| | | __/| |___ |_ _| \___/|_| \__,_|_| |_|\__, |\___| |_| |_| |_| \____| |_| |___/ Welcome to ARMBIAN 5.38.180128 nightly Debian GNU/Linux 9 (stretch) 4.14.15-sunx Edited January 29, 2018 by chwe didn't even know the OPi+
guidol Posted January 29, 2018 Posted January 29, 2018 58 minutes ago, chwe said: PC plus (if he means that by OPi+) & plus 2e have eMMC... but without more information, it's hard to say what's wrong... I think as OPi+ he means the https://www.armbian.com/orange-pi-plus/ The only "pi" with eMMC at my side is the NPi Neo Core2, but also with mainline (image of the NPi Neo Plus2 is working here with eMMC-support, but Iam running this from uSD). My OPi One is using legacy kernel (as Pi-Hole Server) but hasnt a eMMC. 1
Piv Klit Posted January 29, 2018 Posted January 29, 2018 (edited) It´s working here EDIT: (God damn it, didn't see that it was the real Opi+ he is talking about, forgot about that one since the image for the opi+2 says opi+, sorry, nothing to see here ) Edited January 29, 2018 by DEHN.IO Going to bed
nihilista Posted January 29, 2018 Author Posted January 29, 2018 With 4.14.5 kernel/debian next image booting fine (system on emmc), but i had debian legacy kernel and after upgrading no boot.
piknew Posted January 30, 2018 Posted January 30, 2018 In my case - both Orange Pi+ 2 and Orange Pi+ 2e are using emmc. Currently I am not able to provide any output from serial as I have no physical access to my devices (btw. I do not have serial/usb cable to investigate it ). Information (common for both devices, also the same for 2 devices which have no issues: Orange Pi PC and Orange Pi Zero 512MB H2+): - upgrade from 5.35 to 5.36 was OK - upgrade from 5.36 to 5.37 was OK (I have seen this upgrade was very minor, only 1 package has been updated) - upgrade from 5.37 to 5.38 failed for Opi+2 and Opi+2e (actually I am able to confirm for 100% that I am not able to connect to devices and I am 100% sure that this is not an issue related to e.g. different hwaddres, IP etc.) - either device hasn't booted at all or network interfaces are down (this one can be confirmed by anybody who can check by serial interface) - upgrade from 5.37 to 5.38 was OK for OpiPC and OpiZero - there ware no issues during upgrade process - it was completed without any warnings/errors. - Opi+2 and Opi+2e are using eMMC as main boot device - OpiPC and OpiZero are using SD cards as main boot device (obviously) - All 4 platforms are running with legacy kernel I will have physical access to both devices on Friday, 02.02.2018. I have "tool" SD card which will allow me to boot both devices and if there is any suggestion from this forum - I will be able to make necessary corrections (eg. "dd" new file to emmc boot sectors etc.).
Piv Klit Posted January 30, 2018 Posted January 30, 2018 Ok I can confirm that my Orange PI Plus 2 upgrade from Headless Ubuntu 5.36to 5.38 (Stable) worked without problems. Orange PI Plus 2E upgrade from Headless Ubuntu 5.37 (nightly) to 5.38 (nightly) worked without problems. So looks like the legacy images are the problem :/
Igor Posted January 30, 2018 Posted January 30, 2018 I made two additional upgrade tests with a legacy kernel, Orangepi PC+ and Orangepi 2e and it was not possible to detect any problems. http://ix.io/EWl - some old version which was on eMMC -> latest - 5.35 from download -> latest - some old beta -> latest We can't test all possible boards/combinations.
earth08 Posted January 30, 2018 Posted January 30, 2018 I have same problem after i updated today,Till now no success to get it workI M using oPi+2e Did someone get it working? Sent from my AO5510 using Tapatalk
Igor Posted January 30, 2018 Posted January 30, 2018 1 minute ago, earth08 said: I have same problem after i updated today, Till now no success to get it work I M using oPi+2e Sent from my AO5510 using Tapatalk Unless someone, who has this problem, does not provide serial console logs, we will not get anywhere. I can't reproduce it.
IgorS Posted January 30, 2018 Posted January 30, 2018 So, I have OrangePi plus 2e which boots mainline kernel from eMMC, and have MMC card as data volume. I just did apt update, apt upgrade and could'nt boot system anymore. Fortunatelly I have backup image, but anyway... What goes wrong ?!?
flags8192 Posted January 30, 2018 Posted January 30, 2018 I have the same problem. After updating from 5.37 to 5.38 Orange Pi Plus 2E stopped loading. Here is the console log: https://pastebin.com/i9FsCHqt
zador.blood.stained Posted January 30, 2018 Posted January 30, 2018 19 minutes ago, flags8192 said: Here is the console log: https://pastebin.com/i9FsCHqt Looks like u-boot MMC numbering changes broke backwards compatibility with our old boot script (that had "mmc 0" hardcoded everywhere, pre-23-08-2017), now the question is which images are affected. @Igor I would recommend removing new u-boot packages from the repository for all sunxi devices that have eMMC. Or simply for all sunxi devices since I'm not sure if other old (something like pre-5.30) images will be affected. 1
guidol Posted January 30, 2018 Posted January 30, 2018 40 minutes ago, IgorS said: But this update was ok on OPi one. OPi One hasnt a eMMC device ___ ____ _ ___ / _ \ _ __ __ _ _ __ __ _ ___ | _ \(_) / _ \ _ __ ___ | | | | '__/ _` | '_ \ / _` |/ _ \ | |_) | | | | | | '_ \ / _ \ | |_| | | | (_| | | | | (_| | __/ | __/| | | |_| | | | | __/ \___/|_| \__,_|_| |_|\__, |\___| |_| |_| \___/|_| |_|\___| |___/ Welcome to ARMBIAN 5.38 stable Ubuntu 16.04.3 LTS 3.4.113-sun8i Linux pihole 3.4.113-sun8i #18 SMP PREEMPT Wed Jan 24 22:10:49 CET 2018 armv7l armv7l armv7l GNU/Linux root@pihole:~# ls /dev/mmc* /dev/mmcblk0 /dev/mmcblk0p1
earth08 Posted January 30, 2018 Posted January 30, 2018 Will it be any way to get our device working without reinstalling armbian?Please guideSent from my AO5510 using Tapatalk
IgorS Posted January 30, 2018 Posted January 30, 2018 Because I needed instant solution, I switched sytem to mmc and data volume to emmc
earth08 Posted January 30, 2018 Posted January 30, 2018 Because I needed instant solution, I switched sytem to mmc and data volume to emmcThat's correct in your case because u have backup,What if we don't have backup and want our system back onlineSent from my AO5510 using Tapatalk
IgorS Posted January 30, 2018 Posted January 30, 2018 4 minutes ago, earth08 said: That's correct in your case because u have backup, What if we don't have backup and want our system back online Sent from my AO5510 using Tapatalk Well, I think you can do following: Get mmc card Put fresh armbian on it Boot from it Make tar of /mmcblk2p1 (somewhere on network, I use sshfs for this) Shutdown Get mmc on pc an delete everything on it, then utar content of mmcblk2p1 on it. It should work (worked for me) Rgds
IgorS Posted January 30, 2018 Posted January 30, 2018 Just now, IgorS said: Well, I think you can do following: Get mmc card Put fresh armbian on it Boot from it Make tar of /mmcblk2p1 (somewhere on network, I use sshfs for this) Shutdown Get mmc on pc an delete everything on it, then utar content of mmcblk2p1 on it. It should work (worked for me) Rgds I just needed to adjust UUIDS in fstab
earth08 Posted January 30, 2018 Posted January 30, 2018 Well, I think you can do following: Get mmc card Put fresh armbian on it Boot from it Make tar of /mmcblk2p1 (somewhere on network, I use sshfs for this) Shutdown Get mmc on pc an delete everything on it, then utar content of mmcblk2p1 on it. It should work (worked for me) Rgds Dear,I don't get when u say make tar of.Can u please explain?Thanks in adv.Sent from my AO5510 using Tapatalk
IgorS Posted January 30, 2018 Posted January 30, 2018 When you boot in 'fresh' armbian from mmc, your old system is still on emmc, just need way to get it out. Easiest way is to make tar archive from it, maybe on usb pendrive. Insert pendrive, let say it is /dev/sda (check with lsblk) Create mountpoints: mkdir /mnt/src mkdir /mnt/dest Mount pendrive: mount /dev/sda /mnt/dest Mount emmc partition: mount /dev/mmcblk2p1 /mnt/src cd /mnt/dest tar -cvzf my_archive_name.tar.gz -C /mnt/src . (Note dot at the end, is important) when finished cd / umount /mnt/src umount /mnt/dest poweroff On your pendrive is now content of the emmc Then get both to pc and erase all on mmc untar archive from pendrive to mmc Bring to Opi and it should work
IgorS Posted January 30, 2018 Posted January 30, 2018 1 minute ago, IgorS said: When you boot in 'fresh' armbian from mmc, your old system is still on emmc, just need way to get it out. Easiest way is to make tar archive from it, maybe on usb pendrive. Insert pendrive, let say it is /dev/sda (check with lsblk) Create mountpoints: mkdir /mnt/src mkdir /mnt/dest Mount pendrive: mount /dev/sda /mnt/dest Mount emmc partition: mount /dev/mmcblk2p1 /mnt/src cd /mnt/dest tar -cvzf my_archive_name.tar.gz -C /mnt/src . (Note dot at the end, is important) when finished cd / umount /mnt/src umount /mnt/dest poweroff On your pendrive is now content of the emmc Then get both to pc and erase all on mmc untar archive from pendrive to mmc Bring to Opi and it should work All commands as root, of course
earth08 Posted January 30, 2018 Posted January 30, 2018 Dear,Thanks for explaining,I will do that now,Would it be possible to transfer same from mmc to emmc when fix is available?Sent from my AO5510 using Tapatalk
IgorS Posted January 30, 2018 Posted January 30, 2018 2 minutes ago, earth08 said: Dear, Thanks for explaining, I will do that now, Would it be possible to transfer same from mmc to emmc when fix is available? Sent from my AO5510 using Tapatalk Nope, bloody new U-Boot wan't boot from emmc. Until solution, we are trapped on mmc
Igor Posted January 30, 2018 Posted January 30, 2018 2 hours ago, zador.blood.stained said: I would recommend removing new u-boot packages from the repository for all sunxi devices that have eMMC. Or simply for all sunxi devices since I'm not sure if other old (something like pre-5.30) images will be affected. 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.
IgorS Posted January 30, 2018 Posted January 30, 2018 3 minutes ago, IgorS said: Nope, bloody new U-Boot wan't boot from emmc. Until solution, we are trapped on mmc Sorry, I missunderstood you. Yes, when fix comes, will be possible through armbian-config install to emmc.
Recommended Posts