I've tried every single fix for this that has been suggested since I first reported the problem in the forum on September 11, 2024. None of them have worked. Removing the flash plugin was the only fix that did work. Maybe you will get lucky and one of the suggested fixes will work for you.
What I did was to replace my 32GB USB system drive with a 32GB SSD drive.
"This plugin is REQUIRED, for a flash media boot drive, or it will have a short life." This not the same thing as being required by OMV itself.
Gderf you say uninstall flashmemory but looking at the OMV docs it says flashmemory is installed automatically and that it is required.
Where in the docs i this stated?
I think so, since some are connected to my-net or similar.
That's where they are coming from.
Do you have any containers running bridge networking?
I see this too, seems normal to me. Probably docker related.
I want to allow a few users to access/use OMV from remote locations on the internet.
Be more specific.
I can't give a definitive answer. Why not try it and see?
If you create mountpoints in fstab they will be unavailable for selection in the OMV WebGUI.
Using mergerfs doesn't reduce your control over individual drives.
Your migration stuff seems excessive to me. Please review the documentation for the image here:
https://docs.linuxserver.io/images/docker-plex/
All you need to do is come up with a compose file for the plex docker image you are using and create volume bind mounts for your media and existing config directory.
Plex hardware transcoding requires a Plex Pass subscription. Do you have one?
Codeports: - 3000:3000:tcp - 3001:3001:tcpI suggest:
Codeports: - 3000:3000 - 3001:3001Or:
Codeports: - 3000:3000/tcp - 3001:3001/tcp
I have been trying that but when I try to add ethernet it doesn’t find the adaptor at all.
Any chance you disabled the onboard adapter in the BIOS when you added the PCiE adapter?
In the GUI try to add the adapter in the Network Interfaces section.
Is there a way to get the old "dev-disk-by-label" link? The new created drive has the now default uuid format.
That is great for machines but not so good for humans. As I see it, I should create that manually, but will it be usable in/by the UI?
It is not possible to revert OMV to use dev-disk-by-label for any newly added drives. You can create a symlink to the new UUID mountpoint and the symlink can be whatever you want it to be.
Check your version of openmediavault-snapraid plugin. Current is 7.0.13 and has fix under the Arrays menu.
Try removing the failed disk from the mergerfs pool. Then restart the pool or reboot.
You should mention the exact image you are currently using to avoid it being suggested to you.
How long ago did you create the RAID? They do not fully initialize instantly.
sudo omv-update shows sudo: omv-update: command not found
Try sudo omv-upgrade instead.
