mirror of
https://github.com/pikvm/pikvm.git
synced 2026-03-02 18:16:56 -05:00
Unable to update due to pacman error - cannot read db extra #1017
Labels
No labels
component:documentation
help wanted
resolution:delayed
resolution:duplicate
resolution:fixed
resolution:invalid
resolution:rejected
resolution:wontfix
success story
type:bug
type:bug
type:feature
type:question
type:question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/pikvm-pikvm#1017
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Majestic7979 on GitHub (Mar 31, 2025).
Originally assigned to: @mdevaev on GitHub.
pikvm-update
=== PiKVM is in Read-Write mode ===
:: Synchronizing package databases...
core 238.9 KiB 405 KiB/s 00:01 [###########################################################] 100%
extra 9.3 MiB 16.1 MiB/s 00:01 [###########################################################] 100%
community 45.0 B 900 B/s 00:00 [###########################################################] 100%
alarm 95.7 KiB 1063 KiB/s 00:00 [###########################################################] 100%
aur 11.1 KiB 185 KiB/s 00:00 [###########################################################] 100%
pikvm 11.6 KiB 33.2 KiB/s 00:00 [###########################################################] 100%
error: failed retrieving file 'core.db' from mirror.osbeck.com : The requested URL returned error: 404
error: failed retrieving file 'extra.db' from mirror.osbeck.com : The requested URL returned error: 404
error: failed retrieving file 'community.db' from mirror.osbeck.com : The requested URL returned error: 404
warning: too many errors from mirror.osbeck.com, skipping for the remainder of this transaction
++ pacman -S -u --print-format %n
++ grep -v pikvm-os-updater
++ wc -l
error: could not read db 'extra' (Damaged tar archive (bad header checksum))
error: could not read db 'extra' (Damaged tar archive (bad header checksum))
error: could not read db 'extra' (Damaged tar archive (bad header checksum))
error: could not read db 'extra' (Damaged tar archive (bad header checksum))
error: could not read db 'extra' (Damaged tar archive (bad header checksum))
error: could not read db 'extra' (Damaged tar archive (bad header checksum))
error: could not read db 'extra' (Damaged tar archive (bad header checksum))
error: could not read db 'extra' (Damaged tar archive (bad header checksum))
error: could not read db 'extra' (Damaged tar archive (bad header checksum))
error: could not read db 'extra' (Damaged tar archive (bad header checksum))
error: could not read db 'extra' (Damaged tar archive (bad header checksum))
error: could not read db 'extra' (Damaged tar archive (bad header checksum))
error: could not read db 'extra' (Damaged tar archive (bad header checksum))
error: could not read db 'extra' (Damaged tar archive (bad header checksum))
@Majestic7979 commented on GitHub (Mar 31, 2025):
It happens on the original too:
pikvm-update
=== PiKVM is in Read-Write mode ===
:: Synchronizing package databases...
core 238.9 KiB 683 KiB/s 00:00 [###########################################################] 100%
extra 9.3 MiB 18.3 MiB/s 00:01 [###########################################################] 100%
community 45.0 B 750 B/s 00:00 [###########################################################] 100%
alarm 95.7 KiB 1063 KiB/s 00:00 [###########################################################] 100%
aur 11.1 KiB 185 KiB/s 00:00 [###########################################################] 100%
pikvm 11.6 KiB 166 KiB/s 00:00 [###########################################################] 100%
++ pacman -S -u --print-format %n
++ grep -v pikvm-os-updater
++ wc -l
error: could not read db 'extra' (Damaged tar archive (bad header checksum))
error: could not read db 'extra' (Damaged tar archive (bad header checksum))
error: could not read db 'extra' (Damaged tar archive (bad header checksum))
error: could not read db 'extra' (Damaged tar archive (bad header checksum))
error: could not read db 'extra' (Damaged tar archive (bad header checksum))
error: could not read db 'extra' (Damaged tar archive (bad header checksum))
error: could not read db 'extra' (Damaged tar archive (bad header checksum))
error: could not read db 'extra' (Damaged tar archive (bad header checksum))
^[error: could not read db 'extra' (Damaged tar archive (bad header checksum))
error: could not read db 'extra' (Damaged tar archive (bad header checksum))
error: could not read db 'extra' (Damaged tar archive (bad header checksum))
^Xerror: could not read db 'extra' (Damaged tar archive (bad header checksum))
error: could not read db 'extra' (Damaged tar archive (bad header checksum))
error: could not read db 'extra' (Damaged tar archive (bad header checksum))
error: could not read db 'extra' (Damaged tar archive (bad header checksum))
error: could not read db 'extra' (Damaged tar archive (bad header checksum))
@mdevaev commented on GitHub (Mar 31, 2025):
Hello! Here the solution:
@Majestic7979 commented on GitHub (Mar 31, 2025):
Thank you, it's fixed.
While you're here, if you don't mind Maxim, I need to ask your advice please.
I purchased this item:
https://www.aliexpress.com/item/1005006209126315.html?spm=a2g0o.order_list.order_list_main.11.12141802lDXoxI
I wired the NO contact and the COMMON contact to a switch in a normal KVM, this KVM has a button in front of it that when clicked, switches between input 1 and input 2, so I just soldered wires to the contacts and when the wires are shorted for a moment the KVM switches between the inputs. So I tried to follow the guide on pikvm.org for optocoupler (https://docs.pikvm.org/gpio/) using GPIO but it's not switching... could you please kindly advice/walk me through? Here's my override currently:
@Majestic7979 commented on GitHub (Mar 31, 2025):
@Majestic7979 commented on GitHub (Mar 31, 2025):
@Majestic7979 commented on GitHub (Mar 31, 2025):
@mdevaev commented on GitHub (Mar 31, 2025):
The config is fine but this specific relay might be incompatible. Some cheap relays has unique protocols for some reason.
@Majestic7979 commented on GitHub (Mar 31, 2025):
Ah =/ Could you please recommend a link? Cheap as possible and that works well.
Thanks.
@mdevaev commented on GitHub (Apr 3, 2025):
Some which will look like these: http://vusb.wikidot.com/project:driver-less-usb-relays-hid-interface