Good afternoon! I got the email about the October update this morning and told my OSMC on the RasPi to do its thing. On the upside, it failed gracefully… on the downside I can’t get past the error notification in the title.
Should I try doing an ‘apt update’ pass from SSH and see what that gives me?
To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.
Depending on the used skin you have to set the settings-level to standard or higher, in summary:
enable debug logging at settings->system->logging
reboot the OSMC device twice(!)
reproduce the issue
upload the log set (all configs and logs!) either using the Log Uploader method within the My OSMC menu in the GUI or the ssh method invoking command grab-logs -A
publish the provided URL from the log set upload, here
Thanks for your understanding. We hope that we can help you get up and running again shortly.
OSMC skin screenshot:
The log doesn’t show any issues.
Can you reboot and try again?
No joy, basically same as before. (I’ve done four reboots and attempts to update now.)
In the GUI I tell it to check for updates, and it does, then gives an error on “unknown package.” It then prompts me to do a reboot-and-install, which drops back down to the CLI-style installer view where it gets stuck downloading “package 412 of 438” and never finishes.
It looks like I’m pulling from a German mirror for the apt source, is there a way to pick a different mirror that might have less trouble?
Hi,
We need to see newer logs.
If you are familiar with SSH, you can do apt-get update && apt-get dist-upgrade.
Sam
I’m getting a big steaming mess of hash mismatches, like these:
Err:33 http://apt.osmc.tv buster/main armhf perftune-osmc all 1.2.8
Writing more data than expected (47486 > 2228)
Hashes of expected file:
and at the in, no install:
E: Failed to fetch http://ftp.fau.de/osmc/osmc/apt/pool/main/a/armv7-eventlircd-osmc/armv7-eventlircd-osmc_1.4.5_armhf.deb Writing more data than expected (36688 > 1204)
Hashes of expected file:
- SHA256:0563e79cecebbbc87d075665248b431947d615162abcd2d9143cbb66f42f1603
- SHA1:950eeef43486c7e2db679987753420de7ddfe0dc [weak]
- MD5Sum:dfe224c548c10438f8000d4f48624b8f [weak]
- Filesize:36688 [weak]
E: Failed to fetch http://ftp.fau.de/osmc/osmc/apt/pool/main/a/armv7-remote-osmc/armv7-remote-osmc_1.2.3_armhf.deb Writing more data than expected (47486 > 2228)
Hashes of expected file:
- SHA256:0c6fa39718fbe99aab6eb7e82106a6cf00e8b8e569a3efab7667f7bc672b61fb
- SHA1:bdb92982eb8d121e4187fbb56f54f2d5551a365f [weak]
- MD5Sum:e0e95853cfe2317f6472520fab4d5d5a [weak]
- Filesize:1342948 [weak]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
I really think there’s something awry with the German source (ftp.fau.de) here.
I’d suspect your SD card, especially since the logs didn’t show any of this.
Did a boot-time ‘fsck’ just to be on the safe side, everything seems peachy so far.
And if it was the SD card, why are only the ftp.fau.de contents throwing the errors? The ‘apt dist-upgrade’ process downloaded a whole bunch of stuff from security.debian.org and ftp.debian.org without a single glitch.
Well, you didn’t share a full log, so it’s impossible to tell.
Here’s a good test of your SD card:
touch mytestfile
ls -l mytestfile
Then reboot and:
ls -l mytestfile
That will show if the SD card is still writeable.
Weird that using the debug log generation as directed didn’t give you anything to work with. Ugh.
At any rate… for what it’s worth, as people come along later and find this thread (perhaps), as with another “hash mismatch” support thread from a few years ago, it was indeed a “security feature” getting in the way. In my case, the Sophos UTM firewall at home (required for work-from-home purposes). Despite adding ftp-dot-fau-dot-de to the exception rules, etc, etc, I had to actually FULLY DISARM the web filtering engine to get past the hash errors and actually download the updated packages.
Thus continues my love/hate relationship with Sophos products… and I’m currently 43% done with the ‘apt dist-upgrade’ process, so fingers crossed that that’s the end of THIS particular headache. Thank you for the assistance!
(The log I uploaded DID show the hash errors, actually. I just checked.)
Yep, I see that now. I looked in the apt log when I checked your logs. I didn’t look close enough. Lesson learned!
No harm done! I appreciate your taking the time to help dig in.
It might be that your ISP is using a transparent proxy which contains incorrect data.
If you’re familiar with the command line, you can edit file /etc/apt/sources.list to this:
deb http://ftp.debian.org/debian buster main contrib non-free
deb http://ftp.debian.org/debian/ buster-updates main contrib non-free
deb http://security.debian.org/ buster/updates main contrib non-free
# deb http://apt.osmc.tv buster main
deb https://ftp.fau.de/osmc/osmc/apt/ buster main
(I’ve commented out the last line and added a new line using https.)
Then run:
sudo apt-get update
sudo apt-get dist-upgrade
This should at least bypass any dodgy ISP proxy, should one exist.