wolferl99

Members
  • Posts

    42
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

wolferl99's Achievements

Rookie

Rookie (2/14)

0

Reputation

  1. Interestingly the exact same thing happened to me. And thanks, your tip 'remove image, move nzbget appdata. reinstall image, copy back nzbget.conf and python.sh' worked for me too. not sure but it must be related to python2 install during the image install. still looking for a fix
  2. thanks for the info. the TS431S comes with an expander, thats why I need SAS-SAS between it and my case. even if I put all drives into a new case, I still need new adapter cards though (2 X8 ones as x16 ones dont seem to be around much), so it really comes down to new case vs ext drive case.
  3. something like that for the external SAS connection and this for the internal connections?
  4. Hi, as my trusted Asrock E3C224D4I-14S MoBo died, I had to replace it. Went with a Asrock E3C246D4U (CPU Intel Xeon E-2124). I have 12 drives in a Fractal Design Node 804 case, 8 in the internal cages plus 4 in an additional cage in the front. Two problems with the 246 board: a) it doesnt have the 2 onboard mini SAS connections and b) because the CPU is in the different place I can no longer place the additional drive cage in the case. For the time being I am using a AOC-SASLP-MV8 to at least keep the system up albeit slowly. My plan is to get a Silverstone TS431S put the 4 drives in and connect via SAS. Thankfully the new board has 3 PCI E slots x4, x8, x16 (currently running the MV8 in the X4 slot). As the MV8 doesnt really have the bandwith (or better the X4 aspect) to run 4 modern drives at speed, I no longer want to use that. Having the x16 slot seemed like the best option. get a x16 card with 1 external and 2 internal SAS connection, problem solved. But, these either dont exist or only it very fancy versions with way more ports for way more money. Having the luxury of multiple PCIE slots my plan now is: 1. get one x8 card with 2 internal SAS connections (run in x16 slot) 2. get another x8 card with 1 external SAS connection (run in x8 slot) 3. make sure these are HBA not RAID cards (is that as simple as finding a card that doesnt have RAID in the name?) Would like feedback. silly idea? should work? any advice on cards to get? (I am aware of the 8087/8088 cable situation)
  5. 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 is today, vs the old UnMenu days, loading packages in the go file Ha, even found one of my early status emails: " To: root Subject: unRaid Status OK Sent: Jun 22, 2010 6:47 AM Subject:unRaid Status OK Status update for unRAID Tower - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Status: unRaid is OK Server Name: Tower Server IP: 192.168.1.103 Date: Tue Jun 22 06:47:01 GMT+7 2010 Filesystem 1K-blocks Used Available Use% Mounted on /dev/sdf1 3912180 190948 3721232 5% /boot /dev/sde1 312557836 1082464 311475372 1% /mnt/cache /dev/md4 195353928 32840 195321088 1% /mnt/disk4 /dev/md2 1953454928 1378414864 575040064 71% /mnt/disk2 /dev/md3 1953454928 247557880 1705897048 13% /mnt/disk3 /dev/md1 1953454928 1471779012 481675916 76% /mnt/disk1 shfs 6368276548 3098867060 3269409488 49% /mnt/user shfs 6055718712 3097784596 2957934116 52% /mnt/user0 " So a whopping 6TB in /mnt/user? Today any of my disks is larger than this!
  6. 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 User Capacity: 8,001,563,222,016 bytes [8.00 TB] Disk /dev/sdl: 8001.6 GB, 8001563222016 bytes 255 heads, 63 sectors/track, 972801 cylinders, total 15628053168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdl1 1 4294967295 2147483647+ 0 Empty Partition 1 does not start on physical sector boundary. ######################################################################## ========================================================================1.15 == == DISK /dev/sdl IS PRECLEARED with a GPT Protective MBR == ============================================================================ I ran the preclear script via the gui plugin. I checked /boot/preclear_reports/ but there are no new reports. The last one is from November, the last time I ran a preclear. Am I missing something? Are the logs somewhere else? Should I assume that there were no major problems, when the drive is marked precleared? Here's the current smart report. (running an extended smart report right now) root@tower:/boot# smartctl -a /dev/sdl smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.1.18-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: ST8000AS0002-1NA17Z Serial Number: Z840DXXX LU WWN Device Id: 5 000c50 087d2caac Firmware Version: AR15 User Capacity: 8,001,563,222,016 bytes [8.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5980 rpm Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Mon Mar 7 17:22:16 2016 PST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 249) Self-test routine in progress... 90% of test remaining. Total time to complete Offline data collection: ( 0) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 951) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x30a5) SCT Status supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 114 099 006 Pre-fail Always - 81402960 3 Spin_Up_Time 0x0003 098 098 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 2 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 071 060 030 Pre-fail Always - 12772681 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 49 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 2 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 099 000 Old_age Always - 65537 189 High_Fly_Writes 0x003a 098 098 000 Old_age Always - 2 190 Airflow_Temperature_Cel 0x0022 063 060 045 Old_age Always - 37 (Min/Max 18/37) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 2 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 12 194 Temperature_Celsius 0x0022 037 040 000 Old_age Always - 37 (0 18 0 0 0) 195 Hardware_ECC_Recovered 0x001a 114 099 000 Old_age Always - 81402960 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 69879117905966 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 15628053208 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 17547198660 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Self-test routine in progress 90% 49 - # 2 Short offline Completed without error 00% 48 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. root@tower:/boot#
  7. FYI: nzbget after updating the container works fine again here. Thanks gfjardim
  8. 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 my cached nzbget.conf file into the docker /opt/nzbget/webui/ directory. without that, the gui worked but I couldn't changed settings. I used docker exec -i -t NZBGet bash for that. Not sure why that happened, I'm not the biggest docker expert in the world. But, this works for me. Oh, dont forget to manually stop and start the docker image via unraid webgui
  9. 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.
  10. 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.
  11. 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 ...
  12. 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.
  13. 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!
  14. 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 four years with very little problems). But again, it has to be right for you. For some people lowest price is the highest priority, for others most space.