Don Pedro Posted July 30, 2016 Posted July 30, 2016 Hi there Please confirm if other have seen this as well, I can create a small bug report if this is indeed a mistake in the upgrade scripts... Yes, I can confirm, I observed the very same behavior! I had the problem of a bricked Cubie before, see my posts above, and I was able to reanimate it with Igor's help. At that time I just realized that something had gone wrong during the update, the uImage was missing, despite the fact that there's plenty of room on the NAND (I'm even using a 16G Cubie). Now, couple of months later I did an update again that came with a kernel (and presumably with some firmware) update. And bang, this also failed like the time before: Preparing to unpack .../linux-jessie-root-cubietruck_5.16_armhf.deb ... mv: cannot move ‘/boot/bin’ to ‘/boot/bin.old/bin’: Directory not empty Unpacking linux-jessie-root-cubietruck (5.16) over (5.11) ... dpkg: error processing archive /var/cache/apt/archives/linux-jessie-root-cubietruck_5.16_armhf.deb (--unpack): unable to make backup link of `./boot/bin/bananapi.bin' before installing new version: Operation not permitted Processing triggers for systemd (215-17+deb8u4) ... Processing triggers for man-db (2.7.0.2-5) ... Errors were encountered while processing: /var/cache/apt/archives/linux-jessie-root-cubietruck_5.16_armhf.deb E: Sub-process /usr/bin/dpkg returned an error code (1) somebody@cubietruck:~$ Take note of the line "mv: cannot move ‘/boot/bin’ to ‘/boot/bin.old/bin’: Directory not empty" At that time I was already clairaudient due to previous experiences. And, yes, a short glance at /boot revealed me the the very same situation like on your cubie, an existent, incomplete /boot/bin.old, a wrong /boot/bin.old/bin inside and a missing uImage - No chance to survive a reboot. And I did what you did, rename /boot/bin.old and relaunch the update, this time successfully: Setting up linux-firmware-image-sun7i (5.16) ... Setting up linux-headers-sun7i (5.16) ... Compiling headers - please wait ... Setting up linux-image-sun7i (5.16) ... Image Name: Linux kernel Created: Sat Jul 30 15:02:29 2016 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 5605944 Bytes = 5474.55 kB = 5.35 MB Load Address: 40008000 Entry Point: 40008000 Now I had a Kernel uImage again and after a final reboot the Cubie came up back without a hitch: ____ _ _ _ _ / ___| _| |__ (_) ___| |_ _ __ _ _ ___| | __ | | | | | | '_ \| |/ _ \ __| '__| | | |/ __| |/ / | |__| |_| | |_) | | __/ |_| | | |_| | (__| < \____\__,_|_.__/|_|\___|\__|_| \__,_|\___|_|\_\ Welcome to ARMBIAN Debian GNU/Linux 8 (jessie) 3.4.112-sun7i System load: 4.85 Up time: 1 min Memory usage: 5 % of 1998Mb IP: 192.168.xxx.xxx 192.168.xxx.xxx CPU temp: 39°C HDD temp: 34°C Usage of /: 24% of 15G storage/: 50% of 3.6T So, yes, could you please create a small bug report. This is clearly reproducible and should be easily fixable.
mxpycoder Posted September 5, 2016 Posted September 5, 2016 Sorry for the late reply. I didn't get around to reporting this issue. I did so just now and a fix was created within a few minutes: See: https://github.com/igorpecovnik/lib/issues/460
Recommended Posts