Igor Posted January 31, 2019 Posted January 31, 2019 25 minutes ago, thexman said: Thanks for the fix Most thanks got to @ning for looking deeply into the problem making a patch. I just did the maintenance work
thexman Posted January 31, 2019 Posted January 31, 2019 6 minutes ago, Igor said: Most thanks got to @ning for looking deeply into the problem making a patch. I just did the maintenance work So then also thanks @ning 😋, didn't check what was part of the actual fix!
Sergio Posted February 1, 2019 Posted February 1, 2019 22 hours ago, Igor said: Patch is applied and it seems to work, updates pushed up:https://github.com/armbian/documentation/commit/417821896fedd9623bfc6d7dac13cc5392729c80 https://github.com/armbian/upload/commit/3ea43843df0ccfa7e749b41cffa27f38c3ba53e8 ... but it seems not all problems went away. I am experiencing network troubles. Lan cable was not connected to the switch @Igor , can I switch to the nightly build and do the update by apt update&upgrade, or is it necessary to do it manually in a different way?
Igor Posted February 1, 2019 Posted February 1, 2019 Changes were applied also to the stable repository. No need to switch anywhere. I guess all mirrors have also been updated by now. 3
ning Posted February 11, 2019 Author Posted February 11, 2019 please just unhold systemd and do apt update && apt upgrade, everything works fine, I have tried.
markjeronimus Posted October 1, 2019 Posted October 1, 2019 I ran updates, it indeed fixed by sshd at boot, but I don't understand how it broke in the first place. It was always working and without provocation it stopped working (I didn't update). If this happened on my OPi Zero (has no display outputs) instead of my OPi One, it would have bricked. And of course the update broke other stuff and my 800x480 display stopped working. Time to inspect the fex-bin files. [edit] somehow scripts.bin got completely replaced by one that looks like its for another board. One thing I noticed is that instead of the OPi One's 19 GPIOs it lists 88 GPIOs.
markjeronimus Posted October 23, 2019 Posted October 23, 2019 Had another encounter with the ssh problem after burning a year-old image that worked for 100% sure. This is a 'cleaned' image, with bash history and logs purged before ripping. I thought of comparing the 'good' & 'bad' SD card. Found *unattended* upgrade logs that didn't exist before, which happened around 6am when I was asleep. Apparently systemd upgraded and broke the stuff: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811580 (search Failed to validate path /var/run/sshd: Bad file descriptor)
Recommended Posts