Posts by vinny

I'm using ZFS on the rock 5b without issues, for now nvme only but will add a HDD later

i heard ZFS via USB is not recommended but on external power i think it should have no issues, don't plan to unplug it without exporting first, and no RAIDZ

would you change anything in

/etc/sysctl.d/99-openmediavault-nonrot.conf

when using zram?

not sure which file loads last this or sysctl.conf...

it looks like this

GNU nano 7.2 /etc/sysctl.d/99-openmediavault-nonrot.conf
# This file is auto-generated by openmediavault (https://www.openmed>
# WARNING: Do not edit this file, your changes will get lost.
# Modify some kernel parameters to reduce disk I/O 
for non-rotating devices
#
# Default values:
# vm.dirty_background_ratio = 10
# vm.dirty_ratio = 20
# vm.dirty_writeback_centisecs = 500
# vm.dirty_expire_centisecs = 3000
# vm.laptop_mode = 0
# vm.swappiness = 60
# vm.vfs_cache_pressure = 100
vm.dirty_background_ratio = 1
vm.dirty_ratio = 20
vm.dirty_writeback_centisecs = 12000
vm.dirty_expire_centisecs = 12000
vm.laptop_mode = 5
vm.swappiness = 1
vm.vfs_cache_pressure = 50

what is a non rotating device?

Quote from ryecoaaron

You use even more ram and you have two systems trying to move some of the same files to tmpfs.

ok I checked the switches on /etc/default there is armbian-ramlog there it doesn't mention which files but sets 50mb limit for /tmpfs which I figured is not very significant

but we're running OMV anyway so better to handle logs to flashmemory plugin as there are specific OMV logs

so i left armbian-ramlog service disabled and turned armbian-zram-config on, that should leave the logs alone for OMV right?

with this i could go higher on ZFS ARC which is nice for a NAS like OMV

but for now i set ZFS ARC to metadata only and will tune it per dataset to have more control over what's cached or not

reminding that ARC is also compressed

i find it very cool that you can double the effective ram on these little boards because there's no way to upgrade them

i get a software failure screen on the webgui when going to "other software" page but no other errors show up

long live the spice

Quote from macom

Which board do you have?

Which image are you using?

How did you "convert armbian to OMV"?

Check and adjust these environment variables after reading this:

https://docs.openmediavault.or…html#custom-configuration

Code

sudo omv-env set "OMV_CPUFREQUTILS_MINSPEED" "200000"
sudo omv-env set "OMV_CPUFREQUTILS_MAXSPEED" "2000000"
sudo omv-env set "OMV_CPUFREQUTILS_GOVERNOR" "performance"
sudo omv-salt stage run prepare
sudo omv-salt deploy run cpufrequtils

Display More

i found by accident setting the min/max speed blank rather than "" solved the issue

both cpu and nvme were struggling

I'm getting a super annoying bug after i convert armbian to OMV the cpu clocks cap at 408mhz, nvme drops to sata speeds, tested on 2 different armbian images, doesn't happen on vendor image

Quote from ryecoaaron

What were you doing when you got this message?

iirc nothing at all just staring at the web gui

emmc can't handle writes much better than SD. If it is onboard, you can't change it if it fails either. stats are only parts of the writes. There are still many, many things logging that will write a lot. zram doesn't help with any of that. If you have swap, the amount of tmpfs being used really isn't relevant since linux will move anything using tmpfs from ram to swap if the system needs the ram.

so what's the downside of keeping them both enabled?

Quote from ryecoaaron

zram will use even more ram if you keep the flashmemory plugin installed. If you uninstall the flashmemory plugin, then your OS media is not protected from writes.

is this erroor i just got related?

Failed to open file (filename=/tmp/bgstatusGzEbO7, mode=r).

OMV\Exception: Failed to open file (filename=/tmp/bgstatusGzEbO7, mode=r). in /usr/share/php/openmediavault/json/file.inc:78
Stack trace:
#0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(437): OMV\Json\File->open()
#1 /usr/share/openmediavault/engined/rpc/exec.inc(98): OMV\Rpc\ServiceAbstract->getBgProcStatus()
#2 [internal function]: Engined\Rpc\Exec->getOutput()
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(122): call_user_func_array()
#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod()
#5 /usr/sbin/omv-engined(544): OMV\Rpc\Rpc::call()
#6 {main}

OS is on emmc, stats monitoring disabled and no network shares for now i think it may be worth it disabling folder2ram/flashmemory in favour of zram if i keep up with backups

Quote from ryecoaaron

since both systems are 64 bit, I don't think persistent data would really be architecture specific. So I would think you could copy data over. But it might depend on the app.

can confirm it works at least for sqlite and meili databases

i noticed the OMV arm installScript disabled zram on armbian is there any reason to keep it that way? with ZFS every gigabyte counts lol

Quote from ryecoaaron

But you had to install zfs-dkms too. Not really a fan of the radxa image. I prefer the Armbian image.

fixed: the problem was that i had low-level formatted that drive to 4kb sector size(for virtualization, 4k iops, it helps) but only UEFI boot systems can see 4k drives so i formatted it back to 512b and everything works, now tested on armbian with vendor kernel(6.1)

next steps are finding how to migrate the amd64 containers to this new platform i have no clue is it as simple as appending image:aarch64 or image:rockchip(for containers that use gpu/npu)?

i guess the container's databases/data can't just be copied over right?

the zfs plugin was the only thing i installed basically, official radxa image also

Quote from ryecoaaron

is /boot/efi mounted?

yes, sorry for the formatting

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS

mtdblock0 31:0 0 16M 0 disk

mmcblk0 179:0 0 29.1G 0 disk

