GilGonGan

Members
  • Content Count

    26
  • Joined

  • Last visited

Posts posted by GilGonGan

  1. 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.

     


     

  2. 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.

     

     

  3. 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)
     

     

     

  4. 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

  5. On 6/27/2019 at 8:01 PM, Igor said:


    Nothing has been moved or changed in this regard. Armbian repository hasn't changed since it was established. We are just adding to it.

    If Debian or Ubuntu made some changes at their infrastructure, that is out of our power. Debian Jessie is EOL and there is nothing we can do about. Use Debian Stretch (soon Buster) based images.

    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 

  6. 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?

  7. 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?

  8. 6 hours ago, Igor said:


    I am only 100% sure that its not a problem we could recognise as our fault. IMHO there are several hundredths of thousandth installs on this board and in that case forum would be over-flooded with this problem.

     

    Read this https://docs.armbian.com/User-Guide_Getting-Started/#how-to-prepare-a-sd-card and behave accordingly and deploy your install to production when you are 100% sure things are working  well ...

     

    Perhaps a board is just faulty. You have another one?

     

    Moving to SD card and power supply section.

     

    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.

     

  9. 13 hours ago, Igor said:


    Then your card is very very low quality in a combination of a very bad treatment. Are you perhaps serving torrents or other very dangerous IO operations. Most SD cards very not designed for this and Armbian has nothing to do with this. We have implemented measures that helps with SD wear out but hardware limitations can't be changed. Get an SSD or mechanical drive in case you have some strange use case ...

     

     

    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!

  10. 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?

  11. 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)

     

  12. 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!

     

  13. 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.