Posts by cubemin

LUKS is a Linux standard encryption scheme and not dependent on OMV. So yes, it will work in OMV 6.

Quote from venicenerd

Where can I enable this option? I'm not seeing it in OMV under FTP settings. Thanks!

It's on the Advanced page of the FTP settings.

Quote from Agricola

Yes, and I think so. Try it and see. It won’t hurt anything.

Are you sure Agricola ? I have changed multiple settings before applying them before with no issues.

As for moving between sections before applying - I'm not 100% sure but I think any settings made to a section are lost when going to another section (and will show as having reverted when you go back).

It may be that the disk you're having issues with needs a filesystem check, i.e. e2fsck /dev/sdxy where x = the drive letter and y = the partition (usually 1).

As for Emby, is it running alongside OMV or as a Docker container? I use Emby myself and might be able to help with the cache clearing issue.

Or get a phone that's supported by Lineage OS and either add microG or skip the Google services framework altogether. There are plenty of ways.

I don't think you'll need a VPN solution, since rsync connects to remote servers through an SSH tunnel. By simply forwarding your Macbook's SSH port to the public Internet (use a custom port other than 22), then creating a private/public key pair and disabling password-based logins, you should have a straightforward way of running remote backups while maintaining appropriate security.

You may find some of these useful...

Enable the option 'No session reuse required.' That should fix your issue.

Sounds like a Postfix issue; also it looks like Postfix has its own resolv.conf file... I googled and found this thread which may point you in the right direction (hopefully).

Quote from macom

It happened several times the last week that docker pulled not only one image but tried to pull all images. A workaround was (is?) to add the :latest tag.

Not sure if it has been fixed already.

Thankfully, it has been. Portainer 2.51 now adds the ":latest" tag automatically.

macom 's advice is of course spot on, but I'm a bit confused as to how this thread started out about /dev/sdb and /dev/sdc but suddenly we're looking at /dev/dm-0 and /dev/dm-1. Aren't those typically RAID arrays? (Not that one should be able to create an array using just one disk.)

It's showing up in the OMV GUI as mounted as well?

OK, so /dev/sdc is recognized and LUKS decryption is active.

What you didn't mention is whether the filesystem (on /dev/sdc-crypt) is mounted as well.

Is it?

You don't need qemu-kvm- it's superseded by qemu-system-x86 which itself provides a wrapper to run qemu-system-x86 in kvm mode. If you're trying to install updates, update qemu-system-x86 first, ignoring qemu-kvm.

See the outputs from my OMV system:

root@cubeserv:~# apt show qemu-system-x86
Package: qemu-system-x86
Version: 1:5.2+dfsg-9~bpo10+1
Priority: optional
Section: otherosfs
Source: qemu
Maintainer: Debian QEMU Team <pkg-qemu-devel@lists.alioth.debian.org>
Installed-Size: 34.7 MB
Provides: qemu-kvm, qemu-system-i386, qemu-system-x86-64
Depends: libaio1 (>= 0.3.93), libasound2 (>= 1.0.16), libbrlapi0.6, libc6 (>= 2.28), libcacard0 (>= 2.2), libcapstone4 (>= 4), libepoxy0 (>= 1.3), libfdt1 (>= 1.6.0), libgbm1 (>= 7.11~1), libgcc1 (>= 1:4.7), libglib2.0-0 (>= 2.39.4), libgnutls30 (>= 3.6.6), libibverbs1 (>= 1.1.6), libjpeg62-turbo (>= 1.3.1), libncursesw6 (>= 6), libnettle6, libnuma1 (>= 2.0.11), libpixman-1-0 (>= 0.19.6), libpmem1 (>= 1.4), libpng16-16 (>= 1.6.2-1), librdmacm1 (>= 1.0.15), libsasl2-2 (>= 2.1.27+dfsg), libseccomp2 (>= 2.1.0), libslirp0 (>= 4.0.0), libspice-server1 (>= 0.13.1), libtinfo6 (>= 6), libudev1 (>= 183), liburing1 (>= 0.7), libusb-1.0-0 (>= 2:1.0.22), libusbredirparser1 (>= 0.6), libvdeplug2, libvirglrenderer0 (>= 0.7.0), libxendevicemodel1, libxenevtchn1, libxenforeignmemory1, libxengnttab1, libxenmisc4.11, libxenstore3.0 (>= 4.2~), libxentoolcore1, zlib1g (>= 1:1.2.0), qemu-system-common (>> 1:5.2+dfsg-9~bpo10+1~), qemu-system-data (>> 1:5.2+dfsg-9~bpo10+1~), seabios (>= 1.10.2-1~), ipxe-qemu (>= 1.0.0+git-20131111.c3d1e78-1~)
Recommends: qemu-system-gui (= 1:5.2+dfsg-9~bpo10+1), qemu-utils, ovmf
Suggests: samba, vde2, qemu-block-extra (= 1:5.2+dfsg-9~bpo10+1), sgabios
Breaks: qemu-kvm
Replaces: qemu-kvm
Homepage: http://www.qemu.org/
Download-Size: 8,144 kB
APT-Manual-Installed: yes
APT-Sources: http://httpredir.debian.org/debian buster-backports/main amd64 Packages
Description: QEMU full system emulation binaries (x86)
 QEMU is a fast processor emulator: currently the package supports
 i386 and x86-64 emulation. By using dynamic translation it achieves
 reasonable speed while being easy to port on new host CPUs.
 .
 This package provides the full system emulation binaries to emulate
 the following x86 hardware:  i386 x86_64.
 .
 In system emulation mode QEMU emulates a full system, including a processor
 and various peripherals.  It enables easier testing and debugging of system
 code.  It can also be used to provide virtual hosting of several virtual
 machines on a single server.
 .
 On x86 host hardware this package also enables KVM kernel virtual machine
 usage on systems which supports it.

