Hello, posting to provide some feedback: it was the damn swap partition.
OMV on my system is installed on a thumb drive, mainly for ease of backup and not to steal a SATA port.
Swap by default is enabled and located on the thumb drive, causing awful system performance!
As soon as I switched it off and moved to a swapfile on the SSD, the system never experiences high I/O wait and SMB is back to FULL proper speed.
So yes, next time check the SWAP!
Hi there,
Back in the OMV5 days I recall that the flasmemory plugin advised to disable swap and that's what I did back then.
OMV6 flasmemory plugin does not give any advice, but I realized I have a swap partition that is running off my USB stick, and I believe this is the cause of the slowdowns I'm facing.
How do I permanently disable the swap partition?
I already edited /etc/fstab to comment out the swap partition and executed swapoff /dev/sdXY with the correct partition. On the fly the swap partition is emptied and disabled, but after a reboot the swap is enabled again.
There must be a salt config or some other default that is turning it on again, can you assist?
I'm surprised that nobody has reported this before, but what's the point of using the flashmemory plugin if the swap partition is kept on by default on the same usb flash drive we're trying to preserve?
I could re-enable swap by using swapfile on my NVMe drive used for apps and docker, but let's do one step at the time.
Hi,
I am experiencing slow transfer speeds over SMB when handling small files, so I began troubleshooting.
I excluded SMB, and started benchmarking locally on the server.
For this test, I am transferring a folder of 2.2GB, containing 148 files, photos and videos from my smartphone. These are not "so small" files, but vary from 2MB (photos) to 100MB (videos).
I used rsync to show the current and total progress.
I am using a NVMe drive to rule out any HDD weirdness and get the best scenario.
Take a look at these runs. All the same, just deleted the copied folder and run them again.
Only the 4° run took 2 seconds at the expected speed.
During the slow copies, the speed would slow down after about 30%, and iowait skyrocket to 95% (measured via glances) with no load on the server.
Taken during the second copy
The same behaviour can be replicated on HDDs with MergerFS.
As you can see by top, there's no load on the server.
Looks like that writing is the only issue. If I copy the folder from the server to my client using SMB, I top up gigabit speed.
The hardware specs are in my signature below.
What should I do?
If you switch to Snapraid + MergerFS you can spindown your drives anytime you want and increase energy savings when drives are not in use.
Snapraid is perfect for home and media usage.
Buona sera,
oggi ho aperto la pagina dell'interfaccia utente e non mi compaiono più le scelte dei menu a sinistra.
Mi compare solo dashboard.
Cosa può essere successo? Il server però funziona.
Devi fare l'accesso con l'utente admin
[…]
Ciao, non si capisce molto dalla tua risposta, ma credo sia tutto ok.
Salve a tutti.Ho un disco,che mi passa da /dev/sda a /dev/sdd da solo,e quindi dopo non riesco più a vederlo in rete.E' un HD nuovo,un Barracuda da 2.5" da un Tera.Può essere quello?prima con il vecchio non ho mai avuto problemi
Grazie
Ciao, il cambio del nome è normale, succede anche a me. Questo non inficia il comportamento di OMV e delle share di rete, che infatti usa un altro identificativo.
Vedi altri errori? Il problema è un altro.
For reference, here's what my system shows (IPv6 enabled and working)
root@nas:~# ls -al /srv/salt/omv/deploy/hosts/
total 20
drwxr-xr-x 2 root root 4096 May 21 11:47 .
drwxr-xr-x 48 root root 4096 May 21 11:47 ..
-rw-r--r-- 1 root root 3231 Apr 25 19:03 10default.sls
-rw-r--r-- 1 root root 1085 Feb 24 12:54 default.sls
-rw-r--r-- 1 root root 909 Feb 24 12:54 init.sls
root@nas:~# cat /srv/salt/omv/deploy/hosts/20domains.sls
cat: /srv/salt/omv/deploy/hosts/20domains.sls: No such file or directory
root@nas:~#With openmediavault 6.4.0 i hope that many networking issues will be fixed because some things were misconfigured in older versions.
These improvements are always appreciated, thanks!
possible incompatibilities with Linux?
I'm sure it's not this.
I've built this NAS in 2020 (hardware in the signature) with OMV5 and never had that issue.
The issue started to appear only on OMV6 (clean install) but does not happen all the time. I'll check the bios, but WOL and RTC are working by themselves.
Hi,
My OMV installation (6.3.12-1, clean install 6.x) is having an issue that is very annoying.
Sometimes, after the NAS has been in standby (suspend) and is woken up (either by RTC or WOL), network connectivity is down.
OMV/Debian is working, lights are blinking on the LAN port. Reconnecting the LAN port does not help. To solve this, I shutdown and restart the NAS. However, if I'm away, I can't do so.
Below is the syslog when OMV is woken up. There are clearly errors reporting there's no network.
OMV side there are no specific network configs, everything is DHCP, and the IP is reserved on the router.
I have not changed anything in the OS that can interfhere with OMV configs.
Funziona tutto alla grande, ieri sera alla 10:00 l'HPE è andato in sospensione e stamattina alle 8:00 era operativo.
Fantastico!!
Quindi mi consigli di togliere lo S.M.A.R.T da SSD e USB ?
Con la USB non funziona. Puoi tenerlo attivo su SSD, ma potresti ricevere avvisi per valori che non sono problematici.
With USB it does not work. You can keep it active on SSDs, but you may receive warnings for values that are not problematic.
Ho un Ssd Pcie ( Per i docker ) e il Sistema Operativo è su chiavetta USB , c'è qualche accortezza che dovrei considerare / problemi legati al controllo SMART ?
Ho lo stesso setup. Ho attivato lo SMART sui dischi meccanici, ignorando SSD e USB.
Puoi usare il plugin openmediavault-wakealarm per programmare i job dalla GUI.
///
I have the same setup. I activated SMART on mechanical disks, ignoring SSD and USB.
You can use the openmediavault-wakealarm plugin to schedule jobs from the GUI.
You can use the wakealarm plugin to easily schedule RTC wake!
In your scenario, poweroff is fine. I recommend to use standby if you'll need the NAS quickly available.dds
In my case, I shut down the NAS overnight too, but I use standby during the day when I don't need the NAS. But when I do, i use WOL to wake up the NAS which becomes available in 2 seconds.
Nessun problema per i dischi. Aggancerai (monterai) le partizioni esistenti dopo la nuova installazione nella interfaccia di OMV alla sezione partizioni
Io ragiono al contrario:
- Tutti i dispositivi sono impostati su "DHCP" (indirizzo automatico)
- Sul router/modem, imposto gli IP che voglio riservare a quel dispositivo.
Io lo trovo più comodo, perché così li ho tutti in un solo posto.
I could, but at this point I would like to be a "big boy" and actually learn how Docker and my containers work instead of just limping along in someone else's wake. Still, these compose files will act as an effective guide as to what I should end up with. Thank you!
If you do - and it's definitely worth it - there are tons of guides, here on this forum and on YouTube.
Docker is widely popular, and you just need to find the way that suits you.
You'll get used to Yaml's compose files, they are divided in sections and there's always a template made by somebody else, most of the time you'll just need to adjust ports and file paths.
And you can always ask for more help!
Non ho idea di che giri tu stia facendo. Mai usato quella query
Oramai sono abituato con quella configurazione,non saprei quale altro protocollo usare
Ti basta non mettere quella config nel server samba, e di default usa protocolli più aggiornati.
Avevo provato una pennina usb3,ed ora che non ce la metto,qualsiasi modifica con gli hd mi da errore con schermata rossa.E non so come togliere la penna
Collega di nuovo la pendrive, quindi vai nella sezione partizioni e fai "Unmount, quindi salva la configurazione. Ora potrai scollegarla e non avere più l'errore.
Su OMV non puoi rimuovere dischi senza prima scollegarli da UI: il sistema si aspetta sempre i dischi che ha in configurazione.
Trovato l'inghippo
server min protocol=NT1 nella config del samba
Grazie
Samba 1, come avevo detto, non è supportato. I tuoi client sono molto vecchi?
È un protocollo vecchio, insicuro e inefficiente. Evita se puoi
Salve.Ho installato OMV 6 su Debian 11,ma non capisco come mai non mi funzioni il protocollo samba.Se provo il server FTP la periferica collegata,è raggiungibile.Ho su un vecchio Orange con Armbian la versione 5,26 di OMV e funziona tutto.Sbaglio qualcosa?
Grazie
Ciao, se fornisci ulteriori dettagli ti possiamo dare una mano.
Considera anche che SMB1 è disabilitato.
