GilGonGan

You know what, I did a reboot THEN the update, worked fine. Very happy with Armbian over all, considering how cheapo this hardware is. It's a print and DNS server now (!) great stuff. Thanks

Ok so it never recovered. I restored from .IMG file (long process) via DD and rebooted, she's back. What is the CORRECT way for me to apt update / apt upgrade, with docker installed? Do I pause / destroy containers? Type a different command?

I did an apt get update and upgrade on my OrangePi Zero and it seems to have just outright stopped near the end. Setting up libssl1.1:armhf (1.1.1d-0+deb10u2) ... Setting up armbian-config (5.98) ... Setting up libssl-dev:armhf (1.1.1d-0+deb10u2) ... Setting up containerd.io (1.2.10-3) ... Setting up sudo (1.8.27-1+deb10u1) ... Setting up armbian-firmware (5.98) ... Setting up docker-ce-cli (5:19.03.4~3-0~debian-buster) ... Setting up openssl (1.1.1d-0+deb10u2) ... Setting up docker-ce (5:19.03.4~3-0~debian-buster) ... It seems to have just stopped there, I'm leaving it for the time being - but I suspect I broke the system, right? I can restore from an SDCard image I think, I have a file somewhere.

I just want to thank everyone here for their hard work, while I don't understand most of what's going on, as a mostly Windows dude, I get the impression this is some really cool tuning for some really basic hardware, this whole zram compressed swapfile in ram is a way cool concept. I have a 512MB Pi Zero and it just works really really fine for basic stuff, thanks to hard work from folks like you all. (It's a shame I hear newer models run a lot hotter / worse?) lucky I have an older model.

This did end up working, is there a 'correct' CLI way to install docker though?

Thank you Igor - I googled some instructions which are perhaps out of date? I had no idea a simple menu based config was even built in! I'll have a play

OrangePiZero root@orangepizero:~# uname -r 4.19.59-sunxi root@orangepizero:~# cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 10 (buster)" NAME="Debian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" root@orangepizero:~# Only run sud apt get update / upgrade and then sudo apt install docker.io however it threw out this Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details. invoke-rc.d: initscript docker, action "start" failed. * docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Tue 2019-09-17 13:41:42 UTC; 65ms ago Docs: https://docs.docker.com Process: 9480 ExecStart=/usr/sbin/dockerd -H fd:// $DOCKER_OPTS (code=exited, status=1/FAILURE) Main PID: 9480 (code=exited, status=1/FAILURE) dpkg: error processing package docker.io (--configure): installed docker.io package post-installation script subprocess returned error exit status 1 Processing triggers for libc-bin (2.28-10) ... Processing triggers for systemd (241-7~deb10u1) ... Processing triggers for man-db (2.8.5-2) ... Errors were encountered while processing: docker.io E: Sub-process /usr/bin/dpkg returned an error code (1)

I understand linux is free and the work is appreciated, you have no idea, I wish I could contribute./ I'm in my 40's now, I've encountered linux in some form or another literally since the very late 90s with slackware. The issue here is that updating an operating system, using the CLI (which I'm ok with) fails, it simply shouldn't fail, PERIOD It should say as I said "jessie files are now in archive state, edit this file to fix' or "jessie files are now in archive, would you like latest version of jessie branch" - SOMETHING? Instead you've got at least 5 or 10 people across the web, inundating forums with "why the heck do I need to edit sources.list and what EXACTLY do I put there?" - from an end user perspective, arguably, linux is still showing incredibly poor end user design decisions over 20 years on. I don't expect a flashy animated box that says "fix all my problems" but the fact a simple update, won't work, because files were flagged as old is you know.. not great Anyhow - it is what it is, she's working ok now, and I appreciate the reply

Put yourself in the seat of a Linux newbie. Apt get update and upgrade were "broken" for reasons out of our control I didn't do an update for a year. The update server no longer hosted the files I needed for Jessie. I couldn't update Jessie to the latest patch level, period. Without editing files. Others had the same issue. Linux experienced people can try and defend this but from a usability standpoint, this is terrible. Needs a far better error message or an option "Jessie is dead, but would you like the last of the files for it?" Bad design. None the less it's fixed now

More often? I can do this I just want to avoid being so far behind, when I go to update, the repository has moved and I have to edit sources files ( a very unfriendly way of handling things, feels very 1999 linux like, I can't BELIEVE the way it works)

Thanks to all those on this forum, across multiple threads helping me. End of the day, sadly, the best solution was a wiped SDCard (fill 0s) test SDcard (h2testw, full) and re-flash to the latest stretch. 3'rd SDCard a charm, it's booted, I've updated aptupd/upg and installed pihole and it appears to be working fine. Let's hope she stays that way. One thing, in order to avoid this problem in the future, since the jessie library /repository was moved (??) shouidl I make a habit of doing an apt-update / upgrade say once every 2 or 3 months to stay on top of things?

Much like others, sadly my solution ended up being a fully wiped, tested SD card and re-install. Not fun overall.

Thanks to all those on this forum, across multiple threads helping me. End of the day, sadly, the best solution was a wiped SDCard (fill 0s) test SDcard (h2testw, full) and re-flash to the latest stretch. 3'rd SDCard a charm, it's booted, I've updated aptupd/upg and installed pihole and it appears to be working fine. Let's hope she stays that way. One thing, in order to avoid this problem in the future, since the jessie library /repository was moved (??) shouidl I make a habit of doing an apt-update / upgrade say once every 2 or 3 months to stay on top of things?

Thanks for your help, I was concerned because I know new models of Pi run very hot and have weirdo problems, I thought there was a slim chance there's a firmware update in Armbian which may have triggered something? (I know that sounds crazy, but isn't there Raspberry Pi firmware inside Raspbian?) Anyhow, I digress, I've tested a 3'rd SDcard in full and written it, I'll try it, if this fails, I suspect the Orange Pi is sadly toast ! Thanks for help, will update in a few days.

I'm not sure to be honest if it's the card. I tend to use H2TestW before using cards (!!!) which should ensure they're fine! Check out the log. https://forum.armbian.com/topic/10712-orangepi-killing-sd-card-or-device-dying-unsure-bash-usrbinsudo-inputoutput-error/?tab=comments#comment-81090 I mean heck that card was quite new, maybe just a fluke, I'm sending out another one, if that fails then I'm super confused!