October 12, 20169 yr Hi I have just done a fresh install of unraid 6.2 with a pc that has 4x2tb disks in it. I am going to be using this just to sync data from my primary unraid server using a btsync docker. This is what I have done. Step 1 : Preclear 1 data drive. Completed successful preclear. Step 2 : Start array with this 1 data drive. Step 3 : Install btsync docker I then started adding my btsync keys to this new docker and it was not able to find the primary server. Both PC's are on the same subnet and plugged into the same switch. I then decided to reboot both servers to see if that would fix the problem. Now the new unraid server is showing errors on the disk and the docker service is not starting. I then checked the logs and found I/O errors. I am guessing that this is a cable problem possibly as I think I/O errors mean that expected data to and from the disk is not happening? Correct me if I'm wrong. I am going to unplug the cables from the drives and troubleshoot this but thought I should upload my diagnostics to this forum to see if there is anything that I am missing. Thanks EDIT : Adding to this. I started a disk check and it showing a speed of 3.7MB/sec. VERY SLOW. The unraid system itself is also very slow to respond to any commands. A simple refresh of the main page can take up to a minute. tower-diagnostics-20161012-0056.zip
October 12, 20169 yr Community Expert The errors being logged are the loop0 device which is the docker.img file rather than a specific physical drive. It might be worth stopping the array, deleting the current docker.img file and then restarting the array to create a new one. Also how large a docker.img file do you have? It is possible it should be larger, particularly if the btsync docker is not configured correctly so it is creating files inside the docker.img file rather than on the array disks.
Archived
This topic is now archived and is closed to further replies.