Fonzarelli

Members
  • Posts

    39
  • Joined

  • Last visited

Everything posted by Fonzarelli

  1. Thanks for taking the time to look at this. If it will clean up the logs I will disable docker and vm so you're not going through a bunch of extra code, and then re post the diagnostic file again in a day or two when I experience the slow down.
  2. The diagnostics are from the crippled unraid machine.. The internet slowed down only a couple of days after the last reboot. I haven't done another reboot because it doesn't seem to fix the problem although rebooting my modem does.
  3. Yes, the last boot 26 hrs ago was to upgrade to the latest unraid version, at the time of upgrade I had to also reboot the modem or it would not download the update. And after 26 hrs unraid has almost no internet connection. Pi hole is a new docker that I set up only a couple weeks ago.. This problem manifested months ago. I have however completely disabled the docker and vm manager for a period of time and the problem still persists. (about 6 months back I did a complete hardware upgrade to the server and just reused the drives, but I can't say for sure if it started right after the upgrade. I do know that I didn't have this problem on my old build).
  4. I've used the Fing app on my phone to analyze my home network and the few devices that are on the network have unique ip address. At one point I had a static ip set in unraid and thought that was the problem so now I let my modem assign the ip but still the same issue
  5. I'm having a strange problem where my unraid internet connection comes to a grinding halt after a couple of days, it slows down so much that it takes for ever just to download a plugin update. The strange thing is my docker and vm containers all connect through the same ethernet card and they perform at full speed on the internet with my 150mb internet connection, its only the unraid os that loses almost total internet connectivity. I have 2 other devices on my wired network that always perform at top speed. I have tried rebooting unraid and it does not correct the problem, the strange thing is rebooting my internet modem does fix the problem temporary for a couple of days until the speed starts to taper off to almost nothing again. I installed the speedtest plugin and it reports that i have a Download speed of 0.06 Mbit/s even though all my other devices on the network including dockers ad vm's can utilize the 150mb internet connection. Any help would be greatly appreciated, Ive been searching for a solution for months. I have attached the diagnostics file. tower-diagnostics-20180426-2021.zip
  6. Thanks for the quick reply, got it all fixed up
  7. After upgrading to 6.4.0 the unraid gui has defaulted back to port 80. I use to have it mapped to 8008 by adding this line into the go file. /usr/local/sbin/emhttp -p 8008 & With the new unraid version this line doesn't seem to make the change. Is there another way i can set the gui to port 8008?
  8. Thanks for the advice johnnie.black. I did a pre clear and am about to re-sync parity. but regardless I think im going to order up a new drive like you said just because its not worth the chance of failure. ############################################################################################################################ # # # unRAID Server Preclear of disk WD-WX81D65CAT95 # # Cycle 1 of 1, partition start on sector 64. # # # # # # Step 1 of 4 - Zeroing the disk: [12:12:29 @ 136 MB/s] SUCCESS # # Step 2 of 4 - Writing unRAID's Preclear signature: SUCCESS # # Step 3 of 4 - Verifying unRAID's Preclear signature: SUCCESS # # Step 4 of 4 - Post-Read verification: [12:23:11 @ 134 MB/s] SUCCESS # # # # # # # # # # # # # # # # # ############################################################################################################################ # Cycle elapsed time: 24:35:46 | Total elapsed time: 24:35:47 # ############################################################################################################################ ############################################################################################################################ # # # S.M.A.R.T. Status default # # # # # # ATTRIBUTE INITIAL CYCLE 1 STATUS # # 5-Reallocated_Sector_Ct 0 0 - # # 9-Power_On_Hours 4441 4465 Up 24 # # 194-Temperature_Celsius 32 35 Up 3 # # 196-Reallocated_Event_Count 0 0 - # # 197-Current_Pending_Sector 0 2 Up 2 # # 198-Offline_Uncorrectable 2 2 - # # 199-UDMA_CRC_Error_Count 0 0 - # # # # # # # # # # # ############################################################################################################################ # SMART overall-health self-assessment test result: PASSED # ############################################################################################################################ --> ATTENTION: Please take a look into the SMART report above for drive health issues. --> RESULT: Preclear Finished Successfully!.
  9. Here is the result of the extended SMART test. It says the overall test passed but it also shows Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: read failure 60% 4427 842782376 The parity that is failing is a 6TB where all the other drives in my array are 2 and 4TB. not sure if it is less concern for failing sectors considering there is lots of room to rewrite the data in another sector. Or am I wrong? I bought the drive only a couple months ago, but it was in an external enclosure that i broke open so no warranty. smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.9.30-unRAID] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Blue Device Model: WDC WD60EZRZ-00RWYB1 Serial Number: WD-WX81D65CAT95 LU WWN Device Id: 5 0014ee 261dc6eca Firmware Version: 80.00A80 User Capacity: 6,001,175,126,016 bytes [6.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5700 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Sun Nov 5 07:46:49 2017 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: ( 118) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: ( 4604) 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 700) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3035) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 196 195 021 Pre-fail Always - 9175 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1210 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 094 094 000 Old_age Always - 4439 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 22 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 5 193 Load_Cycle_Count 0x0032 194 194 000 Old_age Always - 18941 194 Temperature_Celsius 0x0022 120 113 000 Old_age Always - 32 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 2 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 1 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 Completed: read failure 60% 4427 842782376 # 2 Short offline Completed without error 00% 4422 - 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.
  10. I just noticed this today. Should I be concerned about this error and replace the drive, or is this not something to worry about?
  11. Sorry, forgot to mention wordpress is not in a sub directory it is off the www root... strangely i had joomla running just fine but it is so much more complicated than wordpress i decided to switch. ive had many other websites working directly from the www root but wordpress is giving me problems.
  12. Im trying to set up wordpress with the letsencrypt container. I have read through this entire thread and tried all of the config suggestions but i still cannot access the site properly over the internet. the site is viewable within my lan. Could someone help pick apart my nginx default config and tell me were im going wrong. Is this the only file i have to edit or am I missing something else? # listening on port 80 disabled by default, remove the "#" signs to enable # redirect all traffic to https server { listen 80; server_name _; return 301 https://$host$request_uri; } # main server block server { listen 443 ssl default_server; root /config/www; index index.html index.htm index.php; server_name _; add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always; ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; ssl_prefer_server_ciphers on; client_max_body_size 0; location / { try_files $uri $uri/ /index.html /index.php?$args =404; } location ~ \.php$ { fastcgi_split_path_info ^(.+\.php)(/.+)$; # With php7-cgi alone: fastcgi_pass 127.0.0.1:9000; # With php7-fpm: #fastcgi_pass unix:/var/run/php7-fpm.sock; fastcgi_index index.php; include /etc/nginx/fastcgi_params; } # sample reverse proxy config for password protected couchpotato running at IP 192.168.1.50 port 5050 with base url "cp" # notice this is within the same server block as the base # don't forget to generate the .htpasswd file as described on docker hub location ^~ /couchpotato { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://10.0.1.5:5050/couchpotato; } location ^~ /nzbhydra { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://10.0.1.5:5075/nzbhydra; } location ^~ /nzbget { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://10.0.1.5:6789/nzbget; } location ^~ /sonarr { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://10.0.1.5:8989/sonarr; } location ^~ /nextcloud { include /config/nginx/proxy.conf; proxy_pass https://10.0.1.5:444/nextcloud; } location ^~ /multicraft { include /config/nginx/proxy.conf; proxy_pass http://10.0.1.15:80/multicraft; } } # sample reverse proxy config without url base, but as a subdomain "cp", ip and port same as above # notice this is a new server block, you need a new server block for each subdomain #server { # listen 443 ssl; # # root /config/www; # index index.html index.htm index.php; # # server_name cp.*; # # ssl_certificate /config/keys/letsencrypt/fullchain.pem; # ssl_certificate_key /config/keys/letsencrypt/privkey.pem; # ssl_dhparam /config/nginx/dhparams.pem; # ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; # ssl_prefer_server_ciphers on; # # client_max_body_size 0; # # location / { # auth_basic "Restricted"; # auth_basic_user_file /config/nginx/.htpasswd; # include /config/nginx/proxy.conf; # proxy_pass http://192.168.1.50:5050; # } #}
  13. thank you .. i should have searched the forum some more. just found this
  14. Is there a way to re-install the gui? i havent made any changes for some time and am running the latest 6.3.5 version. but suddenly there are no checkboxes in the gui. when i try to create a vm I cant select the processor cores to use.. i also noticed it on the docker page of the gui also
  15. thanks for the heads up... ill update my flash backup before I forget
  16. Bought a new larger hd for my parity drive and unassigned my existing parity to use as another data drive. Installed the preclear plugin and ran it on both at the same time. Of course the smaller 2 terabyte drive finished the preclear before the 6 terabyte drive so i figured instead of waiting another 12 hours for the 6TB to finish the preclear i would just stop the array and add the 2TB to an empty slot as a data drive and let it format while the other continued to preclear. Well, I hit the stop array button and now I have no access to the web gui.. I wonder if this is a bug... i probably shouldn't have tried to add a drive while preclear was running on another drive. Anyway i can still access unraid through a telnet session. Is there something i could type into telnet to find where it is hanging? thanks, I am running the latest stable release.
  17. I noticed that the drive that has the share on it that owncloud stores data on will never spin down. Is that normal behavior or have I messed up the settings? Or do most people just store all their cloud on the cache disk so the data disks can spin down? The strange thing is Ive installed Open Files and even though owncloud is keeping the disk spun up, there is no sign of folder mounts or files in use from that disk. Thanks for any input.
  18. After some more troubleshooting I have come to the conclusion that the ownCloud docker is keeping the disks spun up. Ill post my ownCloud conundrum in gfjardim's docker thread.
  19. Hi, I did some searching on this topic and tried some of the solutions that I came across, but still haven't fixed my problem. Im hoping someone can figure out the issue Im having. Im running Unraid version 6.1.9 with the following dockers running from the cache drive; gfjardim - CrashPlan aptalca - Duckdns sparklyballs - Krusader yujiod - MineOS gfjardim - ownCloud limetech - PlexMediaServer linuxserver - Transmission For troubleshooting I've installed as suggested in other threads; Fix Common Problems plugin by Squid and also Open Files plugin by dlandon which appears to show that no files are in use on Drive 1 Ive attached the diagnostics zip if that could help sort out this problem. Thanks for helping guys. tower-diagnostics-20160604-1217.zip
  20. Scratch my last post. sifting through the site i came across this https://lime-technology.com/forum/index.php?topic=44312.0 Solved my problem
  21. I accidentally uninstalled the ownCloud docker in an attempt to get the latest update and now even after reinstalling the ownCloud docker i only get an error when i go to the web GUI "Downgrading is not supported and is likely to cause unpredictable issues (from 8.2.1.4 to 8.1.4.2)". I must have updated previously from the ownCloud web GUI interface and now it will not let me run the docker from gfjardim since I have run a newer version previously.. hopefully someone can give me some insight how i can repair my installation without having to start from scratch again.
  22. Glad to hear the data recovery is successful. I've been in the same situation when you realize the catastrophic mistake you've made seconds after you've pressed the button
  23. Just a suggestion, ive had realy good luck with TestDisk for recovering data from repartitioned or formatted drives. Its free and quite simple to use.
  24. I've encountered the same problem before http://lime-technology.com/forum/index.php?topic=11971.msg114236#msg114236 Removing and replacing the same drive can result in data loss if not done correctly.