[OS] Debian Stretch

[Gburas]

yes i did it with the proper user(tried a lot of configuration) and it didn`t work (on win 7) with: ultraVNC, tightVNC, realVNC

[meveric]

yes i did it with the proper user(tried a lot of configuration) and it didn`t work (on win 7) with: ultraVNC, tightVNC, realVNC

Hmm, that's odd.. as I was using Windows 7 with UltraVNC yesterday as well.. but it's probably an older version of UltraVNC.. I'll try the other clients as well.
Have you setup a password for authentication?

[Gburas]

yes

[meveric]

The passwords for VNC clients is mostly limited to 8 characters only, if your password is longer than that, there's a good chance some client do not interpret your input correctly.
Also it's slightly complicated to setup password for Vino (was much better in earlier versions where there still was vino-preferences).

Code: Select all

gsettings set org.gnome.Vino authentication-methods "['vnc']"
gsettings set org.gnome.Vino vnc-password $(echo -n "password"|base64)

(as I said the password shouldn't be longer than 8 characters)

Edit:
Just tested Vino with my version of UltraVNC + Password.

Code: Select all

gsettings set org.gnome.Vino prompt-enabled false
gsettings set org.gnome.Vino require-encryption false
gsettings set org.gnome.Vino authentication-methods "['vnc']"
gsettings set org.gnome.Vino vnc-password $(echo -n "password"|base64)

and I could login with password.

Edit:
downloaded and installed RealVNC VNC-Viewer.... worked as well.
TightVNC tested as well and working.

[kubi]

Could someone please post the apt sources used for stretch?

I have the normal debian repositories working, but the mdrjr.org lines fail with some error. They were working maybe a month ago when I updated from jessie, but now all fails
///// Are these correct?
deb https://oph.mdrjr.net/meveric all xu3
deb https://oph.mdrjr.net/meveric all main testing
deb https://oph.mdrjr.net/meveric stretch main backports

///// The error message
root@odroid-jessie:~# apt update
Hit:1 http://security.debian.org stretch/updates InRelease
Ign:2 http://ftp.debian.org/debian stretch InRelease
Hit:3 http://ftp.debian.org/debian stretch-updates InRelease
Hit:4 http://ftp.debian.org/debian stretch-backports InRelease
Hit:5 http://ftp.debian.org/debian stretch Release
Reading package lists... Done
E: Method https has died unexpectedly!
E: Sub-process https received a segmentation fault.
E: Method /usr/lib/apt/methods/https did not start correctly
E: Failed to fetch https://oph.mdrjr.net/meveric/dists/all/InRelease
E: Some index files failed to download. They have been ignored, or old ones used instead.

[meveric]

The URLs are correct. Check that you have the correct time and date, as HTTPS will fail if your system thinks it's still 1970

[kubi]

The time and date is correct. The https method segfaults:
root@odroid-jessie:~# /usr/lib/apt/methods/https
Segmentation fault

It must be one of the libraries. Maybe something got messed up between the debian repo and yours somehow.
Now it is time to find out where all the libraries came from...

[meveric]

Well and there's the missing info.
You updated from Jessie to Stretch.
There is a lib that is from Deb-multimedia under Jessie that causes issues on Stretch and need to be replaced with the one from Stretch. Can you give me the output of

Code: Select all

 dpkg --list | grep dmo

I think it should be something like librtsp or something similar that needs to be corrected

[kubi]

Interesting...
I have
ii librtmp1:armhf 2:2.4~20150315.gita107cef9b-dmo1+deb8u2 armhf Toolkit for RTMP streams (shared library)
While in the debian repo:
librtmp1_2.4+20151223.gitfa8646d.1-1+b1_armhf.deb
This should be newer, but...
apt does not want to upgrade it. --> I've downloaded and force-installed with dpkg. It complains about that this is an actual downgrade. I think it is because of the + vs. ~ issue in the version.

And now, the https method works like charm

The interesting thing was that the debugger reported a segfault in the libnettle6 library, not in the rtmp...

Thanks for the hints!

[meveric]

Yeah I had to deal with the same issue a couple of times but you can install it with apt-get just fine and don't need to download or force with dpkg.

[dev-rand2]

@meveric Thank you so much for this excellent image! All is working well and I prefer debian over ubuntu (maybe I have an age problem...). I do seem, however, have to have an issue with trim on an SD card not working on an ODROID HC2. I am using a Samsung pro endurance card that allows trimming (e.g. via 'fstrim /' under the odroid XU4 ubuntu image on the HC2 board), but it gives me a "FITRIM ioctl failed: Invalid argument" on this build. Does this perhaps have something to do with the kernel or with a missing module? Is there anything I could try to confirm or help debugging?

[meveric]

hmm you can check if /etc/fstab has the discard option for / set, this could be an issue.
The Kernel should nearly be identical to Ubuntu and shouldn't be an issue.. I'll try if I can recreate this on a regular XU4, as I don't have an HC2 for testing.

[dev-rand2]

Yes, discard was in the fstab for both cases. The thing with the discard option is that it will not log errors even if it doesn't work. At least that's my understanding of it. Interestingly enough 'cat /sys/block/mmcblk1/queue/discard_max_bytes' shows a non-zero number.

[meveric]

I just tried it on my XU4 with Debian Stretch and a SanDisk Extreme Pro SD Card, trim was working fine.
I wonder if its something specific to the HC2. But generally fstrim on SD cards should work.

[dev-rand2]

Thanks! I really appreciate you trying this. I'll dig a bit more and see if I can find anything. It sure is strange, as the kernel clearly supports it (discard_max_bytes is non-zero value).

[dev-rand2]

One more data point: This debian stretch image definitely does support trim on the HC2. I successfully used it on a sandisc card but still no success with the samsung pro endurance, even after copying the kernel and kernel modules from the ubuntu distro. That same samsung card does trim fine in an old raspberry pi, though. Hmm. So maybe just a card specific problem that does not play well with the driver. Anyway, since it seems to be only this specific type of sd cards, that issue is probably not really worth investigating further.

[Gburas]

Hi again
after error during upgrade i have restarted the board and it didn`t boot. I have solid red and blue LED. I have read yours other post and i connected mmc to pc, here`s what i get:

also there`s no space left on partition - i think that was the error, i knew that i should delete old versions but should it be automatic?

can i manually put files on the mmc? so I do not have to reinstall the system

[meveric]

hmm it doesn't look so bad most stuff is there and looks fine.
here is what you can do:
1. delete uInitrd-4.14.28+ and zImage
2. delete everything that has 4.14.55+ in the name
3. delete uInitrd-4.14.69+ -> that one is broken you can see it when you check the size, as it's too small
4. make a copy of vmlinux-4.14.66+ and rename it to zImage

the rest looks fine.

Regarding cleanup:
Debian is tring to keep the last two kernels which in your case would be 4.14.55 and 4.14.66 while installing the next Kernel 4.14.69.
uInitrd-<VERSION> is created outside of the Kernel process and therefore has no cleanup which means it must be cleaned up manually.
The problem is, that bootfs is too small. It's the same size that was used on Kernel 3.10 where the Kernel was somewhat smaller and the process of installing updates worked better for that reason.
Sadly the image was already done when the issue with the Kernel 4.14 size became a issue and changing the size of the bootfs "on the fly" is not possible (or at least not very easy).

I would have to create a new image with a bigger boot partition in order to fix that issue.

[hamburml]

Hello and thanks for the Image!

I used it on my XU4, started your setup-script and installed mate desktop. After a reboot I just got the terminal. I needed to manually install xf86-video-armsoc-odroid - after another reboot the mate desktop was started. Unfortunately the whole desktop was laggy (dragging window from side to side for example). I installed chromium but wasn't able to start it. I created the symlinks but saw that i didn't have libEGL.so and libGLESv2.so - I installed them via malit628-odroid but the mate desktop is still laggy (chromium and firefox doesn't start either).

Any ideas?

Thanks!

[meveric]

Hmm that sounds odd.
Normally the installation of the Desktop should go through without you having to install anything manually.
Did you update the system before you tried to install the Desktop? Means latest Kernel and such things?

[hamburml]

Yeah, I did an update, upgrade and dist-upgrade. After that I installed console-setup and keyboard-configuration to change the keyboard-settings. Afterwards I used setup-odroid to install the desktop-environment. Maybe I overlooked a warning message...

[meveric]

Well I'll see if I can find a empty SD card and try it myself. Maybe something changed at Debian again. But it might take a few days.

[Gburas]

hmm it doesn't look so bad most stuff is there and looks fine.
here is what you can do:
1. delete uInitrd-4.14.28+ and zImage
2. delete everything that has 4.14.55+ in the name
3. delete uInitrd-4.14.69+ -> that one is broken you can see it when you check the size, as it's too small
4. make a copy of vmlinux-4.14.66+ and rename it to zImage

the rest looks fine.

Regarding cleanup:
Debian is tring to keep the last two kernels which in your case would be 4.14.55 and 4.14.66 while installing the next Kernel 4.14.69.
uInitrd-<VERSION> is created outside of the Kernel process and therefore has no cleanup which means it must be cleaned up manually.
The problem is, that bootfs is too small. It's the same size that was used on Kernel 3.10 where the Kernel was somewhat smaller and the process of installing updates worked better for that reason.
Sadly the image was already done when the issue with the Kernel 4.14 size became a issue and changing the size of the bootfs "on the fly" is not possible (or at least not very easy).

I would have to create a new image with a bigger boot partition in order to fix that issue.

I was busy so yesterday i have tried Yours instructions
board booted but it stops and want root password for maintenance, i have tried to update but it didn`t
what`s next?

[Gburas]

Image with status

Wysłane z mojego D6603 przy użyciu Tapatalka

[meveric]

Can you show me the content of /boot again like you did last time?
Do you have access to another linux machine or can boot a live CD so you can check on the rest of the OS rather than only /boot?

[Gburas]

https://photos.app.goo.gl/dnzdHQ2G8gBYtrKS9

i was able to this on odroid, also added screen of booting just before asking root password, and also update command

[meveric]

I'm very confused.. the first 3 images show a running Debian image, the last one from the boot process.
Whats with the first 3 images? Is the image running or not?

[Gburas]

it`s booting, after last image it stops for few minutes then ask to input root password, when i input the password it stays in cli mode and nothing happens
i`m still learning linux(i get along with linux when i buy xu4) so i don`t knew what to do next to make it run mate desktop, network etc.

[Gburas]

When i put root password i can execute commands, When i Press ctrl-d IT shows that

sorry for the image size
Wysłane z mojego D6603 przy użyciu Tapatalka

[meveric]

it`s booting, after last image it stops for few minutes then ask to input root password, when i input the password it stays in cli mode and nothing happens
i`m still learning linux(i get along with linux when i buy xu4) so i don`t knew what to do next to make it run mate desktop, network etc.

that's why there's a setup-odroid tool installed that can install the MATE Desktop for you.
Do you have eMMC and SD card connected at the same time?


If you haven't had anything important installed its probably easier to start from a fresh image and do the update right away.

[Gburas]

it`s booting, after last image it stops for few minutes then ask to input root password, when i input the password it stays in cli mode and nothing happens
i`m still learning linux(i get along with linux when i buy xu4) so i don`t knew what to do next to make it run mate desktop, network etc.

that's why there's a setup-odroid tool installed that can install the MATE Desktop for you.
Do you have eMMC and SD card connected at the same time?


If you haven't had anything important installed its probably easier to start from a fresh image and do the update right away.

yes i knew that tool, i used him when i was installing debian, also i knew that best way is fresh install, even i dont have anything important now (lucky me) but i thought we cen figure this out, next person maybe have something important ;p

but thanks for all the help

[stylon]

I installed the image to an HC1 and during the boot process it stalls for a considerable amount of seconds twice:

Code: Select all

[    3.395696] iommu: Adding device 13e10000.video-scaler to group 7
[   15.053706] thermal thermal_zone0: failed to read out thermal zone (-22)

Code: Select all

[   17.111557] usb 6-1: reset SuperSpeed USB device number 2 using xhci-hcd
[   17.180057] r8152 6-1:1.0 eth0: v1.09.9
[   26.913939] sd 0:0:0:0: [sda] Spinning up disk...
[   28.675057] .
[   28.675209] ready

That's a total of 12+9=21 seconds. Any idea why this is the case? I also have an XU4 lying around and next thing I would try is how the same SD card behaves there. Please note that I already updated the JMicron firmware. The installed kernel version is

Code: Select all

Linux debian-stretch 4.14.73+ #1 SMP PREEMPT Fri Oct 5 12:53:21 UTC 2018 armv7l GNU/Linux

Edit: Installed is a Samsung SSD 850 EVO 2TB.

[meveric]

The first issue:

Code: Select all

[    3.395696] iommu: Adding device 13e10000.video-scaler to group 7
[   15.053706] thermal thermal_zone0: failed to read out thermal zone (-22)

Could indicate a broken thermal CPU sensor, I've heard of a couple of ODROIDs that have broken sensors, but I guess @odroid can answer this better.

The second issue:

Code: Select all

[   17.180057] r8152 6-1:1.0 eth0: v1.09.9
[   26.913939] sd 0:0:0:0: [sda] Spinning up disk...
[   28.675057] .
[   28.675209] ready

Indicates a slow spin up of the harddrive, sadly that's most likely something you can't address, as the system waits for the HDD to report it's ready.

I also have an XU4 lying around and next thing I would try is how the same SD card behaves there.

That's a good idea, that way you can compare how a different system reacts, as the HC1 and XU4 are essentially the same device, it should be a good comparison.
Look especially for the Thermal issue, cause that might be a hardware fault.

Please note that I already updated the JMicron firmware.

I have a Cloudshell 2 and never updated the firmware.
I'm missing UAS support, but aside from that the older firmware seems to run better. For example on the Cloudshell 2 with the newer firmware the system can't distinguish between two different harddrives (Cloudshell 2 has 2x 3.5" HDDs), while with the older firmware that works perfectly fine.
The firmware "might" have an effect on the spin up time, but if so, it's very slightly.

[stylon]

The installed HDD is a Samsung SSD 850 EVO 2TB . Do you expect 9 seconds spinup time?

[stylon]

The first issue:

Code: Select all

[    3.395696] iommu: Adding device 13e10000.video-scaler to group 7
[   15.053706] thermal thermal_zone0: failed to read out thermal zone (-22)

Could indicate a broken thermal CPU sensor, I've heard of a couple of ODROIDs that have broken sensors, but I guess @odroid can answer this better.

I've also seen those other threads about "broken" thermal sensors, but they all hint at also wrong readings. However, measured temperatures of my HC1 seem to be fine and also correlated with CPU load:

Code: Select all

root@debian-stretch:~# cat /sys/devices/virtual/thermal/thermal_zone*/temp
47000
45000
52000
46000
46000

[meveric]

The installed HDD is a Samsung SSD 850 EVO 2TB . Do you expect 9 seconds spinup time?

Even more strange since it shouldn't have spin up time at all then.
I run from HDD (spinning) and my spin up time is about 2 seconds, but I also boot directly from HDD, so it might be started earlier in the boot process.

I've also seen those other threads about "broken" thermal sensors, but they all hint at also wrong readings. However, measured temperatures of my HC1 seem to be fine and also correlated with CPU load:

I agree on that, I just checked on my XU4 that runs from HDD and it also shows the same thermal zone issues on boot, so it seems to be "normal".

It's interesting to see that booting directly from a "slow" spinning hdd, is faster than you booting directly from SD.
My boot process ends after 23 seconds and the server is running by then.
Have you tried moving the OS to the SSD?

[stylon]

The installed HDD is a Samsung SSD 850 EVO 2TB . Do you expect 9 seconds spinup time?

Even more strange since it shouldn't have spin up time at all then.
I run from HDD (spinning) and my spin up time is about 2 seconds, but I also boot directly from HDD, so it might be started earlier in the boot process.

Okay, the second delay was not caused by spinning up the HDD (in this case SSD), but establishing the ethernet link. Both the R8152 and the JMS578 are enabled shortly before and in the dmesg log you can't see that it's waiting some 20-30 seconds for the eth0 to come up. It's only visible in the debug console output. Luckily I have that cable

Surprisingly, the eth0 wait time only disappeared after downgrading the JMS578 back to the v0.1.0.5 firmware . Did anyone notice a similar behaviour? I didn't try switching multiple times between firmware versions. I will most likely stick to the v0.1.0.5 firmware anyway as my hope was that power consumption reduces with the additional support for spinning down the SSD, but actually overall average wattage is 1W higher with the new firmware without changing at all when the SSD spins down. I also noticed that the green LED constantly flashes with the latest firmware, while it should only with SATA transfers.

My boot process ends after 23 seconds and the server is running by then.

Now mine ends at 29 seconds (eth0 probing and SSD "spinup" is now down to almost 0 seconds). However, there's still the 12s delay prior to the thermal zone failure message . I'll have a look at the kernel code where that comes from.

[andrewufrank]

I have been successful in using the new chromium version from testing 70.0.3538.67-2 - it does start ok and seems to work.

[meveric]

That's good to know.
This should mean that it should be ported to Stretch soon.

Thanks for the info

[Zeppelin500]

Hi all,

I use the jessie image at a HC1 with OMV and tvheadend without problems. Thank you maveric!

Now i try to switch to stretch with different ways. (with an image copy)

1. I upgrade first to stretch an after success i try to upgrade OMV but OMV is broken.

2. I upgrade OMV 3 to 4 and after success i change the sources.list and sources.list.d per hand from jessie to stretch.

OMV and TVH work fine but i can't update the system. After apt-get update it stops with

Code: Select all

root@nas:~# apt-get update
Get:1 file:/var/cache/openmediavault/archives  InRelease
Ign:1 file:/var/cache/openmediavault/archives  InRelease
Get:2 file:/var/cache/openmediavault/archives  Release [816 B]
Get:2 file:/var/cache/openmediavault/archives  Release [816 B]
Get:3 file:/var/cache/openmediavault/archives  Release.gpg
Ign:3 file:/var/cache/openmediavault/archives  Release.gpg
0% [Working]

I comment out every line in sources.list and sources.list.d but without success.

Anny ideas?

[meveric]

This is due to the upgrade from Jessie to Stretch and has nothing to do with OMV.
librtmp1 is the wrong verion installed (from Deb Multimedia Debian Jessie) which prevents apt from working correctly on https repos.
Please manually install correct librtmp1 version:

Code: Select all

apt-get install librtmp1=2.4+20151223.gitfa8646d.1-1+b1

[Zeppelin500]

thank you, but:

Code: Select all

root@nas:~# apt-get install librtmp1=2.4+20151223.gitfa8646d.1-1+b1
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version '2.4+20151223.gitfa8646d.1-1+b1' for 'librtmp1' was not found

i have returned the comments in the source lists. In what repository should it be?

[meveric]

It's in the stretch main repository.
Can you post the output of:

Code: Select all

apt-cache policy librtmp1

[Zeppelin500]

Code: Select all

root@nas:~# apt-cache policy librtmp1
librtmp1:
  Installed: 2:2.4~20150315.gita107cef9b-dmo1+deb8u2
  Candidate: 2:2.4~20150315.gita107cef9b-dmo1+deb8u2
  Version table:
 *** 2:2.4~20150315.gita107cef9b-dmo1+deb8u2 100
        100 /var/lib/dpkg/status

[meveric]

ok, it does not find any version at all.
Please try the following:

Code: Select all

cd /etc/apt/sources.list.d/
sed -i "s/^/#/" *.list
apt update
apt install librtmp1=2.4+20151223.gitfa8646d.1-1+b1
sed -i "s/^#//" *.list

If one of the commands causes an error, please to not try the next command, but just report back.
Also make sure the Debian Stretch repositories in /etc/apt/sources.list are activated and not commented out.

[Zeppelin500]

Code: Select all

root@nas:~# cd /etc/apt/sources.list.d/
root@nas:/etc/apt/sources.list.d# sed -i "s/^/#/" *.list
root@nas:/etc/apt/sources.list.d# apt update
Ign:1 http://ftp.debian.org/debian stretch InRelease
Get:2 http://ftp.debian.org/debian stretch-updates InRelease [91.0 kB]
Get:3 http://security.debian.org stretch/updates InRelease [94.3 kB]
Get:4 http://ftp.debian.org/debian stretch-backports InRelease [91.8 kB]
Get:5 http://ftp.debian.org/debian stretch Release [118 kB]
Get:6 http://ftp.debian.org/debian stretch Release.gpg [2,434 B]
Get:7 http://security.debian.org stretch/updates/non-free Sources [1,216 B]
Get:8 http://security.debian.org stretch/updates/contrib Sources [1,384 B]
Get:9 http://security.debian.org stretch/updates/main Sources [186 kB]
Get:10 http://security.debian.org stretch/updates/main armhf Packages [447 kB]
Get:11 http://security.debian.org stretch/updates/main Translation-en [201 kB]
Get:12 http://security.debian.org stretch/updates/contrib armhf Packages [1,768 B]
Get:13 http://security.debian.org stretch/updates/contrib Translation-en [1,759 B]
Get:14 http://security.debian.org stretch/updates/non-free armhf Packages [1,272 B]
Get:15 http://security.debian.org stretch/updates/non-free Translation-en [691 B]
Get:16 http://ftp.debian.org/debian stretch-updates/main Sources [3,748 B]
Get:17 http://ftp.debian.org/debian stretch-updates/main armhf Packages [5,108 B]
Get:18 http://ftp.debian.org/debian stretch-updates/main Translation-en [4,512 B]
Get:19 http://ftp.debian.org/debian stretch-backports/non-free Sources [8,200 B]
Get:20 http://ftp.debian.org/debian stretch-backports/contrib Sources [5,008 B]
Get:21 http://ftp.debian.org/debian stretch-backports/main Sources [528 kB]
Get:22 http://ftp.debian.org/debian stretch-backports/main armhf Packages [503 kB]
Get:23 http://ftp.debian.org/debian stretch-backports/main Translation-en [400 kB]
Get:24 http://ftp.debian.org/debian stretch-backports/contrib armhf Packages [6,152 B]
Get:25 http://ftp.debian.org/debian stretch-backports/contrib Translation-en [6,233 B]
Get:26 http://ftp.debian.org/debian stretch-backports/non-free armhf Packages [6,608 B]
Get:27 http://ftp.debian.org/debian stretch-backports/non-free Translation-en [33.8 kB]
Get:28 http://ftp.debian.org/debian stretch/non-free Sources [79.5 kB]
Get:29 http://ftp.debian.org/debian stretch/main Sources [6,751 kB]
Get:30 http://ftp.debian.org/debian stretch/contrib Sources [44.7 kB]
Get:31 http://ftp.debian.org/debian stretch/main armhf Packages [6,919 kB]
Get:32 http://ftp.debian.org/debian stretch/main Translation-en [5,388 kB]
Get:33 http://ftp.debian.org/debian stretch/contrib armhf Packages [42.1 kB]
Get:34 http://ftp.debian.org/debian stretch/contrib Translation-en [45.9 kB]
Get:35 http://ftp.debian.org/debian stretch/non-free armhf Packages [60.0 kB]
Get:36 http://ftp.debian.org/debian stretch/non-free Translation-en [80.4 kB]
Fetched 22.2 MB in 12s (1,762 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
73 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@nas:/etc/apt/sources.list.d# apt install librtmp1=2.4+20151223.gitfa8646d.1-1+b1
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be DOWNGRADED:
  librtmp1
0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 73 not upgraded.
Need to get 55.1 kB of archives.
After this operation, 18.4 kB disk space will be freed.
Do you want to continue? [Y/n] y
Abort.

[Zeppelin500]

i have try it second time

Code: Select all

root@nas:/etc/apt/sources.list.d# apt install librtmp1=2.4+20151223.gitfa8646d.1-1+b1
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be DOWNGRADED:
  librtmp1
0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 73 not upgraded.
Need to get 55.1 kB of archives.
After this operation, 18.4 kB disk space will be freed.
Do you want to continue? [Y/n] Y
Get:1 http://ftp.debian.org/debian stretch/main armhf librtmp1 armhf 2.4+20151223.gitfa8646d.1-1+b1 [55.1 kB]
Fetched 55.1 kB in 0s (309 kB/s)
dpkg: warning: downgrading librtmp1:armhf from 2:2.4~20150315.gita107cef9b-dmo1+deb8u2 to 2.4+20151223.gitfa8646d.1-1+b1
(Reading database ... 72339 files and directories currently installed.)
Preparing to unpack .../librtmp1_2.4+20151223.gitfa8646d.1-1+b1_armhf.deb ...
Unpacking librtmp1:armhf (2.4+20151223.gitfa8646d.1-1+b1) over (2:2.4~20150315.gita107cef9b-dmo1+deb8u2) ...
Setting up librtmp1:armhf (2.4+20151223.gitfa8646d.1-1+b1) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0xb626d390>
Traceback (most recent call last):
  File "/usr/lib/python3.5/weakref.py", line 117, in remove
TypeError: 'NoneType' object is not callable
Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0xb626d390>
Traceback (most recent call last):
  File "/usr/lib/python3.5/weakref.py", line 117, in remove
TypeError: 'NoneType' object is not callable

yes all in sources.list is activated.

[meveric]

Hm the python weakref module is not part of the default Debian OS, and might be something that comes from OMV, so I'm not sure what is causing this issue.

The installation of librtmp1 seems to have completed correctly though.
So at least that one is fixed.
Try to activate the files under /etc/apt/sources.list.d again:

Code: Select all

sed -i "s/^#//" *.list

and see if apt update works now.

The weakref issue though is a completely different topic I'm afraid.

[Zeppelin500]

update upgrade run, thank you. You fix the main problem.

this are the failures after second run:

Code: Select all

root@nas:~# apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libavresample3 linux-headers-4.9.58+
Use 'apt autoremove' to remove them.
The following packages have been kept back:
  libavcodec57 libavformat57
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up initramfs-tools (0.130) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-image-4.14.81+ (4.14.81-20181116-xu4) ...
update-initramfs: Generating /boot/initrd.img-4.14.81+
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
Image Name:   uInitrd
Created:      Tue Dec 18 16:34:55 2018
Image Type:   ARM Linux RAMDisk Image (uncompressed)
Data Size:    7668466 Bytes = 7488.74 kB = 7.31 MB
Load Address: 00000000
Entry Point:  00000000

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-4.14.81+ with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
mkimage: Write error on /boot/uInitrd-4.14.81+: Success
run-parts: /etc/kernel/postinst.d/uInitrd exited with return code 1
dpkg: error processing package linux-image-4.14.81+ (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of linux-image-4.14-armhf-odroid-xu4:
 linux-image-4.14-armhf-odroid-xu4 depends on linux-image-4.14.81+; however:
  Package linux-image-4.14.81+ is not configured yet.

dpkg: error processing package linux-image-4.14-armhf-odroid-xu4 (--configure):
 dependency problems - leaving unconfigured
Processing triggers for initramfs-tools (0.130) ...
ln: failed to create hard link '/boot/initrd.img-4.14.81+.dpkg-bak' => '/boot/initrd.img-4.14.81+': Operation not permitted
cp: error writing '/boot/initrd.img-4.14.81+.dpkg-bak': No space left on device
dpkg: error processing package initramfs-tools (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 linux-image-4.14.81+
 linux-image-4.14-armhf-odroid-xu4
 initramfs-tools
Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0xb62f5270>
Traceback (most recent call last):
  File "/usr/lib/python3.5/weakref.py", line 117, in remove
TypeError: 'NoneType' object is not callable
Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0xb62f5270>
Traceback (most recent call last):
  File "/usr/lib/python3.5/weakref.py", line 117, in remove
TypeError: 'NoneType' object is not callable
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@nas:~#

[meveric]

Code: Select all

root@nas:~# apt upgrade
The following packages were automatically installed and are no longer required:
  libavresample3 linux-headers-4.9.58+
Use 'apt autoremove' to remove them.

Here are leftover files that should be removed, especially the old Kernel Headers.

Code: Select all

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-4.14.81+ with 1.

This means the boot partition is full and you should clean it up a little.
Sadly with Kernel 4.14 the boot partition is a little too small.

go to /boot and cleanup everything that is not version 4.14.81+ it's not really needed and only there as a backup.
After you cleaned up, try again. Make sure you keep the boot.ini.