GilGonGan

Members
  • Content Count

    17
  • Joined

  • Last visited

About GilGonGan

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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)
  2. 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?
  3. Much like others, sadly my solution ended up being a fully wiped, tested SD card and re-install. Not fun overall.
  4. 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?
  5. 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.
  6. 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!
  7. Looks like I put a faulty SDCard in there by pure accident or there are bigger problems at play. Does OrangePi have issues with Stretch more than Jessie? read issues or any file system design issues? Faster clock on the firmware for the SDCard reader? (shrug) I update to stretch, system kills a card in a week Send a replacement card, kills it in 30 minutes
  8. I just had an OrangePi of mine at a customer site, die on me. It just stopped responding to ping, so I made them a new MicroSD card and mailed it out. Now I think the Pi hates the Stretch release or something and fries SD cards? Check this out: https://pastebin.com/KaMk70vS Literally first login! only been up 15 minutes
  9. Hi all, Downloaded it from here: https://www.armbian.com/orange-pi-zero/ https://dl.armbian.com/orangepizero/archive/Armbian_5.83_Orangepizero_Debian_stretch_next_4.19.38.7z Wrote it to a 16GB MicroSD using rufus. . I'm going to be supporting this remotely (long story!!) but before mailing the SDCard to my tech at the other end, I noticed the partition is only 1GB in size. Is this normal? Will Armbian 'extract' or re-size the partition as part of the first install / boot process?
  10. Thanks for the reply. I had some progress but broke elsewhere. I think some major files may be damaged. https://forum.armbian.com/topic/10480-attempted-jessie-to-stretch-failed-likely-dead-on-reboot/ I may need something called busybox installed, which I do not have unfortunately.
  11. Did you ever solve this? I may have a similar issue, I've been googling for hours and just found your reply. https://forum.armbian.com/topic/10480-attempted-jessie-to-stretch-failed-likely-dead-on-reboot/
  12. Also this after running apt-get remove --purge network-manager update-initramfs: Generating /boot/initrd.img-3.4.113-sun8i E: busybox or busybox-static, version 1:1.22.0-17~ or later, is required but not installed update-initramfs: failed for /boot/initrd.img-3.4.113-sun8i with 1. dpkg: error processing package initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for systemd (232-25+deb9u11) ... Processing triggers for dbus (1.10.26-0+deb9u1) ... Errors were encountered while processing: initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1)
  13. One last reply: here's the full output of the 2 main large errors, sorry quite large: Job for NetworkManager.service failed because the control process exited with error code. See "systemctl status NetworkManager.service" and "journalctl -xe" for details. invoke-rc.d: initscript network-manager, action "start" failed. ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Sat 2019-05-25 15:40:43 AEST; 27ms ago Docs: man:NetworkManager(8) Process: 18510 ExecStart=/usr/sbin/NetworkManager --no-daemon (code=exited, status=226/NAMESPACE) Main PID: 18510 (code=exited, status=226/NAMESPACE) May 25 15:40:43 orangepizero systemd[1]: Failed to start Network Manager. May 25 15:40:43 orangepizero systemd[1]: NetworkManager.service: Unit entered failed state. May 25 15:40:43 orangepizero systemd[1]: NetworkManager.service: Failed with result 'exit-code'. dpkg: error processing package network-manager (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for initramfs-tools (0.130) ... update-initramfs: Generating /boot/initrd.img-3.4.113-sun8i E: busybox or busybox-static, version 1:1.22.0-17~ or later, is required but not installed update-initramfs: failed for /boot/initrd.img-3.4.113-sun8i with 1. dpkg: error processing package initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: network-manager initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) And this one from journal May 25 15:40:44 orangepizero systemd[18536]: NetworkManager.service: Failed at step NAMESPACE spawning /usr/sbin/NetworkManager: Bad file -- Subject: Process /usr/sbin/NetworkManager could not be executed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The process /usr/sbin/NetworkManager could not be executed and failed. -- -- The error number returned by this process is 9. May 25 15:40:44 orangepizero systemd[1]: NetworkManager.service: Main process exited, code=exited, status=226/NAMESPACE May 25 15:40:44 orangepizero systemd[1]: Failed to start Network Manager. -- Subject: Unit NetworkManager.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit NetworkManager.service has failed. -- -- The result is failed. May 25 15:40:44 orangepizero systemd[1]: NetworkManager.service: Unit entered failed state. May 25 15:40:44 orangepizero systemd[1]: NetworkManager.service: Failed with result 'exit-code'. May 25 15:40:44 orangepizero systemd[1]: NetworkManager.service: Service hold-off time over, scheduling restart. May 25 15:40:44 orangepizero systemd[1]: Stopped Network Manager. -- Subject: Unit NetworkManager.service has finished shutting down -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit NetworkManager.service has finished shutting down. May 25 15:40:44 orangepizero systemd[1]: NetworkManager.service: Start request repeated too quickly. May 25 15:40:44 orangepizero systemd[1]: Failed to start Network Manager. -- Subject: Unit NetworkManager.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit NetworkManager.service has failed. -- -- The result is failed. May 25 15:40:44 orangepizero systemd[1]: NetworkManager.service: Unit entered failed state. May 25 15:40:44 orangepizero systemd[1]: NetworkManager.service: Failed with result 'exit-code'. As much as I wish i was a lot smarter and had more time - I will not attempt "takeover.sh" which sounds like a super cool way of rescuing a hosed system. - Complicated and powerful but not something even close to my skillset, super cool though!
  14. Hello! I tried to update jessie dismally, here: https://forum.armbian.com/topic/9984-apt-get-update-pointing-to-404-not-found-ip-151101240204-80/?do=findComment&comment=79685 Since then, I have been attempting to update to strech, I feel like I got close, but it's failed and I strongly suspect, my next reboot will hose it. (I will not reboot it, linux is wondeful!!) I updated my sources.list file to have the following 4 values. deb http://httpredir.debian.org/debian stretch main contrib non-free deb http://httpredir.debian.org/debian stretch-updates main contrib non-free deb http://httpredir.debian.org/debian stretch-backports main contrib non-free deb http://security.debian.org/ stretch/updates main contrib non-free the apt-get update and apt-get upgrade (appear) to be working fine. apt-get dist-upgrade will spit out the following: Errors were encountered while processing: network-manager initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) Upon further investigation I have done the following tips in this post precisely http://forums.debian.net/viewtopic.php?p=122113#p122113 These have failed, it outright refuses to get network-manager on there. Job for NetworkManager.service failed because the control process exited with error code. See "systemctl status NetworkManager.service" and "journalctl -xe" for details. journalctl -xe will produce the following: May 25 15:33:28 orangepizero systemd[17220]: NetworkManager.service: Failed at step NAMESPACE spawning /usr/sbin/NetworkManager: Bad file descriptor -- Subject: Process /usr/sbin/NetworkManager could not be executed When I begin to google that information I start reaching even less google hits and possibly even a bug? https://www.google.com/search?rlz=1C1GCEA_enAU767AU767&ei=K9ToXI64A6LYz7sPvr2qwAE&q="NetworkManager.service"+"bad+file+descripor"&oq="NetworkManager.service"+"bad+file+descripor"&gs_l=psy-ab.3..33i160l2.9570.14812..14992...3.0..0.276.4626.0j13j10......0....1..gws-wiz.......0j0i22i30j33i21.bL0kzS4p6yg Finally, when I log in to the system remotely it even says : "ARMBIAN 5.73 stable Debian GNU/Linux 8 (jessie) 3.4.113-sun8i" "Kernel was updated, please reboot " However, I feel this is very unwise, until I can be certain that the update and upgrades and clean and autoremove and all the commands to maintain the system at least spit back results indicating success.