Posts by belierzz
-
-
Good morning votdev
Here the output (with obvious double entry):
Code
Display More[ { "devicefile": "/dev/disk/by-id/usb-ATA_Samsung_SSD_860_0123456789ABCDE-0:0", "devicetype": "", "enable": true, "tempdiff": 0, "tempmax": 0, "uuid": "f08a0860-7e9f-4cff-a9fe-c3d5b721e3cb" }, { "devicefile": "/dev/disk/by-id/usb-SanDisk_Ultra_Fit_4C530001080405112111-0:0", "devicetype": "", "enable": false, "tempdiff": 0, "tempmax": 0, "uuid": "b545229f-9890-4095-9cd3-52e2159a3806" }, { "devicefile": "/dev/disk/by-id/nvme-CT1000P3SSD8_2318E6D1CF5F", "devicetype": "nvme", "enable": true, "tempdiff": 0, "tempmax": 0, "uuid": "7adda958-9c23-4b18-8204-de825a04e025" }, { "devicefile": "/dev/disk/by-id/ata-WDC_WD80EFBX-68AZZN0_VR2WYL6K", "devicetype": "", "enable": false, "tempdiff": 0, "tempmax": 0, "uuid": "f15e9c07-e5d3-469b-afad-a3f012076e5f" }, { "devicefile": "/dev/disk/by-id/ata-WDC_WD60EFRX-68L0BN1_WD-WX31D97LP09Y", "devicetype": "", "enable": true, "tempdiff": 0, "tempmax": 0, "uuid": "d2285faa-b4df-4c43-bd29-532d16c00204" }, { "devicefile": "/dev/disk/by-id/ata-ST8000NT001-3LZ101_WRQ20HCV", "devicetype": "", "enable": false, "tempdiff": 0, "tempmax": 0, "uuid": "2fd244e3-b50f-4837-8b59-851d0c2ca58e" }, { "devicefile": "/dev/disk/by-id/ata-ST8000NT001-3LZ101_WRQ20HCV", "devicetype": "", "enable": true, "tempdiff": 0, "tempmax": 0, "uuid": "8bf0248c-0a38-4549-b2dc-64c464ce81db" }, { "devicefile": "/dev/disk/by-id/ata-ST8000NT001-3LZ101_WWZ40V0B", "devicetype": "", "enable": true, "tempdiff": 0, "tempmax": 0, "uuid": "2d062b8d-4c8c-4ce8-8086-6e6ee75e4a29" } ]Thanks for your helping hand.
-
As soon as I want to enable SMART monitoring for the a.m. HDD, I still receive the initial error message and need to revert. Temp is monitored correctly, it is just the impossibility to activate SMART in the GUI.
-
Thanks for your swift reply. Pls find attached the requested output (else, "message too long" error).smartmon.txt
-
-
I have 2x the same disk type inside, but with different serials
Code
Display More{ "aam": 0, "apm": 128, "devicefile": "/dev/disk/by-id/ata-ST8000NT001-3LZ101_WWZ40V0B", "spindowntime": 0, "uuid": "ed09eaa2-7e0d-49a3-bb83-8ae63a35b8bd", "writecache": true }, { "aam": 0, "apm": 128, "devicefile": "/dev/disk/by-id/ata-ST8000NT001-3LZ101_WRQ20HCV", "spindowntime": 0, "uuid": "615b47e2-6133-435c-b230-1dbfea26ccf8", "writecache": true }Therefore I do not see a double entry?!
-
Thanks a bunch, votdev
Here you go:
Code
Display Moreroot@raspberrypi:~# omv-confdbadm read --prettify conf.system.hdparm [ { "aam": 0, "apm": 0, "devicefile": "/dev/disk/by-id/mmc-SPCC_0x00015148", "spindowntime": 0, "uuid": "fcc55c75-8b68-49bc-8736-b9966c3ad68f", "writecache": true }, { "aam": 0, "apm": 0, "devicefile": "/dev/disk/by-id/usb-SanDisk_Ultra_Fit_4C530001080405112111-0:0", "spindowntime": 0, "uuid": "58432c63-52b8-41c3-9073-f9c924d93427", "writecache": false }, { "aam": 0, "apm": 0, "devicefile": "/dev/disk/by-id/usb-ATA_Samsung_SSD_860_0123456789ABCDE-0:0", "spindowntime": 0, "uuid": "b7dc0c4d-5c79-4e51-b7c5-750c8edeb53d", "writecache": true }, { "aam": 0, "apm": 0, "devicefile": "/dev/disk/by-id/nvme-CT1000P3SSD8_2318E6D1CF5F", "spindowntime": 0, "uuid": "ac2dfd35-247c-4456-b79e-30a56602d01b", "writecache": true }, { "aam": 0, "apm": 128, "devicefile": "/dev/disk/by-id/ata-WDC_WD80EFBX-68AZZN0_VR2WYL6K", "spindowntime": 0, "uuid": "48be7c99-1318-419c-a1e0-6bbb7ec9019b", "writecache": true }, { "aam": 0, "apm": 0, "devicefile": "/dev/disk/by-id/mmc-SPCC_0x7270000e", "spindowntime": 0, "uuid": "f87bc3b4-ae72-4b32-a8e7-21e3458e64ea", "writecache": true }, { "aam": 0, "apm": 128, "devicefile": "/dev/disk/by-id/ata-ST8000NT001-3LZ101_WWZ40V0B", "spindowntime": 0, "uuid": "ed09eaa2-7e0d-49a3-bb83-8ae63a35b8bd", "writecache": true }, { "aam": 0, "apm": 1, "devicefile": "/dev/disk/by-id/ata-WDC_WD60EFRX-68L0BN1_WD-WX31D97LP09Y", "spindowntime": 248, "uuid": "ef3e6a23-ba73-4edf-b5cb-285a99e97a42", "writecache": true }, { "aam": 0, "apm": 128, "devicefile": "/dev/disk/by-id/ata-ST8000NT001-3LZ101_WRQ20HCV", "spindowntime": 0, "uuid": "615b47e2-6133-435c-b230-1dbfea26ccf8", "writecache": true } ] -
Hi everybody,
I have used a Seagate IronWolf Pro HDD for backup purposes in OMV 7 on a Raspberry Pi 5. No issues. Now I want to use this HDD as internal storage.
If I try to enable SMART for the device, I get the following error with "conflicting ID":
Can anyone tell me where resp. in which file I can fix the issue?
Thanks for your support!
-
Hi,
enable the docker repository as shown in your screenshot and install the "compose" plugin. There you will find all the neccessary for your docker setup.
-
I have installed latest update of docker-compose to version 6.9.3. Unfortunately the compose files are not installed in their respective folders within the folder defined in settings (called "dockercomp"), but in single folders, e.g. dockercompplex, dockercompadguardhome etc.
Anyone has the same issue and / or can point me in the direction how to solve?
-
As you can see the pool is imported and ready to use from Shell, BUT
is not detected by OMV webGUI, so it can works as expected ( I expected that the imported pool can be show or mounted in storage -> filesystem so I can share some folders, see free space, etc...
For me it works exactly as you describe - ZFS pool / datasets show up in OMV6 filesystems and can be shared as usual. I did nothing different than you did.
-
The 6.x zfs plugin (really just backend) has been removed. There are changes that need to be made to the backend that I hadn't seen and the zfs backend is broken.
ryecoaaron: ZFS plugin (backend) works as expected on openmediavault 6.0.5-1.
Thanks for your hard work and continuous support!
-
Ryecoaaron,
Your work is much appreciated and your approach more than only reasonable. Please take your time and no need to rush.
For sure I've made an fresh installation of OMV6 on a different SSD rather than an upgrade and I'm back on OMV5 without ANY hassle. As long as OMV5 is supported, at least I can wait. BR
-
When I say imported, I mean imported by the plugin which can't be done on OMV 6.x other than by an rpc call (no, I haven't looked at what that would take).
I'm in the same position regarding OMV6 and ZFS and imported pool does not show up after importing.
Additionally, already mounted file system (no ZFS) but EXT4) disappears from WebUI as soon as pool is imported and appears again as soon as the pool has been exported.
-
Thanks for the feedback and well understood regarding the swap file systems.
I'm no programmer and certainly not in the position to improve your code. The memory usage tab in the performance statistics show correct values, it is just the overview tab.
As stated - cosmetic only. Thanks and enjoy Christmas holidays.
-
Hi, I have been using OMV 5 for a while now and it is working pretty stable for me.
Only two minor issues that came to my attention recently:- the RAM usage indication on the dashboard deos not reflect the real RAM usage of the system
- I have ZFS installed and at least approx. 4GB of the RAM are used constantly. The RAM indicator shows less than 1% of 16GB RAM used- Since a recent openmediavault update the SWAP partition is shown in the filesystem information, and that was never before. Unfortunately
I can't say when this one has been introduced.Everything else working like a charm. Thanks and keep up the good work!
-
Tried 5.0.2 and is working well! Thanks a bunch, ryecoaaron. No clue why the symlink is not working. At least Debian
tells us how to fix. -
I would say it is a bug in the autoshutdown plugin - or two. One is the PIDfile issue described in the first error message, the second is that one CR is missing in autoshutdown.conf file that can be bypassed with one empty line in the plugin gui expert settings.
-
One empty line in expert settings before TEMPPROCNAMES="-" did the trick. Furthermore updated /lib/systemd/system/autoshutdown.service in line 12.
Code
Display More[Unit] Description=Run autoshutdown script After=network.target After=suspend.target After=hibernate.target After=hybrid-sleep.target [Service] Type=simple Restart=always RestartSec=3 PIDFile=/run/autoshutdown.pid ExecStart=/usr/sbin/autoshutdown.sh [Install] WantedBy=multi-user.target WantedBy=suspend.target WantedBy=hibernate.target WantedBy=hybrid-sleep.target -
The memory usage in the dashboard on OMV 5.0.10 shows constantly 0.6%, whereas the memory usage in the report (as well as cockpit)
show approx. 12G of 16G. The 12G should reflect the reality on my ZFS system, this is also what OMV 4 showed.
