GG73 Posted June 6, 2021 Share Posted June 6, 2021 Hi all, been attempting to transfer my movie files to my new Unraid set up. initially I set it up with 2 new 6tb wd red pro drives, 1 for parity, 1 for files plus a 240gb ssd for cache. on further reading in the forums, I unmounted parity disc and cache whilst I attempt to transfer the files over. The problem is, its still soooo slow. 1.1tb and its saying 3 days! surely I'm doing something is wrong? I have a 2tb old seagate central drive with my original files I want to transfer over to Unraid. this 2tb drive is connected to my router via ethernet. My unraid set up is also connected to my router via ethernet. Im using a MacBook Pro. Any advice would be greatly appreciated, thank you! Quote Link to comment
GG73 Posted June 6, 2021 Author Share Posted June 6, 2021 tower-diagnostics-20210606-1416 Quote Link to comment
trurl Posted June 6, 2021 Share Posted June 6, 2021 Why isn't your attachment a zip file? Tools - Diagnostics downloads a single ZIP file. You shouldn't modify it in any way. Quote Link to comment
GG73 Posted June 6, 2021 Author Share Posted June 6, 2021 (edited) my apologies.i dont beleive I changed anything other than drag it across?tower-diagnostics-20210606-1558 Edited June 6, 2021 by GG73 Quote Link to comment
trurl Posted June 6, 2021 Share Posted June 6, 2021 It should have a .zip file extension. Something about your system has changed the filename. Quote Link to comment
GG73 Posted June 6, 2021 Author Share Posted June 6, 2021 hi, I dont know then, I'm on a Macbook pro it doesnt say its a zip file at any point? Quote Link to comment
trurl Posted June 6, 2021 Share Posted June 6, 2021 Not sure what that "copying" screenshot is supposed to be telling me. Diagnostics is a single file. There shouldn't be any copying of lots of files. It is a single .zip file. If it appears to you as multiple files then your browser has automatically opened the single .zip file. You need to find the .zip file itself, which should be wherever your browser stores downloads. Quote Link to comment
GG73 Posted June 6, 2021 Author Share Posted June 6, 2021 Again, please bear with me. I have attempted it again on a windows PC and it doesn't seem to have altered anything this time. Thanks for your patience tower-diagnostics-20210606-1609.zip Quote Link to comment
trurl Posted June 6, 2021 Share Posted June 6, 2021 Looks like a networking problem. Check cables and ports, both ends, on switches / routers. Jun 6 14:54:20 Tower kernel: tg3 0000:02:00.0 eth0: Link is down Jun 6 14:54:20 Tower kernel: bond0: (slave eth0): link status definitely down, disabling slave Jun 6 14:54:20 Tower kernel: device eth0 left promiscuous mode Jun 6 14:54:20 Tower kernel: bond0: now running without any active interface! Jun 6 14:54:20 Tower kernel: br0: port 1(bond0) entered disabled state Jun 6 14:54:21 Tower dhcpcd[1512]: br0: carrier lost Jun 6 14:54:21 Tower avahi-daemon[1841]: Withdrawing address record for 192.168.1.63 on br0. Jun 6 14:54:21 Tower avahi-daemon[1841]: Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.1.63. Jun 6 14:54:21 Tower avahi-daemon[1841]: Interface br0.IPv4 no longer relevant for mDNS. Jun 6 14:54:21 Tower dhcpcd[1512]: br0: deleting route to 192.168.1.0/24 Jun 6 14:54:21 Tower dhcpcd[1512]: br0: deleting default route via 192.168.1.1 Jun 6 14:54:23 Tower kernel: tg3 0000:02:00.0 eth0: Link is up at 1000 Mbps, full duplex Jun 6 14:54:23 Tower kernel: tg3 0000:02:00.0 eth0: Flow control is on for TX and on for RX Jun 6 14:54:23 Tower kernel: bond0: (slave eth0): link status definitely up, 1000 Mbps full duplex Jun 6 14:54:23 Tower kernel: bond0: (slave eth0): making interface the new active one Jun 6 14:54:23 Tower kernel: device eth0 entered promiscuous mode Jun 6 14:54:23 Tower kernel: bond0: active interface up! Jun 6 14:54:23 Tower kernel: br0: port 1(bond0) entered blocking state Jun 6 14:54:23 Tower kernel: br0: port 1(bond0) entered forwarding state Jun 6 14:54:23 Tower dhcpcd[1512]: br0: carrier acquired Jun 6 14:54:23 Tower dhcpcd[1512]: br0: rebinding lease of 192.168.1.63 Jun 6 14:54:25 Tower ntpd[1586]: Deleting interface #22 br0, 192.168.1.63#123, interface stats: received=2197, sent=2201, dropped=0, active_time=170731 secs Jun 6 14:54:25 Tower ntpd[1586]: 216.239.35.0 local addr 192.168.1.63 -> <null> Jun 6 14:54:25 Tower ntpd[1586]: 216.239.35.4 local addr 192.168.1.63 -> <null> Jun 6 14:54:25 Tower ntpd[1586]: 216.239.35.8 local addr 192.168.1.63 -> <null> Jun 6 14:54:25 Tower ntpd[1586]: 216.239.35.12 local addr 192.168.1.63 -> <null> Jun 6 14:54:28 Tower dhcpcd[1512]: br0: probing for an IPv4LL address Jun 6 14:54:28 Tower dhcpcd[1512]: br0: DHCP lease expired Jun 6 14:54:28 Tower dhcpcd[1512]: br0: soliciting a DHCP lease Jun 6 14:54:33 Tower dhcpcd[1512]: br0: using IPv4LL address 169.254.21.69 Jun 6 14:54:33 Tower dhcpcd[1512]: br0: adding route to 169.254.0.0/16 Jun 6 14:54:33 Tower avahi-daemon[1841]: Joining mDNS multicast group on interface br0.IPv4 with address 169.254.21.69. Quote Link to comment
GG73 Posted June 6, 2021 Author Share Posted June 6, 2021 Thanks for the advice. I have checked cables etc, all seemed fine so I have plugged 2 new cat6 cables in using different ports on router to see if that made a difference but unfortunately still the same slow transfer speeds?. Quote Link to comment
GG73 Posted June 6, 2021 Author Share Posted June 6, 2021 tower-diagnostics-20210606-1704.zip Quote Link to comment
JorgeB Posted June 7, 2021 Share Posted June 7, 2021 Start by checking network bandwidth by running a single stream iperf test. Quote Link to comment
GG73 Posted June 7, 2021 Author Share Posted June 7, 2021 Thanks, how do I do this? Quote Link to comment
GG73 Posted June 7, 2021 Author Share Posted June 7, 2021 Thanks for the info. Will try it tonight Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.