Question about repeated requests to update 79 packages and restart the system

    • New
    Quote from barlowg

    Thank you. I have run the suggested commands and will see what happens.

    The thing that catches my eyes first is your kernel version and architecture:

    Quote from barlowg

    Processor ARMv7 Processor rev 3 (v7l)

    Kernel Linux 5.10.103-v7l+

    Latest RaspiOS kernel is 6.1.19 (on aarch64 but I believe the kernel is always on the same version for both architectures)

    Code
    pi@panela:~ $ uname -a
Linux panela 6.1.19-v8+ #1637 SMP PREEMPT Tue Mar 14 11:11:47 GMT 2023 aarch64 GNU/Linux


    I had a situation coming from OMV5 that the kernel was blocked on that same version of yours (didn't gave much thought since it was a peculiar system with BTRFS root drive with snapshots).


    Did you upgraded from OMV5 or is it a fresh Bullseye install?


    Can you post the output PRIOR to do the updates, each one on codeboxes (PLEASE) of:

    uname -a

    sudo apt list --upgradable

    sudo mount | grep vfat

    • New

    Hi,


    I an fairly sure this was an upgrade from omv5.


    Code
    pi@newnas:~ $ uname -a
Linux newnas 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l GNU/Linux
    Code
    pi@newnas:~ $ sudo apt list --upgradable
Listing... Done
    Code
    pi@newnas:~ $ sudo mount | grep vfat
/dev/sdc1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)

    Unfortunately, as previously posted, I have just run the suggested fixes and there is currently no updates required.

    • New
    Quote from barlowg

    I have just run the suggested fixes and there is currently no updates required.

    If it shows again, post the outputs I asked, please.

    Quote from barlowg

    I an fairly sure this was an upgrade from omv5.

    The issue with the kernel comes from the name of the kernel package it was used at the time, it had "buster" appended.

    With the release of Bullseye, the package "lost" the NAME to have only the version number.


    You can see what you have with:

    Code
    pi@panela:~ $ sudo apt-cache policy raspberrypi-kernel
raspberrypi-kernel:
  Installed: 1:1.20230317-1
  Candidate: 1:1.20230317-1
  Version table:
 *** 1:1.20230317-1 500
        500 http://archive.raspberrypi.org/debian bullseye/main arm64 Packages
        100 /var/lib/dpkg/status


    When you upgraded to OMV6 (my issue also), the version name wasn't updated and it remained on that version (5.10.103) since apt can't understand that the package is the same (with a latest version but without the version name).


    I solved the issue by doing a clean fresh install of RaspiOS Bullseye. (And it is what's recommended by Raspberry Foundation and OMV)

    Not saying that you need to do the same but you won't be able to update the kernel (and it's on a really old version) with a simple apt only.


    Might be possible to force install it but it might also break your system.


    DO THIS AT YOUR OWN RISK and be sure that you want to do it.

    If you want to test anything, make sure you have a FULLY WORKING CLONE of the OS DRIVE.

    This is only by memory and without any practical test so, accept it as it is.


    Maybe running rpi-update will fix it:

    rpi-update at DuckDuckGo


    OR

    sudo apt full-upgrade


    OR

    Downloading the 3 packages to your Pi and install them via dpkg:

    AGAIN, be absolutely sure you want to accept the risks.

    It might render your OS system non-functional unless you have a way to revert it.


    Good luck

    • New

    I just ran the policy command you provided to show the policy:

    Code
    pi@newnas:~ $ sudo apt-cache policy raspberrypi-kernel
raspberrypi-kernel:
  Installed: 1:1.20220308~buster-1
  Candidate: 1:1.20220308~buster-1
  Version table:
 *** 1:1.20220308~buster-1 500
        500 http://archive.raspberrypi.org/debian buster/main armhf Packages
        100 /var/lib/dpkg/status
pi@newnas:~ $
    • New
    Quote from barlowg

    raspberrypi-kernel:

    Installed: 1:1.20220308~buster-1

    This is what I was refering.

    Since apt won't see a kernel package with buster name on it, it won't update.

    • New

    My only concern with doing a "fresh install" is the fact my boot and OS is on USB-SSD.


    I am not sure how to go about it. Can anyone point me to a decent post/how-to guide?


    Also is there a way of saving (export) my existing OMV configuration so that I can load (import) it after the install?


    Regards


    Glyn

    • New
    Quote from barlowg

    Also is there a way of saving (export) my existing OMV configuration so that I can load (import) it after the install?


    R

    No, not posible

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login