bump... anyone? After a bit of fiddling and downgrading SMB version I get about 1/4-1/3 of 1 GBit speed I am used to get with an old Macbook (2011).
same problem here... has anybody got a fix or do I need to switch to another server? Getting as well only 0,3MB/s transfer speeds e.g. when I try to extract a ZIP on OMV over SMB it takes MINUTES! Tried to add the options in "Extra Options" ...nothing changed... Is there anyway to have a SMB3 working together with macOS Catalina?
Quote from "mitchtay"
Assuming you have a standard install you should check the transfer log located at: /var/log/xferlog
It should contain the information that you are looking for.
when I do that I get:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_CTYPE = "de_DE.UTF-8",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
Error opening usage log file: /var/log/proftpd/xferlog
it worked somehow after all. But now the Raid5 seems to be quite slow - I often get disconnects over AFP and SMB andiTunes DAAP. OMV says the RAID is clean. How could I approach this? The newly added HDD is on another SATA lane - could that be the reason?
Everything was clean when I started. I added /dev/sdf now and it's recovering ... hopefully that won't take too long. Guess next time I don't use the GUI for growing.Code
Does this look right now? Space device...?
I tried to grow my RAID5 with the built-in grow function. It took around 16-17 hours and now the RAID is just clean, degraded. (http://d.pr/i/qbFr) ... it states now the 7,28TB (instead of 5,4TB before). But ...Code
Last time I did this there was in the last row a "faulty spare". So /dev/sdb is the added HDD for the RAID5: http://d.pr/i/5STZ
I already clicked (unfortunately a few times since I thought ...nothing would happen) in the resize button here http://d.pr/i/j9Ur then I noticed this message in /var/log/messages:
Is everything fine? I see the Filesystem is now becoming larger... that is a good sign, isn't it?? I am a bit afraid something went wrong. What would be my next step (besides waiting for the resize to be done)?
Will the 5th drive be added on its own (which is now 'removed' - but that drive was never removed - that is what makes me concerned... I can access the RAID over afp though... so everything is still there.
Hope someone knows how to handle this!
output from fdisk -lCode
Output from /proc/mdstat
Output from mount:Code