SidebandSamurai

No I did not do the new permission process. It appears that access to all the files are just fine. I can see all the folders in windows Explorer. Sincerely Sideband Samurai

Thanks for your reply! I have disconnected the mouse as instructed. I also rebooted the sever so that I have a clean syslog to view. I still have the problem. Here is what I have done. I had my friend copy a file from one of his other unraid servers to his local machine. This was successful. I then had him copy the file from the local machine to the dataserver which is the server we are troubleshooting. It failed to copy the file after a minute or two of transferring the file. Next I had him copy the same file to a brand new windows 8.1 PC with a freshly installed operating system and nothing else installed. This file copied successfully. Next I had him copy a group of 18 files from the Windows 8.1 PC to the DataServer. This also copied successfully with the exception that there were times, the throughput dropped to 0 for about 15 seconds, then picked up again. Also the Windows 8.1 PC did have an error occur during the copy where it told him that there was some type of network error. We talked a little bit and he hit Retry and the copy resumed to completion. Enclosed is a copy of the new syslog to review. -- Sideband Samurai syslog.txt

Please find attached the complete syslog on the system. syslog.1 and syslog. Thanks. Syslog.zip

Ok, I will look at this. Thanks.

dgaschlk, what I posted on October 29, is what I retrieved from the server. I did exactly as you asked. Sideband Samurai

Your include parameters were wrong also. Disk1,Disk2 does not exist where as disk1,disk2 (Notice the small "D") does exist. Glad you got it working though. Sideband Samurai

Request 1: root@DataServer:~# ifconfig eth0 Link encap:Ethernet HWaddr 14:da:e9:68:64:6a inet addr:192.168.1.52 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5598318 errors:0 dropped:72 overruns:0 frame:0 TX packets:6935386 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1456034311 (1.3 GiB) TX bytes:3573943744 (3.3 GiB) Interrupt:40 Base address:0xc000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:290 errors:0 dropped:0 overruns:0 frame:0 TX packets:290 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:147032 (143.5 KiB) TX bytes:147032 (143.5 KiB) Request 2 root@DataServer:~# ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes Thanks for the help Syslog is attached. Sideband Samurai syslog.zip

Thanks for the suggestion Switchman, but this server has always run on a static IP. Sideband Samurai

hmmm, That link now shows it at 139.99

I have a friend who is using unRAID I am helping him support the server. I believe its licensed as a Plus server. We just recently upgraded to 5.0 final. I really don't remember what version he was on before we upgraded. I did the upgrade, I don't remember if we backed up the flash drive or not. Anyway, everything upgraded fine, his sever is healthy, we had a bad memory stick that would not allow the system to boot which was resolved. Now comes the problem. When a copy to the server is made, say for example 1 file, it works just fine most of the time. If I select 3 files, then the first file will begin to copy and about 1 minute or two later, the copy process will freeze, and windows will report that the network drive is not available. When I cancel the copy and attempt to access the drive, there is a X across the drive and windows continues to report its not available. Then about 30 seconds later, the drive will be accessible again and everything is fine. We have attempted the copy from a couple of computers all with the same result. It appears that the server will stream media fine, but I have not fully tested this yet either. No errors are reported in the syslog, and if required I will post the syslog. I am currently in the middle of gathering what type of network chip he is using. I know its a realtek chipset. we cant replace the NIC card with a PCI card because the motherboard does not have any PCI or PCIe 1X slots. Only one PCIe 16x slot. This post was to start off a question, if anyone else has seen this problem. Downgrading is not a solution because I don't know what version he was on prior to the upgrade. I will be posting additional info soon. Thanks for your help. Sideband Samurai

Will This work for you? http://www.newegg.com/Product/Product.aspx?Item=N82E16817998183&nm_mc=KNC-GoogleAdwords&cm_mmc=KNC-GoogleAdwords-_-pla-_-SSD+%2f+HDD+Accessories-_-N82E16817998183&gclid=CN-HxcnAnboCFcs9QgodhmQAsQ Its used for SSD's but could work for a 1TB 2.5" drive. This one can mount two 2.5" laptop drives into a PCI slot: http://www.scythe-usa.com/product/acc/064/slotrafter_detail.html If you want to use 3.5" drives then you would basically have to fasten the hard drive directly to the PCI bracket plate. I have seen it done, it not pretty but works very well. The other way is to customize yourself a 3.5" bracket made out of copper clad PCB, you etch the PCB so there is no copper and mount the drive to it. then secure the assembly into the empty PCI slot. This project again demonstrates 2.5" drives but could be adapted for 3.5" as well. http://www.electrocave.com/home/projects/2-5-inch-hard-drive-in-a-pci-slot -- Sideband Samurai

Your UNRAID server should have a static IP assigned. Your DHCP pool should be set to assign address from 192.168.1.50 to 192.168.1.254. The numbers from 192.168.1.1 to 192.168.1.49 would be considered your static range, as DHCP would not assign these lower numbers because they are not included in the pool. If your DHCP server is not set up this way it should be adjusted, and allow the UNRAID server to remain on the .4 address. This avoids accidental changes in the IP address for the server. Your DHCP server would normally be located on your router. --Sideband Samurai

