Beiträge von szech

    i was in the same boat as OP.


    i used wget to manually download replacements of the troublesome keys and install them with $ gpg --import my_fresh.gpg


    then the steps in post #8, and the update management in the admin UI worked without any errors.

    I had exactly this issue.

    Couldn't even run the updater in the omv web interface without an error.


    In my case i fixed it by removing all the smb integrations, all the references in the omv interface (virus scan, shared folders, SMART schedules etc etc), unmounted the file systems and finally the drives themselves.


    Then i restarted the system with the media drives unplugged, and was able to run the updater.

    I also removed any reference to media disks in the omv interface so there is just the system disks.


    Then i shut down and plugged the drives back in, and remounted all the filesystems and restored all the integrations.


    This fixed the issue.


    I suspect it was caused by omv having stale entries in its database, so its expecting drives to exist in /srv/ that are no longer there.


    Doing this was less work than re-installing and rebuilding from scratch, so its worth a try imo.