Aux

Thanks @martinayotte you not relay read the whole Thread You have also read what is under the video written?

As announced, because I can not create a log I have made a short video And I still notice something. In the folder /boot is a subfolder /boot/bin This folder is called after the update /boot/bin.old is the order so?

Exactly, I have to buy one that I will not need the next 10 years ... ;-)

To your information, I had 2 other SD cards tested, 2 different power supplies, different USB cables, now I am to get 2 raspberrypi or how?

A good idea, but for serial debug session has no tools I'll take a short video for youtube

Then please tell me how I should make it if the system does not find the system partition where are the logs stored?

Stimme ich vollkommen zu ! @tkaiser Oh come the junk with the SD card and power supply it is certainly not !!!!! And that does not solve the problem. It ran for over a year and now the cable or SD card is defective and in two cases at the same time? This is a no go

But I have already tried other SD card, now will still apply another power supply, when it does not work then I probably switch to other disto. Since there is apparently no solution for it, much more - I am apparently not the only one @ Wolf2000 wrote me by e-mail that he exactly the same problem has. Except for that, I will now not open a new thread to just have to re-write and write the same ...

Thank you for your answer @tkaiser! But if I update all packages have the same problem, what now? Have the update at least 5 times in various combinations tasted, since is what is lazy. I have never had such problems with ARMBIAN before.

I wanted to know which package makes the system stupid and did the installation step by step look at the bottom Install - sunxi-tools (1.4.2-1~armbian5.31+1) reboot status = all works Install - linux-jessie-root-next-bananapi 5.31 reboot status = all works Install - armbian-tools-jessie 5.30 reboot status = all works Install - linux-dtb-next-sunxi 5.31 reboot status = system broken - This update caused the problems!!!

Sorry guys but there is something completely wrong. Backup image recovered, update process from 5.25 to 5.30/31 started, reboot same errors. This time the complete update with "linux-u-boot-next-bananapi_5.31_armhf.deb". Dpkg.log - https://pastebin.com/SV22r1R3 There are no other usable logs or have I overlooked what? On the system runs openmediavault, is it possible that has an influence? before update cat /etc/*-release # PLEASE DO NOT EDIT THIS FILE BOARD=bananapi BOARD_NAME="Banana Pi" VERSION=5.25 LINUXFAMILY=sunxi BRANCH=next ARCH=arm IMAGE_TYPE=stable PRETTY_NAME="Debian GNU/Linux 8 (jessie)" NAME="Debian GNU/Linux" VERSION_ID="8" VERSION="8 (jessie)" ID=debian HOME_URL="http://www.debian.org/" SUPPORT_URL="http://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/

I have changed it but no hope for improvement. Now comes "/dev/mmcblk0p1 not exist" ... I know I have backup on sd card written and the update process from 5.25 to 5.30 again but without "linux-u-boot-next-bananapi_5.30_armhf.deb" because it was locked in the repository. Now I have the above error ....

Apparently, the SD card is no longer recognized after the update, what now?

I would like to describe more in detail. The update from Armbian 5.25 to 5.30 / 4.9.12-sunxi does not work. Using the u-boot-sunxi-with-spl.bin on / dev / mmcblk0 brings nothing. Have some pictures made, maybe this will help?

I think I have found the problem. The linux-u-boot-bananapi-next 5.30 was not installed. http://apt.armbian.com/ jessie/main linux-u-boot-bananapi-next armhf 5.30 404 Not Found

Well, thank you very much @Igor, will try again ;-)

I tried but had not worked, Had possibly flashed wrong drive mmcblk0p1 instead of mmcblk0 ??

Hi, its a my first post here :-) same issue with update from Armbian 5.25 to 5.30 bootloop on Banana Pi. Have now done backup back, Will now wait until the problem is solved...