├─mmcblk0p1 179:1 0 16M 0 part /config

├─mmcblk0p2 179:2 0 300M 0 part /boot/efi

└─mmcblk0p3 179:3 0 28.8G 0 part /var/folder2ram/var/cache/samba

/var/folder2ram/var/lib/monit

/var/folder2ram/var/lib/rrdcached

/var/folder2ram/var/spool

/var/folder2ram/var/lib/openmediavault/rrd

/var/folder2ram/var/tmp

/var/folder2ram/var/log

/

mmcblk0boot0 179:32 0 4M 1 disk

mmcblk0boot1 179:64 0 4M 1 disk

zram0 252:0 0 3.9G 0 disk [SWAP]

though the efi folder appears to be empty

Quote from ryecoaaron

https://openmediavault-docs.re…opment/internaltools.html

Ahh you're awesome, i had totally forgotten about the config.xml

is this other error related?

it says no efi is mounted when i try to update initramfs

radxa@rock-5b:~$ sudo update-initramfs -u -k all

update-initramfs: Generating /boot/initrd.img-6.1.43-19-rk2312

Couldn't find EFI system partition. It is recommended to mount it to /boot or /efi.

Alternatively, use --esp-path= to specify path to mount point.

update-initramfs: Generating /boot/initrd.img-6.1.43-15-rk2312

Couldn't find EFI system partition. It is recommended to mount it to /boot or /efi.

Alternatively, use --esp-path= to specify path to mount point.

lsblk

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS

mtdblock0 31:0 0 16M 0 disk

mmcblk0 179:0 0 29.1G 0 disk

├─mmcblk0p1 179:1 0 16M 0 part /config

├─mmcblk0p2 179:2 0 300M 0 part /boot/efi

└─mmcblk0p3 179:3 0 28.8G 0 part /var/folder2ram/var/cache/samba

/var/folder2ram/var/lib/monit

/var/folder2ram/var/lib/rrdcached

/var/folder2ram/var/spool

/var/folder2ram/var/lib/openmediavault/rrd

/var/folder2ram/var/tmp

/var/folder2ram/var/log

/

mmcblk0boot0 179:32 0 4M 1 disk

mmcblk0boot1 179:64 0 4M 1 disk

zram0 252:0 0 3.9G 0 disk [SWAP]

[7:29 PM]

Quote from ryecoaaron

If you have a zfs mntent entry in the database, you will have this. You will have to manually edit the database. I haven't tried zfs on cm3588 (I don't use zfs).

and where is this database located?

Quote from ryecoaaron

omv didn't add that modprobe entry. You are running into some very strange issues.

well everywhere i searched ppl said OMV disables the second interface when you configure another to avoid routing issues, blocking the driver via modprobe.d seemed to make sense

it's a fresh install on top of a fresh arm debian install

i tried installing on omv7/debian kernel 6.1 on a rk3588 board even though zfs-dkms is installed the board won't boot

now i removed everything related to zfs reformatted the(secondary) zfs drive to be able to boot

i think it broke my OMV installation, i keep getting this error spam every 5 seconds

Quote

No file system backend exists for 'zfs'.

OMV\Exception: No file system backend exists for 'zfs'. in /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc:480

Stack trace:

#0 [internal function]: Engined\Rpc\OMVRpcServiceFileSystemMgmt->getList()

#1 /usr/share/php/openmediavault/rpc/serviceabstract.inc(122): call_user_func_array()

#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod()

#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(622): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}()

#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(146): OMV\Rpc\ServiceAbstract->execBgProc()

#5 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(532): OMV\Rpc\ServiceAbstract->callMethodBg()

#6 [internal function]: Engined\Rpc\OMVRpcServiceFileSystemMgmt->getListBg()

#7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(122): call_user_func_array()

#8 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod()

#9 /usr/sbin/omv-engined(544): OMV\Rpc\Rpc::call()

#10 {main}

Display More

this is not working on arm boards right?

managed to bring the nic back to life

fix: delete the file under /etc/modprobe.d/***.conf

i made the mistake of running omv-firstaid on a clean install and configuring up a wlan interface for a quick setup

and now the ethernet nic is gone from ip-a i can see it with lspci and kernel module is loaded but can't find the interface anywhere I tried deleting files in /etc/netplan, running omv-salt etc

guess i could manually add a file to /etc/netplan but i don't remember the interface name?

Thanks in advance.

Quote from jata1

Most containers have pre-built images for the common architectures (arm64 and amd/intel). Need a bit more info on what you are trying to do.

If you really need to build yourself (and I do for one container that is only built for amd when i needed arm64) is.

1. create the compose in the OMV plugin and save but don't pull/start it

2. download the required build files (yes you clone/download the repo.

3. add the additional folders and files to the compose folder (together with compose.yml etc.

4. if necessary edit the dockerfile and build.sh etc

5. update the compose file so it includes the build directive - see below example

6. also worth adding the pull_policy: never directive as you are not pulling this image

7. save the compose file

8. use the build button (cog icon on files menu bar in compose plugin) to try to build it

9 prepare for errors that you will need to work through

Code

services:
  overpass:
    image: overpass:dev
    container_name: overpass-test
    hostname: overpass-test
    pull_policy: never
    build: .  # dot means build from the same folder as the compose yml location 
    ports:
      - 8085:80
    volumes:
      - /symlinks/omv-system/appdata/overpass-test:/db

Display More

Display More

thanks for the comprehensive answer i'll research more, i overlooked the build button too

Quote from ryecoaaron

The plugin sets the build flag if it finds "build:" in the compose file - https://github.com/OpenMediaVa…ined/rpc/compose.inc#L530

Thanks