Posts by SiliconSage

Quote from ryecoaaron

You do know that OMV has one developer and I am the only dev of omv-extras plugins, right? We both work on OMV in our spare time.

Yes, I did know. And I do really appreciate your work.

But I was talking about the technical backgrounds. For me as an end user (on amd64 actually) it is just too risky to update my server and have to be afraid every time it could break.

Did Volker consider to use some other base like Buildroot?

ZimaOS and Home Assistant do rely on it:

Home Assistant Operating System | Home Assistant Developer Docs

The Home Assistant Operating System is a purpose built operating system specifically designed to run Home Assistant on single board computers and x86-64…

developers.home-assistant.io

Quote from ryecoaaron

Debian is damn good.

I agree.

Quote from ryecoaaron

Why are they reliable??? TrueNAS scale is based on debian too

And macOS on BSD. And Manjaro on Arch. And Ubuntu on Debian...

But, unlike OMV, they all do maintain their own packages. They run beta and RC cycles to ensure smooth updates.

Honesty, this (sometimes fatal) dependency on upstream Debian made leave OMV again after just one month.

Also, the lack of warning before the 7.5.0 update in spite the amount of network less rendered machines made me doubt.

There are many free alternatives out there like ZimaOS, TrueNAS Scale, YunoHost where you receive reliable updates from one source.

Maybe one day, OMV will also shift away from plain Debian and control and maintain its own packages.

Nevertheless, thank you Volker and team for providing this nice piece of software for free and your countless hours of support.

Maybe OMV can use Safari's clipboard API with these adjustments?

Javascript Clipboard API write() does not work in Safari

I'm using javascript Clipboard API to copy an image to the clipboard. It works in Chrome and Edge but not in Safari in spite of official documentation of…

stackoverflow.com

True, I'm working with Safari 18 on macOS 15 here.

Seems to be indeed some clipboard API restriction.

Works fine in Firefox so far.

OK, thanks. 37° C is also the more realistic value because the drive was not in real usage the last couple of hours.

I setup openmediavault from scratch today and installed the kubernetes plugin.

openmediavault 7.6.0-1

openmediavault-k8s 7.4.3-1

After activating the plugin I tried to copy the token to clipboard. But it does fail with: Failed to copy data to the clipboard.

I tried with my own user and original OMV admin. Also rebooting the whole machine did not help.

Both binaries k3s and kubectl are available on CLI (via SSH).

Hello. As you set the thread to solved immediately, I am not sure if it is still relevant for you.

Anyways:

Quote from votdev

Please post the content of /etc/smartd.conf.

DEFAULT -a -o on -S on -T permissive -W 0,50,55 -n never,q
/dev/disk/by-id/ata-Samsung_SSD_870_EVO_4TB_xxx \
  -m mail@mydomain.de -M exec /usr/share/smartmontools/smartd-runner


/dev/disk/by-id/nvme-WD_BLACK_SN770M_2TB_xxx -d nvme \
  -m mail@mydomain.de -M exec /usr/share/smartmontools/smartd-runner

Quote from votdev

Do you have configured default values for all devices?

I think so.

Quote from votdev

The configuration is generated according this https://github.com/openmediava…es/etc-smartd_conf.j2#L17

-W DIFF[,INFO[,CRIT]] critical temp is setting from UI + 5 degrees, so this is correct. The UI setting is the INFO value. See https://linux.die.net/man/5/smartd.conf

Thank you for looking up and sharing the insights. But how does this make sense from a user perspective? When I select 50° C in the GUI, then I expect to get a notification when reaching 50° C, not 55. I kindly suggest to adjust openmediavault's way to process the data.

Another issue I encountered on a fresh openmediavault (version 7.6.0-1) this morning:

One drive's temperature on the dashboard is 37° C. I turned on temperature monitoring and set it to 50° C.

openmediavault sent me a mail immediately telling:

Quote

The following warning/error was logged by the smartd daemon:

Device: /dev/disk/by-id/nvme-WD_BLACK_SN770M_2TB_xxx, Temperature 56 Celsius reached critical limit of 55 Celsius (Min/Max ??/56)

Executing smartctl -a shows:

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        37 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    1%
Data Units Read:                    24.682.646 [12,6 TB]
Data Units Written:                 73.273.104 [37,5 TB]
Host Read Commands:                 125.716.680
Host Write Commands:                423.734.597
Controller Busy Time:               865
Power Cycles:                       910
Power On Hours:                     8.233
Unsafe Shutdowns:                   385
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    227
Critical Comp. Temperature Time:    322
Temperature Sensor 1:               57 Celsius
Temperature Sensor 2:               37 Celsius


Error Information (NVMe Log 0x01, 16 of 256 entries)
No Errors Logged

So there seem to be two temp sensors on the drive. openmediavault's dashboard shows the Temperature or sensor 1's value? But smartd daemon watches sensor 2 and throws the alert accordingly?

Thanks

Hi, is this a bug in the GUI?

I turned on S.M.A.R.T. temperature monitoring and set the maximum to 50°C:

E-Mail notifications are turned on.

After applying the S.M.A.R.T. settings I received this email:

Quote

host name: xxx

DNS domain: fritz.box

The following warning/error was logged by the smartd daemon:

Device: /dev/disk/by-id/nvme-WD_BLACK_SN770M_2TB_xxxxx, Temperature 61 Celsius reached critical limit of 55 Celsius (Min/Max ??/61)

Device info:

WD_BLACK SN770M 2TB, S/N:xxxxx, FW:731100WD, NSID:1, 2.00 TB

Display More

The message does refer to a 55 Celsius maximum. So it does look like the selection list in the GUI is mismatched.

Quote from ojtindrum

On my system?

IP is set to static in my modem prefs so yeh always the same ip (the pi was not getting an IP at all)

Sure it makes sense to set a static IP for servers. Nevertheless there are also other ways to fix the IP. E.g. I can setup my DHCP server to always provide the same IP to a certain MAC address. Or you can work with the hostnames in your network, not with IP addresses at all.

So it looks for me that the issue does only occur when setting a static IP. DHCP setups are not affected.

Did you set to static IP before updating?

Quote from votdev

The problem here was that many systems have been using an old configuration for ages. In the course of time, however, changes in the kernel and UDEV have resulted in the device names now being completely different than they were back then. These were changes over which the OMV project has no influence.

P.S. Wouldn't it make sense to warn about a certain risk of 'braking changes' in the Blog and how to fix it in the case of emergency? At least for the 7.5.0 update.

Blog | openmediavault

When updating Home Assistant e.g., I have the feeling that the list of braking changes is longer than the actual improvements.

Thank you, Volker.

So with a fresh setup this specific issue wouldn't affect me anyways.

Grüße aus Mannheim

Hey!

I am new to OMV. I have a lot of experience with Bash, so a fix like this wouldn't be a problem for me. But since I specifically chose a ready-made system like OMV to obtain a certain level of reliability, I wonder: How often do such showstoppers occur?