Plesk

Plesk update completes with a Warning: Information on some packages might not be actual: inconsistencies were detected in the system’s package manager database

Symptoms

Cause

There is a known glitch in the upgrade to grub-efi-amd64-signed and grub-efi-amd64-bin packages, where they both need to be upgraded, but they depend on each other and neither one of them wants to go first. This in turn creates issues with the package installers for Debian-based operating systems to hang and that prevents further package updates and upgrades form happening.

Resolution

Due to the importance of the related grub packages in connection with the server booting process, the recommended course of action is to contact your server provider or Linux administrator to solve the issue with system packages.

As an alternative solution to this issue, you may execute the following steps:

Warning: In certain conditions, these steps may make your server unable to boot, due to which you should take precautions and execute the steps below at your own risk

1. Log into your server via SSH

2. Execute the following command in order to get the updates for all system packages:

# apt update

3. Execute the following command in order to reinstall only the grub-efi-amd64-signed package:

# apt --only-upgrade install grub-efi-amd64-signed

4. Execute the following command in order to make sure the grub-efi-amd64-bin package is installed

# apt install grub-efi-amd64-bin

5. Now that the dependencies are resolved, execute the following command in order to upgrade all system packages:

# apt upgrade

6. The final step is to perform an update of all Plesk packages by executing the following command:

# plesk installer update

Additional information

apt - grub-efi-amd64-signed dependency issue in Ubuntu 22.04LTS - Ask Ubuntu

Fixing grub-efi-amd64-signed dependency issue in Ubuntu 22.04LTS | DeviceTests

System updates warning in Plesk: Information on some packages might not be actual: inconsistencies were detected in the system's package manager database. Please resolve this issue manually

Exit mobile version