Can I track down and reverse certain recent updates?

[ajgreeny]

To be doubly sure what you are currently running let's see the output of command

lsb_release -a

[deadflowr]

What do your /etc/apt/sources.list show?

FTR this shows upgraded packages

/var/log/dpkg.log:2021-09-27 17:14:56 upgrade ipxe-qemu:all 1.0.0+git-20180124.fbe8c52d-0ubuntu2.2 1.0.0+git-20190109.133f4c4-0ubuntu3.2
/var/log/dpkg.log:2021-09-27 17:14:56 upgrade ipxe-qemu-256k-compat-efi-roms:all 1.0.0+git-20150424.a25a16d-0ubuntu2 1.0.0+git-20150424.a25a16d-0ubuntu4
/var/log/dpkg.log:2021-09-27 17:16:00 upgrade qemu:amd64 1:2.11+dfsg-1ubuntu7.37 1:4.2-3ubuntu6.17
/var/log/dpkg.log:2021-09-27 17:16:00 upgrade qemu-system-common:amd64 1:2.11+dfsg-1ubuntu7.37 1:4.2-3ubuntu6.17
/var/log/dpkg.log:2021-09-27 17:16:02 upgrade qemu-utils:amd64 1:2.11+dfsg-1ubuntu7.37 1:4.2-3ubuntu6.17
/var/log/dpkg.log:2021-09-27 17:16:02 upgrade qemu-block-extra:amd64 1:2.11+dfsg-1ubuntu7.37 1:4.2-3ubuntu6.17
/var/log/dpkg.log:2021-09-27 17:16:03 upgrade qemu-system:amd64 1:2.11+dfsg-1ubuntu7.37 1:4.2-3ubuntu6.17
/var/log/dpkg.log:2021-09-27 17:16:03 upgrade qemu-user-binfmt:amd64 1:2.11+dfsg-1ubuntu7.37 1:4.2-3ubuntu6.17
/var/log/dpkg.log:2021-09-27 17:16:03 upgrade qemu-user:amd64 1:2.11+dfsg-1ubuntu7.37 1:4.2-3ubuntu6.17
/var/log/dpkg.log:2021-09-27 17:16:14 upgrade qemu-slof:all 20170724+dfsg-1ubuntu1 20191209+dfsg-1

The bolded strings are focal packages, which s what it upgraded those to.

[Heeter]

Thank you for your help guys:

root@serv:/home/adminpc# lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.3 LTS
Release:	20.04
Codename:	focal
root@serv:/home/adminpc#

root@serv:/home/adminpc# cat /etc/apt/sources.list
# 

# deb cdrom:[Ubuntu-Server 18.04.3 LTS _Bionic Beaver_ - Release amd64 (20190805)]/ bionic main restricted

# deb cdrom:[Ubuntu-Server 18.04.3 LTS _Bionic Beaver_ - Release amd64 (20190805)]/ bionic main restricted

# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://ca.archive.ubuntu.com/ubuntu/ focal main restricted
# deb-src http://ca.archive.ubuntu.com/ubuntu/ bionic main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://ca.archive.ubuntu.com/ubuntu/ focal-updates main restricted
# deb-src http://ca.archive.ubuntu.com/ubuntu/ bionic-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://ca.archive.ubuntu.com/ubuntu/ focal universe
# deb-src http://ca.archive.ubuntu.com/ubuntu/ bionic universe
deb http://ca.archive.ubuntu.com/ubuntu/ focal-updates universe
# deb-src http://ca.archive.ubuntu.com/ubuntu/ bionic-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu 
## team, and may not be under a free licence. Please satisfy yourself as to 
## your rights to use the software. Also, please note that software in 
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://ca.archive.ubuntu.com/ubuntu/ focal multiverse
# deb-src http://ca.archive.ubuntu.com/ubuntu/ bionic multiverse
deb http://ca.archive.ubuntu.com/ubuntu/ focal-updates multiverse
# deb-src http://ca.archive.ubuntu.com/ubuntu/ bionic-updates multiverse

## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://ca.archive.ubuntu.com/ubuntu/ focal-backports main restricted universe multiverse
# deb-src http://ca.archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse

## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
# deb http://archive.canonical.com/ubuntu bionic partner
# deb-src http://archive.canonical.com/ubuntu bionic partner

