You are not logged in.

#26 2019-10-29 18:27:19

loqs
Member
Registered: 2014-03-06
Posts: 19,098

Re: [solved] Error: failed retrieveing core.db: Resolve timeout.

This warning and this error?

warning: could not fully load metadata for package pacman-5.2.0-2
error: failed to prepare transaction (invalid package)

Offline

#27 2019-10-29 18:38:02

r00tr4t
Member
Registered: 2013-01-16
Posts: 101

Re: [solved] Error: failed retrieveing core.db: Resolve timeout.

It came from installing pacman with 

 pacman --root=/mnt pacman 

Now I tested

 pacman --sysroot /mnt pacman 

and that worked and - Suu aslo works but not -Syu.

Offline

#28 2019-10-29 18:43:15

loqs
Member
Registered: 2014-03-06
Posts: 19,098

Re: [solved] Error: failed retrieveing core.db: Resolve timeout.

Please post the command and outputs together.  It makes it easier for others to follow.
If I understand correctly the failing command is:

pacman --sysroot /mnt -Syu pacman

What output is that command producing?

Last edited by loqs (2019-10-29 18:43:44)

Offline

#29 2019-10-29 18:52:24

r00tr4t
Member
Registered: 2013-01-16
Posts: 101

Re: [solved] Error: failed retrieveing core.db: Resolve timeout.

Sorry. I'm writing alltings on my phone only, outputs, commands and comments.

 pacman --sysroot /mnt -S pacman 

works

 pacman --sysroot /mnt -Syu pacman
error : failed retrieveing file core.db from ftp.acc.umu.se : Resolveing timed out after 10000ms

Offline

#30 2019-10-29 18:59:27

r00tr4t
Member
Registered: 2013-01-16
Posts: 101

Re: [solved] Error: failed retrieveing core.db: Resolve timeout.

What about changing

 /etc/pacman.conf
#DBPath = /var/lib/pacman

To

 /etc/pacman.conf
DBPath = /mnt/var/lib/pacman

Offline

#31 2019-10-29 19:07:16

loqs
Member
Registered: 2014-03-06
Posts: 19,098

Re: [solved] Error: failed retrieveing core.db: Resolve timeout.

Does the following work?

pacman --root /mnt -Syu pacman

See the tip box from pastebin to post from the console.

pacman -Qkk &> tmp.log

Then please upload tmp.log

Offline

#32 2019-10-29 19:18:07

r00tr4t
Member
Registered: 2013-01-16
Posts: 101

Re: [solved] Error: failed retrieveing core.db: Resolve timeout.

loqs wrote:

Does the following work?

pacman --root /mnt -Syu pacman

See the tip box from pastebin to post from the console.

pacman -Qkk &> tmp.log

Then please upload tmp.log

Wow that's handy.
tmp.log
Next I upload the output for the pacman install.

Offline

#33 2019-10-29 19:36:27

r00tr4t
Member
Registered: 2013-01-16
Posts: 101

Re: [solved] Error: failed retrieveing core.db: Resolve timeout.

pacman.log for the installation.

Offline

#34 2019-10-29 19:52:41

r00tr4t
Member
Registered: 2013-01-16
Posts: 101

Re: [solved] Error: failed retrieveing core.db: Resolve timeout.

The output of find

Offline

#35 2019-10-29 20:13:07

loqs
Member
Registered: 2014-03-06
Posts: 19,098

Re: [solved] Error: failed retrieveing core.db: Resolve timeout.

Networking is configured / working in the live environment?

ping ftp.acc.umu.se

Offline

#36 2019-10-29 20:29:32

r00tr4t
Member
Registered: 2013-01-16
Posts: 101

Re: [solved] Error: failed retrieveing core.db: Resolve timeout.

Offline

#37 2019-10-29 20:36:15

loqs
Member
Registered: 2014-03-06
Posts: 19,098

Re: [solved] Error: failed retrieveing core.db: Resolve timeout.

Only difference is pacman uses curl by default so

/usr/bin/curl -L -C - -f -o /dev/null http://ftp.acc.umu.se/mirror/archlinux/core/os/x86_64/core.db

Offline

#38 2019-10-29 20:46:28

