Upgrade from Debian 10 w/ OMV 5 to Debian 11 w/ OMV 6

  • Desktop environments can be uninstalled...

    Is there an optimal way to do it?

    I tried apt remove task-desktop but I feel is going to remove too much stuff. especially python modules...


    The openmediavault package is removed. You might be able to reinstall it but you have quite the mess. sudo apt-get install openmediavault Running the fix script won't hurt either.

    I'll try, otherwise I'll restore from the backup.


    With the fix script you mean omv-firstaid?

    • Offizieller Beitrag

    With the fix script you mean omv-firstaid?

    No. The fix5to6upgrade script- https://github.com/OpenMediaVa…-Developers/installScript

    Is there an optimal way to do it?

    Depends on the desktop environment that is installed. If you have xfce installed, sudo apt-get purge --autoremove xfce* It should remove dependencies of omv with that command but double check the list of packages it is going to remove.

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.5


    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!

    • Offizieller Beitrag

    You can disable it with tasksel (fal present)

    and apt autoremove

    That is like a bull in a china shop. Just have to be careful it doesn't remove something OMV needs which would uninstall OMV.

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.5


    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 managed to continue the upgrade with fix broken dependencies.

    I've also removed all desktop environments, purging xfce also removed something from openmediavault.


    Now it's done but I get 502 Bad Gateway when I try to login.


    Running the fix script ends with:



    I'm trying to understand what is still missing.

    I had to unmask with systemctl the openmediavault-* services.

    • Offizieller Beitrag

    What is the output of: dpkg -l | grep openme

    Did you try omv-firstaid?

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.5


    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!

  • omv-firstaid did not help

    the fix5to6upgrade script did help


    what did the magic at the end was


    sudo omv-salt stage run deploy


    now I'm the WebUI and seems to work pretty well...


    I'm installing the Proxmox 5.15 Kernel right now!

    (the update did not update the PGP for the bullseye rep, I had to do it manually)


    The only stain is omv-aptclean:


    8. Updating plugin index...

    /usr/sbin/omv-aptclean: 50: /usr/sbin/omv-mkaptidx: not found


    Is this ab-normal?


    What is the output of: dpkg -l | grep openme

    • Offizieller Beitrag

    Is this ab-normal?

    yep. To fix: RE: OMV 5 to OMV 6 upgrade issue

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.5


    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!

  • yep. To fix: RE: OMV 5 to OMV 6 upgrade issue

    Fantastic...


    The most resilient upgrade script I've ever seen :P

    I never thought it could end well.


    I get sometimes a 504 error:



    But then retrying the same action works fine.

    Should I be worried?

    Don't see any messages in daemon or syslog


    Unfortunately the Proxmox 5.15 kernel is unstable for me :(


    Like many earlier it has some issue with the AMD SATA controller:



    Which results in a single port out of 8 having issues...


    And also has some issue with the Marvell NIC driver:

    Code
    [   10.596675] UBSAN: array-index-out-of-bounds in drivers/net/ethernet/aquantia/atlantic/aq_nic.c:1262:48
    [   10.596691] index 8 is out of range for type 'aq_vec_s *[8]'
    • Offizieller Beitrag

    But then retrying the same action works fine.

    Should I be worried?

    I'm guessing that is caused by your disk errors. Otherwise, what kind of media is the OS installed on?

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.5


    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'm guessing that is caused by your disk errors. Otherwise, what kind of media is the OS installed on?

    I think I got it also while running the 5.11 Kernel but now I'm not so so sure...

    Let me see if it happens again.


    The system is running on another disk, M.2 PCIe.

    That was my new media array, 50TB Raid5.

    But there's no real disk error... I had another 6TB Raid5 on those ports and I had the same errors with the same port with another Disk and other SATA cables...

    It's a weird effect of some obscure bug in the kernel...

    The vanilla 5.10 and Proxmox 5.11 are running just perfect.

    I had to boot a couple dozen times with Proxmox 4.x kernels to find one that would work...

    • Offizieller Beitrag

    I had to boot a couple dozen times with Proxmox 4.x kernels to find one that would work...

    Sounds like buggy or obscure hardware. What kind of board is it?

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.5


    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!

    • Offizieller Beitrag

    I would call that bleeding edge hardware in the server world.

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.5


    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 would call that bleeding edge hardware in the server world.

    Indeed.

    Not a big issue, it's manageable at the end.


    Seems to work really well so far!


    Didn't get again the error 504 so it was probably the kernel.


    I have one last issue that I'm struggling to fix...


    After the upgrade the NICs got a couple of IPs in dhcp.

    And it doesn't seem I can't remove them...


    In OMV GUI they are set with 2 static IPs.

    And also ifconfig shows only the 2 static IPS;


    enp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

    inet 192.168.178.2 netmask 255.255.255.0 broadcast 192.168.178.255

    ether 24:5e:be:65:4f:b4 txqueuelen 1000 (Ethernet)

    RX packets 58653 bytes 33821235 (32.2 MiB)

    RX errors 0 dropped 0 overruns 0 frame 0

    TX packets 9400 bytes 949525 (927.2 KiB)

    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


    enp5s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

    inet 192.168.178.3 netmask 255.255.255.0 broadcast 192.168.178.255

    ether a8:a1:59:58:1f:05 txqueuelen 1000 (Ethernet)

    RX packets 109262 bytes 19987541 (19.0 MiB)

    RX errors 0 dropped 0 overruns 0 frame 0

    TX packets 242624 bytes 314669182 (300.0 MiB)

    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    device memory 0xfc600000-fc61ffff


    I thought they were removed but then the UrBackup client connected to the server using the ip 192.168.178.44


    And indeed with ip address:


    2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000

    link/ether a8:a1:59:58:1f:05 brd ff:ff:ff:ff:ff:ff

    inet 192.168.178.3/24 brd 192.168.178.255 scope global enp5s0

    valid_lft forever preferred_lft forever

    inet 192.168.178.44/24 brd 192.168.178.255 scope global secondary noprefixroute enp5s0

    valid_lft forever preferred_lft forever

    3: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000

    link/ether 24:5e:be:65:4f:b4 brd ff:ff:ff:ff:ff:ff

    inet 192.168.178.2/24 brd 192.168.178.255 scope global enp4s0

    valid_lft forever preferred_lft forever

    inet 192.168.178.54/24 brd 192.168.178.255 scope global secondary noprefixroute enp4s0

    valid_lft forever preferred_lft forever


    Not sure how I can get out of this :P

    • Offizieller Beitrag

    Since you had a desktop environment installed, there probably another source of network config like network-manager. I would:


    sudo apt-get purge --autoremove network-manager

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.5


    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!

  • Since you had a desktop environment installed, there probably another source of network config like network-manager. I would:

    Indeed there was. It also removed the Proxmox 5.15 for whaterver reason.


    Sadly the only outcome is that it enabled ipv6 at reboot.

    Re-applying the network interfaces config from the WebUI removed it.

    Disabling ipv4 on the 2nd NIC left the dhcp address active.


    Another suggestion for the offending package to remove?

    • Offizieller Beitrag

    Another suggestion for the offending package to remove?

    I wasn't suggesting that network-manager was the only option. I wasn't going to try to enumerate every method of configuring a network in Debian. I would guess /etc/network/interfaces is configured? I would remove the file. You could even remove the ifupdown package. Make sure the only netplan files in /etc/netplan/ are the ones created by OMV.

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.5


    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 would guess /etc/network/interfaces is configured? I would remove the file. You could even remove the ifupdown package. Make sure the only netplan files in /etc/netplan/ are the ones created by OMV.


    Removed interfaces and was re-created by OMV, it's empty only referencing interfaces.d which does not exist


    In /etc/netplan only the OMV files:

    -rw-r--r-- 1 root root 43 Aug 15 05:39 10-openmediavault-default.yaml

    -rw-r--r-- 1 root root 328 Aug 15 05:39 20-openmediavault-enp4s0.yaml

    -rw-r--r-- 1 root root 186 Aug 15 05:39 20-openmediavault-enp5s0.yaml


    Which are looking fine, as configured in the UI


    I have removed ifupdown package as well


    But still no luck


    Is it normal that the networking service is masked?


    ● networking.service

    Loaded: masked (Reason: Unit networking.service is masked.)

    Active: inactive (dead)

  • From what I'm reading online seems Debian 11 should have the systemd-networkd services masked.

    Which is not the case for me.

    Could be it's conflicting with netplan? or netplan is using it?


    Output of networkctl:


    IDX LINK TYPE OPERATIONAL SETUP

    1 lo loopback carrier unmanaged

    2 enp5s0 ether routable configured

    3 enp4s0 ether routable configured

    4 docker0 bridge routable unmanaged

    6 veth8e8199f ether routable unmanaged

    8 veth1ad689d ether routable unmanaged

    10 veth174d2b7 ether routable unmanaged

    12 veth5f4289b ether routable unmanaged

    14 veth902ace7 ether routable unmanaged

    16 veth093e921 ether routable unmanaged


    10 links listed.


    systemctl status systemd-networkd.socket

    ● systemd-networkd.socket - Network Service Netlink Socket

    Loaded: loaded (/lib/systemd/system/systemd-networkd.socket; disabled; vendor preset: enabled)

    Active: active (running) since Mon 2022-08-15 08:56:38 CEST; 1h 6min ago

    Triggers: ● systemd-networkd.service

    Docs: man:systemd-networkd.service(8)

    man:rtnetlink(7)

    Listen: route 1361 (Netlink)

    CGroup: /system.slice/systemd-networkd.socket


    status systemd-networkd.service

    ● systemd-networkd.service - Network Service

    Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled-runtime; vendor preset: enabled)

    Active: active (running) since Mon 2022-08-15 08:56:40 CEST; 1h 1min ago

    TriggeredBy: ● systemd-networkd.socket

    Docs: man:systemd-networkd.service(8)

    Main PID: 9890 (systemd-network)

    Status: "Processing requests..."

    Tasks: 1 (limit: 18363)

    Memory: 4.1M

    CPU: 626ms

    CGroup: /system.slice/systemd-networkd.service

    └─9890 /lib/systemd/systemd-networkd


    Aug 15 08:56:47 solidpc systemd-networkd[9890]: veth1ad689d: Gained carrier

    Aug 15 08:56:47 solidpc systemd-networkd[9890]: veth1321f05: Link DOWN

    Aug 15 08:56:47 solidpc systemd-networkd[9890]: veth1321f05: Lost carrier

    Aug 15 08:56:47 solidpc systemd-networkd[9890]: veth902ace7: Lost carrier

    Aug 15 08:56:47 solidpc systemd-networkd[9890]: veth902ace7: Gained carrier

    Aug 15 08:56:47 solidpc systemd-networkd[9890]: veth753ad81: Link DOWN

    Aug 15 08:56:47 solidpc systemd-networkd[9890]: veth753ad81: Lost carrier

    Aug 15 08:56:47 solidpc systemd-networkd[9890]: veth093e921: Lost carrier

    Aug 15 08:56:47 solidpc systemd-networkd[9890]: veth093e921: Gained carrier

    Aug 15 08:56:51 solidpc systemd-networkd[9890]: enp4s0: Gained carrier


    systemctl status systemd-networkd-wait-online.service

    ● systemd-networkd-wait-online.service - Wait for Network to be Configured

    Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled-runtime; vendor preset: disabled)

    Active: active (exited) since Mon 2022-08-15 08:56:45 CEST; 1h 8min ago

    Docs: man:systemd-networkd-wait-online.service(8)

    Process: 9903 ExecStart=/lib/systemd/systemd-networkd-wait-online (code=exited, status=0/SUCCESS)

    Main PID: 9903 (code=exited, status=0/SUCCESS)

    CPU: 27ms


    Aug 15 08:56:40 solidpc systemd[1]: Starting Wait for Network to be Configured...

    Aug 15 08:56:45 solidpc systemd[1]: Finished Wait for Network to be Configured.

Jetzt mitmachen!

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