Failed update to Linux Mint 21.1

[w6jve]

I have a related question

I tried to upgrade from 21 to 21.1 using the update manager. There were some errors about
unable to access repositories, so I tried to abort the upgrade. Now when I try to start it again
it seems to think the upgrade has already been done. The update manager doesn't show
the upgrade. System Information says it is Linux Mint 21.1 Vera which it can't be since the
upgrade was not done.

[kato181]

w6jve,
Please do not cross post. If you need help then please start your own thread. Your problem is unrelated to the OP question. Try the following if you have a timeshift snapshot.
Boot into your live session usb and do a timeshift system restore, it will return your system to the latest working system.
You should refrain from aborting an upgrade as you may well bork the system, and make in unbootable.
Read the following before trying again..
https://linuxmint-user-guide.readthedoc ... nt-21.html

[w6jve]

Since the system is working, just confused about its own version, I think I'll just
leave it as is and wait for the next update.

I was hoping there was some file containing the "21.1" that could just be removed or edited so
the upgrade could be started over.

[SMG]

Since the system is working, just confused about its own version, I think I'll just
leave it as is and wait for the next update.

There is no next update if you do not have this one working properly.

Please open the System Reports app and click the System Information tab on the left. Your computer's information should come up in the right pane. Then click Copy, and paste the results into a reply window here so we can see how Linux Mint views your hardware.

[w6jve]

Thanks. Here's what I got

Code: Select all

System:
  Kernel: 5.15.0-56-generic x86_64 bits: 64 compiler: gcc v: 11.3.0 Desktop: Cinnamon 5.6.5
    tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy
Machine:
  Type: Laptop System: Dell product: OptiPlex 760 v: N/A serial: <superuser required> Chassis:
    type: 16 serial: <superuser required>
  Mobo: Dell model: 0G919G v: A00 serial: <superuser required> BIOS: Dell v: A16
    date: 08/06/2013
CPU:
  Info: dual core model: Intel Core2 Duo E8500 bits: 64 type: MCP arch: Core Yorkfield rev: A
    cache: L1: 128 KiB L2: 6 MiB
  Speed (MHz): avg: 3159 min/max: N/A cores: 1: 3159 2: 3159 bogomips: 12635
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 ssse3
Graphics:
  Device-1: Intel 4 Series Integrated Graphics vendor: Dell driver: i915 v: kernel ports:
    active: HDMI-A-2 empty: DP-1, DP-2, HDMI-A-1, VGA-1 bus-ID: 00:02.0 chip-ID: 8086:2e12
  Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting unloaded: fbdev,vesa
    gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1400x1050 s-dpi: 96
  Monitor-1: HDMI-2 mapped: HDMI-A-2 model: L2046NV res: 1400x1050 dpi: 87 diag: 510mm (20.1")
  OpenGL: renderer: Mesa Intel Q45/Q43 (ELK) v: 2.1 Mesa 22.0.5 direct render: Yes
Audio:
  Device-1: Intel 82801JD/DO HD Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
    chip-ID: 8086:3a6e
  Device-2: Logitech Headset H390 type: USB driver: hid-generic,snd-usb-audio,usbhid
    bus-ID: 8-2:2 chip-ID: 046d:0a44
  Sound Server-1: ALSA v: k5.15.0-56-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Intel 82567LM-3 Gigabit Network vendor: Dell driver: e1000e v: kernel port: ece0
    bus-ID: 00:19.0 chip-ID: 8086:10de
  IF: enp0s25 state: up speed: 100 Mbps duplex: full mac: <filter>
  Device-2: Edimax EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS] type: USB
    driver: rtl8192cu bus-ID: 1-3:4 chip-ID: 7392:7811
  IF: wlx74da38aecc98 state: up mac: <filter>
Drives:
  Local Storage: total: 153.39 GiB used: 18.32 GiB (11.9%)
  ID-1: /dev/sda vendor: Western Digital model: WD1601ABYS-01C0A0 size: 153.39 GiB
    speed: 3.0 Gb/s serial: <filter>
Partition:
  ID-1: / size: 45.52 GiB used: 18.32 GiB (40.2%) fs: ext4 dev: /dev/sda7
Swap:
  ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda5
