• Hallo Gast!
    Noch bis zum 10.05. kannst Du an unserer Hardwareluxx Hardware-Umfrage 2026 teilnehmen! Als Gewinn verlosen wir unter allen Teilnehmern dieses Mal ein Notebook für bis zu 1.800 EUR - über eine Teilnahme würden wir uns sehr freuen!

Datenübertragungsrate OMV auf Pi4

seppelchen

Foto-Master of 03/11
Thread Starter
Mitglied seit
17.06.2005
Beiträge
11.080
Ort
Bretten
Servus,

ich habe seit ein paar Wochen ein kleines NAS mit OMV laufen. Funktioniert auch soweit prima, allerdings weiß ich nicht, ob nicht doch mehr als die erreichten ~40MB/s möglich ist (Anzeige unter Windows).

Waren es anfänglich per WiFi nur unter 10MB/s, kam ich dann per LAN auf ~17. Danach wurde das NT gegen ein neues originales getauscht und nun sind es die max. 42MB/s.

Eine 120er SSD ist per Startech USB Adapter angeschlossen, darauf läuft OMV. Die Daten sind auf einer 500GB M.2 SATA SSD die mittels SSK Adapter angeschlossen ist. Beides sind Empfehlungen aus dem Raspberry Forum.

Geht da mehr? Wie sind eure Übertragungsraten?
 
Wenn Du diese Anzeige nicht sehen willst, registriere Dich und/oder logge Dich ein.
Wie sind die SSDs angeschlossen? USB2.0 oder USB3.0? Bei 2.0 wären knapp 40MB/s ok
 
Beide Platten sind an den USB 3.0 Buchsen angeschlossen.

Aber das wäre ein Ansatz, muss man gucken wie man das ausliest.

edit: bedeutet das 2.0 root hub auch USB 2.0? Ich tausche einfach mal die Stecker, das weiß ich es ja...

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 14b0:0206 StarTech.com Ltd. 20AB
Bus 002 Device 003: ID 0bda:9210 Realtek Semiconductor Corp. RTL9210 M.2 NVME Adapter



edit2: Nein, das bedeutet es nicht...

Bus 002 Device 002: ID 0bda:9210 Realtek Semiconductor Corp. RTL9210 M.2 NVME Adapter
Couldn't open device, some information will be missing
Negotiated speed: SuperSpeed (5Gbps)
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.20
bDeviceClass 0 [unknown]
bDeviceSubClass 0 [unknown]
bDeviceProtocol 0
bMaxPacketSize0 9
idVendor 0x0bda Realtek Semiconductor Corp.
idProduct 0x9210 RTL9210 M.2 NVME Adapter
bcdDevice f0.01
iManufacturer 1 SSK
iProduct 2 SSK Storage

Bus 002 Device 003: ID 14b0:0206 StarTech.com Ltd. 20AB
Couldn't open device, some information will be missing
Negotiated speed: SuperSpeed (5Gbps)
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.20
bDeviceClass 0 [unknown]
bDeviceSubClass 0 [unknown]
bDeviceProtocol 0
bMaxPacketSize0 9
idVendor 0x14b0 StarTech.com Ltd.
idProduct 0x0206 20AB
bcdDevice 1.00
iManufacturer 2 XLR8_PL1
iProduct 3 20AB

Dann weiß ich auch nicht weiter... Das originale NT habe ich auch mit einem 5,1V 5A getauscht (da zwei Platte dran hängen), hat aber keinen Unterschied gebracht.

/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 5000M
|__ Port 001: Dev 002, If 0, Class=Mass Storage, Driver=uas, 5000M
|__ Port 002: Dev 003, If 0, Class=Mass Storage, Driver=uas, 5000M

edit3: Kabeltausch hat auch nichts gebracht. Ein aktiver USB Hub wird bei Verwendung von mehreren Platte empfohlen. Mal gucken was es da so gibt... im Prinzip reichen mir die 40MB, 4GB in 2 Min. damit kann ich eigentlich leben, zumal ich nicht ständig Daten hin- und herschiebe.
 
