Post apt upgrade script

  • Hello...

    I recently updated to OMV5 as my last build was slowly compounding errors..

    Anyways.. I updated packages today (2020-04-21) via SSH and the terminal said to run a particular script after completion... I thought I had copied the script name to the clipboard but when the upgrade finished and the cli gui cleared I discovered I had an empty clip/buffer.

    Does anyone know what script it was that I was supposed to run a manual of after the update? I remember something about db something or other?? But not much else...


    Cheers,


    M

    • Offizieller Beitrag

    Are you referring to this one? RE: OMV 5.0 - finally out! :-)

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • No thats not it... I did a clean OMV5 install which went really well once I straightened out my Plex DB restore (mucked up the pathing)..

    It happened somewhere during this apt update / apt upgrade cycle...


    2020-04-21 08:36:58 status installed openmediavault:all 5.4.0-1

    2020-04-21 08:36:58 status triggers-pending openmediavault:all 5.4.0-1

    2020-04-21 08:36:58 status triggers-awaited openmediavault:all 5.4.0-1

    2020-04-21 08:36:58 configure git:amd64 1:2.20.1-2+deb10u3 <none>

    2020-04-21 08:36:58 status unpacked git:amd64 1:2.20.1-2+deb10u3

    2020-04-21 08:36:58 status half-configured git:amd64 1:2.20.1-2+deb10u3

    2020-04-21 08:36:58 status installed git:amd64 1:2.20.1-2+deb10u3

    2020-04-21 08:36:58 trigproc rsyslog:amd64 8.1901.0-1 <none>

    2020-04-21 08:36:58 status half-configured rsyslog:amd64 8.1901.0-1

    2020-04-21 08:36:59 status installed rsyslog:amd64 8.1901.0-1

    2020-04-21 08:36:59 trigproc openmediavault:all 5.4.0-1 <none>

    2020-04-21 08:36:59 status half-configured openmediavault:all 5.4.0-1

    2020-04-21 08:37:00 status installed openmediavault:all 5.4.0-1

    2020-04-21 08:37:00 configure openmediavault-omvextrasorg:all 5.3 <none>

    2020-04-21 08:37:00 status triggers-pending openmediavault:all 5.4.0-1

    2020-04-21 08:37:00 status unpacked openmediavault-omvextrasorg:all 5.3

    2020-04-21 08:37:00 status half-configured openmediavault-omvextrasorg:all 5.3

    2020-04-21 08:37:03 status triggers-awaited openmediavault-omvextrasorg:all 5.3

    2020-04-21 08:37:03 configure openmediavault-nut:all 5.1.0-1 <none>

    2020-04-21 08:37:03 status unpacked openmediavault-nut:all 5.1.0-1

    2020-04-21 08:37:03 status half-configured openmediavault-nut:all 5.1.0-1

    2020-04-21 08:37:03 status triggers-awaited openmediavault-nut:all 5.1.0-1

    2020-04-21 08:37:03 trigproc openmediavault:all 5.4.0-1 <none>

    2020-04-21 08:37:03 status half-configured openmediavault:all 5.4.0-1

    2020-04-21 08:37:03 status installed openmediavault-nut:all 5.1.0-1

    2020-04-21 08:37:03 status installed openmediavault-omvextrasorg:all 5.3

    2020-04-21 08:37:05 status installed openmediavault:all 5.4.0-1


    But damned if I know which package / installer script brought up the prompt...

  • Was it by any chance "omv-confdbadm populate"?

    I ran into that one today.


    Edit:

    I also ran into problems with the script: /usr/share/openmediavault/confdb/create.d/conf.system.omvextras.sh

    It didn't like the command "omv-grubiso", giving error "Unsupported architecture." After I commented it out, I could finish the upgrade.

    • Offizieller Beitrag

    also ran into problems with the script: /usr/share/openmediavault/confdb/create.d/conf.system.omvextras.sh

    It didn't like the command "omv-grubiso", giving error "Unsupported architecture." After I commented it out, I could finish the upgrade.

    What kind of system? omv-grubiso should only run on systems where it finds the update-grub command (should not exist on unsupported arches like arm).

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • What kind of system? omv-grubiso should only run on systems where it finds the update-grub command (should not exist on unsupported arches like arm).

    On a Raspberry Pi 4B, I saw the if and apparently it was satisfied. As I already wrote, commenting out those three lines solved the problem. And I don't know how omv-grubiso came to reside on it, will look into removing it.

    EDIT:

    Checked, saw both update-grub and update-grub2 in /usr/sbin.

    • Offizieller Beitrag

    On a Raspberry Pi 4B, I saw the if and apparently it was satisfied. As I already wrote, commenting out those three lines solved the problem. And I don't know how omv-grubiso came to reside on it, will look into removing it.

    EDIT:

    Checked, saw both update-grub and update-grub2 in /usr/sbin.

    I know commenting out the lines "fixes" your system but grub should never be installed on an RPi. What is the output of: dpkg -l | grep grub omv-grubiso is installed by omv-extras. I guess I could make it exit without error but I really want to know why/how grub is installed.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • I know commenting out the lines "fixes" your system but grub should never be installed on an RPi. What is the output of: dpkg -l | grep grub omv-grubiso is installed by omv-extras. I guess I could make it exit without error but I really want to know why/how grub is installed.

    It was:

    Code
    ii  grub-common                         2.02+dfsg1-20                       armhf        GRand Unified Bootloader (common files)
    ii  grub2-common                        2.02+dfsg1-20                       armhf        GRand Unified Bootloader (common files for version 2)

    Gone after: apt remove grub-common grub2-common


    EDIT:

    No, I don't know how it came to be on my system, but it was removed before you gave your reply.

    • Offizieller Beitrag

    Curious why it was installed. I changed omv-extras as well - https://github.com/OpenMediaVa…d7a45513ec68d0d9ee9d3d329 - but I'm not going to push out a new release. So, it will be out with the next release.

  • Curious why it was installed. I changed omv-extras as well - https://github.com/OpenMediaVa…d7a45513ec68d0d9ee9d3d329 - but I'm not going to push out a new release. So, it will be out with the next release.

    Looks good, but I would code the change a level higher, checking both for the presence of update-grub and the correct architecture.

    Yes, I am a programmer, different system (AS/400) and language (CLP, COBOL, RPG and RPGLE), but I can read this code by now.


    EDIT:

    FYI: Just checked my RPi 3b+ and grub seems to be there to:

    Code
    ii  grub-common                         2.02~beta3-5+deb9u2
    ii  grub2-common                        2.02~beta3-5+deb9u2
    • Offizieller Beitrag

    but I would code the change a level higher, checking both for the presence of update-grub and the correct architecture.

    I know but I made it quick. Maybe I will add the extra check when I get a chance. The arch test needs to stay in omv-grubiso in case someone runs it from the command line though.

    FYI: Just checked my RPi 3b+ and grub seems to be there to:

    Not sure why. I have and RPi2,3, and 4 running and none of them have it. The omv-extras script has been this way for a long time (at least six months) without issues. So, I think you have a unique case where something you are doing is installing grub-common.

    • Offizieller Beitrag

    Update instructions updated too.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!