Posts by ananas

WD30EFRX are the CMR (Conventional Magnetic Recording) drives, no issues with these drive type and RAID.

For these E-Mails take a look here:

mdadm: cannot be set as devname. Reason: Not POSIX compatible | openmediavault

Or simply: "chattr +i /var/www/openmediavault/assets/images/login.jpg"

Your drives WD40EFAX are so called SMR (Shingled Magnetic Recording) drives and are known to cause trouble with RAID.

How about the drive types in your other RAID ?

I'm using MiniDLNA since 2014 without any issue,

and I was glad that ryecoaaron ported it to OMV8.

Just did a full backup of my system drive before running the upgrade.

All went well and smooth. (no need to run fix7to8upgrade)

Many thanks to Volker and Aaron for all their work.

You could try:

apt-get install -s <package-name>

to see which dependencies would get installed, the less, the better.

A full backup of your system drive BEFORE is not a bad idea.

(that way I installed syncthing on my OMV box as it did not show any dependencies)

Maybe somebody should update Problem/Solution #3

If the user is member of the group "openmediavault-admin" then that user has the same power in the WebUI as the admin user.

If you have installed OMV v7.x (very likely, because it's the actual version ) you need to install the "openmediavault-md" plugin.

Then under "Storage --> Multiple Device" you should see your RAID-1 Array.

Under "Storage --> File Systems" you should see your filesystem.

Now mount your existing filesystem and (re-)create your shares.

Out of curiosity,

what kind of PCIe card did you use in favor of the Intel i219 ?

I'm using the MiniDLNA plugin with my LG-TV since years, small footprint, easy to configure and works like a charm.

Just make sure that the "minidlna" user has read permissions on your media files.

The rsyslog documentation is a PITA (old vs. new config syntax)

Here is my finally working config file:

# Provides TCP syslog reception
module(load="imtcp")
input(type="imtcp" port="514")

# Provides UDP syslog reception, not needed till now
# module(load="imudp")
# input(type="imudp" port="514")

$template routerlog, "/var/log/banane.log"
if $fromhost-ip == "192.168.0.1" then -?routerlog
& stop

Next thing will be "logrotate"

I hope the man page is not as bad as the one of rsyslog

My routers syslog is stored in a ramdisk and lost upon a reboot/crash.

For debugging purposes I would like to log to some persistant storage.

So I have cretaed an additional .conf file in /etc/rsyslog.d with the following content

# Provides TCP syslog reception
module(load="imtcp")
input(type="imtcp" port="514")

:fromhost-ip, isequal, "192.168.0.1" /var/log/banane.log
& stop

When using logger "some blabla" on the router I can see it in it's syslog but not in the specified logfile on the OMV box.

Any hint appreciated

I would like my OMV box to accept remote syslog messages from my router.

All the config files have a header like this:

# This file is auto-generated by openmediavault (https://www.openmediavault.org)

# WARNING: Do not edit this file, your changes will get lost.

How can I add the required changes to the config files w/o loosing them ?

You also might create a user (or use an existing one) and add him to the "openmediavault-admin" group.

The device tree information is available via /proc/device-tree.

You change the device tree information by modifying the underlying *.DTS and/or *.DTSI source files and send them through the device tree compiler (dtc) to generate the DTB (device tree binary) file, which is read at boot time or part of the kernel image being loaded.

Why not running syncthing as native application on OMV ?

I did a test on a VM and:

apt-get install syncthing -s did not show any dependencies

After installing syncthing create a user in the OMV Gui, in my case the user "syncthing"

Make sure that his homedir is on your "main storage"

After that:

systemctl enable syncthing@syncthing.service

systemctl start syncthing@syncthing.service

After that modify ~syncthing/.config/syncthing/config.xml

serach for 127.0.0.1 and replace with 0.0.0.0

systemctl restart syncthing@syncthing.service

Syncthing has it's own Gui available on https://192.168.xx.yy:8384

It's up to you to set a password

List Folder Content = Read Permissions on the directory.

Neither Read nor execute the contents = no permissions on the file(s)

I guess the Read/Write or Read-Only permissions in the gui apply to both, the directories and the files.

You can only archive this by using "setfacl" on the command line.

There are lot's of discussions regarding hardware recommendations.

You might start here:

Thread

Why I chose an N100 over a Raspberry PI5

I have a server at a relative's house, it is an old i2500k whose motherboard has started to have problems, so I have to replace the hardware. This server serves as a remote backup to my server, plus provides a media center and other services in that home. So I looked for alternatives for these basic needs:

- Connect a minimum of 4 existing hard drives on the original server through SATA ports.
- Preferably, although not essential, reuse the minitx box and power supply in which the original server…

chente

Nov 17th 2023

Do not use the full wipe from the GUI, it takes ages.

Read the wipefs manpage and use it, much faster ...

You will have to install OMV without any disk in slot 1-4, this will install GRUB on the SSD.

Next step is to insert a SD-Card or USB-Stick (internal)

Boot OMV from SSD and install GRUB on the SD-Card/USB-Stick. (read the man page "man grub-install")

Now insert disk(s) into slot 1-4 and when done correct, it should still boot OMV.