Zuletzt bearbeitet:
Was sagt ne lokale Benchmark der SSDs? Datentransfer per SMB? Vermute ne vermurkste SMB config. Das Feintuning da ist Gefrickel :d

Ggfl hilft dir der Thread weiter, finde auf anhieb nichts besseres mit paar Settings zum testen:
Ist auch sehr lange her, dass ich SMB benutzt habe, daher kP mehr über die genauen Werte/Settings, aber ich war da auch ewig dran am debuggen und optimieren :d

hier mal ne Uralt config:
Code:
#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = WORKGROUP

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;   bind interfaces only = yes



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
   max log size = 1000

# We want Samba to only log to /var/log/samba/log.{smbd,nmbd}.
# Append syslog@1 if you want important messages to be sent to syslog too.
   logging = file

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller".
#
# Most people will want "standalone server" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
   server role = standalone server
   syslog = 0
   obey pam restrictions = yes
   security = user
   client max protocol = SMB3
   use sendfile = no
     getwd cache = yes
   socket options = TCP_NODELAY IPTOS_LOWDELAY #SO_RCVBUF=65536 #SO_SNDBUF=65536
;   max xmit = 2048
   large readwrite = no
;   aio read size = 16384
;   aio write size = 16384
;   read raw = yes
;   write raw = yes
;   write cache size = 512
;   aio max threads = 50
;   allocation roundup size = 4096
# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
   unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
   pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
   map to guest = bad user

########## Domains ###########

#
# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain controller'
# or 'domain logons' is set
#

# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#   logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
#   logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe. 
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe. 
; add group script = /usr/sbin/addgroup --force-badname %g

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;   include = /home/samba/etc/smb.conf.%m

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;   idmap config * :              backend = tdb
;   idmap config * :              range   = 3000-7999
;   idmap config YOURDOMAINHERE : backend = tdb
;   idmap config YOURDOMAINHERE : range   = 100000-999999
;   template shell = /bin/bash

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 means that usershare is disabled.
#   usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
   usershare allow guests = yes

#======================= Share Definitions =======================

#[homes]
#   comment = Home Directories
#   browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
#   read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
#   create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
#   directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# The following parameter makes sure that only "username" can connect
# to \\server\username
# This might need tweaking when using external authentication schemes
#   valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700

#[printers]
#   comment = All Printers
#   browseable = no
#   path = /var/spool/samba
#   printable = yes
#   guest ok = no
#   read only = yes
#   create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
#[print$]
#   comment = Printer Drivers
#   path = /var/lib/samba/printers
#   browseable = yes
#  read only = yes
#   guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin


;[hdd_8]
;   comment = hdd_8
;   path = /mnt/8tb
;   read only = no
;   writable = yes
;   guest ok = no
;   browsable = yes
;   force user = hc2
;   force group = hc2
;   create mask = 0775
;   directory mask = 0775
;   force create mode = 0775
;   force directory mode = 0775

[hdd_5]
   comment = hdd_5
   path = /mnt/5tb/hdd1
   read only = no
   writable = yes
   guest ok = no
   browsable = yes
   force user = hc2
   force group = hc2
   create mask = 0775
   directory mask = 0775
   force create mode = 0775
   force directory mode = 0775

Grad:
Code:
   use sendfile = no

   getwd cache = yes

   socket options = TCP_NODELAY IPTOS_LOWDELAY
   large readwrite = no
waren hilfreich bei mir.
 
Zuletzt bearbeitet:
Hardwareluxx setzt keine externen Werbe- und Tracking-Cookies ein. Auf unserer Webseite finden Sie nur noch Cookies nach berechtigtem Interesse (Art. 6 Abs. 1 Satz 1 lit. f DSGVO) oder eigene funktionelle Cookies. Durch die Nutzung unserer Webseite erklären Sie sich damit einverstanden, dass wir diese Cookies setzen. Mehr Informationen und Möglichkeiten zur Einstellung unserer Cookies finden Sie in unserer Datenschutzerklärung.


Zurück
Oben Unten refresh