You could look in your web console. The web console shows both data drives and parity drives. The parity drive will be the first drive, and will be identified by a number that looks like this: ST3000DM001-1CH166_W1F12655 (sdb) 2930266532 The serial number is the last 8 numbers in this identification string. In this case it tells you /dev/sdb Also the serial number may be different depending on manufacturer. the /dev/sdX drives are usually assigned in order from port0 to port 2 (for a basic 3 drive system). If your parity is on /dev/sdc, and your flash is on /dev/sda, start with sdb and port0 and count up until you get to sdc. in this example, your drive is most likely on port1. Pull port 1 and verify the serial number. If the serial number matches, you have the parity drive. Its what I did to identify my parity drives when I upgraded from 2tb to 3tb.

you can use Midnight commander. mc is the command. then you can move files from one drive to the other. Sideband Samurai

Hi, Just wanted to ask if you have upgraded to Release 5 yet? Sideband Samurai

No one has asked this question, so I will. You suspect problems, what kind of problems do you suspect? Do you have smart reports on each of the drives you can post? - Sideband Samurai

I don't know if this matters or not, but you should upgrade to the official 5.0 release. It could be the driver was updated between RC-16 and 5.0 release. - Sideband Samurai

I guess I have one more question that fits here. When pre-clearing disks, how many cycles should I run on the drive before it is considered good. For each 4TB drive I pre-clear each cycle takes 24 hours. If I run 5 cycles that's 5 days before I can put the drive into service. I want to use best practices at this point to make sure the hardware is sound. Just wanted feedback on what people do. When I originally put the system together, I ran only one pre-clear and the drives have performed flawlessly. Thanks. - Sideband Samurai

Really? Its always good practice to open a new thread. THAT is the general rule on ALL forum sites. As an example, the OP was using release 4.7. Also the OP's hardware is different than yours. For those reasons and others you should post a new thread. The advantage to that is your solution will be easier to find instead of buried in another thread. That helps others, not just you. Not only that but that also follows the policy of this forum. When you open your own thread, there is nothing stopping you from referencing this one, and answering all the questions I posed to you in my last post. We really need to know about your unraid system and something about your network. We are not mind readers you know.

I remember reading that You never want the drive to completely fill up, you always want to leave up to 10% of the drive free for the RiserFS journal. Filling the drive up, then loosing power and you could be in a really big mess. You always need to save some space for the RiserFS journal. Same thing in Unraid, if you have 10% or less of any drive left, it is recommended that you stop adding files until another drive is added. This posting on the unraid Forms also suggests 10% or more should remain free on each drive to keep performance at maximum. http://lime-technology.com/forum/index.php?topic=26061.0 Sideband Samurai

Joe and everyone; Thanks for all your feedback, Everything has been resolved. Ultimately it was RAM in the server causing all my concerns. -- Sideband Samurai

I have replaced the RAM in the unraid server and it has passed 15 cycles of the memory test with out any errors. Memory was upgraded from 512mb to 2GB.

RockDawg, Well you really should start a new thread. As the OP's issues are not yours though your symptoms are the same. Please open a new thread and when you do that, describe your network, is it wired, wireless, powerline, or a combination of all of these etc. Is it 10mb, 100MB, 1GB. What brand switches are you using. are you using cat 6 cable, cat 5e etc, What operating systems are in use. describe your unraid server, what version, processor, ram, number of drives, and also provide system logs for us to look at. How are able to reproduce the problem, describe how you reproduce the problem. Go through these tests, do use the OP as your description just to be lazy. Provide as much detail as possible. You have an excellent resource available to you, use it to your advantage. Above all ** DO NOT use this thread ** :-) --Sideband Samurai

Joe L. Thanks for your suggestion, I have definitely confirmed that I have a RAM issue. I just started retesting memory with just one stick installed and have found the bad module right off the bat. I will swap the other module in just to make sure they both are not defective and get rid of the bad module. This really makes me feel lots better and also explains the kernel panics I started seeing recently. I will still continue to post on this thread until I have the system up on all my 3TB drives. -- Sideband Samurai

Joe L. Excellent analysis. The system ONLY has 512MB. I had forgotten that it was that short of ram. I have NOT had a problem with it for the Year or so its been in production. It has been really reliable all through the RC phase of the 5.0 release. I am currently pre-clearing another drive in another system. With firmware cc29, it seems to be performing much better than with the CC43 firmware. One main difference is that this drive is pre-clearing on a different system with lots (8GB) of ram. Its 11 hrs into the pre-clear process and its on the last step, so we will see soon enough. My drive is a ST3000DM001-1CH1 3TB hard drive. As for parity checks, they all have been successful with zero errors. I have ran a total of 3. For now, I have the server shutdown, while I complete the preclear on this new drive. Joe, I have previous posts about weather or not the -A is required in the pre-clear script. I was concerned that with out the -A option, it tells me that the partition will not be aligned. Can you take a look at my previous posts on this thread and give me your opinion? Thanks for your time. Sincerely, Sideband Samurai