G Speed

I have parity still, and it's being written to, as the files are being transferred.. RAM is same specs, just larger.. 4 X 512mb =2GB - Previously 2 X 2GB = 4GB - Currently

and almost done...

Hey everyone, I think something may be wrong... but I'm not exactly sure.. 6.0-beta12.. Transferring some movies from PC to unraid 120gb worth... Getting an average speed of 60-80mb/s... <- Laptop drive seems to be the bottleneck.. Usually I get an average of 35mb/s.. The drive I'm transferring it to, is a 3TB RED. Parity is the same.. The only change to the system is I swapped out 4 X 512mb sticks of ram, for 2 X 2gb sticks? I have no cache drive?

Thanks so much!!!!!

01 December 2014 Samba 4.1.14 Available for Download This is the latest stable release of the Samba 4.1 series. Last update on Unraid Summary of changes from 6.0-beta6 to 6.0-beta7 samba: update to 4.1.11 A fair amount of changes since the last update Major enhancements in Samba 4.1.12 include: o New parameter "winbind request timeout" has been added (bug #3204). Please see smb.conf man page for details. o Fix smbd crashes when filename contains non-ascii character (bug #10716). o dnsserver: Handle updates of tombstoned dnsNode objects (bug #10749). Changes since 4.1.11: --------------------- o Michael Adam <[email protected]> * BUG 10369: build: Fix configure to honour '--without-dmapi'. * BUG 10737: s3:idmap: Don't log missing range config if range checking not requested. * BUG 10741: Fix flapping VFS gpfs offline bit. o Jeremy Allison <[email protected]> * BUG 3204: s3: winbindd: On new client connect, prune idle or hung connections older than "winbind request timeout". Add new parameter "winbind request timeout". * BUG 10640: lib: tevent: make TEVENT_SIG_INCREMENT atomic. * BUG 10650: Make "case sensitive = True" option working with "max protocol = SMB2" or higher in large directories. * BUG 10716: Fix smbd crashes when filename contains non-ascii character. * BUG 10728: 'net time': Fix usage and core dump. * BUG 10773: s3: smbd: POSIX ACLs. Remove incorrect check for SECINFO_PROTECTED_DACL in incoming security_information flags in posix_get_nt_acl_common(). * BUG 10794: vfs_dirsort: Fix an off-by-one error that can cause uninitialized memory read. o Björn Baumbach <[email protected]> * BUG 10543: s3: Enforce a positive allocation_file_size for non-empty files. o Kai Blin <[email protected]> * BUG 10466: provision: Correctly provision the SOA record minimum TTL. o David Disseldorp <[email protected]> * BUG 10652: Samba 4 consuming a lot of CPU when re-reading printcap info. * BUG 10787: dosmode: Fix FSCTL_SET_SPARSE request validation. o Amitay Isaacs <[email protected]> * BUG 10742: s4-rpc: dnsserver: Allow . to be specified for @ record. o Daniel Kobras <[email protected]> * BUG 10731: sys_poll_intr: Fix timeout arithmetic. o Ross Lagerwall <[email protected]> * BUG 10778: s3:libsmb: Set a max charge for SMB2 connections. o Volker Lendecke <[email protected]> * BUG 10716: lib: strings: Simplify strcasecmp. * BUG 10758: lib: Remove unused nstrcpy. * BUG 10782: smbd: Properly initialize mangle_hash. o Stefan Metzmacher <[email protected]> * BUG 9831: s4:setup/dns_update_list: make use of the new substitution variables. * BUG 10723: Allow netr_ServerReqChallenge() and netr_ServerAuthenticate3() on different connections. * BUG 10749: s4-rpc: dnsserver: Handle updates of tombstoned dnsNode objects. * BUG 10751: s4-rpc: dnsserver: return DNS_RANK_NS_GLUE recors when explicitly asked for. * BUG 10773: libcli/security: Add better detection of SECINFO_[uN]PROTECTED_[D|S]ACL in get_sec_info(). o Marc Muehlfeld <[email protected]> * BUG 10761: docs: Fix typos in smb.conf (inherit acls). o Shirish Pargaonkar <[email protected]> * BUG 10755: samba: Retain case sensitivity of cifs client. o Arvid Requate <[email protected]> * BUG 9570: passdb: Fix NT_STATUS_NO_SUCH_GROUP. o Har Gagan Sahai <[email protected]> * BUG 10759: Fix a memory leak in cli_set_mntpoint(). o Roel van Meer <[email protected]> * BUG 10777: Don't discard result of checking grouptype. Changes since 4.1.12: --------------------- o Michael Adam <[email protected]> * BUG 10809: s3:smbd:open_file: Use a more natural check. o Jeremy Allison <[email protected]> * BUG 10717: s3: winbindd: Old NT Domain code sets struct winbind_domain->alt_name to be NULL. Ensure this is safe with modern AD-DCs. * BUG 10779: pthreadpool: Slightly serialize jobs. * BUG 10809: s3: smbd: Open logic fix. * BUG 10830: s3: nmbd: Ensure the main nmbd process doesn't create zombies. * BUG 10831: s3: lib: Signal handling - ensure smbrun and change password code save and restore existing SIGCHLD handlers. * BUG 10848: s3: smb2cli: Query info return length check was reversed. o Günther Deschner <[email protected]> * BUG 9984: s3-libnet: Make sure we do not overwrite precreated SPNs. o Björn Jacke <[email protected]> * BUG 10814: docs: Mention incompatibility between kernel oplocks and streams_xattr. o Volker Lendecke <[email protected]> * BUG 10735: Fix unstrcpy. * BUG 10797: s3: smbd: streams - Ensure share mode validation ignores internal opens (op_mid == 0). * BUG 10813: vfs_media_harmony: Fix a crash bug. * BUG 10860: registry: Don't leave dangling transactions. o Christof Schmitt <[email protected]> * BUG 10826: s3-winbindd: Use correct realm for trusted domains in idmap child. * BUG 10837: idmap_rfc2307: Fix a crash after connection problem to DC. * BUG 10838: s3-winbindd: Do not use domain SID from LookupSids for Sids2UnixIDs call. o Andreas Schneider <[email protected]> * BUG 9984: s3-libnet: Add libnet_join_get_machine_spns(). * BUG 9985: s3-libads: Add all machine account principals to the keytab. * BUG 10816: nmbd: Send waiting status to systemd. * BUG 10817: libcli: Fix a segfault calling smbXcli_req_set_pending() on NULL. * BUG 10824: nsswitch: Skip groups we were not able to map. Changes since 4.1.13: --------------------- o Michael Adam <[email protected]> * BUG 10472: Revert buildtools/wafadmin/Tools/perl.py back to upstream state. o Jeremy Allison <[email protected]> * BUG 10711: nmbd fails to accept "--piddir" option. * BUG 10896: s3-nmbd: Fix netbios name truncation. * BUG 10904: s3: libsmbclient-smb2. MacOSX 10 SMB2 server doesn't set STATUS_NO_MORE_FILES when handed a non-wildcard path. * BUG 10920: s3: nmbd: Ensure NetBIOS names are only 15 characters stored. o Günther Deschner <[email protected]> * BUG 10942: Cleanup add_string_to_array and usage. o David Disseldorp <[email protected]> * BUG 10898: spoolss: Fix handling of bad EnumJobs levels. * BUG 10905: spoolss: Fix jobid in level 3 EnumJobs response. o Amitay Isaacs <[email protected]> * BUG 10620: s4-dns: Add support for BIND 9.10. o Björn Jacke <[email protected]> * BUG 10835: nss_winbind: Add getgroupmembership for FreeBSD. o Volker Lendecke <[email protected]> * BUG 10932: pdb_tdb: Fix a TALLOC/SAFE_FREE mixup. o Stefan Metzmacher <[email protected]> * BUG 10472: pidl/wscript: Remove --with-perl-* options. * BUG 10921: s3:smbd: Fix file corruption using "write cache size != 0". o Jose A. Rivera <[email protected]> * BUG 10889: vfs_glusterfs: Remove "integer fd" code and store the glfs pointers. o Matt Rogers <[email protected]> * BUG 10933: s3-keytab: Fix keytab array NULL termination. o Richard Sharpe <[email protected]> * BUG 10880: S3: source3/smbd/process.c::srv_send_smb() returns true on the error path.

Ahh, now thats different. My NMT was freezing while streaming from UNRAID and PC, so I knew something was fishy with it. Thats strange indeed, as I am running 5.0.6 with spin-down delay of 15min and everything is working flawlessly. Older version of samba

I have tried my green's and red's, both do it.. Spin down doesn't matter, because when it freezes drive is still spinning. It's the communication between unraid and wd live.. it's the only thing that makes sense.. Considering a flash card with same file, plays without a flaw on the wd live box Considering, I have been using my qnap box for the past 40 days without a hitch streamin to the wd live box.. which is hooked up to the same switch as the unraid box

Hey Everyone... still having this issue.. had the server off for 40+ days waiting for the next beta.. Well all installed, no plugins.. same issue.. Any ideas? Log shows nothing when it happens? I still think it's something to do with this samba: update to 4.1.11.. from 6.0-beta7 Which is from August 01/14 Where do I go to ask the developers, to upgrade.. 08 September 2014 - Samba 4.1.12 20 October 2014 - Samba 4.1.13 01 December 2014 - Samba 4.1.14

write speed LOL parity right now is like 120mbs

Tower emhttp: sendFile: sendfile /usr/local/emhttp/webGui/images/good.png: Broken pipe Can access shares, can access telnet.. Can't see GUI

Hey Everyone, Building a new system... not exactly sure what is a better choice.. System Specs ASUS AM1I-A AM1 AMD Athlon 5350 Kabini Quad-Core 2.05GHz Socket AM1 25W Desktop Processor Want something that's low in power, cheap and has ECC Sad thing is the most sata ports available is 2 or 4.... The board does have 1 PCI-Express x4 slot.. Currently Have 2 Reds and 4 Greens, that I will move over.. So what are my options? HighPoint RocketRAID 2680 SGL PCI-Express x4 Low Profile SATA / SAS RAID Controller Card - $107.99 SUPERMICRO AOC-SASLP-MV8 PCI-Express x4 Low Profile SAS RAID Controller - -$116.99 Are those overkill? Do I need PCI-Express X4? Currently with my 5 year old mobo, sata2.. X 6 I'm getting around 30-35mbs.. would I be getting the same? Never used a controller card before?

Already tested ram all good, network card is built into mobo, but if it was losing connection I would be able to see that in the syslog.. also would be able to see that in my router log. This has happened before.. Working Fine, Samba version XXX Next Version of Unraid, New Samba - Issues Next Version of Unraid, Newer Samba - All good I wish I could see what my media player was doing...

Nothing... Tried a different switch and router too. Still same thing. The media player hasn't been updated in over a year lol

lol... it happens regardless if it's just me or multiple people in the household

Sadly no.... sab is running on a different server. I have nothing at all running on the server.. I have also never a had problem with multiple people accessing a different drive or even the same drive.. to watch a movie or show.. Still happens when I'm the only one accessing/watching a movie..

bump!! Still happening, syslog is still showing nothing.. Still 100% Random 7 Mins in.. a show... sometimes not at all 1:10 mins in a movie.. it's very very random Any chance for Samba 4.1.12 in next beta...? I think we are using 4.1.11 now

So I watched two episodes of a show First - 35:10 Freeze Second - 41:30 Whole show played without a hitch? I have had a problem like this before in the early versions of os5 beta.. I recall upgrading to the next beta and it worked fine.

Nope. The first part of the movie may be able to fit into ram and thus the drive is never accessed while the bits are in ram. It won't be until the drive is idle for the timeout and the memory is fully used before the drive is accessed again. "continuously" was a bad choice of words; but the file WOULD be accessed enough that no spin-down timer is going to expire. NO player that I'm aware of buffers enough of the movie that there wouldn't be any accesses until the spin-down time has expired. Note that the minimum spin-down you can set is 15 minutes -- and the OP has indicated this is NOT the case here. But even at 15 minutes, it's simply not realistic that the player wouldn't access the movie during that time. I'm not talking about buffers on the player side. I'm talking about the built in native linux filesystem buffering that seems to take place. I see what seems to be this happening on my system that has 8 GB ram on unraid. I haven't looked enough at this to validate beyond doubt that is exactly the case. However, here us what i oibserve... If my movie is smaller than that ( 7.7 GB or less ) the drives never seem to be accessed again. If my movie is larger than that or runtime is longer than my idle spindown setting ( 2 hours now ) then I get stuttering/pausing at the exact moment I hear the unraid drives spinning up. Nah... that's not the problem - I also doubt it's buffering to ram Movie 1 first pause at 1h:30ish mins Movie 2 first pause 30ish mins, then twice more Tv Show..42 Mins, not one skip Random, HD looks good, Nothing in Syslog... WDTV Firmware is still the same, Router and Switches all Restarted.. Am I missing something? This was not happening with beta5 or 6

Nope. The first part of the movie may be able to fit into ram and thus the drive is never accessed while the bits are in ram. It won't be until the drive is idle for the timeout and the memory is fully used before the drive is accessed again. "continuously" was a bad choice of words; but the file WOULD be accessed enough that no spin-down timer is going to expire. NO player that I'm aware of buffers enough of the movie that there wouldn't be any accesses until the spin-down time has expired. Note that the minimum spin-down you can set is 15 minutes -- and the OP has indicated this is NOT the case here. But even at 15 minutes, it's simply not realistic that the player wouldn't access the movie during that time. However, I have experienced the issue if I pause the movie for a more than seven or eight minutes. (I have the spindown parameter set at 30 minutes.) The reason for this post is not really that bit of information. The spindown time can actually be set in two different places. The first one is the obvious place--- under the 'Settings' tab, on the "Disk Settings' page. The second place is on the 'Main' page under the settings for each disk. Just click on the disk label (i.e., 'Disk 4') and you will see a place where the spindown time can be set for that disk. I am not sure which setting has precedence if they are different! (I am assuming that version 6beta is the same as ver 5.0.5 in this regard.) Everything is set the same, regardless this is happening as the file is being accessed lol

Using SMB.. reported my self lol to move to OS 6 duH!

It's static... Simple enough to test, disable spindown and watch a few movies. True - but no need to test. That's simply NOT the issue. As the OP noted, the movies are "... All single files " ==> so the file is continuously being accessed. No matter what the spindown setting is, the drive containing the movie is never going to be idle long enough to spin down. G Speed: Is this a new issue? If it's been working in the past, then think very carefully about what you may have changed. Has anything been moved? Did you add any new equipment in the mix? (New router; new cables; new switch; etc.) Did you recently upgrade to v6? (and if so, was this ever an issue with v5?) Anything you can think of that might have changed in the topology of your network may provide a clue as to what's happening. Hardware/Network all the same. The only change is going from beta5or6 to 9.. hoping it would help out with the webgui not being able to be access after less than 24hours. Had 9 for awhile, but most of that was watching tv shows... 30-45mins long.. never noticed a problem... Let alone much smaller bitrates so it would be able to cache/buffer a crap load more then a movie..... watched a movie on 9 started doing it... Upgraded to 10, Webgui is great now but skipping is still appearing... Here's the drive that the movies are on.. ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 182 180 021 Pre-fail Always - 5883 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 52 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 791 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 10 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 3 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 49 194 Temperature_Celsius 0x0022 129 115 000 Old_age Always - 21 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0

If it was spinning down, then I should be able to see it in the syslog?

35 Mins in movie.. freeze... just like the first one I watched this morning Syslog shows nothing...

Just want to make sure, all this looks okay Sep 28 17:19:26 Tower dhcpcd[1279]: eth0: carrier lost Sep 28 17:19:26 Tower dhcpcd[1279]: eth0: deleting host route to 192.168.0.191 via 127.0.0.1 Sep 28 17:19:26 Tower dhcpcd[1279]: eth0: deleting route to 192.168.0.0/24 Sep 28 17:19:26 Tower dhcpcd[1279]: eth0: deleting default route via 192.168.0.1 Sep 28 17:19:26 Tower dhcpcd[1279]: eth0: deleting IP address 192.168.0.191/24 Sep 28 17:19:26 Tower dhcpcd[1279]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' NOCARRIER Sep 28 17:19:26 Tower avahi-daemon[1420]: Withdrawing address record for 192.168.0.191 on eth0. Sep 28 17:19:26 Tower avahi-daemon[1420]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.191. Sep 28 17:19:26 Tower avahi-daemon[1420]: Interface eth0.IPv4 no longer relevant for mDNS. Sep 28 17:19:26 Tower kernel: r8169 0000:02:00.0 eth0: link down Sep 28 17:20:29 Tower dhcpcd[1279]: eth0: carrier acquired Sep 28 17:20:29 Tower dhcpcd[1279]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' CARRIER Sep 28 17:20:29 Tower kernel: r8169 0000:02:00.0 eth0: link up Sep 28 17:20:29 Tower dhcpcd[1279]: eth0: using ClientID 01:20:cf:30:64:4e:63 Sep 28 17:20:29 Tower dhcpcd[1279]: eth0: reading lease `/var/lib/dhcpcd/dhcpcd-eth0.lease' Sep 28 17:20:29 Tower dhcpcd[1279]: eth0: rebinding lease of 192.168.0.191 Sep 28 17:20:29 Tower dhcpcd[1279]: eth0: sending REQUEST (xid 0x4ffd978), next in 3.23 seconds Sep 28 17:20:32 Tower dhcpcd[1279]: eth0: sending REQUEST (xid 0x4ffd978), next in 7.67 seconds Sep 28 17:20:34 Tower dhcpcd[1279]: eth0: soliciting a DHCP lease Sep 28 17:20:34 Tower dhcpcd[1279]: eth0: sending DISCOVER (xid 0x8ae28878), next in 4.33 seconds Sep 28 17:20:39 Tower dhcpcd[1279]: eth0: sending DISCOVER (xid 0x8ae28878), next in 7.81 seconds Sep 28 17:20:46 Tower dhcpcd[1279]: eth0: sending DISCOVER (xid 0x8ae28878), next in 16.01 seconds Sep 28 17:20:46 Tower dhcpcd[1279]: eth0: offered 192.168.0.191 from 192.168.0.1 Sep 28 17:20:46 Tower dhcpcd[1279]: eth0: sending REQUEST (xid 0x8ae28878), next in 4.40 seconds Sep 28 17:20:46 Tower dhcpcd[1279]: eth0: acknowledged 192.168.0.191 from 192.168.0.1 Sep 28 17:20:46 Tower dhcpcd[1279]: eth0: checking for 192.168.0.191 Sep 28 17:20:46 Tower dhcpcd[1279]: eth0: sending ARP probe (1 of 3), next in 1.56 seconds Sep 28 17:20:48 Tower dhcpcd[1279]: eth0: sending ARP probe (2 of 3), next in 1.60 seconds Sep 28 17:20:50 Tower dhcpcd[1279]: eth0: sending ARP probe (3 of 3), next in 2.00 seconds Sep 28 17:20:52 Tower dhcpcd[1279]: eth0: leased 192.168.0.191 for infinity Sep 28 17:20:52 Tower dhcpcd[1279]: eth0: adding IP address 192.168.0.191/24 Sep 28 17:20:52 Tower avahi-daemon[1420]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.191. Sep 28 17:20:52 Tower avahi-daemon[1420]: New relevant interface eth0.IPv4 for mDNS. Sep 28 17:20:52 Tower avahi-daemon[1420]: Registering new address record for 192.168.0.191 on eth0.IPv4. Sep 28 17:20:52 Tower dhcpcd[1279]: eth0: adding host route to 192.168.0.191 via 127.0.0.1 Sep 28 17:20:52 Tower dhcpcd[1279]: eth0: adding route to 192.168.0.0/24 Sep 28 17:20:52 Tower dhcpcd[1279]: eth0: adding default route via 192.168.0.1 Sep 28 17:20:52 Tower dhcpcd[1279]: eth0: writing lease `/var/lib/dhcpcd/dhcpcd-eth0.lease' Sep 28 17:20:52 Tower dhcpcd[1279]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' BOUND Sep 28 17:20:52 Tower dhcpcd[1279]: eth0: sending ARP announce (1 of 2), next in 2.00 seconds Sep 28 17:20:54 Tower dhcpcd[1279]: eth0: sending ARP announce (2 of 2)

Have always used IP lol All single files Will give it a shot.... and report back after the next movie tonight lol