Posts by Deimos

Guess I'm leaving it running in its current "headless zombie" state, and do a full reinstall next time I'm over there.

I do find it extremely concerning that an update seemingly "suicided" OMV out of my server for some reason.

This might shine some extra light on things:

myusername@raspberrypi:~ $ dpkg -l | grep openmediavault
lsb_release -a
df -h
find / -name omv-firstaid 2>/dev/null
rc  openmediavault                       7.4.17-1                            all          openmediavault - The open network attached storage solution
rc  openmediavault-flashmemory           7.0.1                               all          folder2ram plugin for openmediavault
ii  openmediavault-keyring               1.0.2-2                             all          GnuPG archive keys of the openmediavault archive
rc  openmediavault-omvextrasorg          7.0                                 all          OMV-Extras.org Package Repositories for OpenMediaVault
rc  openmediavault-zfs                   7.1.1                               arm64        OpenMediaVault plugin for ZFS
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 12 (bookworm)
Release:        12
Codename:       bookworm
Filesystem      Size  Used Avail Use% Mounted on
udev            2.0G     0  2.0G   0% /dev
tmpfs           405M  4.7M  400M   2% /run
/dev/mmcblk0p2   29G  3.9G   24G  15% /
tmpfs           2.0G     0  2.0G   0% /dev/shm
tmpfs           5.0M   48K  5.0M   1% /run/lock
tmpfs           2.0G  2.5M  2.0G   1% /tmp
/dev/mmcblk0p1  510M   61M  450M  12% /boot/firmware
radxa-hat-pool  3.6T  780G  2.8T  22% /radxa-hat-pool
tmpfs           405M     0  405M   0% /run/user/1000

Seems to me like the last time I ran an update in OMV it went fully haywire? This is crazy.

I will try that once I get home, but for the record, it can't have been an issue with the installation since as I mentioned above, I used the first aid tool a few weeks ago and it worked fine.

root@raspberrypi:~# /usr/sbin/omv-firstaid
bash: /usr/sbin/omv-firstaid: No such file or directory

root@raspberrypi:~# sudo /usr/sbin/omv-firstaid
sudo: /usr/sbin/omv-firstaid: command not found

EDIT:

Also tried running the sudo variety from my user, not root. Same outcome as the above sudo attempt.

As the title describes.

For context this is a server I have set up and running at a remote location, I cannot physically access it without hopping on a plane.

I can access my samba share over SFTP no problem works fine. I can login over Putty (I use private/public key) and it works fine, the server is there.

But if I teamview into a computer on the server's local network and attempt to access the web-GUI on the server I get the "403 Forbidden" error.

If I ssh into the server and attempt to run "omv-firstaid" the cli returns:

bash: omv-firstaid: command not found

Even if I sudo su and run the command as root I get that result.

So basically this server is working, but I cannot make any changes to the configuration over the web-GUI.

It'll be a while before I'm on location again and able to do something like reinstall the whole thing, and in the meantime my fear is a power interruption causing the server to power-cycle and it not restarting properly and me losing the use of the server until I'm back there.

Any way for me to deal with this issue 100% remotely? I don't even know where to start.

I don't know if this could be relevant but a couple weeks ago I had to run omv-firstaid to reset the online password (I forgot it).

I'm not a big OMV power user. I've been using it for almost a decade very successfully but I only really "pop the hood" and mess with things when I have an issue to solve, want to improve something, or feel like my systems might reeeeally need a profound update (only recently updated one of my NAS from OMV4 to OMV7 ).

This means my perspective is very different from that of much more active/involved community members.

I have noticed something that could be causing issues and troubleshooting needs for absolute beginners: there's conflicting information on how to install OMV out there. This seems to be mostly due to outdated information not being marked as such. A quick example, let's say you're new to OMV and want to install it on an ARM SBC.

One easy-to-find resource is the OMV documentation page on installation, which seems like a pretty solid starting point.

However there are also guides in the forum and other resources that seem targeted at this situation. Here's one guide post from 2019, here's one from 2023. Here's the entry on the omv-extras wiki to which the 2019 post points. So there are at least 4 sets of instructions out there on how to do this.

I am inclined to assume that the documentation page is the most current, but nothing on that page tells me (the hypothetical beginner in this hypothetical scenario) when it was last edited. The only date on it is the copyright blurb at the bottom, which mentions 2018. This could lead me to believe that all those other resources are more recent and thus more up-to-date. Some of them are pinned posts in the guides section of the official forums, after all.

The point of this post is mostly just to point out this issue that I've noticed.

There are several resources out there on how to do the same thing, many of them under direct control of the OMV team.

Maybe it would make sense to mark outdated resources as outdated/legacy? Or to have the date of last edit visible on the docs pages?

Just trying to save some people some trouble .

I'm trying to get an overview of the correct steps/sequence for installing OMV7 and ZFS on a ROCKPro64.

(yes I know some people think ZFS on an SBC is overkill, but I've been using it for years just fine with zero issues since I only use the "base" features of ZFS, nothing fancy, don't worry, I just like it much more than RAID)

(I'm basically trying to go from OMV6 to OMV7 with a clean install)

As far as I see it, the sequence would be:

1. install minimal Bookworm armbian
2. in armbian-config change the kernel version to a mature kernel version for which a header-package is available (like "Linux 6.6.63-current-rockchip64")
3. in armbian-config, install kernel headers
4. exit armbian-config, install zfs-dkms and zfsutils-linux, zfs-dkms uses headers to build ZFS module
5. install OMV
6. after finishing OMV setup, install OMV extras, then install the OMV-ZFS plugin
7. create/import ZFS pool, Bob is my uncle

Is any of this wrong?

EDIT:

ah, and after step 3 I would set the kernel and related packages to be on hold and prevent updates

That was one of the first things I did back when I first attempted to get this going.

Is my OMV acting in an unexpected way?

Not sure how much it matters, I'm on 6.9.16-1 (Shaitan).

You mean like this?

it has been enabled all along

(sorry for the giant delay, I literally moved half-way across the country, haven't had much time to focus on this)

mine looks very different:

#This file blablabla
#WARNING: Do not blablabla

ZED_EMAIL_ADDR=-----@------.--- (redacted by me right now)
ZED_NOTIFY_INTERNAL_SECS=3600

Nothing about verbose or excluded subclass, plus those lines with "root@omvt" you have on yours at the start and end are missing from mine.

Howdy!

I'm trying to get verbose zfs/zed notifications over e-mail.

The normal e-mail notifications are working fine, but I see no way to make zed verbose, since:

• if I manually configure it in /etc/zfs/zed.d/zed.rc, the settings get lost (the file itself tells you it's pointless to do config there since it's auto-generated by OMV)
• there's no setting on the web interface to configure verbose zed notifications.

Any ideas?