Why is the fix7to8upgrade script sometimes required for plugins?

  • I was upgrading two machines from 7 to 8; omv-extras was installed on them.

    On one machine, an error popped up regarding ‘HDD Fan Control’.

    The system booted up after a restart, but when I tried to log in via the web GUI, I got a ‘502 – Bad Gateway’ error; even changing the password via SSH using omv-firstaid didn’t help.

    I found this on the forum: RE: OMV7 to OMV8 Bad Gateway 502

    Code
    wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/fix7to8upgrade | sudo bash

    As far as I can tell, this is from omv-extras.


    Why was this required on one machine but not on the other, given that it worked fine on the other one?


    Translated with DeepL.com (free version)

    • Official Post

    As far as I can tell, this is from omv-extras.

    I wrote it but it isn't really for omv-extras.

    Why was this required on one machine but not on the other, given that it worked fine on the other one?

    Because the upgrade didn't go perfect. The script is just fixing the common failures.

    omv 8.5.8-1 synchrony | 7.0 proxmox kernel

    plugins:

    omvextrasorg 8.0.3 | kvm 8.3.2 | compose 8.1.24 | cterm 8.0.3 | borgbackup 8.2.1 | tempmon 8.0.5 |

    mergerfs 8.0.2 | scripts 8.0.6 | writecache 8.2.4 | backup 8.1 | kernel 8.0.16


    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!

  • Now there's a problem with the machine.

    I can't install K8s.

    • Official Post

    the hddfanctrl plugin is having problems. I would remove it and then maybe try reinstalling it. That isn't a plugin I maintain.

    omv 8.5.8-1 synchrony | 7.0 proxmox kernel

    plugins:

    omvextrasorg 8.0.3 | kvm 8.3.2 | compose 8.1.24 | cterm 8.0.3 | borgbackup 8.2.1 | tempmon 8.0.5 |

    mergerfs 8.0.2 | scripts 8.0.6 | writecache 8.2.4 | backup 8.1 | kernel 8.0.16


    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!

    • Official Post

    So K8s installed, but the terminal was throwing up an error about hddfanctrl?

    yes


    Does hddfanctrl work with OMV 8?

    As I said, I don't maintain it or use it but I was told it did work with omv8. That is why it is in the omv8 repo.

    omv 8.5.8-1 synchrony | 7.0 proxmox kernel

    plugins:

    omvextrasorg 8.0.3 | kvm 8.3.2 | compose 8.1.24 | cterm 8.0.3 | borgbackup 8.2.1 | tempmon 8.0.5 |

    mergerfs 8.0.2 | scripts 8.0.6 | writecache 8.2.4 | backup 8.1 | kernel 8.0.16


    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!

  • szymon1051

    Added the Label resolved
  • Want to try to upgrade my rpi4 4GB (OS on SSD). Will take down all composer containers before, and then...


    sudo omv-upgrade

    sudo omv-release-upgrade

    running the script


    Is this the correct order? Do i have to disable flashmemory plugin before?

    OMV 7.x | RPi 2 Mod.B V1.1 | Sandisk Extreme Pro microSD 32 GB | 3x WD7500BEKT
    OMV 8.x | RPi 3 Mod.B | OS, Memory extension, docker on SSD each
    OMV 8.x | RPi 4 B 4GB | OS, docker on SSD each

    • New
    • Official Post

    Is this the correct order?

    omv-release-upgrade runs omv-upgrade. so, no reason to do that. Backup before running.


    Do i have to disable flashmemory plugin before?

    No. The upgrade will automatically move your system to openmediavault-writecache.

    omv 8.5.8-1 synchrony | 7.0 proxmox kernel

    plugins:

    omvextrasorg 8.0.3 | kvm 8.3.2 | compose 8.1.24 | cterm 8.0.3 | borgbackup 8.2.1 | tempmon 8.0.5 |

    mergerfs 8.0.2 | scripts 8.0.6 | writecache 8.2.4 | backup 8.1 | kernel 8.0.16


    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!

  • And your script? After or before rebooting, when omv-release-upgrade has finished?

    OMV 7.x | RPi 2 Mod.B V1.1 | Sandisk Extreme Pro microSD 32 GB | 3x WD7500BEKT
    OMV 8.x | RPi 3 Mod.B | OS, Memory extension, docker on SSD each
    OMV 8.x | RPi 4 B 4GB | OS, docker on SSD each

    • New
    • Official Post

    And your script? After or before rebooting, when omv-release-upgrade has finished?

    Depends on if something goes wrong. it won't hurt to run but if the upgrade goes well, it isn't needed. post the output of omv-release-upgrade before rebooting if you are worried about it.

    omv 8.5.8-1 synchrony | 7.0 proxmox kernel

    plugins:

    omvextrasorg 8.0.3 | kvm 8.3.2 | compose 8.1.24 | cterm 8.0.3 | borgbackup 8.2.1 | tempmon 8.0.5 |

    mergerfs 8.0.2 | scripts 8.0.6 | writecache 8.2.4 | backup 8.1 | kernel 8.0.16


    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!

  • Seems, everything went fine. Thank you.


    P.S.: Rpi3B as well, even without running the script

    OMV 7.x | RPi 2 Mod.B V1.1 | Sandisk Extreme Pro microSD 32 GB | 3x WD7500BEKT
    OMV 8.x | RPi 3 Mod.B | OS, Memory extension, docker on SSD each
    OMV 8.x | RPi 4 B 4GB | OS, docker on SSD each

    Edited once, last by KlausR ().

Participate now!

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