Posts by vcruser

Thanks Zafkiel.

After apt-mark unholding the those firmware updates and then upgrading them I was able to install the Proxmox Kernel. I chose 6.5 and it went without issue.

Now HW transcoding is working again and with the latest updates!

Greetings,

I have the latest OMV v7 installed on a on a Beelink S12 N95 which I use as a media server. System info is below...

Version: 7.7.0-2 (Sandworm)
Processor: Intel(R) N95
Kernel: Linux 6.12.9+bpo-amd64
System Time: 2/24/2025, 6:27:38 PM
Uptime: 15 minutes
Load Average: 0.02, 0.10, 0.05
Memory Usage: 9.7% of 7.54 GiB

I discovered recently that one or more of these listed package updates break hardware transcoding (VA-API). This list was copied from the System/Update Management/Updates page in OMV.

Package Information
firmware-iwlwifi 20240709-2~bpo12+1
Binary firmware for Intel Wireless cards

Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org>
Homepage: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
Repository: Debian Backports/stable-backports
Size: 12.49 MiB
firmware-misc-nonfree 20240709-2~bpo12+1
Binary firmware for various drivers in the Linux kernel

Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org>
Homepage: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
Repository: Debian Backports/stable-backports
Size: 4.05 MiB
firmware-realtek 20240709-2~bpo12+1
Binary firmware for Realtek wired/Wi-Fi/BT adapters

Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org>
Homepage: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
Repository: Debian Backports/stable-backports
Size: 2.06 MiB

So, what I would like to do is blacklist these updates so OMV never tries to update these.

Actually, while composing this thread, I found a way to do this. I ran these commands then rebooted. Now these packages don't show up as "updates available" in the OMV gui.

sudo apt-mark hold firmware-iwlwifi
sudo apt-mark hold firmware-misc-nonfree
sudo apt-mark hold firmware-realtek

However, I do have a question though. If I run "sudo apt dist-upgrade" to upgrade OMV, or other packages, will that over-ride the "hold" status of the packages I marked and update them anyway?

Thanks

Quote from whant_to_know

Code

Someone out there must have gotten this to work even if you "shouldn't" do that. So please anyone have an idea?

I have a "recordings" shared folder that can be accessed with both SAMBA and NFS.

Under the Storage, Shared folders menu "Owner", "Group", and "Others" fields all have "Read/Write/Execute" selected. Be sure "Recursive" is checked before applying any changes.

For NFS I use "insecure,crossmnt,no_root_squash,nohide,no_subtree_check" and "Read/Write" selected.

For SMB/CIFS "Guests allowed" is selected and "Browseable", "Follow symlynks", "Extended attributes", and "Store DOS attributes" are checked (nothing else).

All my Windows PC's can access the SMB "recordings" folder and my media server (which also uses OMV) accesses the NFS "recordings" share. The media server machine with OMV uses "Remote Mount" to access the NFS share.

Display More

I have OMV 7.1.1.1-1 running on a Beelink Mini PC with an N95 Intel CPU. Every time I reboot or awake from sleep I get several repeating emails about NGINX either failing or succeeding.

Here are samples of the emails I get.

[email address]
6:51 AM (49 minutes ago)
to me

The system monitoring needs your attention.

Host:        beelink
Date:        Wed, 05 Jun 2024 06:39:15
Service:     nginx
Event:       Does not exist
Description: process is not running

This triggered the monitoring system to: restart

—
You have received this notification because you have enabled the system monitoring on this host.
To change your notification preferences, please go to the 'System | Notification' or 'System | Monitoring' page in the web interface.

[email address]
The system monitoring needs your attention.

Host:        beelink
Date:        Wed, 05 Jun 2024 02:12:19
Service:     nginx
Event:       Execution succeeded
Description: process is running after previous exec error (slow starting or manually recovered?)

This triggered the monitoring system to: alert

—
You have received this notification because you have enabled the system monitoring on this host.
To change your notification preferences, please go to the 'System | Notification' or 'System | Monitoring' page in the web interface.

The only notifications I have enabled are "Memory" and "S.M.A.R.T." Other than this issue OMV seems to be running normally. What I would like to do is prevent such emails from happening if possible.

Attached is the boot log output

Quote from ryecoaaron

