Jump to content

Videodude

Members
  • Posts

    20
  • Joined

Posts posted by Videodude

  1. I've been having an issue with my Docker Containers the past few months. I click "check for updates" and 7 of my 8 containers will say "update ready". I'll go through the motions of updating them all one by one. After updated, for the next few days clicking "check for updates" will show them all as "up-to-date", however after 1-2 weeks those same containers will show as "update ready" again, even though after the update the version of the application is the same.

     

    I don't know what logs or information to post here that would help with troubleshooting the issue. Please let me know and I'll post away. This issue is so annoying!!

  2. it's any version you want it to be from 14 to 16 (jarvis beta4) by setting the VERSION variable.

     

    Mr. Balls - Is the VERSION variable something that you can set via the UNRAID web interface, or is that command line only? Can you see what version it's running from the web interface once the docker is up and running?

  3. I don’t know if you have plans to add more Seagates to the SASLP, but so you’re not surprised, expect parity check to slow down considerably with each additional disk you add past the 3 you have now.

     

    Honestly, I'm actually considering removing my SASLP cards. My UnRAID system was built back in 2011 with 2 of those cards and 15 HDD trays (I had 10 of the slots filled), and I just recently upgraded everything to the latest version of UnRAID and replaced all the drives. My mobo has 6 SATA on-board connections, and that's more than enough for my system today (I only need 4 of them with these new high capacity drives).

  4. Initial parity build != parity check. Totally different operation, you need to do a check after the build completes if you want full confidence in the array. Many people see much higher speeds on the build than they do on the check.

     

    Good point, and thanks for the correction. Once my build is complete and my data is on the array, I'll run a check to see the times.

  5. Just set up a new UnRAID server with 3 of these drives - 1 parity + 2 data.

     

    My preclear times were the same as jbuszkie. My parity check is way faster though. I'm at ~15.5 hours to complete the initial parity of the 3 drive array. These 3 drives are plugged into my AOC-SASLP-MV8 card.

     

     

    Oh, and those clicks are annoying. I have them on all 3 drives though, so it must be normal. The SMART data is all fine and they all passed their preclear with flying colors.

  6. I'm almost finished building a new UnRAID setup with 3 of these drives (1 parity + 2 data). Just thought I'd share my numbers.

     

    My preclear time was just over 60 hours for the 3 drives. This was with the flast post-read flag set, although I may have messed that up.

     

    I'm almost finished with building my parity as well now. I'm about 11 hours in and 75% finished. The total time when finished should be about 15.5 hours total, which honestly isn't too bad in my mind considering the parity drive is 8TB.

×
×
  • Create New...