I realised such a strange behaviour in iOS when visiting the GitHub page at https://github.com/openmediava…af494dae53c46a77498b55936 for example. Scrolling down slowly let the browser freak out.
Posts by votdev
-
-
Yep. The translation is in the locale file. Do you see anything that isn't translated other than the confirmation dialog? While I can't find it in code, I'm guessing the confirmation dialog does not use gettext which means it wouldn't read from the locale file. votdev
Please open a tracker issue for that, otherwise I will miss to check it.
-
LostInCompilation Would be great to see the output of the browser console (dev tools - F12 in common browsers) when this error appears.
-
The dashboard widgets randomly change position
This is not under control of the OMV UI. The browser is responsible of positioning and rendering the widgets.
Nevertheless, i never saw any problems here.
-
-
According to Salt issues this should have been fixed in a version from 2016 (see https://github.com/saltstack/salt/issues/40912).
Have you enabled IPv6? Can you post the /etc/hosts file?
-
OMV only does a apt-get install via UI by intention, but to install backported kernels you need to run a dist-upgrade. You can do that via CLI by running apt-get dist-upgrade or omv-upgrade.
-
These are the supported platforms: amd64, arm64See also
-
I have not yet experienced any problems with OMV 5 and Gnome, so it is kind of hard to wrap my head around this step.
That's your experience, but not ours.
Gnome (or any desktop environment) and OMV are working against each others in many areas like systemd, file system and network configuration. To minimize our maintenance and prevent users from doing the wrong I decided to prevent the side-by-side installation because it simply does not work.
Please see https://github.com/openmediavault/openmediavault/pull/1175.
-
Run omv-mkworkbench all all from CLI to fix that.
-
Das Dateisystem der WD 6TB ist schon unter /media/Cloud_files eingehängt, deshalb wird das Dateisystem auch nicht mehr in der OMV UI angezeigt. Da das einhängen manuell (oder von einer anderen Software) getätigt wurde, zeigt die OMV UI dieses Dateisystem auch nicht als gemountet an. Du musst dafür sorgen dass /media/Cloud_files ausgehängt wird, um es anschließend über die OMV UI einzuhängen. Dann kannst Du in der UI freizugebende Ordner anlegen.
Alternativ kannst Du wie bereits getätigt mittels des openmediavault-sharerootfs Plugin freizugebende Ordner innerhalb des root Dateisystems anlegen. Hierzu dann /media/Cloud_files/foo/bar angeben.
-
Du verwendest den falschen Action-Button. Ich denke 'Erstellen' ist nicht das was Du möchtest, da damit ein neues Dateisystem erstellt wird. Dazu muss die Festplatte leer sein, was in Deinem Fall nicht zutrifft. Du musst 'Einhängen' auswählen.
-
Please run omv-mkaptidx as root from CLI. Did it work afterwards?
-
Please check https://github.com/openmediavault/openmediavault/issues/1302 which information is necessary to enhance OMV to auto-detect your disk correctly. If you provide that information in a new GitHub issue, then i can do the necessary coding.
Alternatively buy me the hardware to reproduce it locally.
-
That's incorrect, OMV6 supports F2FS out-of-the-box. The UI allows to create filesystems of that type and all userland tools are installed automatically. If it does not work, then there is a problem which is out of the OMV scope
-
OMV detects that the disk is connected via USB, so the -d sat attribute is added automatically. Without extending the auto-detection source code it will not be possible to fix that. An alternative will be to replace the sat by sntrealtekin the config.xml file. Afterward you need to restart the omv engine via monit restart omv-engined.
Code contributions to enhance the auto-detection are welcome.
-
You need to enable SMART monitoring in the SMART | Devices page.
-
Use the UI to create the users, then the SMB passwords will be created automatically.
-
Adding such UI fields is against the philsophy of OMV to keep it simple by using most common settings that make 99% of the users happy. But you can customize the configuration file that way that it will not override your settings when OMV rebuilds the configuration. Check https://openmediavault.readthe…html#custom-configuration how to do that.
You can use the environment variables OMV_NUT_UPSMON_POLLFREQ, OMV_NUT_UPSMON_POLLFREQALERT and OMV_NUT_UPSMON_DEADTIME. Use Salt states to append custom directives to upsmon.conf.
-
I think the 1000MHz value is incorrect. Please check the official cpufrequtils documentation which values are allowed and correct.