r00tr4t
Member
Registered: 2013-01-16
Posts: 101

Re: [solved] Error: failed retrieveing core.db: Resolve timeout.

loqs wrote:

Only difference is pacman uses curl by default so

/usr/bin/curl -L -C - -f -o /dev/null http://ftp.acc.umu.se/mirror/archlinux/core/os/x86_64/core.db

Yes that works

Offline

#39 2019-10-29 21:04:55

loqs
Member
Registered: 2014-03-06
Posts: 19,098

Re: [solved] Error: failed retrieveing core.db: Resolve timeout.

Misread the log as containing only one command not two.  When not using --root command seems to work

pacman --root=/mnt -Syu pacman
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (1) pacman-5.2.0-2

Total Installed Size:  4.42 MiB
Net Upgrade Size:      0.00 MiB

checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
:: Processing package changes...
reinstalling pacman...
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...

with --sysroot

pacman --debug --sysroot /mnt -Syu pacman
debug: pacman v5.1.3 - libalpm v11.0.3
debug: config: attempting to read file /etc/pacman.conf
debug: config: new section 'options'
debug: config: CacheDir: /home/var/pacman/pkg
debug: config: HoldPkg: pacman
debug: config: HoldPkg: glibc
debug: config: arch: x86_64
debug: config: chomp
debug: config: SigLevel: Required
debug: config: SigLevel: DatabaseOptional
debug: config: LocalFileSigLevel: Optional
debug: config: new section 'core'
debug: config file /etc/pacman.conf, line 78: including /etc/pacman.d/mirrorlist
debug: config: new section 'extra'
debug: config file /etc/pacman.conf, line 81: including /etc/pacman.d/mirrorlist
debug: config: new section 'community'
debug: config file /etc/pacman.conf, line 87: including /etc/pacman.d/mirrorlist
debug: config: new section 'multilib'
debug: config file /etc/pacman.conf, line 96: including /etc/pacman.d/mirrorlist
debug: config: finished parsing /etc/pacman.conf
debug: setup_libalpm called
debug: option 'logfile' = /var/log/pacman.log
debug: option 'gpgdir' = /etc/pacman.d/gnupg/
debug: option 'hookdir' = /etc/pacman.d/hooks/
debug: option 'cachedir' = /home/var/pacman/pkg/
debug: registering sync database 'core'
debug: database path for tree core set to /var/lib/pacman/sync/core.db
debug: "/var/lib/pacman/sync/core.db.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/core.db.sig could not be opened
debug: missing optional signature
debug: setting usage of 15 for core repository
debug: adding new server URL to database 'core': http://ftp.acc.umu.se/mirror/archlinux/core/os/x86_64
debug: adding new server URL to database 'core': https://ftp.acc.umu.se/mirror/archlinux/core/os/x86_64
debug: adding new server URL to database 'core': http://archlinux.dynamict.se/core/os/x86_64
debug: adding new server URL to database 'core': https://archlinux.dynamict.se/core/os/x86_64
debug: adding new server URL to database 'core': http://ftp.myrveln.se/pub/linux/archlinux/core/os/x86_64
debug: adding new server URL to database 'core': https://ftp.myrveln.se/pub/linux/archlinux/core/os/x86_64
debug: adding new server URL to database 'core': https://mirror.osbeck.com/archlinux/core/os/x86_64
debug: registering sync database 'extra'
debug: database path for tree extra set to /var/lib/pacman/sync/extra.db
debug: "/var/lib/pacman/sync/extra.db.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/extra.db.sig could not be opened
debug: missing optional signature
debug: setting usage of 15 for extra repository
debug: adding new server URL to database 'extra': http://ftp.acc.umu.se/mirror/archlinux/extra/os/x86_64
debug: adding new server URL to database 'extra': https://ftp.acc.umu.se/mirror/archlinux/extra/os/x86_64
debug: adding new server URL to database 'extra': http://archlinux.dynamict.se/extra/os/x86_64
debug: adding new server URL to database 'extra': https://archlinux.dynamict.se/extra/os/x86_64
debug: adding new server URL to database 'extra': http://ftp.myrveln.se/pub/linux/archlinux/extra/os/x86_64
debug: adding new server URL to database 'extra': https://ftp.myrveln.se/pub/linux/archlinux/extra/os/x86_64
debug: adding new server URL to database 'extra': https://mirror.osbeck.com/archlinux/extra/os/x86_64
debug: registering sync database 'community'
debug: database path for tree community set to /var/lib/pacman/sync/community.db
debug: "/var/lib/pacman/sync/community.db.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/community.db.sig could not be opened
debug: missing optional signature
debug: setting usage of 15 for community repository
debug: adding new server URL to database 'community': http://ftp.acc.umu.se/mirror/archlinux/community/os/x86_64
debug: adding new server URL to database 'community': https://ftp.acc.umu.se/mirror/archlinux/community/os/x86_64
debug: adding new server URL to database 'community': http://archlinux.dynamict.se/community/os/x86_64
debug: adding new server URL to database 'community': https://archlinux.dynamict.se/community/os/x86_64
debug: adding new server URL to database 'community': http://ftp.myrveln.se/pub/linux/archlinux/community/os/x86_64
debug: adding new server URL to database 'community': https://ftp.myrveln.se/pub/linux/archlinux/community/os/x86_64
debug: adding new server URL to database 'community': https://mirror.osbeck.com/archlinux/community/os/x86_64
debug: registering sync database 'multilib'
debug: database path for tree multilib set to /var/lib/pacman/sync/multilib.db
debug: "/var/lib/pacman/sync/multilib.db.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/multilib.db.sig could not be opened
debug: missing optional signature
debug: setting usage of 15 for multilib repository
debug: adding new server URL to database 'multilib': http://ftp.acc.umu.se/mirror/archlinux/multilib/os/x86_64
debug: adding new server URL to database 'multilib': https://ftp.acc.umu.se/mirror/archlinux/multilib/os/x86_64
debug: adding new server URL to database 'multilib': http://archlinux.dynamict.se/multilib/os/x86_64
debug: adding new server URL to database 'multilib': https://archlinux.dynamict.se/multilib/os/x86_64
debug: adding new server URL to database 'multilib': http://ftp.myrveln.se/pub/linux/archlinux/multilib/os/x86_64
debug: adding new server URL to database 'multilib': https://ftp.myrveln.se/pub/linux/archlinux/multilib/os/x86_64
debug: adding new server URL to database 'multilib': https://mirror.osbeck.com/archlinux/multilib/os/x86_64
:: Synchronizing package databases...
debug: url: http://ftp.acc.umu.se/mirror/archlinux/core/os/x86_64/core.db
debug: maxsize: 26214400
debug: using time condition: 1572373516
debug: opened tempfile for download: /var/lib/pacman/sync/core.db.part (wb)
debug: curl returned error 28 from transfer
error: failed retrieving file 'core.db' from ftp.acc.umu.se : Resolving timed out after 10000 milliseconds
debug: url: https://ftp.acc.umu.se/mirror/archlinux/core/os/x86_64/core.db
debug: maxsize: 26214400
debug: using time condition: 1572373516
debug: opened tempfile for download: /var/lib/pacman/sync/core.db.part (wb)
debug: curl returned error 28 from transfer
error: failed retrieving file 'core.db' from ftp.acc.umu.se : Resolving timed out after 10000 milliseconds

