It's a simple window.onbeforeunload hook in the HTML code that forces browser to display the dialog, nothing fancy and a default feature of browsers. The browser decides when to display the dialog, so it seems a problem with the browser and not the OMV code. Maybe a browser plugin causes the issue.
Try the file /etc/openmediavault/php.ini and report back.
One question, you run the command in the UI and the error occurs when the output is shown in the 'Execute' dialog?
Oh, I see the problem. The database seems not to be migrated during package installation. Was the installation aborted or has it failed?
To fix the issue run omv-confdbadm migrate conf 5.6.0
Clear the browser cache to fix this issue.
I have the same issue now.
# systemctl status openmediavault
Unit openmediavault.service could not be found.
# systemctl status openmediavault-engined
Loaded: masked (Reason: Unit openmediavault-engined.service is masked.)
Active: inactive (dead)
root@omv:~# dpkg -l |grep openm
ii openmediavault 5.6.0-1 all openmediavault - The open network attached storage solution
ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive
When i run omv-engined -f -d it is working.
Also re-installed the openmediavault package, nothing solved.
What do do?
Run systemctl unmask openmediavault-engined.service and systemctl restart openmediavault-engined.serviceto get it working again.
Could you please add -v -v to the extra options and then re-run the job? Please also run journalctl -f in parallel to check if there are more useful information why the job fails. I assume the shell is missing something when running the rsync job to a remote system.
Hello, I am also quite new to OMV and been struggling with a similar problem. I have 2 disks with 4TB capacity which I want to mount in Raid mirror in OMV. I wiped both disks using using wipefs (because through OMV it would have taken ages) but the disks do not show under the "Create RAID device" option. Both disks are visible under "Disks" tab.
Could anyone give me some advice? I would appreciate it.
If the disks are connected via USB, then they are not listed in the UI with reason. You have to create the RAID manually in this case.
i decided to reinsert the relative path in the 61-openmediavault-dev-disk-by-id.rules (removed with the new version)
and now my serial number show correctly and no more error 'failed with exit code 1'.
I'm wondering because systemd developers told me that it is not necessary to use absolute paths. And it seems no a generic issue, otherwise the forum and bug tracker would be flooded with reports about that. So i assume something else must be causing the issue? Maybe a custom kernel, other udev/systemd packages from sources other than the Debian repositories, ...
I don't have an account with Github or have the slightest idea of how to use it, what its for or anything like that. How do I do what you keep saying and how does that help me?
As said, the forum is not meant to be to discuss and track code improvements. Implementing such a feature requires multiple iterations, and GitHub is the best approach for that because that way code changes and discussions are on sync.
If you want to get your HBA supported in OMV please go that route.
Hmmm, 11 disks does not really look like a home solution, but ok.
Here are the commands to be executed. I used /dev/sde here because i assume that this is attached to the HBA.
Please create a new feature request on GitHub and post the command outputs there, the forum is not meant to be used for that.
But wouldn't it be much more straight-forward if we had an field in the gui with the "erweiteren optionen" like we have for every other samba share?
I don't want to have such fields in OMV anymore, and there are plans to remove them from other pages in OMV6. The do not fit into the concept of OMV anymore. An no, OMV is not designed to allow the user to customize things, it's intention is to ship a configuration that matches 99,9% of the users requirements. Now with Salt it is easy to customize the system if needed, but i don't want to support that via UI anymore.
Looks like the installation is corrupted, e.g. erroneous filesystem or defective disk.
But as soon as I add more like the second argument:
omv-env set OMV_SAMBA_HOMES_VFSOBJECTS "btrfs shadow_copy2"
I get an error:Code
Uhhh, you found a bug: https://github.com/openmediava…cbb0814ab2a8c0ed792f428c4
And I would like to add the following lines:
vfs objects = recycle btrfs shadow_copy2
shadow:format = @GMT_%Y.%m.%d-%H.%M.%S
shadow:sort = desc
shadow:snapdir = .snapshots
Is there a possibility?
Yes, but you need towrite your own SLS file, see https://openmediavault.readthe…html#the-saltstack-states.
Here is the origin of the Samba SLS files.
Please search the forum to find examples how to do that.
One hint: You need to place a file called 31customhomes.sls in/srv/salt/omv/deploy/samba/.
The first thing to do is to find out which arguments must be set to get smartctl -x '/dev/sde' running successful. The next step is then to find a way to auto-detect your HBA and tell the OMV backend to append that necessary command args for devices that are attached to your HBA.
The command line should look like something mentioned here: https://www.smartmontools.org/…upported_RAID-Controllers
P.S.: I found various problems with this HBA
When I go to Smartmontools.com they released V7.2 a month ago whereas the error code implies this is a 3 year old tool at v6.6. is OMV using older tools?
OMV is based on Debian, so it can only use what they are shipping. But Debian backports critical bugs to their older package version. OMV6 (based on Debian 11) will include 7.2.
But the smartmontools version is totally independend from your issue. The problem is that OMV does not know about your HBA and because of that smartmontools is not called with the necessary command args.
If you want to get your HBA supported in OMV you need to contribute to the project, because without hardware we are not able to implement it. Please check the following GitHub PRs that are implementing the necessary logic to support other HBAs.
Please open an issue for a feature request at https://github.com/openmediavault/openmediavault/issues providing all necessary information that are mentioned in the PRs above.
THX for the reply. But there must be a space to store the current output, or not?
This is all up to you. Cron is simply executing what you've configured. If shred does not support logging to syslog then you have to do it somehow. If you need to do it manually, the problem is how to redirect the shred output line by line to syslog. But i assume there should be a solution out there anywhere.
Clear your browser cache and retry to set the timezone.