deb http://security.ubuntu.com/ubuntu focal-security main restricted
# deb-src http://security.ubuntu.com/ubuntu bionic-security main restricted
deb http://security.ubuntu.com/ubuntu focal-security universe
# deb-src http://security.ubuntu.com/ubuntu bionic-security universe
deb http://security.ubuntu.com/ubuntu focal-security multiverse
# deb-src http://security.ubuntu.com/ubuntu bionic-security multiverse
root@serv:/home/adminpc#

Regards and thank you guys again.

[TheFu]

Appears you have a 50% 18.04 system and a 50% 20.04 system.
Something isn't right.

I'd pave the road and start fresh. "I say we take off and nuke the entire site from orbit. It's the only way to be sure.”

[ajgreeny]

Appears you have a 50% 18.04 system and a 50% 20.04 system.
Something isn't right.

I'd pave the road and start fresh. "I say we take off and nuke the entire site from orbit. It's the only way to be sure.”

Hmm!
Not sure that's correct. The active lines in your sources are all for focal and all the bionic lines and repos are commented out so I'm really baffled.
However, a new clean start may solve your problems.

I've never upgraded from version to version of my systems so can not really help much more with potential difficulties of version upgrades.

[TheFu]

Hmm!
Not sure that's correct. The active lines in your sources are all for focal and all the bionic lines and repos are commented out so I'm really baffled.
However, a new clean start may solve your problems.

I've never upgraded from version to version of my systems so can not really help much more with potential difficulties of version upgrades.

I could be confusing Heeter's system with another post here that was all 18.04 the last 7 days.

I've upgraded a KVM host from 10.04 --> 12.04 --> 16.04 --> 18.04 without many issues. Newer KVM/libvirt machine types still support the older machine types. That host has been losing VMs the last 2+ yrs, since newer hardware on another system is 10x faster and has 2x more RAM. That other system was loaded with 18.04 and is still running it. For example, so systems:

<type arch='x86_64' machine='pc-i440fx-trusty'>hvm</type>
<type arch='x86_64' machine='pc-i440fx-xenial'>hvm</type>
<type arch='x86_64' machine='pc-i440fx-xenial'>hvm</type>
<type arch='x86_64' machine='pc-i440fx-trusty'>hvm</type>
<type arch='x86_64' machine='pc-i440fx-trusty'>hvm</type>
<type arch='x86_64' machine='pc-i440fx-xenial'>hvm</type>
<type arch='x86_64' machine='pc-1.0'>hvm</type>
<type arch='x86_64' machine='pc-i440fx-xenial'>hvm</type>
<type arch='x86_64' machine='pc-i440fx-xenial'>hvm</type>

The pc-1.0 is actually a Xen VM which I migrated from 2008 Xen to KVM in 2010-ish.
Oddly, I don't have any newer VMs, since I cleaned up all the play VMs for 21.04 a few days ago.

Hummmmm. There's a bug: https://bugs.launchpad.net/ubuntu/+s...t/+bug/1902654
There is some information in the bug about keyboards and console types when a VM is migrated to pc-i440fx-wily .... hummmmmm.
Basically, VMs don't like when the hypervisor goes from 18.04 --> 20.04 or later.

[Heeter]

Hey Guys,

Cannot thank you enough for all your input. I really do appreciate for all your quick responses. Means a lot right now, as I don't have too much time to get the mailserver running.

Is there someway that I can try to just upgrade to 20LTS from this?

Just need to get the VMs backup for a couple of days until I can make a plan on fresh install. Need to anyways, the LVM partitioning on this setup needs to be rethought out too.

Regards

[TheFu]

be sure to read the bug in my last post. 20.04 could make you have to create a new VM and reload the OS for the mailserver. No upgrade.

[Heeter]

be sure to read the bug in my last post. 20.04 could make you have to create a new VM and reload the OS for the mailserver. No upgrade.

Thank you Fu. Ugh, I misread the bug. I thought that by upgrading, that It would fix it. Good thing that you mentioned that.





If any of you can assist me directly, please pm me,

[ajgreeny]

Hey Guys,

<snip>

Is there someway that I can try to just upgrade to 20LTS from this?

Just need to get the VMs backup for a couple of days until I can make a plan on fresh install. Need to anyways, the LVM partitioning on this setup needs to be rethought out too.

Regards

From the terminal output you showed us

root@serv:/home/adminpc# lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.3 LTS
Release:	20.04
Codename:	focal

it appears that you are already using 20.04, the latest LTS version available, so your inability to boot the VMs is not related to that, unless it is a symptom of moving from 18.04 to 20.04 at some point in the past.
Do you know when you upgraded, or is that all hidden in a mysterious past that you can't remember?