Possibly corrupted installation, checking if there's a fix before reinstalling

Hey folks, I'm trying to see if I can salvage an OMV installation without throwing in the towel and rebuilding the entire thing.

I can identify a few errors but I'm curious if they are part of a greater permissions issue or something that one of you can identify for me. I've been poking around but my brain is breaking.

I got this running on a Raspberry Pi 4B, pretty standard setup.

Here's the story:

• Due to an ID10T error when swapping out a case, I physically broke the USB ports and had to get a replacement Pi 4B.
• I took the SD card from the old Pi (containing OMV) and put it into the new one, hoping most of it would translate over with little reconfiguration needed
• I initially had to drop in via the console with a monitor connected and run omv-firstaid to take care of the network interface remapping (new NIC and all considering it's a different Pi), but after that I could get into the web UI.
• This is where I discovered the gauntlet of problems: I couldn't mount my two USB BTRFS disks (exit code '32': mount: /srv/dev-disk-by-label-datadisk: unknown filesystem type 'btrfs'). After going down a Google rabbit hole, it seems that apparently the BTRFS kernel module didn't load in correctly or something. I was looking at a GitHub issue about udev rules and replacing them, but I wasn't sure if this was the case.
• The OpenVPN plugin also died. The service will not start, the OpenVPN log just states ERROR: Cannot open TUN/TAP dev /dev/net/tun: No such file or directory (errno=2)
• Lastly (maybe not leastly), the Docker service is unable to start. Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; echo "Restarting docker ..." && systemctl restart docker.service ': Restarting docker ...

I feel there is a chance all of these might be related, but I'm not entirely certain. It's a bit overwhelming and I'm tempted to just blow it away and reinstall (not the end of the world honestly), but I was curious if anyone had any suggestions or ideas before I do that. I almost feel it's something with file permissions on the SD card but I'm not sure, it's just a guess.

Thanks!

Here's a sample detailed error for a disk not mounting (I couldn't put it in a bulleted list without it getting mangled):

Error #0:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; mount -v --source '/dev/disk/by-label/datadisk' 2>&1' with exit code '32': mount: /srv/dev-disk-by-label-datadisk: unknown filesystem type 'btrfs'. in /usr/share/php/openmediavault/system/process.inc:182
Stack trace:
#0 /usr/share/php/openmediavault/system/filesystem/filesystem.inc(742): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(931): OMV\System\Filesystem\Filesystem->mount()
#2 [internal function]: Engined\Rpc\OMVRpcServiceFileSystemMgmt->mount(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('mount', Array, Array)
#5 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('FileSystemMgmt', 'mount', Array, Array, 1)
#6 {main}

And here is a detailed OpenVPN error when I try to get the service configured/reinstalled:

Error #0:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color openvpn 2>&1' with exit code '1': raspberrypi:
----------
          ID: stop_openvpn_service
    Function: service.dead
        Name: openvpn
      Result: True
     Comment: The service openvpn is already dead
     Started: 10:24:06.166260
    Duration: 131.063 ms
     Changes:
----------
          ID: setup_openvpn
    Function: cmd.run
        Name: /usr/sbin/omv-openvpn setup
      Result: False
     Comment: iptables/1.8.2 Failed to initialize nft: Protocol not supported
     Started: 10:24:06.301770
    Duration: 575.022 ms
     Changes:
----------
          ID: start_openvpn_service
    Function: service.running
        Name: openvpn
      Result: False
     Comment: One or more requisite failed: omv.deploy.openvpn.default.setup_openvpn
     Started: 10:24:06.878462
    Duration: 0.016 ms
     Changes:

Summary for raspberrypi
------------
Succeeded: 1
Failed:    2
------------
Total states run:     3
Total run time: 706.101 ms in /usr/share/php/openmediavault/system/process.inc:182
Stack trace:
#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/config.inc(167): OMV\Engine\Module\ServiceAbstract->deploy()
#2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(588): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusVp...', '/tmp/bgoutputn3...')
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#7 /usr/share/openmediavault/engined/rpc/config.inc(189): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)
#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#12 {main}

^Noted, and understandable. I think I just fixed it though, after trying literally everything. It seemed several kernel modules were missing somehow (I was messing with that once upon a time).

The fix was actually somewhat simple (though apparently not always recommended). It was to run sudo rpi-update and let it grab the latest pre-release kernel which appeared to fix all the missing stuff.

Now docker is working, the disks are mounted again, and OpenVPN configures without errors.

I think we can call this case closed!