jcreynoldsii

That got it. Thanks!

Got the bugs worked out by specifying a -i in the Extra Parameters section under advanced view. Does anyone know the schema if there is one for adding this automatically via the XML.

I am creating my first docker and I am running into an issue that I was hoping someone who is a lot more familiar with creating dockers would be able to help out with. It downloads an image which is only 75 MB, however the latest release says its 128 MB. The docker container doesn't actually start with unraid and the config directory contains no files. I believe it has something do with my RUN mkdir /NodeLink command. Git: https://github.com/jcreynolds/NodeLink Hub: https://hub.docker.com/r/jcreynolds/nodelink/ EDIT: I believe the issue has to do with running .exe file. Any help would be appreciated. Thanks, jc

Oddly enough that worked. Thanks

How do I set the security privileges for sub-directories of my main shares? It tells me I don't have the proper permissions to modify any folders/files within the sub-directories.

SOLVED. Has to enable Shares

I don't have a cache drive, where is the proper place for /config data.

I enabled user shares and now I can stop the array again. Going to re-install my docker containers. I will post my results here.

I have been having using try to stop the array. It gets stuck on retrying to unmount. A search on the forums leads me to believe the shares not being set up.

I installed some Docker Containers and I can no longer get to their web interface. tower-diagnostics-20150706-1813.zip

Well that escalated quickly. How unfortunate, I'll never buy a Seagate again.

At 23:59:59 today a leap second will be added to the time. So essentially 23:59:59 is going to occur twice today. I don't believe this will have any negative implications on you. However, I would like to hear what others have to say about it.

Preclearing the Seagate drive as we speak. The other drive I gave up on it is dead. It just clicks in an external as well.

Just seems weird all of a sudden I have issues with reallocated sectors and disk errors. I guess Seagate drives really are a piece of sh*t.

I just upgraded the PSU: http://www.newegg.com/Product/Product.aspx?Item=N82E16817153198 MOBO: http://www.newegg.com/Product/Product.aspx?Item=N82E16813128659 CPU: http://www.newegg.com/Product/Product.aspx?Item=N82E16819113379 Memory: http://www.newegg.com/Product/Product.aspx?Item=N82E16820231314 I guess drive 3 could be failing I just don't want to believe it at this time. As far as the bios goes I will have to check when I get home.

I had my array up and running on 6.0.0 with no issues. I started having issues as soon as I went to 6.0.1. I plan to back track and clear my config, reformat my thumb drive and install 6.0.0 and try to rebuild my array.

All disks were precleared 3x prior to going into an array.

I currently do not have any data on my unraid server. I am a new to unraid and I just have been recently getting everything together. Perhaps I clear my config and start all over from scratch.

I do have another disk but its not a 4tb drive, I assume that doesn't matter?

Attached bennysrv-diagnostics-20150629-1224.zip

I came down to look as my unraid box and saw that one of my drives had 780 million errors on it. So I powered down my server and and checked all sata and power connections and rebooted. Unraid would not boot and the disk is clicking. So I changed out the sata cable and went to a different port on the MOBO and I still have the same result. After waiting for a while the server finally came up but it says disk 2 is not installed. Can anyone give me advice on what to do next? If you need logs let me know I will post them. I also now have another drive showing reallocated sectors, WTF? Is that just a coincidence or could it be related? Forgot to mention this all happened after I upgraded to 6.0.1. Is there any known issues with this version?

How much per drives if multiples are bought? How many hours have these drives been running and do they have warranties?

Thanks for everyone's feedback, these are just a couple drives I had sitting around. Seems like Seagate drives aren't worth a damn.

It appears that one of the drives is indeed bad, however the other one seems to be good however there were a few things at their thresholds. Can anyone interpret these results and enlighten me? Thanks, JayC

Do you still have 4 left?