USB:
  Hub-1: 1-0:1 info: Full speed or root hub ports: 6 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002
  Device-1: 1-3:4 info: Edimax EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]
    type: Network driver: rtl8192cu rev: 2.0 speed: 480 Mb/s chip-ID: 7392:7811
  Hub-2: 2-0:1 info: Full speed or root hub ports: 6 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002
  Hub-3: 3-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
  Device-1: 3-1:2 info: Logitech Optical Wheel Mouse type: Mouse driver: hid-generic,usbhid
    rev: 2.0 speed: 1.5 Mb/s chip-ID: 046d:c018
  Device-2: 3-2:3 info: Cherry GmbH Keyboard type: Keyboard driver: hid-generic,usbhid rev: 1.0
    speed: 1.5 Mb/s chip-ID: 046a:0001
  Hub-4: 4-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
  Hub-5: 5-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
  Hub-6: 6-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
  Hub-7: 7-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
  Device-1: 7-2:2 info: Future Devices FT232 Serial (UART) IC type: <vendor specific>
    driver: ftdi_sio,gpio_stub_drv rev: 2.0 speed: 12 Mb/s chip-ID: 0403:6001
  Hub-8: 8-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
  Device-1: 8-2:2 info: Logitech Headset H390 type: Audio,HID
    driver: hid-generic,snd-usb-audio,usbhid rev: 1.1 speed: 12 Mb/s chip-ID: 046d:0a44
Sensors:
  System Temperatures: cpu: 40.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: apt: 2636
  Active apt repos in: /etc/apt/sources.list
    1: deb http: //us.archive.ubuntu.com/ubuntu/ yakkety universe
  Active apt repos in: /etc/apt/sources.list.d/additional-repositories.list
    1: deb http: //security.ubuntu.com/ubuntu xenial-security main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb http: //packages.linuxmint.com vera main upstream import backport
    2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
    3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
    4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
    5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
Info:
  Processes: 189 Uptime: 4h 11m Memory: 3.67 GiB used: 1.78 GiB (48.3%) Init: systemd v: 249
  runlevel: 5 Compilers: gcc: 11.3.0 alt: 11/9 clang: 14.0.0-1ubuntu1
  Client: Unknown python3.10 client inxi: 3.3.13

[SMG]

Thanks. Here's what I got

System:
Kernel: 5.15.0-56-generic x86_64 bits: 64 compiler: gcc v: 11.3.0 Desktop: Cinnamon 5.6.5
tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy

This looks to me like your update happened. Not only is it showing as Linux Mint 21.1, but you also have the Cinnamon 5.6.5 which is only available in LM21.1.

You also have the vera repo.

Code: Select all

    1: deb http: //packages.linuxmint.com vera main upstream import backport

This looks like the update succeeded. Is there some indication you have on your system that all of it may not have completed? If so, please give us details.

[w6jve]

Well I assumed it had failed because there were those error messages about repositories that could not be
contacted and I tried to kill the updater and there was not very much time expended. Maybe it went on in the
background. Now I just tried running the update manager and told it to refresh and here is what has come
back so far.

Could not download all repository indexes

The repository may no longer be available or could not be contacted because of network problems. If available an older version of the failed index will be used. Otherwise the repository will be ignored. Check your network connection and ensure the repository address in the preferences is correct.
The repository 'http://us.archive.ubuntu.com/ubuntu yakkety Release' does not have a Release file.Updating from such a repository can't be done securely, and is therefore disabled by default.See apt-secure(8) manpage for repository creation and user configuration details.GPG error: http://security.ubuntu.com/ubuntu xenial-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32The repository 'http://security.ubuntu.com/ubuntu xenial-security InRelease' is not signed.



After that it said the system is up to date.

[SMG]

Well I assumed it had failed because there were those error messages about repositories that could not be
contacted and I tried to kill the updater and there was not very much time expended.

If they were the same messages you just posted, they state they did not stop the process. The process continued and apparently finished.

Now I just tried running the update manager and told it to refresh and here is what has come
back so far.

Could not download all repository indexes

This is the repo section from your inxi output.

Code: Select all

Repos:
  Packages: apt: 2636
  Active apt repos in: /etc/apt/sources.list
    1: deb http: //us.archive.ubuntu.com/ubuntu/ yakkety universe
  Active apt repos in: /etc/apt/sources.list.d/additional-repositories.list
    1: deb http: //security.ubuntu.com/ubuntu xenial-security main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb http: //packages.linuxmint.com vera main upstream import backport
    2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
    3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
    4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
    5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse

The repository may no longer be available or could not be contacted because of network problems. If available an older version of the failed index will be used. Otherwise the repository will be ignored.

This means the process is not stopped.

The repository 'http://us.archive.ubuntu.com/ubuntu yakkety Release' does not have a Release file.Updating from such a repository can't be done securely, and is therefore disabled by default.

yakkety was Ubuntu 16.10 and it is the first active repo in the list above. You are currently running LM21 which is based on Ubuntu 22.04 jammy so I'm not sure why you have an Ubuntu 16.10 repository.

GPG error: http://security.ubuntu.com/ubuntu xenial-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32The repository 'http://security.ubuntu.com/ubuntu xenial-security InRelease' is not signed.

xenial was Ubuntu 16.04 and it is the second active repo in your list above. I have seen many people still using signal from xenial, but I don't know if that is why you have it in your list.