Posts by mbinax

I solved by repeating from scratch the Nvidia drivers installation procedure (for OMV7).

Immediately after setup, I noticed some drivers available for update in the "OMV updates" screen but I didn't run them and everything went fine.

Unfortunately, these updates have been performed automatically later and now Plex container (and also a few other containers running with "nvidia" runtime) stopped working again!

How can I fix this?

Tks so much.

Hello!

About ten days ago I followed this guide to setup my NVIDIA Drivers from scratch (for OMV7).

I also edited my existent PLEX container.

The procedure was completed successfully, except that PLEX was not able to use NVIDIA for transcoding...

However, I was able to restart and use the old/new PLEX container...

Some days ago I noticed that OMV has updated NVIDIA drivers (without rebooting).

This is the current setup:

Unfortunately... yesterday night... after a restart, the PLEX container is no longer able to start due to the following error:

Failed starting container: failed to create task for container: failed to create shim task: OCI runtime create failed: could not apply required modification to OCI -specification: error modifying OCI spec: failed to inject CDI devices: unresolvable CDI devices runtime.nvidia.com/gpu=all: unknown

FYI, this is the PLEX container configuration:

Damn...Why does it happen?

Any idea?!?

Furthermore, I don't understand why transcoding isn't working... my processor is an AMD Ryzen 3700, could that be affecting it?

Quote

Yes, replace them with conventional drives

What do you mean for "conventional"?

Maybe "CMR" is conventional?

Thank you.

I've set SMART tasks to monitor my drives:

• short self-test > weekly
• long self- test > monthly

However, I am a bit concerned because now the drive that is reported "corrupted" is /dev/sda, whereas until a few days ago it was /dev/sdb.

I'm afraid both will have to be changed....

Currently, my RAID is made with 6TB drives (3x Seagate "ST6000NM0115-1YZ110", 3x Seagate "ST6000NM0095"): considering the cost of HDDs, should I gradually replace them with more modern and larger but (hopefully) less expensive HDDs?

Quote from geaves

You can double check the drive removal by running mdadm --detail /dev/md0 from the cli

If you see 'removed' next to /dev/sdb then mdadm has remove the disk from the array, all you need to do is to replace the drive;

Shut down and remove the failed drive

Install a new drive -> start up

Storage Disks -> select the drive and do a quick/short wipe, this will prepare the drive for OMV to use

Raid Management/Md - Plugin there should be an option 'recover', click on that and your new drive should be displayed, select it and click OK the drive will then be added to the array

Display More

Confirmed, the drive is already removed, as you can see below.

Since this situation occurs, my NAS it stops and turns itself off.

When turned on (manually), I'm receiving mails like this one:

This is an automatically generated mail message from mdadm

running on diynas-omv


A DegradedArray event had been detected on md device /dev/md0.


Faithfully yours, etc.


P.S. The /proc/mdstat file currently contains the following:


Personalities : [raid6] [raid5] [raid4] [raid0] [raid1] [raid10] 

md0 : active raid5 sdd[5] sda[2] sdc[4] sdf[1] sde[0]

     29301969920 blocks super 1.2 level 5, 512k chunk, algorithm 2 [6/5] [UUU_UU]

     bitmap: 44/44 pages [176KB], 65536KB chunk


unused devices: <none>

I suppose this situation depends on the harddrive damaged, am I right?

Then... before proceeding to remove it, I'm just asking to myself how can I recognize the right drive to remove! Any idea also here?

Hello,

about 4 years ago I set up the NAS with 6TB disks, which I configured in RAID5.

Since a few days I've been getting a warning message from the daily checks done by OMV, so I investigated and noticed that RAID 5 is on 5 disks (instead of all 6 installed ones); also, the missing disk has a "Warning" with "Bad sectors".

I guess I need to replace the disk, but what would be the correct procedure?

Could you point me to a guide?

