armandocerna

Members
  • Posts

    13
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

armandocerna's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Anyone have any thoughts on this, specifically regarding the sata controllers? Thinking of buying this as an upgrade to my current unraid box. http://www.newegg.com/Product/Product.aspx?Item=N82E16813157475
  2. Actually I think I read the update screen wrong I am on the latest testing version available.
  3. This is so awesome. Exactly what docker needed. I can't wait to get docker 1.3 on unraid.
  4. Any update on this? I would love to update my nzbget container to the latest version.
  5. I had to modify his instructions a bit too after the docker build his docker run command wasn't working for me I ended up doing something like this, and since I have used the docker ui mostly I don't have a seperate containers just for volumes mount points I just define them directly in the docker run command. l used something like this, you will need to change the paths. docker run -d --cap-add=NET_ADMIN --net=none --volumes-from transmission_config -v /mnt/cache/.incomplete:/incomplete -v /mnt/user/downloads/complete:/complete --name transmission transmission Once you run that you can start and stop the container you just need to run pipework manually. I think you could add it into your go file with something like sleep 120; /boot/config/pipework
  6. I got it working. The pipework piece is fairly simple first grab a copy of pipe work from https://github.com/jpetazzo/pipework Once you start the docker transmission container it is waiting for pipework to run. I just ran it from an ssh session. Here is the syntax I used: pipework br0 transmission 192.168.0.50/[email protected] Assuming br0 is your bridged interface you can check with an ifconfig. The IP 192.168.0.50 is the address I am assigning the transmission instance, followed by the subnet mask of my network and finally the default gateway on my network. Once you run pipework the docker container will establish the vpn connection. Assuming you followed his steps to get your PIA vpn credentials into the correct directory before running the docker build command.
  7. I'm not sure if if the concept of inodes exist on btrfs formatted volumes. But you can get the appearance of being out of disk space by running out of inodes. Check to see if you are using all available inodes on the volume "df -i"
  8. I had a failed data drive and wanted to upgrade my array to 4tb drives at the same time. I tried to initiate the parity copy and I got it started at 9% it just stops. Is there anything I can do to resolve this? My assumption is that I have some bad parity somewhere that is causing this issue. I am willing to cut my losses and rebuild parity with the failed drive empty. I can try salvage most of the data off of the failed drive outside of unraid.
  9. I understand what you are saying about replacing the failed drive and upgrading the parity drive are different steps. What I want to avoid though is replacing my failed 2tb drive with another 2tb drive. I would like to use the opportunity to buy 3tb drives instead. Being that I have to replace my failed drive first I won't have a 3tb parity drive installed yet and will be replacing the failed disk with a larger disk. Are there any problems with this?
  10. Hello, I have a failed drive that is not the parity drive that I will be replacing soon, currently my parity drive is a 2tb drive and the failed drive is also a 2tb drive. I would like to take this opportunity to upgrade to a 3tb parity drive instead of a 2tb one. My assumption is that I have to replace the failed drive first if I replace a 2tb drive with a 3tb drive without having a 3tb parity drive can I eventually get the 3tb once I replace the parity drive after the failed drive has rebuilt. Please let me know if I am missing something.