Posts by backslash

I installed OMV on the eMMC because I don't intend to use UGOS anyway. On the eMMC I just installed OMV. Docker data files with more dynamic file changes are being stored on a dedicated SSD. So I think the lifespan of the eMMC shouldn't be an issue.

Best Usenet provider is Eweka from my experience. This is a good offer: https://www.eweka.nl/de/landing/special-deal-evm-1

Instead of NZBGet I recommend SABnzbd in a docker container: https://hub.docker.com/r/linuxserver/sabnzbd

Depends really on the usage of that particular drive. I spin down drives which I only occasionally use during the week for e.g. streaming a movie in the evening or doing a backup once in a while. I don't see a point in having drives with such usage scenarios spin 24/7 and waste rather expensive energy here in Germany. Other things like OMV itself and docker services I serve from energy efficient SSDs anyway where spin down doesn't apply/matter.

Of course you should make sure that your spinned down drive(s) don't spin up constantly during the day/night due tue misconfiguration and/or some kind of service which of course would be counter productive. Hd-idle is the only service which spins down HDDs reliably for me.

Just wondering if it would be possible to prevent the spin up of HDDs each time OMV updates/changes are being applied?

In my case OMV is installed on an eMMC but still the HDDs spin up every time from standby when updates/changes are being applied.

The installation is actually straightforward and I had no need for any workarounds: The Ugreen NASyncs are great for Openmediavault

By incident I got a very cheap used Ugreen DXP2800 without an actual need for a new NAS since my custom build NAS based on a J5040 CPU works just fine. But it was an offer I couldn't resist.

The installation of OMV couldn't be more straightforward:

1. I updated the preinstalled UGOS to the most recent version and did a factory reset (optional step)

2. Did a backup of the internal eMMC (32GB) using Clonezilla just in case I want to restore the UGOS partition at some point in the future (optional step)

3. Booted into BIOS (Ctrl + F2) and disabled the Watchdog

4. Installed OMV onto the eMMC (OMV can of course be installed to any other device and the boot order can also be changed in the BIOS)

5. Booted OMV

Everything works perfect except for the HDD/LAN activity LEDs which can be fixed: https://github.com/miskcoo/ugreen_leds_controller It would be great to get the LED controller as a plugin at some point for OMV. Personally I don't care about the LEDs because I never look at my NAS once it is set up and running. The power LED works just fine out of the box.

The Ugreen will of course replace my custom build NAS because it does everything I need in a very slick and silent overall package.

Hey,

this is how I configured the FTP service. Sorry for German screens but you should get the idea.

OMV:

Router:

If you don't have a permanent external IP you will need a dynamic DNS service or use cloudflare etc.

Amiga forever!

I pulled the trigger today and upgraded from OMV 6 to 7. Everything went smoothly after following the instructions on page 1 of this thread. Amazing job guys and big thank you to everyone involved.

I had this issue recently trying to access OMV using Chrome on macOS after I upgraded to Sequoia. If this matches your setup then you need to allow local network access for Chrome in the macOS security settings. Until recently this setting got disabled once you rebooted the Mac. This is a known bug and I think it got resolved with macOS 15.1.1

Forget hdparm and just use hd-idle. Only hd-idle spins down harddrives reliably.

Thread

Auto-Spindown of hdd's does not work on OMV6

Hi there,
just a short (bug?) report

autospindown on my hdd's does not work on my system
parameters are set correct
hdparm.conf looks fine
(Hidden Content)

using hdparm -y /dev/sdx works fine, just the auto-spinoff does not.

i had to install hd-idle to send the hdd's to sleep
my /etc/default/hd-idle (time is unlike to hdparm in seconds here)
(Hidden Content)

wsxws

Nov 3rd 2021

Sowas ist natürlich immer schwierig aus der Ferne zu lösen weil es an allem möglichen liegen kann. Daher vermutlich die geringe Resonanz. Mit meinen Problemen wurde mir immer zügig geholfen.

Create a Gmail App Password and use that to authenticate in OMV with the settings below:

Ich bin auf Ventura unterwegs mit der aktuellsten Version von OMV und das Vererben von Berechtigungen ist bei mir deaktiviert und es funktioniert alles wie soll.

You will need a usenet provider like Eweka (the best one imo) and a downloader like SABnzbd that can deal with NZB files to download stuff (binaries) from the usenet. Some users prefer to use VPN in addition but I don't.

Quote from dav3yb

This is pretty similar to what I'm working on currently... I've got the same ASRock J5040 board, and was hoping to build a bit of a custom case with a 4-bay drive cage I salvaged from a server at work.

My main question to anyone using this board is: are you just using the onboard network? I had some issues where the NIC wasn't detected at all after installing to a USB drive, which was my original plan. After a bit of googling, it seems the Realtek controller it uses wasn't very well supported overall. That lead me to looking at a better NIC (and a 2.5g one at that) to go into the PCIe 1x slot. (any NIC recommendations btw?)

I did discover that the M.2 Wifi slot is running off of one of the PCIe lanes, and put a 2-port SATA controller in mine, which I was going to use to add a proper boot SSD.

Mainly curious about the NIC situation and this board, and if I need to do something specific to get it working better, or if just picking up a PCIe card is the better bet anyways.

Display More

I am using the onboard NIC and never had an issue with it. Neither while installing OMV nor while actually running it.

Quote from FrederikSchack

Ok, thanks, now I can't find that particular powersupply, but it seems like there could be quite some power to save.

The Mean Well GST90A12 is supposed to be a good (reliable and efficient) alternative to the Salcar one. Maybe you can find that one in your region.

Quote from chente

Be carefull with that. At the time of server booting, the disk drives consume high peaks of energy and the system is also stressed. If you choose 4 large capacity disks with consumption close to 8 or 10W, you would get dangerously close to the limit of the power supply.

It's not an issue with four HDDs. The bios makes sure that not all drives are being powered up at the same time when powering up the system. I am using this setup for many years now. But I agree, with more than four 3,5" HDDs one should utilize a traditional 300W ATX PSU at least.

Quote from FrederikSchack

Did you have the possibility to test the power consumption?

I didn't but these guys did: https://www.elefacts.de/test-1…a_und_passiver_4_kern_cpu It's in German but you can easily translate the page within Google Chrome.

I am using the same board with a 90W PicoPSU and an external 72W power supply from Salcar and I can power four 3,5" HDDs without any issues.

A good alternative to free up a SATA port is to use a M.2 SSD USB adapter (UGREEN) or a PCIe adapter (MZHOU M.2 SSD adapter) if you have no use for the one PCIe slot.