Posts by pcon

    This works for me

    For OMV 4.x only

    cd /etc/apt/sources.list.d

    sudo mv omv-extras-org.list omv-extras-org.bak

    echo "deb arrakis main" | sudo tee omv-extras-org.list

    cd /etc/apt/trusted.gpg.d/

    sudo wget

    sudo apt-key add omvextras2026.asc

    sudo apt-get update


    omv-update was terminated with some errors like: 403 Forbidden or failed to fetch. How to fix this problem?



    It si possibile to expand the raid 1 to raid 5

    mdadm /dev/md0 --grow --level=5 --raid-devices=3 --add /dev/newdisk

    Do first a backup and and than change the raid level with mdam grow. Maybe it is faster to backup the data, to break up the RAID 1 array, to create a RAID 5 with the 3 disks and restore the data to the RAID 5 than to do the mdadm grow.

    mdadm manpage

    OMV don‘t have a calender function, Nextcloud can do this.

    Have you tested some other protocoll like FTP or have you done a speedtest with iperf? This can help to check the network speed of you device and can be compared to the SMB speed. Also helpfull is to check the net speed with to other devices. Can you do the tests and post the results?

    You have a RAID 10, which means 2 x RAID 1 with 2 disks of 4 GB each. The 2 x RAID 1 are combined to 1 x RAID 0 with 8 TB. When a disk is replaced in your RAID 1 array, the disk must be at least 4GB in size for the RAID 1 mirror to be restored, the RAID 1 of 4GB cannot be smaller. A larger disk (6TB) than 4 TB can be installed in RAID 1, but the RAID 1 will be restored with 4 TB.

    The following applies to a RAID 1 WITHOUT RAID 0 array. If you want to bring the RAID 1 array to the new disk size of 6 TB, you have to install a second disk with 6 TB. Procedure: Replace one disk with a larger one, rebuild the RAID 1 array, dissolve the RAID 1 array, adjust the partitions, rebuild the RAID 1 array with the second large disk. That's it. With RAID 0 this procedure is not possible, because as soon as a side/disk of RAID 0 is defective or is removed, the RAID 0 is bricked. In your case: data backup of the 8TB from RAID 0, break up RAIDs, create RAIDs with 4 bigger disks and restare the data. That's the theory.

    Practically: Save the data from the RAID 0 to another media, break up the RAID 0 array and create a RAID 5 with the 4 disks, restore the data to the RAID 5, thus turning the 8TB into 12TB of disk space.

    Un Raspi 4 con 4 GB va bene. Le 2 HDD di 10 GB non li puoi attaccare direttamente al USB del Pi 4. Al Pi 4 puoi usare direttamente 1 x HDD 2,5“ o 2 x SSD o 1 x HDD 3,5“ con alimentatore. Per 2 o più HDD si pu usare un USB HDD case con l’alimentazione o il Raspberry 4 SATA HAT Quad NAS.

    Per me il Raspi e un buon NAS con OMV e con 1 x HDD, per un NAS con 2 x HDD preferisco un Odroid-HC 4 che costa ca. 85€ inclusivo case e attacchi per due 3,5“ HDD e funziona anche con OMV.

    OMV funziona anche in Italiano 🇮🇹

    Maybe as a virtual machine or as a docker container, but this don't make sense, because OMV has a own firewall (iptables) and the infirme developers recommend virtual environments only for testing and development purposes.

    Yesterday I get this 2 Emails where the monitoring system restart the HDD filesystems. Here the messages:

    Any idea why both filesytems (HDDs) are no readable?

    cu pcon

    Nel video viene usato il Port 9000 per omv. Cambia i Port di omv, così poi usare il Port 80 e il Port 443 per il Pihole, oltremente devi cambiare i Port del Docker Container. USA sulla la sinistra il Port 8080 -> 80 e 4443 -> 443.

    Il protocollo (port) 443 (HTTPS) non funziona per piHole e pihole non si può collegare sul Port 443. c’è qualche altra cosa che usa il Port 443 sul Pi, come il login su OMV?