Rockpro 64 cannot upgrade

    • OMV 4.x
    • Rockpro 64 cannot upgrade

      I am getting
      The following packages have unmet dependencies:

      Unable to correct problems, you have held broken packages.
      Code included not sure how to fix it?

      Source Code

      1. | '__/ _ \ / __| |/ / '_ \| '__/ _ \| '_ \| || |_
      2. | | | (_) | (__| <| |_) | | | (_) | (_) |__ _|
      3. |_| \___/ \___|_|\_\ .__/|_| \___/ \___/ |_|
      4. |_|
      5. Linux rockpro64 4.4.167-1138-rockchip-ayufan-geff8a74c8db9 #1 SMP Wed Mar 6 12:51:51 UTC 2019 aarch64
      6. The programs included with the Debian GNU/Linux system are free software;
      7. the exact distribution terms for each program are described in the
      8. individual files in /usr/share/doc/*/copyright.
      9. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
      10. permitted by applicable law.
      11. Last login: Mon Mar 25 08:10:03 2019 from 192.168.2.101
      12. root@rockpro64:~# sudo apt-get update -y
      13. Get:1 file:/var/cache/openmediavault/archives InRelease
      14. Ign:1 file:/var/cache/openmediavault/archives InRelease
      15. Get:2 file:/var/cache/openmediavault/archives Release
      16. Ign:2 file:/var/cache/openmediavault/archives Release
      17. Get:3 file:/var/cache/openmediavault/archives Packages
      18. Ign:3 file:/var/cache/openmediavault/archives Packages
      19. Get:4 file:/var/cache/openmediavault/archives Translation-en
      20. Ign:4 file:/var/cache/openmediavault/archives Translation-en
      21. Get:3 file:/var/cache/openmediavault/archives Packages
      22. Ign:3 file:/var/cache/openmediavault/archives Packages
      23. Get:4 file:/var/cache/openmediavault/archives Translation-en
      24. Ign:4 file:/var/cache/openmediavault/archives Translation-en
      25. Get:3 file:/var/cache/openmediavault/archives Packages
      26. Ign:3 file:/var/cache/openmediavault/archives Packages
      27. Get:4 file:/var/cache/openmediavault/archives Translation-en
      28. Ign:4 file:/var/cache/openmediavault/archives Translation-en
      29. Get:3 file:/var/cache/openmediavault/archives Packages
      30. Ign:3 file:/var/cache/openmediavault/archives Packages
      31. Get:4 file:/var/cache/openmediavault/archives Translation-en
      32. Ign:4 file:/var/cache/openmediavault/archives Translation-en
      33. Get:3 file:/var/cache/openmediavault/archives Packages
      34. Ign:3 file:/var/cache/openmediavault/archives Packages
      35. Get:4 file:/var/cache/openmediavault/archives Translation-en
      36. Ign:4 file:/var/cache/openmediavault/archives Translation-en
      37. Get:3 file:/var/cache/openmediavault/archives Packages
      38. Get:4 file:/var/cache/openmediavault/archives Translation-en
      39. Ign:4 file:/var/cache/openmediavault/archives Translation-en
      40. Hit:5 http://security.debian.org stretch/updates InRelease
      41. Hit:6 http://ppa.launchpad.net/ayufan/rock64-ppa/ubuntu xenial InRelease
      42. Hit:7 http://apt.syncthing.net syncthing InRelease
      43. Hit:9 https://openmediavault.github.io/packages arrakis InRelease
      44. Ign:10 https://dl.bintray.com/openmediavault-plugin-developers/arrakis stretch InRelease
      45. Hit:11 https://download.docker.com/linux/debian stretch InRelease
      46. Ign:12 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-sync stretch InRelease
      47. Hit:13 http://packages.openmediavault.org/public arrakis InRelease
      48. Ign:14 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-docker stretch InRelease
      49. Hit:8 http://cdn-fastly.deb.debian.org/debian stretch-backports InRelease
      50. Get:15 https://dl.bintray.com/openmediavault-plugin-developers/arrakis stretch Release [4389 B]
      51. Hit:15 https://dl.bintray.com/openmediavault-plugin-developers/arrakis stretch Release
      52. Hit:16 http://packages.openmediavault.org/public arrakis-proposed InRelease
      53. Get:17 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-sync stretch Release [3540 B]
      54. Get:18 http://deb.ayufan.eu/orgs/ayufan-rock64/pre-releases InRelease [1339 B]
      55. Hit:17 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-sync stretch Release
      56. Get:19 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-docker stretch Release [3540 B]
      57. Hit:19 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-docker stretch Release
      58. Ign:23 http://cdn-fastly.deb.debian.org/debian stretch InRelease
      59. Hit:24 http://cdn-fastly.deb.debian.org/debian stretch-updates InRelease
      60. Hit:25 http://cdn-fastly.deb.debian.org/debian stretch Release
      61. Fetched 1339 B in 23s (57 B/s)
      62. Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7f973dcb70>
      63. Traceback (most recent call last):
      64. File "/usr/lib/python3.5/weakref.py", line 117, in remove
      65. TypeError: 'NoneType' object is not callable
      66. Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7f973dcb70>
      67. Traceback (most recent call last):
      68. File "/usr/lib/python3.5/weakref.py", line 117, in remove
      69. TypeError: 'NoneType' object is not callable
      70. Reading package lists... Done
      71. root@rockpro64:~# sudo apt-get install linux-rock64 -y
      72. Reading package lists... Done
      73. Building dependency tree
      74. Reading state information... Done
      75. Some packages could not be installed. This may mean that you have
      76. requested an impossible situation or if you are using the unstable
      77. distribution that some required packages have not yet been created
      78. or been moved out of Incoming.
      79. The following information may help to resolve the situation:
      80. The following packages have unmet dependencies:
      81. linux-rock64 : Depends: board-package-rock64-0.8-98 but it is not installable
      82. Depends: u-boot-rockchip-rock64-2017.09-rockchip-ayufan-1045-g9922d32c04 but it is not installable
      83. Depends: linux-image-4.4.167-1161-rockchip-ayufan-g6f1664023387 but it is not installable
      84. Depends: linux-headers-4.4.167-1161-rockchip-ayufan-g6f1664023387 but it is not installable
      85. E: Unable to correct problems, you have held broken packages.
      86. root@rockpro64:~#
      87. root@rockpro64:~#
      88. root@rockpro64:~#
      89. root@rockpro64:~# sudo apt-get install linux-rockpro64 -y
      90. Reading package lists... Done
      91. Building dependency tree
      92. Reading state information... Done
      93. Some packages could not be installed. This may mean that you have
      94. requested an impossible situation or if you are using the unstable
      95. distribution that some required packages have not yet been created
      96. or been moved out of Incoming.
      97. The following information may help to resolve the situation:
      98. The following packages have unmet dependencies:
      99. linux-rockpro64 : Depends: board-package-rockpro64-0.8-98 but it is not installable
      100. Depends: u-boot-rockchip-rockpro64-2017.09-rockchip-ayufan-1045-g9922d32c04 but it is not installable
      101. Depends: linux-image-4.4.167-1161-rockchip-ayufan-g6f1664023387 but it is not installable
      102. Depends: linux-headers-4.4.167-1161-rockchip-ayufan-g6f1664023387 but it is not installable
      103. E: Unable to correct problems, you have held broken packages.
      Display All
    • Again: updating OMV version on Rockpro64

      There is really no reason to copy&paste random stuff from the Internet. If you run a RockPro64 it makes no sense at all to execute sudo apt-get install linux-rock64 -y as you did (this is for Rock64 and as such incompatible). Just use OMV's UI if you're not familiar with the command line. And most probably start again from scratch, this time using latest release version and not trying to ruin the installation by executing weird stuff you found somewhere on the net.
    • I'm having a similar issue. My system worked fine until I tried to install docker and then it went south. What I have installed still works ok, I just cannot complete anything that requires an update. It keeps crapping out trying to remove docker-ce. Eventually I just have to hit revert to get the yellow message block to go away.

      logs follow:

      =================================================================
      HISTORY LOG
      Start-Date: 2019-03-25 12:11:34
      Commandline: apt-get --yes --allow-downgrades --allow-change-held-packages --fix-missing --allow-unauthenticated --reinstall install openmediavault-omvextrasorg
      Install: openmediavault-omvextrasorg:armhf (4.1.15)
      Remove: docker-ce:armhf (5:18.09.3~3-0~debian-stretch)
      Error: Sub-process /usr/bin/dpkg returned an error code (1)
      End-Date: 2019-03-25 12:11:38


      =================================================================
      =================================================================


      TERM LOG
      Log started: 2019-03-25 12:11:34
      (Reading database ...
      (Reading database ... 5%
      (Reading database ... 10%
      and so on
      (Reading database ... 95%
      (Reading database ... 100%
      (Reading database ... 72904 files and directories currently installed.)
      Removing docker-ce (5:18.09.3~3-0~debian-stretch) ...
      Unrecognized character \xE8; marked by <-- HERE after zP<-- HERE near column 3 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Cwd.pm line 1.
      Compilation failed in require at /usr/share/perl/5.24/File/Path.pm line 6.
      BEGIN failed--compilation aborted at /usr/share/perl/5.24/File/Path.pm line 6.
      Compilation failed in require at /usr/bin/deb-systemd-helper line 85.
      BEGIN failed--compilation aborted at /usr/bin/deb-systemd-helper line 85.
      dpkg: error processing package docker-ce (--remove):
      subprocess installed post-removal script returned error exit status 255
      Errors were encountered while processing:
      docker-ce
      Log ended: 2019-03-25 12:11:38

      ==========================================================

      any thoughts?

      Kevin
      I'm on Dialup !!! ;(
    • I'm having a similar issue. My system worked fine until I tried to install docker and then it went south. What I have installed still works ok, I just cannot complete anything that requires an update. It keeps crapping out trying to remove docker-ce. Eventually I just have to hit revert to get the yellow message block to go away.

      logs follow:

      =================================================================
      HISTORY LOG
      Start-Date: 2019-03-25 12:11:34
      Commandline: apt-get --yes --allow-downgrades --allow-change-held-packages --fix-missing --allow-unauthenticated --reinstall install openmediavault-omvextrasorg
      Install: openmediavault-omvextrasorg:armhf (4.1.15)
      Remove: docker-ce:armhf (5:18.09.3~3-0~debian-stretch)
      Error: Sub-process /usr/bin/dpkg returned an error code (1)
      End-Date: 2019-03-25 12:11:38


      =================================================================
      =================================================================


      TERM LOG
      Log started: 2019-03-25 12:11:34
      (Reading database ...
      (Reading database ... 5%
      (Reading database ... 10%
      and so on
      (Reading database ... 95%
      (Reading database ... 100%
      (Reading database ... 72904 files and directories currently installed.)
      Removing docker-ce (5:18.09.3~3-0~debian-stretch) ...
      Unrecognized character \xE8; marked by <-- HERE after zP<-- HERE near column 3 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Cwd.pm line 1.
      Compilation failed in require at /usr/share/perl/5.24/File/Path.pm line 6.
      BEGIN failed--compilation aborted at /usr/share/perl/5.24/File/Path.pm line 6.
      Compilation failed in require at /usr/bin/deb-systemd-helper line 85.
      BEGIN failed--compilation aborted at /usr/bin/deb-systemd-helper line 85.
      dpkg: error processing package docker-ce (--remove):
      subprocess installed post-removal script returned error exit status 255
      Errors were encountered while processing:
      docker-ce
      Log ended: 2019-03-25 12:11:38

      ==========================================================

      any thoughts?

      Kevin
      I'm on Dialup !!! ;(
    • tkaiser wrote:

      Again: updating OMV version on Rockpro64

      There is really no reason to copy&paste random stuff from the Internet. If you run a RockPro64 it makes no sense at all to execute sudo apt-get install linux-rock64 -y as you did (this is for Rock64 and as such incompatible). Just use OMV's UI if you're not familiar with the command line. And most probably start again from scratch, this time using latest release version and not trying to ruin the installation by executing weird stuff you found somewhere on the net.
      I am just following the wiki from pine64 wiki.pine64.org/index.php/ROCK…_eMMC_Boot.5D_.5B0.7.9.5D
      1.7 link to the prerelease github.com/ayufan-rock64/linux-build/releases/

      So what is the exact link for OMV if it not ayufan version since @ sourceforge.net/projects/openm…ngle%20Board%20Computers/ there is none?

      Source Code

      1. root@rockpro64:~# sudo apt-get install linux-rockpro64 -y
      2. Reading package lists... Done
      3. Building dependency tree
      4. Reading state information... Done
      5. Some packages could not be installed. This may mean that you have
      6. requested an impossible situation or if you are using the unstable
      7. distribution that some required packages have not yet been created
      8. or been moved out of Incoming.
      9. The following information may help to resolve the situation:
      10. The following packages have unmet dependencies:
      11. linux-rockpro64 : Depends: board-package-rockpro64-0.8-98 but it is not install able
      12. Depends: u-boot-rockchip-rockpro64-2017.09-rockchip-ayufan-10 45-g9922d32c04 but it is not installable
      13. Depends: linux-image-4.4.167-1161-rockchip-ayufan-g6f16640233 87 but it is not installable
      14. Depends: linux-headers-4.4.167-1161-rockchip-ayufan-g6f166402 3387 but it is not installable
      15. E: Unable to correct problems, you have held broken packages.
      16. root@rockpro64:~#
      Display All

      The post was edited 1 time, last by Nefertiti ().

    • An apparently got the last pre-release version 7 now I remember the stable version I started with was very sluggish this why I went to the pre release
      anyway yes I nid the 3 commands to upgrade even the rock64 onesudo apt-get update -y
      sudo apt-get install linux-rock64 -y
      sudo apt-get install linux-rockpro64 -y

      I just did it and now I am @
      pre -release 8.)0rc4 the problem why I got the error to upgrade I did not edit properly the nano /etc/apt/sources.list.d/ayufan-rock64.list
      and it does not matter to me to be on a pre-release since I like to live dangerously.
      Display Spoiler

      /sdio-hciattach.service.
      Creating new extlinux.conf...
      Installing new extlinux.conf...
      Processing triggers for rsyslog (8.24.0-1) ...
      Setting up linux-rockpro64 (0.8.0rc4) ...
      root@rockpro64:~#


      Source Code

      1. root@rockpro64:~# sudo apt-get install linux-rockpro64 -y
      2. Reading package lists... Done
      3. Building dependency tree
      4. Reading state information... Done
      5. linux-rockpro64 is already the newest version (0.7.14).
      6. 0 upgraded, 0 newly installed, 0 to remove and 62 not upgraded.

      The post was edited 3 times, last by Nefertiti ().

    • github.com/ayufan-rock64/linux-build/releases/tag/0.7.9


      these are the stable ones for the rock64 and rockpro64


      I FOLLOWED THE RECOMMENDATIONS AND USED THE ARMHF VERSION
      I just decompressed to the iso... and flashed to the emmc chip using balenaEtcher
      worked like a champ, booted right up... ready to rocknroll.
      I did purchase the emmc adapter to usb from rock/pine64 and the emmc card came from them also.



      stretch-openmediavault-rock64-0.7.9-1067-arm64.img.xz 290 MB


      stretch-openmediavault-rock64-0.7.9-1067-armhf.img.xz 305 MB


      stretch-openmediavault-rockpro64-0.7.9-1067-arm64.img.xz 291 MB


      STRETCH-OPENMEDIAVAULT-ROCKPRO64-0.7.9-1067-ARMHF.IMG.XZ 303 MB
      I'm on Dialup !!! ;(
    • doogleaelf wrote:

      My bad, these are the latest ;)

      github.com/ayufan-rock64/linux-build/releases/tag/0.7.14


      stretch-openmediavault-rock64-0.7.14-1081-arm64.img.xz
      298 MB
      stretch-openmediavault-rock64-0.7.14-1081-armhf.img.xz
      310 MB
      stretch-openmediavault-rockpro64-0.7.14-1081-arm64.img.xz
      299 MB
      stretch-openmediavault-rockpro64-0.7.14-1081-armhf.img.xz
      311 MB
      Not really since it is indicated as pre - release and be aware tkaiser wont be happy!
      The only one I know it is this one but it did not work for me github.com/ayufan-rock64/linux-build/releases/tag/0.7.9
      Images
      • 2019-03-25_210622.jpg

        25.96 kB, 657×169, viewed 10 times
    • Nefertiti wrote:

      it does not matter to me to be on a pre-release since I like to live dangerously
      Good to know. So while being the opposite of a Linux expert you choose to use software versions that are tagged as for 'experts and developers only' by the creator. These pre-releases are for people trying to help by identifying and nailing down bugs, not for people who barely know what they're doing -- especially on the command line.

      Dealing with your 'reports' of stuff failing or 'I remember the stable version I started with was very sluggish this why I went to the pre release' is just a waste of time and not related to OMV at all. Good luck with this attempt!

      For anyone else reading this: please don't behave silly and fiddle around on the command line if you don't know what you're doing. Use OMV's UI and there the update tab. If there's no update shown, there's nothing to update.

      If you're a RockPro64 user only use ayufan's versions tagged as RELEASE (no pre-release if you're not a developer or experienced tester willing to provide useful feedback to ayufan) and if in doubt ask at the Pine64 forum for device specific stuff which might then end up like this anyway: forum.pine64.org/showthread.php?tid=7020
    • Sorry your right about that. As far as the other stuff goes... I wish these so called experts would come down off the mountain once in a blue moon. I have used the command line before... why... because the omv scripts simply didn't work. Right out of the gate with the rock64, it would not set the ip address properly. I'm not blaming anyone... I don't have time or the patience for that... I reserve that for all the liberal dump arse democrats ;). I read forum subject after forum subject... not barking at anyone and figured it out. My intention was not to learn everything about linux, it was to watch videos and tutorials and such. But alas such is the life of linux.... you are expected to be an expert and if not.. too bad for you.

      I must say though that I really love the little rock64. That thing just hums along. I use two WD network drives, I guess you call them personal NAS. Use remote mount and don't even bother using smb at all. Works like a champ. I have about 5000 videos, 10k songs, run plex and sit on my 30.00 cheap arse RCA tablet and chromecast to my tv. I don't have cable. Thats what live youtube is for ;)
      I'm on Dialup !!! ;(
    • doogleaelf wrote:

      Right out of the gate with the rock64, it would not set the ip address properly
      And I still have not the slightest idea why people are doing this. There is no need to fiddle around with 'static IP addresses' configured the manual way. DHCP works, DNS works. Since decades.

      If you power on your OMV box it gets an address by the local DHCP server and usually is accessible by its name. Does one of the following work for you from another machine on the network:

      Source Code

      1. ping rock64
      2. ping rock64.local
    • I use static because I set my DHCP on the router to zero clients which makes it effectively static. I then limit access using MAC addys. Very easy to setup on the router. It's all on one line per device. I don't need to remember silly host names. I can just use ip's. Sounds bass ackwards but guess what... I don't have to pray that winblows doesn't have issues with host names, I just use the ip. I do alot of crazy stuff on my host pc's. I use NTLite alot and am always testing how lean I can get winblows. I use virtualbox alot and vagrant and don't wish to poke around looking for what IP it is... I already know. Sure I could reserve an ip... why bother... one less thing to worry about.
      I'm on Dialup !!! ;(