Someone could just set up a cron job to run every minute that runs this command to do that:

systemctl --type=mount --plain --quiet --no-pager --failed | awk '{ print $1 }' | grep -E 'srv-mergerfs|srv-remotemount' | xargs -r systemctl restart

This script would work for my setup but I don't use mergerfs. Would this script work?

systemctl --type=mount --plain --quiet --no-pager --failed | awk '{ print $1 }' | grep srv-remotemount | xargs -r systemctl restart

Ok, thanks for the info.

This is just a test setup so not worried if something goes wrong.

I have the ZFS plugin installed and was attempting to set up a pool using two hard drives.

The hard drives are populating a two bay USB hard drive caddy. The drives show up as sdb and sdc in the Disks menu. They have been quick wiped from the gui and are available to use as devices to create file systems from the File Systems menu.

However, when I try to create a pool in the ZFS plugin there are no devices that show up.

Am I doing something wrong?

system info

Quote

Version
7.0.5-1 (Sandworm)

Processor
Intel(R) Core(TM) i3-4010U CPU @ 1.70GHz

Kernel
Linux 6.5.13-3-pve

System Time
4/5/2024, 10:34:28 AM

Uptime
8 minutes

Load Average
0.04, 0.15, 0.09

Memory Usage
6.0% of 7.67 GiB

Display More

Quote from acalisesi

The new dashboard widget to display the temperatures of all physical disks shows black color as background in Dark mode.

In attachment you can see it.

I didn't like the big black rectangles either so I changed the S.M.A.R.T. widget to bring back the disk temps. It's not hard to do.

Post

RE: Feature request: Please bring back drive temps to dashboard´s SMART widget and keep optional drive temp widget.

prtigger1 I discovered the dashboard widgets are easy to modify so I hacked the "smart_status.yaml" file to bring back the disk temps.

Just ssh to your omv and...
(Code, 3 lines)

then look for the line...
(Code, 1 line)

and change it to...
(Code, 1 line)

Then update using
(Code, 2 lines)

It should just come back with a command prompt when finished. If you mess up you will get a bunch of errors so you will need to fix the error in your file.

Then Ctl+Shift+R to refresh the browser and it should look like…

vcruser

Feb 23rd 2024

From the plugin gui you could try "Add quota options", apply, then "Remove quota options".

Should I open a "New Issue" on OMV github for this?

I have an extra disk that I wanted to use to create a new file system. When selecting a device from the menu it showed the extra disk plus all the disks from the zfs pool. Of course I didn't select any of the disks from the zfs pool for the new file system but I don't think they should show up here. Don't know what would happen if I accidently selected the wrong disk.

The top four disks in this image are in my ZFS pool. The bottom one (dev/sde) is the extra disk I intended for creating a new file system.

Here is the details of the ZFS pool

Pool status (zpool status):
  pool: zfs1
 state: ONLINE
  scan: scrub repaired 0B in 03:03:43 with 0 errors on Sun Mar 10 04:27:44 2024
config:

    NAME                                          STATE     READ WRITE CKSUM
    zfs1                                          ONLINE       0     0     0
      raidz1-0                                    ONLINE       0     0     0
        ata-WDC_WD40EFPX-68C6CN0_WD-WX62A928XYRJ  ONLINE       0     0     0
        ata-WDC_WD40EFPX-68C6CN0_WD-WX62A928XS78  ONLINE       0     0     0
        ata-WDC_WD40EFPX-68C6CN0_WD-WX72D320C626  ONLINE       0     0     0
        ata-WDC_WD40EFPX-68C6CN0_WD-WXU2D53EE78A  ONLINE       0     0     0

errors: No known data errors

Quote from vcruser

Does the fact that one drive has a lower cache size than the other three possibly cause this?

The WD40EFZX drive has 10 MB/Sec slower interface transfer rate according to the data sheet. Possibly due to the smaller cache size

Today I replaced this drive so now all the drives in the array are identical and the drive access LEDs are behaving as expected now.

I have a 4 disk raid 5 using OMV 7 in clean state. Three of the SATA drives are WD40EFPX (256Mb cache) and one is a WD40EFZX (128Mb cache). All 4 drives are CMR. The drive controller is an LSI 9207-8i in IT mode. My drive bay has a multicolor LED for each drive, green for power and orange for drive activity.

