Is there an error reported when running
omv-engined -d -f
in the CLI as root user?
Is there an error reported when running
omv-engined -d -f
in the CLI as root user?
[ERROR ] {'pid': 4088, 'retcode': 1, 'stdout': '', 'stderr': '2024/07/22 15:46 :03 [emerg] 4089#4089: open() "/etc/nginx/sites-enabled/tu_sitio.conf" failed (2 : No such file or directory) in /etc/nginx/nginx.conf:60\nnginx: configuration f ile /etc/nginx/nginx.conf test failed'}
Did you manually edit nginx. conf?
Or did you install something else that is using nginx?
The error itself occurs when in windows explorer trying to delete a file on the NAS.
Are the files you try to change on the SD card or on another drive?
Won't it make backups and detect corrupted files easly?
BTRFS supports snapshots. It can detect corruption and may even heal them. Depends on the configuration.
So what is happening here is the relative path is the real folder on the file system and the name is an arbitary value used in OMV, or to be used as a convention to create a share such as SMB? But the actual folder itself can have an identical name to another folder.
Correct.
I was hoping I could create the same folders on a separate HD and sync exactly the same attributes to the second disk.
The name of the folder has nothing to do with the attributes and the content of the folder. Even is the name of the folders are different, the content of the folders can be the same.
It should still boot up?
Yes.
Please note that OMV6 and the underlying Debian version will be end of life around the end of the month.
The release-upgrade is quite smooth. These steps are valid also for the upgrade from 6 to 7
In the second link they are talking about an "all-in-one-container". Is that what you are using.
In any case you can backup the volumes that you bind mounted in the volumes: sections
For this
Can be automated with the rsnapshot plugin as it provides the possibility to run a command before and another command after the backup.
You can have identical folder names on file system level ("relative path" in the GUI). But you cannot have identical shared folders names.
Simple example of a solution for unique shared folder names:
source folder: data
target folder: data_backup
This way you have unique shared folders names and they tell you, what is the source and what is the backup.
Below example for a test folder. Relative Path is the same on different filesystems (devices). Shared Folder Name is unique.
Not having this capability seems to restrict a user for some common use cases such as this.
Which ones?
If you use the rsync functionality of OMV, you have to select a shared folder as source and another one as target. How would you do this, if you would have shared folders with the same name, but pointing at different folders on the filesystem?
I get the error "You need Unix User\root to make changes to this file.
Where do you get this error?
What are you doing when you get the error?
the only fix is to reflash the SD card
Maybe the SD card is dying. Test it with h2testw or f3
Everytime I seem to install a patch everything seems to break.
You have to fix that first, before you do the upgrade.
Which version do you currently have?
As subject says, if I upgrade the motherboard/CPU for better transcoding, is there a way to keep everything the same without reinstalling?
Yes. Most likely you only have to configure the network interface using omv-firstaid from CLI.
I get an empty page with nothing useful
Please post a screenshot
From CLI use omv-firstaid to configure the workbench. Watch out for any error message.
Yes, that is what I would do.
I would use the NAS as single source. Each client accesses the same data on the NAS.
Otherwise how do you want to resolve situations when files are changed on two clients and synced with the NAS.
I would look at attribute 197 and 198 and probably replace the drive.
I wonder if I could copy files locally on the OMV system from one local disk to another local disk using shell commands.
Yes you can.
Or use midnight commander.