Interrupt signal received

Looks like an issue with DNS resolution inside the chroot.

Looking at the 0 sized files and pacman -Qkk output the linux-headers package is not shown as installed by pacman but the package contents is.

pacman --root=/mnt --dbonly -S linux-headers

Or you could try booting the installed system now.  See Pacman#Search_for_a_package_that_contains_a_specific_file to identify if a package owns the other 0 length files.

Offline

#40 2019-10-29 21:13:03

r00tr4t
Member
Registered: 2013-01-16
Posts: 101

Re: [solved] Error: failed retrieveing core.db: Resolve timeout.

I'm going to reboot the computer now and see if it works.

Offline

#41 2019-10-29 21:33:53

r00tr4t
Member
Registered: 2013-01-16
Posts: 101

Re: [solved] Error: failed retrieveing core.db: Resolve timeout.

:: running early hook(udev)
Warning /lib/modules/5.3.7-arch1-ARCH/modules.device not found - ignoring
Start version 243.51-1-arch
:: running hook (udev)
:: trigger events...
Waiting 10 seconds for device /dev/disk/by-partuid/db40a5e2-051d-4044-862a-2099e324db51...
ERROR device 'PARTUID= db40a5e2-051d-4044-862a-2099e324db51' not found. Skipping fuck.
:: mount  'PARTUID= db40a5e2-051d-4044-862a-2099e324db51' on real root
mount: /new_root: can't find 'PARTUID= db40a5e2-051d-4044-862a-2099e324db51'
You are now being dropped in to an emergency shell.
sh: can't access tty: job control turned off
(roots)#_

