The correct procedure is the one you followed. Create a backup, install OMV, run omv-regen, and rebuild from the backup. If you have omv-kernel installed, it will ask you to reboot mid-process and run omv-regen again to finish.
I have no idea what the problem could be in your case. Please tell me the output of dpkg -l | grep openme and I'll try to recreate it this weekend.
Are there any special conditions in your hardware or software system?
Did you check the omv-regen log for errors?
I'm sorry, but I think the problem lies elsewhere. There's nothing in omv-regen that would cause a failed login to the server.
In point 9 after rebooting the system did you run omv-regen again?
Did you receive any error messages? You can check the log.
Just moved over from an Asustor NAS and my RAID array mounted perfectly in OMV, however I have a question about expansion. I want to replace each disk one-by-one with larger drives, and eventually expand the arrays. Used to do that by just removing a drive in the Asustor, but understand with mdadm, I should remove the drive one-by-one, shutdown, swap the disk, boot back up and add the new drive to the array.
The Asustor format is however actually two arrays on each disk, the first array is a 4 disk RAID 1, and the second, a 4 disk RAID 5. I understand normally its possible to replace and grow the arrays in the GUI, but will the OMV GUI through 'Multiple Disks' handle this set-up given there are actually two arrays on each disk?
Asustor is probably using the same procedure as other commercial NAS. It creates a RAID 1 with a small replicated partition on each drive to house the operating system (or part of it). The rest of the drive is used with another partition to house user data, depending on the file system type the user chooses; in this case, you chose RAID 5.
So, my advice would be to get rid of all that since you no longer need it and create a new RAID using the OMV GUI. That is, if you still want to continue using a RAID. Obviously, you'll need a backup of all your data first, which you should already have, considering that RAID is not a backup. https://www.raidisnotabackup.com/
Welcome to OMV.
The kernel you're using is version 6.12, which corresponds to Debian 12 Bookworm. The OMV version was correct, 7.7.9-1. Your problem was that the plugins weren't displaying correctly in the OMV GUI. What's the output now from:
dpkg -l | grep openme
Find the fix6to7upgrade script and run it.
Since newbie guide isn' t ready for idiots like me, can I ask someone for a guidance how to properly rename folders?
You can delete the shared folder in the OMV GUI. This action will not delete the folder or the data in the file system.
You can then modify the folder name (if desired) using an SSH connection to the server.
You can then create a new shared folder pointing to that folder in the file system. Use the tree icon next to the relative path in the OMV GUI to ensure you're choosing the correct folder.
There are many ways to do this.
For example, with Clonezilla, you can install the openmediavault-kernel plugin to start from within Clonezilla. I think this could be considered straightforward.
Another option is to use the openmediavault-timeshift plugin. It's not exactly a backup, but it allows you to roll back to a previous version in case of a potential problem.
You also have the openmediavault-backup plugin, which offers different methods for backing up your operating system. All are easy to configure; the tricky part can be the restoration, depending on the method you choose. So you should experiment until you can verify that you can restore; until then, you won't really have a usable backup.
You'll need to provide more details about what you've done and what's happening exactly. The information you're providing isn't sufficient.
Have you looked at the common problems? https://wiki.omv-extras.org/do…wireguard#common_problems
Yeah but that refers to local disks only. So, if i understand it correctly, on the second omv box I need to create a share that i can then remote mount (omv-extras) on my primary omv box and then it should work like ?
In general, everything in OMV works through shared folders. If you perform a remote mount, you then have to create a shared folder from that remote mount. At that point, you can configure the rsync copy with that shared folder as if it were any other local folder. rsync doesn't know if that shared folder is local or remote.
The alternative is to configure an rsync module on one of the servers and access that module directly from rsync on the other server. This has several advantages. 1. You don't have to perform a remote mount. 2. The remote share doesn't have to be permanently online; this is a requirement of the remote mount plugin to prevent errors.
I thought about CZ. I feared that disk full space would not be used by this method.
Look in the Clonezilla documentation. There's a cloning option that allows you to use the entire space on the destination drive.
What do you about about omv-kernel?
It seems that it helps on install rescue utility...
omv-kernel allows you to boot from Clonezilla. I didn't include the wiki link in my first post because the existing version is still OMV6. However, I don't think there should be many differences with OMV7, so you can take a look at it for reference. https://wiki.omv-extras.org/do…=omv6:omv6_plugins:kernel
Did you see this? https://wiki.omv-extras.org/do…rroring_backup_with_rsync
There's more information about rsync in that guide that might help you.
Am I right, or is there a better way to do what I want?
You can use CloneZilla. The openmediavault-kernel plugin might be helpful.
First of all, Raid is not a backup. https://www.raidisnotabackup.com/
I would use the mergerfs plugin to merge data drives. https://wiki.omv-extras.org/do…mv7:omv7_plugins:mergerfs
If you're going to use a USB drive for backups, check out the openmediavault-usbbackup plugin. USB backup plugin (openmediavault-usbbackup)
As for syncing smartphones, you can use Syncthing in a Docker container. https://wiki.omv-extras.org/do…7:docker_in_omv#syncthing
That last link has some suggestions on data drive configurations to optimize Docker.
There are some issues with the openmediavault-flashmemory plugin that could be affecting your system. Read this thread:
The easiest way is to clone the USB drive with USBImager
You can read it here. https://wiki.omv-extras.org/do…ackup#cloning_flash_media
Is this a new OMV installation? If so, have you clicked the Discover button in the ZFS plugin GUI?
I tested it and with stock bios config it consumes 35W idle, no usb devices, no hdmi just motherboard+cpu+ram+ssd and ethernet connected.
Too much to replace a RPi2 that consumes 6W at 100% usage
I need to downclock an reduce the energy consumption...35W is like keeping on 5 good size led lamp all day long
If you are willing to spend money to reduce consumption, look at N100.
dpkg --configure -a
The error is already telling you what to do. Run this command: dpkg --configure -a
These words bring infinite peace to my weak systemist heart
I am very happy to act as a tranquilizer for your health. 
