wolferl99

Members
  • Content Count

    38
  • Joined

  • Last visited

Everything posted by wolferl99

  1. After enjoying the free version for a while, I bought my first licenses 2010: " ============================================================= Lime Technology, LLC - Online Order ============================================================= Invoice No.: 2327 Order No.: 110628526 Date: 06/16/2010 " IIRC 4.7 was my first version, but I could be mistaken. Apart from some smaller hickups, mostly related to hardware (ECC vs non ECC memory comes to mind), things have gone pretty smoothly. I still can't believe how smooth and integrated everything i
  2. Hi, following situation. I ran a preclear on a drive over the weekend and I assume it finished sometime last night. This morning we had an extended power outage and the server shutdown and then restarted a couple of hours later. I can't seem to find the preclear reports. It looks like the drive was cleared, as I see this, when I run a preclear -t on it: Pre-Clear unRAID Disk /dev/sdl ################################################################## 1.15 Device Model: ST8000AS0002-1NA17Z Serial Number: Z840DXXX LU WWN Device Id: 5 000c50 087d2caac Firmware Version: AR15 Us
  3. FYI: nzbget after updating the container works fine again here. Thanks gfjardim
  4. Ok, I looked into it a bit and found what my problem was. In my nzbget.conf file, that sits on my cache drive and is 'volume mapped' into the docker container, I had to change two line items: From WebDir=/usr/share/nzbget/webui To WebDir=/opt/nzbget/webui And From ConfigTemplate=/usr/local/share/nzbget/nzbget.conf To ConfigTemplate=/opt/nzbget/webui/nzbget.conf Looks like the nzbget location changed from /usr/local/share/nzbget to /opt/nzbget. At least that's my deduction based on the config file. Oh, and I think I manually copied over m
  5. same 404 here. looking at the changes, it seems he moved stuff from install.sh to config.sh but commented out these lines: +# # Fix a potential lack of template config +# if [[ -f /usr/share/nzbget/nzbget.conf ]]; then +# cp /usr/share/nzbget/nzbget.conf /usr/share/nzbget/webui/ +# elif [[ -f /usr/share/nzbget/webui/nzbget.conf ]]; then +# cp /usr/share/nzbget/webui/nzbget.conf /usr/share/nzbget/ +# fi not sure why he moved it but commented it out. could be an easy fix.
  6. Seeing the way LT communicates with its users (see announcement thread for rc1 2 3, might be 4 by the time I'm done), I really don't feel like either testing nor providing feedback. I know, doesn't add to the conversation but it might be important to understand why people chose not to participate. I'll be happily using the final version once it's out for 2 weeks without problems.
  7. Very nice! And yall just remember that it will take some time to compile the new version, depending on the CPU/memory available (~ 10min here). If you don't, you might waste time troubleshooting for no reason ...
  8. great thread, thanks everyone. One slight addition: it might make sense to lock rsync down a bit for security reasons. If you want/need to, simply add a hosts allow statement to your rsync.conf file, e.g [mnt] path = /mnt comment = /mnt files read only = FALSE hosts allow = 192.168.0.100 only allowing 192.168.0.100 to rsync to this box.
  9. Hear ya. That's why I bought in 3 different batches from 3 different vendors in 3 different states over, you guessed it, a 3 week time frame. It's still the same drive model, that's a risk I'm willing to take. smaller footprint was a main driver, so going with a bunch of smaller drives simply wouldn't have been practical as this will replace my main box and I need the space. I'll spend a lot of time, automating smart reports so at least drive failures don't come out of the blue. In 4 years I'll build a new box with 2 16TB drives before my 6TB ones fail!
  10. That's pretty much what I did. I bought 7x 4TB drives a year ago, replacing a huge pile o'drives. Selling my old drives on Fleabay, I got close to the then-current per-TB price fir them. same here. just replaced a 11 drive 2TB/4TB server with a nice clean 6x6TB setup. I know if I had waited another few months, the drives would have been cheaper/larger etc pp. That will always be the case as there is always technical improvements. Gotta find the right compromise for you. I like the confidence of having a brand new system that should run for a few years easily (my old box ran for
  11. Hi, thanks for the update. Yeah, the memory was a pita. I tried the following: - http://www.newegg.com/Product/Product.aspx?Item=N82E16820148545&cm_re=BLS2KIT8G3D1609DS1-_-20-148-545-_-Product MEM 8Gx2|CRUCIAL BLS2KIT8G3D1609DS1 - http://www.newegg.com/Product/Product.aspx?Item=N82E16820148802 Crucial 16GB (2 x 8GB) 240-Pin DDR3 SDRAM ECC Registered DDR3 1600 (PC3 12800) Server Memory Model CT2K8G3ERSLD4160B - http://www.newegg.com/Product/Product.aspx?Item=N82E16820239291&cm_re=KVR16N11K2-_-20-239-291-_-Product MEM 8Gx2|KST KVR16N11K2/16 R None of which worked! Ei
  12. Two more WD60EFRX data points preclear_report_sdg ========================================================================1.15 == invoked as: ./preclear_disk.sh /dev/sdg == WDCWD60EFRX-68MYMN1 WD-WXCxxxxxxx33 == Disk /dev/sdg has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 1000448 Bytes == Last Cycle's Pre Read Time : 15:15:10 (109 MB/s) == Last Cycle's Zeroing time : 12:28:00 (133 MB/s) == Last Cycle's Post Read Time : 27:52:22 (59 MB/s) == Last Cycle's Total Time : 55:36:32 == == Total Elapsed Time 55:36:32 == ==
  13. Nothing too spectacular, but I wanted to provide the results of one of of my 6TB WD Reds preclear as another datapoint. I have 3 more reports of the same model, but they are a bit off because I adjusted the timezone halfway through the process. But the times were very comparable to this one: ========================================================================1.15 == invoked as: ./preclear_disk.sh /dev/sdg == WDCWD60EFRX-68MYMN1 WD-WX11D7 == Disk /dev/sdg has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 1000448 Bytes == L
  14. Did you use ECC memory Reginald? Just got the same case/board and it wont start at all with my non ECC memory. As the case doesn't have a speaker, I dont know if it sends emergency beeps, but it simply does not output a picture via VGA.
  15. looking good. any chance to use hotswap cages with this case?
  16. That looks exactly like it for me when I went from 5 to 5.03. In my case there was a segfault for libc used by wget in the syslog. never fixed it and downgraded to 5.
  17. john, you seem to have the same problem I just experienced after upgrading to 5.03 from 5.0. a segfault in libc when running wget. that causes the startup/install to fail and not download the latest and greatest. because of that other plugins (like sabnzdb) didnt start either. I didnt have the segfault with 5.0. Unfortunately I wasn't able to fix it. there must be some plugin conflict, but I didnt have the time to investigate after 20 minutes and downgraded back to 5.0. all good now, vbox working fine. just thought I'd share.
  18. Hi All, just precleared a new seagate 4TB and wanted a second set of eyes on the report. root@Tower:/boot/preclear_reports# cat preclear_rpt_Z30066L1_2013-12-03 ========================================================================1.14 == invoked as: ./preclear_disk.sh -A /dev/sdf == ST4000VN000-1H4168 Z30066L1 == Disk /dev/sdf has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 9:25:43 (117 MB/s) == Last Cycle's Zeroing time : 8:08:29 (136 MB/s) == Last Cycle's Post Re
  19. Just remember that your license key is tied to your thumb drive. You will need a new key for a replacement drive. Unless you only use the free version of course.
  20. noticed, that I never resolved this topic. So, better late than never: I'm happy to report, that the new PSU: SeaSonic X Series X650 Gold did the trick. No problem since! ps: strangely I can't modify the original post. no 'modify' option. Obviously I could change this reply but not the orig. So mods fell free to add [solved] to the title. cheers
  21. "The promo code PREBLKFR84 has expired and is no longer valid."
  22. Fascinating. I have 8 2tb greens running 24x7 for 2 years now and not a single problem. They must have quite a QA variety. For 4tb I'm aiming for either WD reds or Hitachis (backblaze cant go wrong, right)