Posts by backslash

Ich betreibe meine Kiste mit einer PicoPSU und lasse sie durchlaufen weil auch ein Tvheadend Server auf der Kiste läuft. Ich lege nur die Platten schlafen. Tvheadend nimmt auf eine gesonderte Partition der Boot Platte (SSD) auf. Ich denke, der Stromverbrauch sollte sich so in Grenzen halten. Jedenfalls ist unsere Stromrechnung für einen Dreipersonenhaushalt recht überschaubar.

Native Installation via APT unter Buster sollte nach wie vor klappen. Gibt ja auch das entprechende Paket von Tvheadend. Das war auch der Tenor bei Kodinerds als ich vor einiger Zeit mal danach gefragt hatte.

https://apt.tvheadend.org/unstable/dists/buster/main/

Allerdings ich selbst habe es unter Buster noch nicht ausprobiert.

Quote from davidh2k

Es gibt von ryecoaaron ein Script zum upgraden.

Alles was ich bisher gesehen habe, sah doch sehr nach Gebastel aus. Da kann ich auch gleich neu installieren und habe dann eine wirklich saubere Installation ohne Altlasten.

Nativ läuft es bei mir seit Monaten absolut stabil und die Einrichtung mit der Kodinerds Anleitung ist doch recht problemlos. Ich bin allerdings noch auf OMV 4 unterwegs weil ich den Upgrade Aufwand bisher gescheut habe. Leider gibt es ja bei OMV keinen einfachen Upgrade Pfad und auf einer erneute Installation/Einrichtung habe ich derzeit keine Lust.

Nutze ebenfalls eine dedizierte Partition für Aufnahmen und Timeshift die ich einfach im Tvheadend Webfrontend nach der Installation eingetragen habe. In meinem Fall nutze ich den selben Ordner für Aufnahmen und Timeshift: /srv/dev-disk-by-label-Aufnahmen/Aufnahmen

Native Installation ist keine Option?

https://www.kodinerds.net/inde…0d2bb98ea4dea537c7353be89

I always proceed like this: I do the one disk installation with OMV and then shrink the system partition and create a new "data" partition using gparted as described in this tutorial (in german):

https://www.technikaffe.de/anl…rung_der_systemfestplatte

The data partition on the OMV disk (SSD) I only use for disposable data like tvheadend recordings. All addtional drives I use fore "real" data.

Of course I mentioned the external PSU that is required and provided the respective link in addition. From the link I provided:

"We do not use a conventional ATX power supply in the NAS Basic, but use a PicoPSU-90 (DC-DC converter) in combination with an economical Salcar 72W external power supply. This allows the idle consumption to be reduced to approx. 10 watts. The power supply is sufficiently large with 72 watts and can easily supply up to 4 data hard drives."

You can add more by using such an adapter. I did the same.

https://www.amazon.de/DELOCK-A…143210&s=computers&sr=1-8

I never calculated the required watts and simply followed the recommendation on the website I posted. They mention that you can easily power 4 harddrives with the 90 watt Pico(PSU) and the 72 watt externel PSU that they recommend. The 80 watt Pico should be sufficient to power up to 3-4 harddrives for sure.

80 watts is ok but 90 would be better if you can get one. Especially if you intend to add addtional harddrives at some point. In addition to the PicoPSU you will need an actual PSU like this one which gets plugged into the PicoPSU:

https://www.amazon.de/gp/produ…kCode=as2&tag=elefacts-21

To close the ATX PSU hole on any ATX case I got myself this in addition:

https://www.amazon.de/Nanum-AT…048329&s=computers&sr=1-2

The benefit of PicoPSU solution is zero noise because there are no active PSU vents and excellent power efficiency.

https://www.youtube.com/watch?v=FnHlqWUHLAI

The ASRock boards are very picky in regards to RAM. You should either pick the RAM that is recommended on the website that I provided or look up recommended RAM for the board on the ASRock website.

The Pico PSU solution is way more efficient compared to an oldschool ATX PSU. If it is availaible in your country then you should definately go with the Pico PSU.

I can recommend this setup (sadly in German):

https://www.elefacts.de/test-5…x_sata_im_mini_itx_format