Below you can see - from OMV GUI - the RAID configuration (labeled as "degraded."

Here you can see the detail of the missing disk, namely "sdb":

Finally, here is some data taken from CLI to help understand the overall situation:

root@diynas-omv:/srv/dev-disk-by-label-RAID5/# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4] [raid0] [raid1] [raid10] 
md0 : active raid5 sdc[4] sdd[0] sdf[1] sde[5] sda[2]
      29301969920 blocks super 1.2 level 5, 512k chunk, algorithm 2 [6/5] [UUU_UU]
      bitmap: 40/44 pages [160KB], 65536KB chunk
unused devices: <none>

root@diynas-omv:/srv/dev-disk-by-label-RAID5/# blkid
/dev/sdf: UUID="add77410-4af9-84b4-4a1b-f4c9a53296ae" UUID_SUB="540cd822-1281-aead-7f6f-ca4f0842dc80" LABEL="DIYNAS-OMV:RAID5" TYPE="linux_raid_member"
/dev/nvme0n1p5: UUID="21dbc86c-cfc1-4b4a-a9ed-566388d70285" TYPE="swap" PARTUUID="5b2a273a-05"
/dev/nvme0n1p1: UUID="975fe369-9535-4459-80f8-f86795bdcb26" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="5b2a273a-01"
/dev/sdd: UUID="add77410-4af9-84b4-4a1b-f4c9a53296ae" UUID_SUB="9e5d7091-039a-77b5-77b8-c3450cc7cac8" LABEL="DIYNAS-OMV:RAID5" TYPE="linux_raid_member"
/dev/sdb: UUID="add77410-4af9-84b4-4a1b-f4c9a53296ae" UUID_SUB="f6d205c8-bc1a-5cd1-6a8a-7458a4b0c817" LABEL="DIYNAS-OMV:RAID5" TYPE="linux_raid_member"
/dev/md0: LABEL="RAID5" UUID="b143f942-1f22-42e0-b92d-4e4c557ff36c" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sde: UUID="add77410-4af9-84b4-4a1b-f4c9a53296ae" UUID_SUB="f5ddc7d4-d721-6796-e75e-733251246271" LABEL="DIYNAS-OMV:RAID5" TYPE="linux_raid_member"
/dev/sdc: UUID="add77410-4af9-84b4-4a1b-f4c9a53296ae" UUID_SUB="1e112d20-45bd-32d0-9ebf-69bea2a73f9b" LABEL="DIYNAS-OMV:RAID5" TYPE="linux_raid_member"
/dev/sda: UUID="add77410-4af9-84b4-4a1b-f4c9a53296ae" UUID_SUB="93903863-bbf5-8435-c86f-c1dc338c5bb7" LABEL="DIYNAS-OMV:RAID5" TYPE="linux_raid_member"

root@diynas-omv:/srv/dev-disk-by-label-RAID5/# fdisk -l | grep "Disk "
Disk /dev/nvme0n1: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Samsung SSD 970 EVO Plus 250GB          
Disk identifier: 0x5b2a273a
Disk /dev/sdc: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: ST6000NM0095    
Disk /dev/sdf: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: ST6000NM0095    
Disk /dev/sdd: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: ST6000NM0095    
Disk /dev/sda: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: ST6000NM0115-1YZ
Disk /dev/sde: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: ST6000NM0115-1YZ
Disk /dev/sdb: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: ST6000NM0115-1YZ
Disk /dev/md0: 27.29 TiB, 30005217198080 bytes, 58603939840 sectors

root@diynas-omv:/srv/dev-disk-by-label-RAID5/# cat /etc/mdadm/mdadm.conf
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.


# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#


# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
# used if no RAID devices are configured.
DEVICE partitions


# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes


# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# instruct the monitoring daemon where to send mail alerts
MAILADDR my-mail@my-domain.com
MAILFROM root


# definitions of existing MD arrays
ARRAY /dev/md0 metadata=1.2 name=DIYNAS-OMV:RAID5 UUID=add77410:4af984b4:4a1bf4c9:a53296ae

root@diynas-omv:/srv/dev-disk-by-label-RAID5/# mdadm --detail --scan --verbose
ARRAY /dev/md0 level=raid5 num-devices=6 metadata=1.2 name=DIYNAS-OMV:RAID5 UUID=add77410:4af984b4:4a1bf4c9:a53296ae
   devices=/dev/sda,/dev/sdc,/dev/sdd,/dev/sde,/dev/sdf

Thank you very much!

Hello,

I am monitoring the resources of my NAS and consistently notice high CPU consumption by Nginx (SWAG):

The reverse proxy is used in a Docker container with this compose file:

version: "2"
services:
swag:
image: ghcr.io/linuxserver/swag
container_name: swag
cap_add:
- NET_ADMIN
environment:
- PUID=1000
- PGID=100
- TZ=Europe/Rome
- URL=my_domain.it
- SUBDOMAINS=wildcard
- VALIDATION=dns
- DNSPLUGIN=cloudflare
- EMAIL=my_email@address.com
volumes:
- /srv/dev-disk-by-label-RAID5/appdata/swag:/config
ports:
- 443:443
- 80:80 #optional
restart: unless-stopped

Someone else have the same?

Quote from gderf

All you need to do is come up with a compose file for the plex docker image you are using and create volume bind mounts for your media and existing config directory.

Thanks. I'll try this approach..

Quote from gderf

Plex hardware transcoding requires a Plex Pass subscription. Do you have one?

Yes, sure. I have Plex Pass.

Let me show below all current container configurations, to migrate in a compose file.

Docker image:

linuxserver/plex:latest

Mapping section:

Env section:

PUID=1000
PGID=100
VERSION=docker
UMASK_SET=022
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOME=/root
LANGUAGE=en_US.UTF-8
LANG=en_US.UTF-8
TERM=xterm
NVIDIA_DRIVER_CAPABILITIES=all
NVIDIA_VISIBLE_DEVICES=all
DEBIAN_FRONTEND=noninteractive
PLEX_DOWNLOAD=https://downloads.plex.tv/plex-media-server-new
PLEX_ARCH=amd64
PLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR=/config/Library/Application Support
PLEX_MEDIA_SERVER_HOME=/usr/lib/plexmediaserver
PLEX_MEDIA_SERVER_MAX_PLUGIN_PROCS=6
PLEX_MEDIA_SERVER_USER=abc
PLEX_MEDIA_SERVER_INFO_VENDOR=Docker
PLEX_MEDIA_SERVER_INFO_DEVICE=Docker Container (LinuxServer.io)
S6_CMD_WAIT_FOR_SERVICES_MAXTIME=0
S6_VERBOSITY=1
S6_STAGE2_HOOK=/docker-mods
LSIO_FIRST_PARTY=true
VIRTUAL_ENV=/lsiopy
TMPDIR=/run/plex-temp

Hello, I'm currently running Plex Server into a historic Docker container (since 5y ago).

This container was built "from scratch", through the Portainer GUI.

I'd like to move ahead this (old style) approach, by using Stocks and compose file to "rebuild" the current container.

I'm worried because:

• I'm not sure if this is possible, and how
• I don't want to lose my current configs and/or history (libraries, agents, lists, watched items, ...)

FYI : apart of the compose adoption... another reason-why for the migration is that I've just installed a Nvidia P2000, but Plex Server is not using hardware transcoding, even if the option is enabled in the server settings, NVIDIA drivers (570) and Container Toolkit are installed with toolkit running.

Solved here:

New update available | openmediavault

I hope this can help someone else

Hello.
I've the same issue, my OMV is updated from OMV5 but this is the first time that an error occurs...

This is the output of the command grep -ri stable /etc/apt

/etc/apt/apt.conf.d$ grep -ri stable /etc/apt
grep: /etc/apt/trusted.gpg.d/debian-archive-bullseye-stable.gpg: il file binario corrisponde
grep: /etc/apt/trusted.gpg.d/debian-archive-bookworm-stable.gpg: il file binario corrisponde
grep: /etc/apt/trusted.gpg.d/debian-archive-buster-stable.gpg: il file binario corrisponde
/etc/apt/sources.list.d/omvdocker.list:deb [signed-by=/usr/share/keyrings/docker.gpg arch=amd64] https://download.docker.com/linux/debian bullseye stable
/etc/apt/apt.conf.d/50unattended-upgrades://   a,archive,suite (eg, "stable")
/etc/apt/apt.conf.d/50unattended-upgrades:        // archives (e.g. from testing to stable and later oldstable).
/etc/apt/apt.conf.d/50unattended-upgrades:        // new stable).
/etc/apt/apt.conf.d/50unattended-upgrades://      "o=Debian,a=stable";
/etc/apt/apt.conf.d/50unattended-upgrades://      "o=Debian,a=stable-updates";

Can someone help me to solve it, please?

How should I launch the following command in docker, to be able to update Nextcloud db?

occ db:add-missing-indices

I tried with this command, with no success:

Hello!

I'm using OMV6 with Docker and Portainer.

It was s a lot since I didn't use Tautulli: unfortunately, today I noticed that it's not working any more.

In the log - from Portainer - I caught this:

Someone knows why this happens, and how to solve?

Ok, solved.

Thank you!

Quote from ryecoaaron

Did you include a package name after apt-get install?

Uhm, no.
Shall I? Sorry, I'm not so expert...

Quote from ryecoaaron

what does it tell you when you try to manual install those packages with apt-get install

Reading package lists... Done

Building dependency tree... Done

Reading state information... Done

0 upgraded, 0 newly installed, 0 to remove and 11 not upgraded.

Some QEMU packages does not update during GUI update procedure.

Is this "correct"?

Please, consider that I'm not really using QEMU/KVM... I just tried to "play" with it adding a couple of Pools and one Network (not really used).

Quote from macom

Did you follow the link? It tells you what has been ported or what a replacement is.

Sorry, what link do you mean?

Quote from Zoki

Thread

omv-extras plugins - porting progress to OMV 6.x (done)

Here is the current status of porting omv-extras plugins to OMV 6.x. If the plugin isn't on the list, it won't be ported or is a core OMV plugin.

25 of 25 - done


openmediavault-anacron - done
openmediavault-apttool - done
openmediavault-autoshutdown - done (thanks to nrandon)
openmediavault-backup - done
openmediavault-borgbackup - done
openmediavault-developer - done
openmediavault-downloader - done
openmediavault-fail2ban - done
openmediavault-flashmemory - done
openmediavault-kvm - done
…

ryecoaaron

Jul 24th 2021

Containers will just survive.

What about plugins?
Is there any way to understand if they are migrated to OMV6 or not?

Quote from Zoki

Update procedure depends on the services you are using.

In general:

• check that all plugins you use have been migrated
• ssh to the server and (as root) omv-release-upgrade

Is it worth it? OMV5 will be end-of-life soon and if you want to get updates / support ...

And yes, I upgraded from OMV 5 to OMV6 all of my systems.

Thank you!

I'm using services as containers, within Portainer:

How/Where can I check about plugins migration to OMV6?

I've installed just someone:

• openmediavault-flashmemory 5.0.9 (repo: /)
• openmediavault-diskstats 5.1.1-2 (repo: openmediavault archive/usul)
• openmediavault-autoshutdown 5.1.21 (repo: /)
• openmediavault-kvm 5.1.7 (repo: /)
• openmediavault-omvextrasorg 5.6.6 (repo: /)
• openmediavault-resetperms 5.6 (repo: /)
• openmediavault-wol 3.4.2 (repo: /)