Not good!

Offline

#42 2019-10-29 21:40:40

loqs
Member
Registered: 2014-03-06
Posts: 19,098

Re: [solved] Error: failed retrieveing core.db: Resolve timeout.

Back to the installation media.  Make sure /boot is mounted as well as the root filesystem.
Chroot in then `pacman -S linux` then try again.

Offline

#43 2019-10-29 21:41:54

r00tr4t
Member
Registered: 2013-01-16
Posts: 101

Re: [solved] Error: failed retrieveing core.db: Resolve timeout.

Is modules.device loaded from UEFI?
No its a kernel module.

Offline

#44 2019-10-29 21:42:28

r00tr4t
Member
Registered: 2013-01-16
Posts: 101

Re: [solved] Error: failed retrieveing core.db: Resolve timeout.

Ok. I will try that.

Offline

#45 2019-10-29 22:23:22

r00tr4t
Member
Registered: 2013-01-16
Posts: 101

Re: [solved] Error: failed retrieveing core.db: Resolve timeout.

log I get a lot of modification time mismatch.
And the zero length files are still present .

Last edited by r00tr4t (2019-10-29 22:33:34)

Offline

#46 2019-10-29 22:32:26

loqs
Member
Registered: 2014-03-06
Posts: 19,098

Re: [solved] Error: failed retrieveing core.db: Resolve timeout.

backup file: filesystem: /etc/fstab (Modification time mismatch)

Modification of configuration files due to system configuration or use of the package is expected.

Offline

#47 2019-10-29 22:35:32

r00tr4t
Member
Registered: 2013-01-16
Posts: 101

Re: [solved] Error: failed retrieveing core.db: Resolve timeout.

I'm going to try a reboot now and see if it works.

Offline

#48 2019-10-29 22:53:36

r00tr4t
Member
Registered: 2013-01-16
Posts: 101

Re: [solved] Error: failed retrieveing core.db: Resolve timeout.

 :: running early hook(udev)
Warning /lib/modules/5.3.7-arch1-ARCH/modules.device not found - ignoring
Start version 243.51-1-arch
:: running hook (udev)
:: trigger events...
Waiting 10 seconds for device /dev/disk/by-partuid/db40a5e2-051d-4044-862a-2099e324db51...
ERROR device 'PARTUID= db40a5e2-051d-4044-862a-2099e324db51' not found. Skipping fuck.
:: mount  'PARTUID= db40a5e2-051d-4044-862a-2099e324db51' on real root
mount: /new_root: can't find 'PARTUID= db40a5e2-051d-4044-862a-2099e324db51'
You are now being dropped in to an emergency shell.
sh: can't access tty: job control turned off
(roots)#_

But I think I forgot to mount the UEFI partition last time.

Offline

#49 2019-10-29 23:00:06

r00tr4t
Member
Registered: 2013-01-16
Posts: 101

Re: [solved] Error: failed retrieveing core.db: Resolve timeout.

I am calling it for the day I'm back in about 9 hours. Thank you for your time today loqs, se you to morrow.

/MS

Offline

#50 2019-10-29 23:48:15

WorMzy
Administrator
From: Scotland
Registered: 2010-06-16
Posts: 13,678
Website

Re: [solved] Error: failed retrieveing core.db: Resolve timeout.

Please stop multiposting. If you are the last person to post in a thread, and you have something to add, please use the edit button to amend the last post.

Mod note: not an installation issue, moving to NC.


Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

Board footer

Powered by FluxBB