I love Garuda for its looks and functionality but, for a week or so now, there have been update errors described variously but usually 'error: could not read db ‘extra’. As Garuda is a rolling release I like to update daily and more or less there is some form of error every day. Some errors like ACPI errors we are told we can ignore. The same with
systemd-tmpfiles[577]: Failed to write file "/sys/module/pcie_aspm/parameters/policy": Operation not permitted'
But its not a good look for Garuda, these issues rarely appear in my other systems, ArcoLinux and EndeavorOS.
Looks and reliability perception are what makes or breaks a Linux Distro.
One thing that seems to fix it is running the Refesh Mirror List with Reflector Simple every time before trying an update. is this really necessary everytime?
Todays Garuda INIXI
Thanks, I’m forever rebooting. I did search this Forum as well as others, as we should, and you are right, I’m not the only one to have this error.
However, none of the other suggested fixes, fixed it though. That is why I posted.
My ‘Error’ and I will try not to make it again, was posting the compulsory Garuda inixi to avoid chastisement from SGS, before yet another reboot. Given the frequency of the update error over the last few weeks, and the many reboots over the last few days, I do not believe this is going to help in this case. I might be wrong.
Oh well, I’m sure a fix will eventually come along regardless of my plea for help.
There are no penalties/chastisement here, the people seeking help should just be cooperative and make it easier for the helpers by posting garuda-inxi.
I would also prefer not to have to point this out again and again.
But someone has to play the bogeyman here in the forum
Perhaps someone could explain to me what the problem is?
It is certainly not Garuda’s fault when these messages appear.
Similar to unknown file system Nvme with Grub?
If modules or hardware are not present, similar error messages appear.
I update at least twice a day and don’t need to change anything in the pacman config.
upd
:: Synchronizing package databases...
garuda is up to date
core 129,0 KiB 262 KiB/s 00:00 [---------------------------------------------------] 100%
extra 8,3 MiB 9,92 MiB/s 00:01 [---------------------------------------------------] 100%
multilib 139,2 KiB 282 KiB/s 00:00 [---------------------------------------------------] 100%
chaotic-aur 2,6 MiB 2,63 MiB/s 00:01 [---------------------------------------------------] 100%
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
Package (4) Old Version New Version Net Change Download Size
multilib/lib32-pixman 0.43.0-2 0.43.2-1 0.00 MiB 0.27 MiB
extra/linux-zen 6.7.1.zen1-1 6.7.2.zen1-1 0.01 MiB 135.06 MiB
extra/linux-zen-headers 6.7.1.zen1-1 6.7.2.zen1-1 0.00 MiB 25.79 MiB
extra/pixman 0.43.0-2 0.43.2-1 0.00 MiB 0.27 MiB
Total Download Size: 161.39 MiB
Total Installed Size: 265.04 MiB
Net Upgrade Size: 0.02 MiB
:: Proceed with installation? [Y/n]
Maybe you do not skip the mirrorlist refresh?
Just open new help request. I don’t see in the first topic about freezes.
╭─kevin@kevin in ~
╰─λ upd
:: Synchronising package databases...
garuda is up to date
core 129.0 KiB 483 KiB/s 00:00 [------------------------------------] 100%
extra 8.3 MiB 17.8 MiB/s 00:00 [------------------------------------] 100%
multilib is up to date
chaotic-aur 2.6 MiB 3.95 MiB/s 00:01 [------------------------------------] 100%
--> Refreshing mirrorlists using rate-mirrors, please be patient..🍵
:: Synchronising package databases...
garuda downloading...
core downloading...
extra downloading...
multilib downloading...
chaotic-aur downloading...
--> Applying keyring updates before starting full system update..
warning: archlinux-keyring-20231222-1 is up to date -- skipping
error: could not read db 'extra' (gzip decompression failed)
warning: chaotic-keyring-20230616-1 is up to date -- skipping
warning: garuda-hotfixes-1.1.2-1 is up to date -- skipping
there is nothing to do
:: Starting full system upgrade...
error: could not read db 'extra' (gzip decompression failed)
error: could not read db 'extra' (gzip decompression failed)
error: could not read db 'extra' (gzip decompression failed)
error: could not read db 'extra' (gzip decompression failed)
error: could not read db 'extra' (gzip decompression failed)
error: could not read db 'extra' (gzip decompression failed)
error: could not read db 'extra' (gzip decompression failed)
error: could not read db 'extra' (gzip decompression failed)
error: could not read db 'extra' (gzip decompression failed)
error: could not read db 'extra' (gzip decompression failed)
error: could not read db 'extra' (gzip decompression failed)
error: could not read db 'extra' (gzip decompression failed)
error: could not read db 'extra' (gzip decompression failed)
error: could not read db 'extra' (gzip decompression failed)
error: could not read db 'extra' (gzip decompression failed)
error: could not read db 'extra' (gzip decompression failed)
error: could not read db 'extra' (gzip decompression failed)
error: could not read db 'extra' (gzip decompression failed)
error: could not read db 'extra' (gzip decompression failed)
error: could not read db 'extra' (gzip decompression failed)
^C⏎
I notice on your ‘Upd’ there is no mirror list refresh. Should we use the Skip Mirror List Switch and use Upd instead of the link in the Garuda Assistant. We can do this by editing the alias?
This afternoons inxi is coming in a moment after i restart (again) to get rid of the swoosh!
And, if we do skip the mirror list thing this happens
kevin@kevin in ~
╰─λ garuda-update -a --skip-mirrorlist
:: Synchronising package databases...
garuda is up to date
core 129.0 KiB 592 KiB/s 00:00 [------------------------------------] 100%
extra 8.3 MiB 13.2 MiB/s 00:01 [------------------------------------] 100%
multilib is up to date
chaotic-aur is up to date
error: failed retrieving file 'extra.db' from sg.mirrors.cicku.me : transfer closed with 22 bytes remaining toread
error: failed retrieving file 'extra.db' from ca.mirrors.cicku.me : transfer closed with 137 bytes remaining to read
:: Starting full system upgrade...
warning: lib32-pixman: local (0.43.2-1) is newer than multilib (0.43.0-2)
resolving dependencies...
looking for conflicting packages...
Packages (2) linux-zen-6.7.2.zen1-1 linux-zen-headers-6.7.2.zen1-1
Total Download Size: 160.85 MiB
Total Installed Size: 263.57 MiB
Net Upgrade Size: 0.02 MiB
:: Proceed with installation? [Y/n] n
Are we not supposed to be using the handy link in the Garuda Assistant.
When this is used we get the multiple errors a few posts above?
You can break the error flood with Ctrl+C but it is not right.
I can’t understand that. Because I don’t have this problem.
Perhaps you should refrain from updating for a while until the Upstream problem has been resolved.
The mirrors in Germany that I use work.
Right well this is getting a bit silly. I have just updated my mirrors using the handy app in the Garuda Assistant. I deselected the UK ones and selected only the German one.
I still get an error
:: Synchronising package databases...
garuda is up to date
core 129.0 KiB 419 KiB/s 00:00 [------------------------------------] 100%
extra is up to date
multilib 139.2 KiB 438 KiB/s 00:00 [------------------------------------] 100%
chaotic-aur 2.6 MiB 4.54 MiB/s 00:01 [------------------------------------] 100%
--> Refreshing mirrorlists using rate-mirrors, please be patient..🍵
:: Synchronising package databases...
garuda downloading...
core downloading...
extra downloading...
multilib downloading...
chaotic-aur downloading...
error: failed retrieving file 'extra.db' from sg.mirrors.cicku.me : transfer closed with 22 bytes remaining toread
:: Starting full system upgrade...
warning: lib32-pixman: local (0.43.2-1) is newer than multilib (0.43.0-2)
resolving dependencies...
looking for conflicting packages...
Packages (2) linux-zen-6.7.2.zen1-1 linux-zen-headers-6.7.2.zen1-1
Total Download Size: 160.85 MiB
Total Installed Size: 263.57 MiB
Net Upgrade Size: 0.02 MiB
:: Proceed with installation? [Y/n] n
Press enter to exit
# Magic Transit
Cloudflare AS13335 ᴄᴀɴ
# Open Source Mirror
## Announcements:
1. As of 01/05/2024, HTTP/2 has been temporarily disabled due to some internal issues.
2. The next scheduled maintenance is set on 02/01/2024 1700UTC.
3. For any other concerns with the open source mirror, please contact mirrors[aT]cicku[d0t]me (replace [] w/ RFC 5322). **An answer is not guaranteed when the question is out of scope.**
However, using the UK and the German mirrors seems to have fixed it.
For now!