For the third update in a row, my update is failing.
[Last failed update; first failed update.]
After each of the last two updates, I had to reformat from scratch, and the error would still persist. Both times “hardware corruption” was suggested, but there was no evidence of it in the logs.
Logs available at https://paste.osmc.tv/eyuvejozok
====================== APT sources.list =================== ZZz2wrJ1
#deb http://ftp.debian.org/debian stretch main contrib non-free
#deb http://ftp.debian.org/debian/ stretch-updates main contrib non-free
#deb http://security.debian.org/ stretch/updates main contrib non-free
deb https://ftp.tu-graz.ac.at/mirror/debian/ stretch main contrib non-free
deb https://ftp.tu-graz.ac.at/mirror/debian/ stretch-updates main contrib non-free
deb http://security.debian.org/ stretch/updates main contrib non-free
deb https://ftp.fau.de/osmc/osmc/apt/ stretch main
#deb http://apt.osmc.tv stretch main
Your sources.list isn’t standard. This is likely causing the problem.
That was the source list I was given during to fix the last failed update:
What is the output of apt-get update && apt-get dist-upgrade?
The system journal is massively spammed by this message:
Feb 05 02:34:56 Oswin kernel: [amlogic] ##### cec write error! #####
Feb 05 02:34:56 Oswin kernel: [amlogic_cec] amlogic_cec_irq_handler(): cec msg status: rx: 0x0; tx: 0x3
which occurs almost 26,000 times in the log. (Doubless more occurred since the syslog has been totally cleared of all startup information.)
The last recorded update in the APT log is for 2018-01-19. @LexPendragon did you once again have the same hash sum errors as in the previous post?
Hit:1 http://security.debian.org stretch/updates InRelease
Ign:2 Index of /mirror/debian stretch InRelease
Hit:3 Index of /osmc/osmc/apt stretch InRelease
Get:4 Index of /mirror/debian stretch-updates InRelease [91.0 kB]
Hit:5 Index of /mirror/debian stretch Release
Fetched 91.0 kB in 6s (14.1 kB/s)
Reading package lists… Done
Reading package lists… Done
Building dependency tree
Reading state information… Done
Calculating upgrade… Done
The following NEW packages will be installed:
vero2-image-3.10.105-9-osmc
The following packages will be upgraded:
armv7-eventlircd-osmc armv7-splash-osmc base-files-osmc curl libcurl3 libcurl3-gnutls libtiff5 mediacenter-addon-osmc vero2-kernel-osmc vero2-mediacenter-osmc
10 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 39.9 MB/57.6 MB of archives.
After this operation, 26.6 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 Index of /osmc/osmc/apt stretch/main armhf vero2-mediacenter-osmc armhf 17.6.0-22 [39.9 MB]
Err:1 Index of /osmc/osmc/apt stretch/main armhf vero2-mediacenter-osmc armhf 17.6.0-22
GnuTLS recv error (-24): Decryption has failed.
E: Failed to fetch https://ftp.fau.de/osmc/osmc/apt/pool/main/v/vero2-mediacenter-osmc/vero2-mediacenter-osmc_17.6.0-22_armhf.deb GnuTLS recv error (-24): Decryption has failed.
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
You can see the output in my last post to Sam.
So it looks like you were getting hash sum errors when the connection is unencrypted and now you’re getting decryption errors when encrypted.
Let’s throw a few commands around and see what comes out of the woodwork, if anything. If nothing throws up an error you can Ctrl-C them after a few seconds.
openssl s_client --connect ftp.fau.de:443
wget https://ftp.fau.de/osmc/osmc/apt/pool/main/v/vero2-mediacenter-osmc/vero2-mediacenter-osmc_17.6.0-22_armhf.deb -O /dev/null
curl https://ftp.fau.de/osmc/osmc/apt/pool/main/v/vero2-mediacenter-osmc/vero2-mediacenter-osmc_17.6.0-22_armhf.deb > /dev/null
Since the error refers to GnuTLS, you’ll need to install one package to try this one:
sudo apt-get install gnutls-bin
gnutls-cli -d 1 -p 443 ftp.fau.de
Update: You are getting a very large number of dropped RX packets on your eth0 interface:
eth0: flags=-28605<UP,BROADCAST,RUNNING,MULTICAST,DYNAMIC> mtu 1500
inet 192.168.23.16 netmask 255.255.255.0 broadcast 192.168.23.255
ether 08:61:60:11:20:b7 txqueuelen 1000 (Ethernet)
RX packets 62973741 bytes 980189136 (934.7 MiB)
RX errors 0 dropped 598 overruns 0 frame 0
TX packets 38675334 bytes 2743297310 (2.5 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 40
It might not be the source of your problems but it’s worth noting.
wget gave me this error four times, but eventually completed:
2018-02-05 15:00:38 (3.12 MB/s) - Read error at byte 21069824/39875910 (Decryption has failed.). Retrying.
The last command started out this way:
root@Oswin:/home/osmc# curl https://ftp.fau.de/osmc/osmc/apt/pool/main/v/vero2-mediacenter-osmc/vero2-mediacenter-osmc_17.6.0-22_armhf.deb
!
debian-binary 1517761674 0 0 100644 4 2.0 control.tar.gz 1517761674 0 0 100644 1250
�Ymo�6���WpnlC�B�/���Ү(�� )��P�-��H���…
And then seems to go off to a lot of binary.
You missed off the > /dev/null part. 
Yes I did, one moment…
root@Oswin:/home/osmc# curl https://ftp.fau.de/osmc/osmc/apt/pool/main/v/vero2-mediacenter-osmc/vero2-mediacenter-osmc_17.6.0-22_armhf.deb > /dev/null
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
1 38.0M 1 592k 0 0 340k 0 0:01:54 0:00:01 0:01:53 341k
48 38.0M 48 18.4M 0 0 2698k 0 0:00:14 0:00:06 0:00:08 3657k
curl: (56) SSL read: error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac, errno 0The curl and wget have problems. What about the other two commands?
I’m beginning to suspect something on your network, eg router. Is the router supplied by Comcast?
What does ifconfig eth0 show now?
root@Oswin:/home/osmc# ifconfig eth0
eth0: flags=-28605<UP,BROADCAST,RUNNING,MULTICAST,DYNAMIC> mtu 1500
inet 192.168.23.16 netmask 255.255.255.0 broadcast 192.168.23.255
ether 08:61:60:11:20:b7 txqueuelen 1000 (Ethernet)
RX packets 134870 bytes 179781055 (171.4 MiB)
RX errors 0 dropped 1 overruns 0 frame 0
TX packets 54834 bytes 7392208 (7.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 40
(I just rebooted because of a lock-up.)
The network is entirely mine: OSMC device to a Unifi In-Wall WAP, to a dumb TP-LINK Gigabit Switch to the Unifi EdgeMax Router, to the Surfboard SB6190 cable modem. Also, there are four other Linux systems on the network that have no trouble getting updates. (Though they are all OpenSUSE.)
To test the network a bit more, I tried the command from one of the other systems:
alexius@Quicksilver:~> curl https://ftp.fau.de/osmc/osmc/apt/pool/main/v/vero2-mediacenter-osmc/vero2-mediacenter-osmc_17.6.0-22_armhf.deb > /dev/null
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 38.0M 100 38.0M 0 0 4847k 0 0:00:08 0:00:08 --:–:-- 6302k
And then tried a different port for the OSMC:
root@Oswin:/home/osmc# curl https://ftp.fau.de/osmc/osmc/apt/pool/main/v/vero2-mediacenter-osmc/vero2-mediacenter-osmc_17.6.0-22_armhf.deb > /dev/null
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
8 38.0M 8 3360k 0 0 1392k 0 0:00:27 0:00:02 0:00:25 1391k
curl: (56) SSL read: error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac, errno 0
Nice work. I’ll have to think about this one.
Just out of interest, does
curl --tlsv1.2 https://ftp.fau.de/osmc/osmc/apt/pool/main/v/vero2-mediacenter-osmc/vero2-mediacenter-osmc_17.6.0-22_armhf.deb > /dev/null
make a difference?
And what’s the RX dropped packet count now?
That doesn’t seem to make a difference:
root@Oswin:/home/osmc# curl --tlsv1.2 https://ftp.fau.de/osmc/osmc/apt/pool/main/v/vero2-mediacenter-osmc/vero2-mediacenter-osmc_17.6.0-22_armhf.deb > /dev/null
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
9 38.0M 9 3744k 0 0 1285k 0 0:00:30 0:00:02 0:00:28 1284k
curl: (56) SSL read: error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac, errno 0
And the dropped packets (after I ran that command) is now at 2.
Basic question: this Unifi In-Wall WAP has how many other devices connected to it by cable?
I assume it’s then connected by cable to the dumb switch and then onto the router, right?
Your assumption is correct, but there are no other items connected by cable.
OSMC ----- WAP ------ TP-Link — Router — Cable Modem
So all your OpenSUSE boxes hang off either the dumb switch or the router, right?
If so, what’s the chance of you getting a long cable and attaching the Vero to either the router or switch?
Half of the OpenSUSE boxes are actually on WiFi (through the WAP that the OSMC box uses.)
I can take the WAP out of the middle and use the uplink to go straight to the OSMC device. Or I can plug my laptop into the other side of the WAP and test it that way. (Whichever I can get to first.) I can report back.