and

root@cubeserv:~# apt show qemu-kvm
Package: qemu-kvm
Version: 1:3.1+dfsg-8+deb10u8
Priority: optional
Section: oldlibs
Source: qemu
Maintainer: Debian QEMU Team <pkg-qemu-devel@lists.alioth.debian.org>
Installed-Size: 110 kB
Depends: qemu-system-x86
Homepage: http://www.qemu.org/
Tag: role::shared-lib
Download-Size: 72.8 kB
APT-Sources: http://deb.debian.org/debian buster/main amd64 Packages
Description: QEMU Full virtualization on x86 hardware
 QEMU is a fast processor emulator.  This package provides just a wrapper
 script /usr/bin/kvm which run qemu-system-x86 in kvm mode for backwards
 compatibility.

If I may ask - wouldn't it be far simpler to go with a "real" UPS (APC or Cyberpower) and plug everything into it? You'd have complete protection for all devices including the hard disks, and one of your RPis could communicate with the UPS via USB (and keep the other one in the loop as well).

Naja, OMV hat ein Dashboard, in dem man weitere Infotabellen hinzufügen kann.

Cockpit hat ebenfalls eine Systemzusammenfassung, die grafisch recht ansprechend ist. Der Nachteil beider Methoden ist natürlich: man muss sich erstmal einloggen...

Oder per SSH auf Tools wie z.B. top zugreifen.

Ansonsten fällt mir im Moment nichts ein...

Use the remaining 2TB for a second partition - you could use it for temporary storage, downloads, anything. It would just be a shame to waste it. 🙂

Quote from OMV-Newbie2

Somit kann ich weewx nicht einfach über die Konsole installieren und konfigurieren.

Mir scheint es so, dass Du in der Tat genau das tun kannst. Es gibt keinen offensichtlichen Grund, warum weewx und OMV (welches ja auf Debian basiert) nicht nebeneinander auf derselben Hardware laufen sollten. Ich schlage vor, einfach mal die weewx-Dokumentation zu studieren.

Have had this happen to me, but that was a while ago with Portainer 2.1.1. So it's not a new issue in 2.5.0.

It appears to be a problem specifically with ghrc.io images, which you have to use advanced mode to pull anyway.

Don't use the secure wipe - it's literally a waste of time. Use the quick wipe.

Can you confirm that /dev/md126 entry is really, truly gone?

When you go to grow your RAID5 array, it should show you the new disk /dev/sdd. If you see /dev/mdxxx (where xxx could be 126 or some other odd number except 0), then something is not right.