A lot of external Disks (via USB) use controllers (USB2SATA Bridges) which hide features of the disk and may use own (firmware depended) timeouts. its logic.. you use an usblink.. not sata... only the backend between controller and disk is sata.
emulating something is never the same as the original.
Beiträge von Rd65
-
-
Befor you set params with hdparm on omv, try them in the shell.
Many Disks do not support acousticmanagement and apm as example.
Most Disks run unconfigured at its best. Don't disable caches...
look at smart errors... there are lot of possible error sources by managing disks.. -
the dhcp data seem to be ok.
but the warning/error on dhcp -v point to a missconfig of the resolver daemon.
in old times /etc/resolv.conf was a file containing a nameserverip. easy and well done.
in modern times /etc/resolv.conf is a link to a file which is handeled/manages bei the resolv deamon.
if this link is broken, the system complains about... and resolving may gone wrong.
the idea was to manage the resolv.conf depending on events like upcomming and ending dialup modem connections, offlinemode and so on... but on 24/7 systems like a nas this is crap.
in the case the host file and /or hostname is even wrong too... the System can't find its own name. Sometimes this will break nginx. maybe nss-myhostname help.. but the reason for this is a bunch of missconfigured configs.so the way is:
set a hostname and the domain in omv... or at the system (/etc/hostname)
check your /etc/hosts fileCode# cat /etc/hosts # This file is auto-generated by openmediavault (https://www.openmediavault.org) # WARNING: Do not edit this file, your changes will get lost. 127.0.0.1 localhost 127.0.1.1 nas.local nas
check if # hostname --fqdn
shows a well formated hostname like this -> nas.local
(2 names with a dot)
now do a #dpkg-reconfigure resolvconf
this will restore the resolv.conf-symlink
mybe you need to delete the /etc/resolv.conf at first.
check your /etc/network/interfacesCode# The loopback network interface auto lo eth0 iface lo inet loopback # The primary network interface iface eth0 inet dhcp
shoud look like this - but replace all eth0 with your network adapter name.
enpXsY or whatever - depends on your hardware, udev and lot's of script crap. list with #cat /proc/net/devdo a #omv-initsystem
omv will re-read configs
#rebootnow dhcp will setup via the daemon resolvconf a working and linked resolv.conf
read about
https://wiki.debian.org/NetworkConfiguration
and
take a look at this:
https://askubuntu.com/question…resolv-conf-must-be-a-sym -
please do a
$ sudo dhclient -v
and tell me:
$ cat /var/lib/dhcp/dhclient.leases
these are the infos from your router about your client. if you dont want post this, doubleselfcheck the values.
-
on a working and well managed machine i would say:
please post the result of
#nmap --script broadcast-dhcp-discoverbut i am afraid this will go wrong now.
maybe you can try
#dhcpdump -i yourinterfacename
or
#dhclient -v -
as i told... do the steps and it will work.
maybe you mixup dhcp wiht dns?
you get your adress by dhcp from the router and if your router is your dns forwarder, he knows a hostname combined wit this adress (and mac). then it dosn't matter if you get static ip (as a static lease) or a well known hostname managed by your router.
no reason for static adresses, no reason to play on nameserver entrys. the router do it for you.
no there is no need to reinstall.. use a backup -
reset your network with omav-firstaid 1. to dhcp on ipv4 and after reboot reset 2. your webcontrolinterface and 3. use your router as dns provider. there is no need to change network config on providerchange, this is managed by the router.
Its not a good idea to use a external dns server without knowlege because in this way clients ask 1000 things about the internal home-net to external DNS Servers .. without any sense. -
OMV4 is based on Stretch. OMV5 is based on Debian. If you install OMV on top of Debian you will end up with the same system as if you were using the image. Maybe some different packages will be installed.OMV5 on Buster... its all debian.
but you can even install OMV4 on Buster(backports) with netinstalls... if you dont want to be a betatester for OMV5. -
first of all.. changing network configs while login via ssh, http or rdp most times go wrong! You pull the carpet while you stand on.
if you use a headless PI, this makes it complex, on a Nas with desktop access its easy to change network things.
on a Nas with Desktop call http://127.0.0.1 to do configs in omv.
But you can change ipv6 while using ipv4 and vice versa. but this is complex too.
the easyest way is not touching default dhcp behavior after installation and do not enter/change anything about networks in omv.
the most systems are in well working dhcp mode after installation. There is no need to play on this configs.
don't touch netconfigs via net. -
original debian images lie on original debian servers, not on sourceforge....
https://www.debian.org/CD/netinst/
Dont know what the diference to sourceforge images is ... im trust only in debian images, not even in ubuntu.
download a iso or img what ever you need fitting your hardware requirement, boot it an install as described in link i've posted. -
Does that make sense? Jessie is end of life since more than one year.
it think it make sens because it fix issues and give time to migrate - if you want migrate.
The issue is a wakeup call... but if you don't want migrate, you can stay on jessie and live with old software. its a decission of the root, not of paket maintainers far away to migrate.
But I would also recommend the update. -
it may be a better solution to (re)write a plugin to manage the "networkmanager" config tool which is linux standard.
it manages all kinds of netlinks including wifi and wifi-ap, bridging, lan, vpn, wan, ipv6... and its easy to configure.
you can use networkmanager now by disable the interface in omv but you will not see any statitics about your net-device. (depends on monit-config i think.)Networkmanager configures all Links not setup in /etc/network/interfaces so you need to remove all entrys excluding lo ... (thats the reason to disable netconfig in omv too) ...
# cat /etc/NetworkManager/system-connections/Ethernet
[connection]
id=Ethernet
uuid=5b308d2b-xxxx-xxxx-xxxx-072fa216df27
type=ethernet
autoconnect-priority=-999
permissions=
timestamp=1573283596[ethernet]
duplex=full
mac-address=XX:XX:XX:68:FF:A7
mac-address-blacklist=
speed=1000[ipv4]
address1=192.168.xx.xx/24,192.168.xx.1
dns=192.168.xx.1;
dns-search=fritz.box;
may-fail=false
method=manual[ipv6]
addr-gen-mode=stable-privacy
dns-search=fritz.box;
ip6-privacy=2
may-fail=false
method=auto# cat /etc/network/interfaces
# The loopback network interface
auto lo
iface lo inet loopback
# Include additional interface stanzas.
source-directory interfaces.d -
update to omv4 is ONE solution...
you need to change your repository... thats all.
https://unix.stackexchange.com…ssie-backports-repository
they removed old versions fom the mirrorservers, use archive.debian.org instead.
deb [check-valid-until=no] http://archive.debian.org/debian jessie-backports main -
Bei mir läuft eine Gigablue quadplus auf OpenATV (es geht aber auch jede andere Distribution) incl. Platte mit nfs und samba Fileserver Diensten, in omv nutze ich das omv remote-mount plugin um mir das Share vom Receiver erst im Nas einzubinden, um es dann wieder über omv als Smaba Share anzubieten. So habe ich auch das Share von der Fritzbox eingebunden und beide Shares im Nas und damit alles unter einer ip/Account in omv zur Verfügung, evtl stelle ich das aber noch auf schnelleres nfs um. Bei der Fritzbox muss man ein wenig tricksen da sie nur cifs/smb1 kann, auf dem Receiver läuft aber ein normaler Samba server, via nfs/ftp/scp geht das bei der Box aber auch. Möglich wäre zudem auch ein Diskless Receiver, der sich ein Share (den Filme-Ordner des Nas oder der Fritzbox) einbindet und darauf aufzeichnet. Da ich aber nicht will, das alles an Mediendiensten aus ist wenn das NAS in den Standby geht, nutze ich den Weg mit lokaler Platte im Receiver und Remote-share auf dem Nas respektive eigenen Shares auf Receiver und Fritzbox. Ich hatte mal überlegt, omv auf den Receiver aufzusetzen aber die Entwicklerphilosopie von omv und openATV vertragen sich leider nicht sonderlich gut. Ist aber auch nicht tragisch, so macht jede Kiste ihren Job, kann aber alles vom Nas aus erreichen und alles ist gut. DLNA als Service läuft hier auf alle 3 Maschinen.
Was ich leider noch nicht hinbekommen habe ist dem Plex Server (nicht durch omv kontrolliert, also ohne das plexplugin/docker) auf dem Nas bei zu bringen, das er den Receiver mit OpenATV/Sat als Quelle für LiveTV/DVR nutzen soll... irgendwie fehlt auf dem OpenATV da wiederum ein Plugin... aber das fummel ich mir noch zurecht. Für die Fritzbox am Kabelanschluss gibts auch Receiverfunktionen über den dvb-c Repeater...aber dazu fehlt mir jedoch der Kabelanschluss um das mit Plex zu testen. Vielleicht kriegt mein Nas statt dessen noch eine SatReceiver-Karte verpasst und die Gigablue fliegt raus. Mal sehen...
-
use debian netinstall (stretch with backport or buster) in all subscriptions (main non-free contrib), then add omv repo to sources list, install and update omv. ready, steady, go. its documeted here https://openmediavault.readthe…stallation/on_debian.html
-
Hu?
why you insert things in /etc/apt/sources.list?
i never told that.
strange...
and why sid? buster is stable and strech oldstable....
verry strange...
do you use sid as your nas-os?
one more time... STRANGE!
thats the way not to do... -
ok, so in my opinion, the raid is not part of the problem.
But you can test more things.
install #apt install iperf3
on your server and on a client depend on os.
https://iperf.fr/iperf-download.php#windows
but you can use android, mac or windows too.
its a command line executable without gui.
start in a shell #iperf3 -s
this will be your server.
now connect with
a shell, cmd, cli or what ever you use as terminal on your client:
#iperf3 -c server-ip
and you will see statistics.
try #iperf3 -? or -h, you can change blocksizes and more things.
You can connect local (to your own ip) or you connect via ethernet, wlan or whatever.
connecting to your own ip (in a second shell) may test the local networkstack, connecting to a server behind a switch tests the switch and the network hardware on both sides.
you may change the role of client and server... (and open the Win firewall or disable for iperf3 at first)
now you are able to test your network, including network adapters without trouble from other devices.
if you identify slow connetions, or broken hardware, you may change networkhardware or doublecheck the configs.
If it is all fine, the the problem is not the network.
iperf3 is your friend to testing throuput and reliability of networks!
use itCode
Alles anzeigen$ sudo iperf3 -c nas Connecting to host nas, port 5201 [ 5] local 192.168.xx.xx port 32842 connected to 192.168.xx.xx port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 5.23 MBytes 43.9 Mbits/sec 0 123 KBytes [ 5] 1.00-2.00 sec 5.03 MBytes 42.2 Mbits/sec 0 208 KBytes [ 5] 2.00-3.00 sec 4.85 MBytes 40.7 Mbits/sec 0 222 KBytes [ 5] 3.00-4.00 sec 4.54 MBytes 38.1 Mbits/sec 0 222 KBytes [ 5] 4.00-5.00 sec 4.41 MBytes 37.0 Mbits/sec 0 222 KBytes [ 5] 5.00-6.00 sec 4.91 MBytes 41.2 Mbits/sec 26 103 KBytes [ 5] 6.00-7.00 sec 4.60 MBytes 38.6 Mbits/sec 0 123 KBytes [ 5] 7.00-8.00 sec 4.60 MBytes 38.6 Mbits/sec 0 123 KBytes [ 5] 8.00-9.00 sec 4.97 MBytes 41.7 Mbits/sec 0 123 KBytes [ 5] 9.00-10.00 sec 4.47 MBytes 37.5 Mbits/sec 0 123 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 47.6 MBytes 39.9 Mbits/sec 26 sender [ 5] 0.00-10.00 sec 46.7 MBytes 39.2 Mbits/sec receiver iperf Done. ----------------------------------------------------------- Server listening on 5201 ----------------------------------------------------------- Accepted connection from 192.168.xx.xx, port 32840 [ 5] local 192.168.xx.xx port 5201 connected to 192.168.xx.xx port 32842 [ ID] Interval Transfer Bandwidth [ 5] 0.00-1.00 sec 4.57 MBytes 38.3 Mbits/sec [ 5] 1.00-2.00 sec 4.62 MBytes 38.7 Mbits/sec [ 5] 2.00-3.00 sec 4.59 MBytes 38.5 Mbits/sec [ 5] 3.00-4.00 sec 4.66 MBytes 39.1 Mbits/sec [ 5] 4.00-5.00 sec 4.53 MBytes 38.0 Mbits/sec [ 5] 5.00-6.00 sec 4.57 MBytes 38.4 Mbits/sec [ 5] 6.00-7.00 sec 4.73 MBytes 39.7 Mbits/sec [ 5] 7.00-8.00 sec 4.78 MBytes 40.1 Mbits/sec [ 5] 8.00-9.00 sec 4.80 MBytes 40.2 Mbits/sec [ 5] 9.00-10.00 sec 4.66 MBytes 39.0 Mbits/sec [ 5] 10.00-10.05 sec 233 KBytes 37.5 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth [ 5] 0.00-10.05 sec 0.00 Bytes 0.00 bits/sec sender [ 5] 0.00-10.05 sec 46.7 MBytes 39.0 Mbits/sec receiver
the upper part shows statistics from client side, the lower part are server statistics.
Lots of Retrys show problems... slow or variant speeds show problems.. and so on.
This is my wlan link.$ iperf3 -t 60 -P 100 -c nas
this wil test 100 parallel connections for 60 Sec on a 1 GB Line.
and it say:[SUM] 0.00-60.00 sec 6.54 GBytes 937 Mbits/sec 0 sender
[SUM] 0.00-60.00 sec 6.52 GBytes 934 Mbits/sec receiver
+ 1 mp3 music stream from plexTake and a look on your cpu stats..
top - 22:16:34 up 2 days, 21:09, 2 users, load average: 0.67, 0.40, 0.28the load should not go through the ceiling
an older but common way to do these testings is using the echo service on inetd:
take a look at https://en.wikipedia.org/wiki/Echo_Protocol
all *nixes support that, but need to install some software too. but iperf3 is the easy way to do that. -
use zless.
#zless /var/log/file.gz
or logwatch as i told...
-
# ls -la /usr/share/mkconf/iptables.d
ls: cannot access '/usr/share/mkconf/iptables.d': No such file or directorywhatever you mean... this path is wrong.
-
SATA - /dev/sdX
SSD - /dev/sdX
SCSCi - /dev/sdX
IDE - /dev/hdXeven a usb3 mounted 8tb disk will be shown as /dev/sdX
Code
Alles anzeigen[152771.859735] usb 9-2: new SuperSpeed USB device number 2 using xhci_hcd [152771.884154] usb 9-2: New USB device found, idVendor=0bc2, idProduct=3322 [152771.884157] usb 9-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [152771.884158] usb 9-2: Product: Expansion Desk [152771.884160] usb 9-2: Manufacturer: Seagate [152771.884160] usb 9-2: SerialNumber: --------- [152771.891955] scsi host17: uas [152771.892438] scsi 17:0:0:0: Direct-Access Seagate Expansion Desk 9401 PQ: 0 ANSI: 6 [152771.893055] sd 17:0:0:0: Attached scsi generic sg13 type 0 [152771.893126] sd 17:0:0:0: [sdl] Spinning up disk... [152772.927225] . [152773.951243] . [152774.975170] . [152775.999170] . [152777.023153] . [152778.051132] . [152779.071086] . [152780.095041] . [152781.119040] . [152782.143005] . [152783.166969] . [152784.190920] . [152785.214891] . [152785.214970] ready [152785.215290] sd 17:0:0:0: [sdl] 15628053167 512-byte logical blocks: (8.00 TB/7.28 TiB) [152785.268122] sd 17:0:0:0: [sdl] Write Protect is off [152785.268126] sd 17:0:0:0: [sdl] Mode Sense: 4f 00 00 00 [152785.268279] sd 17:0:0:0: [sdl] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [152785.269078] sd 17:0:0:0: [sdl] Optimal transfer size 33553920 bytes [152785.405887] sdl: sdl1 sdl2 [152785.406911] sd 17:0:0:0: [sdl] Attached SCSI disk