I use the recommended PicoPSU instead of a full blown ATX PSU:

https://www.amazon.de/gp/produ…kCode=as2&tag=elefacts-21

https://www.amazon.de/gp/produ…kCode=as2&tag=elefacts-21

Just wanted to say thank you for a great piece of software. OMV is my first NAS because I was never convinced of the ready made solutions. It does everything I want it to and runs 24/7 rock stable without any issues.

Great stuff!

backslash

Is the WD Drive a WD10EACS? If yes then you won't be able to spin down the drive with hdparm reliably. A potential alternative is to use hd-idle instead of hdparm to spin down the drive.

Still I managed to spin down the drive with hdparm and these settings in the hdparm.conf but the time when the WD10EACS goes to sleep is still somewhat random:

https://forum.openmediavault.o…ot-spinning-down-anymore/

I deactivated the IntelliPark feature on both WD drives with idle3-tools beforehand. I consider to replace the WD10EACS with a WD Blue drive in the foreseeable future though.

This most likely isn't related to OMV nor Debian. Myself and probably many other users are running OMV without an attached display. Since this is the most likely usage scenario for OMV and a NAS in general, I assume that it is rather connected to your specific hardware (mainboard/BIOS).

Maybe your BIOS considers a missing display being an error. Usually there is a setting in the BIOS like "Halt on all errors" or something similar. Try deactivating that particular or similar sounding setting.

I nailed the issue down to hdparm in conjunction with my WD Green HDDs.

I managed to spin down my two HDDs (WD30EZRX and WD10EACS) reliably by altering the hdparm.conf manually:

quiet
/dev/disk/by-id/ata-Samsung_SSD_850_EVO_250GB_S3R0NF1J800330R {
    write_cache = on
}
/dev/disk/by-id/ata-WDC_WD30EZRX-00D8PB0_WD-WCC4N0ZCFKS7 {
    apm = 255
    spindown_time = 240
    write_cache = on
}
/dev/disk/by-id/ata-WDC_WD10EACS-00D6B0_WD-WCAU41299383 {
    apm = 255
    spindown_time = 240
    write_cache = on
}

Mainly apm needed to be deactivated with the value 255 because the drives do not support apm. In addition I deactivated the IntelliPark feature of the drives with idle3-tools:
https://forum.openmediavault.o…in-Down-Probleme-beheben/

The WD30EZRX spins down acording to the settings in the hdparm.conf whereas the WD10EACS ignores the specified spindown time but this is a known problem in conjunction with the WD10EACS model. Still the WD10EACS spins down after a while reliably now though it happens after some hours and not minutes as specified in the hdparm.conf.

What boggles me, is the fact that it worked reliably for both drives when I installed OMV 4.1.22 the first time, though I just enabled spindown through the web UI.

One of the updates between 4.1.22 and now seems to alter the behaviour of OMV/Debian in a way that the spindown does not work anymore. It could also be a newer version of hdparm that behaves differently now compared to before.

I did a fresh install of OMV 4 with all updates from the update manager applied but the drives are still not spinning down. It seems that one of the recent Debian/OMV updates prevents the drives from spinning down properly.

Sadly this heavily lowers the value of OMV for me.

So far my harddrives have been spinning down reliably but since recently the drives are not spinning down anymore.

I made no changes to my configuration apart from the regular updates that are showing up in the update manager. The 4.19 kernel update being one of the more recent updates.

My system consists of one SSD for OMV and two HDDs for storage (no RAID).

Any hints?

I used this guide (sadly in german) and it works like charm: https://www.technikaffe.de/anl…rung_der_systemfestplatte

I use the additional space on my OMV bootdisk for Tvheadend recordings. No issue for me if I lose some recordings in case the SSD dies for whatever reason.

Unter OMV habe ich keine Erfahrungswerte mit dem Ruhezustand, da ich OMV durchlaufen lasse und nur die Platten schlafen lege. Ich hatte aber ähnliche Probleme als ich noch LibreELEC samt Tvheadend Server auf dem Board installiert hatte und mit dem Ruhemodus experimentiert habe: https://forum.libreelec.tv/thr…pollo-lake-based-systems/