I notice that the three WD40EFPX drives stay green all the time and only the WD40EFZX drive shows any drive activity indicated by the orange LED flickering occasionally when the raid is being written to. Of course all the drives are being written too but I wonder why I only see the LED change color for the one drive. I tried swapping drive bays and the activity light behavior follows the drive.

Does the fact that one drive has a lower cache size than the other three possibly cause this?

I was going to add quotas using the plugin and try it out. After adding quotas for a drive I did not see any aquota files. Tried a reboot but still no files. Were the supposed to be added?

Quote from ryecoaaron

If you remove the files, the mount options have to be removed. The plugin's "Remove quota options" button does both.

After using the remove quota options the files remained even after reboot. So, I deleted them manually.

Once, early on I tried to remove aquota.user and aquota.group which caused OMV to not boot.

Just now installed the plugin and used the "Remove quota options" button. Then removed the aquota.user/group files without issues.

Yes, "hack" was probably a poor choice of words on my part. Also, OMV users are not discouraged from creating their own widgets. Searching the forum you will find some instruction for creating widgets as well as in the OMV documentation. OMV 6.x documentation - dashboard.d

This is the widget code for "smart_info.yaml". I attached the file if interested.

version: "1.0"
type: dashboard-widget
data:
  id: 5e518804-d1f7-11ee-966d-77e35ad4fd0d
  type: grid
  reloadPeriod: 60000
  permissions:
    role:
      - admin
  title: _("S.M.A.R.T. Info")
  description: _("Displays the S.M.A.R.T. info of all monitored disk devices.")
  # Text used in templates and therefore cannot be automatically extracted
  # by i18n tools.
  i18n:
    - _("Good")
    - _("Unknown")
    - _("Device is being used outside design parameters.")
    - _("Device was used outside of design parameters in the past.")
    - _("Device has a few bad sectors.")
    - _("Device has many bad sectors.")
  grid:
    item:
      content: '{{ canonicaldevicefile }}<br>{{ temperature | notavailable }}{% if temperature %}°C{% endif %}'
      class: 'omv-cursor-pointer omv-text-center omv-text-nowrap {% set overallStatusColor = { "BAD_ATTRIBUTE_NOW": "omv-background-color-pair-error", "BAD_ATTRIBUTE_IN_THE_PAST": "omv-background-color>
      tooltip: '{% set overallStatusText = { "GOOD": "Good", "BAD_STATUS": "Unknown", "BAD_ATTRIBUTE_NOW": "Device is being used outside design parameters.", "BAD_ATTRIBUTE_IN_THE_PAST": "Device was us>
      url: '/storage/smart/devices/details/{{ devicefile | encodeuricomponent }}'
    emptyMessage: _("No monitored devices.")
    store:
      proxy:
        service: Smart
        get:
          method: getListBg
          params:
            start: 0
            limit: -1
          task: true
      sorters:
        - prop: devicefile
          dir: asc
      filters:
        - operator: "truthy"
          arg0:
            prop: "monitor"

Quote from ryecoaaron

If you are going to make that file, change the filename, id and title in the data section. Generate a new id with the uuid command from the command line.

Thanks, I was wondering where the id came from.

prtigger1 I discovered the dashboard widgets are easy to modify so I hacked the "smart_status.yaml" file to bring back the disk temps.

Just ssh to your omv and...

 sudo nano/usr/share/openmediavault/workbench/dashboard.d/smart_status.yaml

then look for the line...

content: '{{ canonicaldevicefile }}'

and change it to...

content: '{{ canonicaldevicefile }}<br>{{ temperature | notavailable }}{% if temperature %}°C{% endif %}'

Then update using

sudo omv-mkworkbench all

It should just come back with a command prompt when finished. If you mess up you will get a bunch of errors so you will need to fix the error in your file.

Then Ctl+Shift+R to refresh the browser and it should look like this.

You may just want to make a new file with a different file name in case you want to go back to just Status without disk temps. I had to change the id number of my new file so I wasn't identical to the other one.

I prefer having the S.MA.R.T status and Disk temperature all in one like it was previously. Seems like a step backwards to me.