Jump to content

KDP

Members
  • Content Count

    13
  • Joined

  • Last visited

Community Reputation

0 Neutral

About KDP

  • Rank
    Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I just finished copying all my pages to text documents to paste over to the new wiki. I deleted and cleared the data from the old docker and reinstalled using "edge". Email seems to be working again. I have also restarted the docker a few times and it connects properly every time so far. I am about to start putting my pages back in and will let you know if I experience any future problems. Thanks for your time.
  2. This morning I have restarted the container about 10 times and its worked every time, which is unusual, so I cannot get you a NGINX log. If you believe that the "edge" version is more stable I am more than happy to try it. Does this mean I will lose all my current pages? If so that is not a huge deal as I only have about 20 or so and can simply copy them into text documents to paste into the new version. I am just looking for stability at this point (and a working email function).
  3. Here is the log file you requested. Thanks for taking the time to look at it. I restarted the docker and it fails to allow me to connect to the web interface. I then pulled the log file so it should hopefully show where the issue is coming from. mediawiki-json.log
  4. Will just the UnRaid logs be sufficient? There did not seem to be any logs inside the docker for MediaWiki. Any other information that I could include that would be helpful?
  5. I am having issues getting email to work. It worked once for some reason when I first set the docker up and i authenticated my account and has not worked since. I am seeing an error "Unknown error in PHP's mail() function." All of the configurations for the email match those of my stand alone mediawiki and I have re-verified them as being accurate. An additional problem I am having is that anytime I restart the docker I have a 50 50 chance that I won't be able to access the mediawiki wedpage. I have to delete the docker and reinstall the docker and my wiki is back up.
  6. It apparently isn't the cable as I tried a known good one and ended up with the same problem. I just wish I had tested it when WD sent it to me years ago. Thanks for taking the time to assist me.
  7. Thanks so much for pointing that out Johnnie. I have never read a SMART report before and I was a bit overwhelmed. I was googling how to decipher the data and everything always talked about how to look at the values it outputs and what they mean so I completely overlooked a lot of the remaining output.
  8. I am currently in the process of upgrading my unraid server. I had 3 drives that were not in my current unraid box. I memtested my system for 36 hours no problem. I attached the 3 drives and started the preclear plugin on them. One drive failed almost instantly. It wasnt a surprise because it is an old WD Black 2TB that I couldnt remember where I got it from. One is a WD Green 2TB that ran while I slept and was still running when I went to work. I came home and it failed/aborted on pre-read. I actually opened the factory package for this drive which I believe was a warranty replacement for a previous failed drive. I have attached the preclear log and both the smart long and short log. The short test in unraid ran all the way to 90% and then staid there for a while and finally stopped with Errors occurred - Check SMART report. The long test did not make it past 10% and errored out as well. Is this drive just crapped out? Sucks I didn't check it when I got it returned because its been sitting around for a couple years. preclear.txt smart long.txt smart short.txt
  9. Daughter had a few hijackers so it probably ended up on her side.
  10. I scanned mine and my wife's machine. She had a 2 adwares and I had a clean bill of health. I checked through the router settings and there are no port forwarding entries and the night that it occurred there were only 2 devices attached to my wireless so I don't think it was a router intrusion. I am kinda hoping something shows up on my daughters machine that I am scanning tonight just so I can have an actual idea as to why it occurred. However the blocking of internet access in the router to my unRaid box seems to have stopped whatever was going on.
  11. So tonight I noticed that my entire network was acting up. Reset the router and my switches but still issues. I was transferring a new movie I bought but noticed all of my disks were spinning. I spun them all down and within a few minutes they all started spinning again. I blocked internet access to my server and spun them all down again and they stayed asleep. I am currently scanning my family computers, but is it possible that something has infected my unRAID server allowing someone to copy my backups?
  12. So I was looking at the web interface today and noticed that one of my drives is showing 1213 errors. I looked at the syslog and there seems to be a lot of handle_stripe read errors showing up when my server did its parity check on the first. The parity check says everything is fine so I am just looking for some informed opinions about what is going on. I am running 5beta6a (its been running great for everything I use it for and figured I would wait til the final to update). I have included a smart report and syslog to assist in determining the issue. smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green (Adv. Format) family Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WCAZA2955441 Firmware Version: 51.0AB51 User Capacity: 2,000,398,934,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sun Nov 6 21:23:21 2011 EST 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: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (37980) 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: ( 255) 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 199 199 051 Pre-fail Always - 539 3 Spin_Up_Time 0x0027 206 171 021 Pre-fail Always - 4691 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 73 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 096 096 000 Old_age Always - 3600 10 Spin_Retry_Count 0x0032 100 253 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 - 17 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 9 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 535 194 Temperature_Celsius 0x0022 109 103 000 Old_age Always - 41 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 001 001 000 Old_age Always - 65506 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 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 - 0 SMART Error Log Version: 1 ATA Error Count: 12 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 12 occurred at disk power-on lifetime: 3458 hours (144 days + 2 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 c8 b0 00 e0 Error: UNC at LBA = 0x0000b0c8 = 45256 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 00 c8 b0 00 e0 08 2d+06:51:32.725 READ DMA ef 10 02 00 00 00 a0 08 2d+06:51:32.725 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 2d+06:51:32.721 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 2d+06:51:32.721 SET FEATURES [set transfer mode] Error 11 occurred at disk power-on lifetime: 3458 hours (144 days + 2 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 c8 b0 00 e0 Error: UNC at LBA = 0x0000b0c8 = 45256 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 00 c8 b0 00 e0 08 2d+06:51:30.040 READ DMA ef 10 02 00 00 00 a0 08 2d+06:51:30.040 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 2d+06:51:30.036 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 2d+06:51:30.036 SET FEATURES [set transfer mode] Error 10 occurred at disk power-on lifetime: 3458 hours (144 days + 2 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 c8 b0 00 e0 Error: UNC at LBA = 0x0000b0c8 = 45256 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 00 c8 b0 00 e0 08 2d+06:51:27.355 READ DMA ef 10 02 00 00 00 a0 08 2d+06:51:27.355 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 2d+06:51:27.351 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 2d+06:51:27.351 SET FEATURES [set transfer mode] Error 9 occurred at disk power-on lifetime: 3458 hours (144 days + 2 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 c8 b0 00 e0 Error: UNC at LBA = 0x0000b0c8 = 45256 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 00 c8 b0 00 e0 08 2d+06:51:24.669 READ DMA ef 10 02 00 00 00 a0 08 2d+06:51:24.669 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 2d+06:51:24.665 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 2d+06:51:24.665 SET FEATURES [set transfer mode] Error 8 occurred at disk power-on lifetime: 3458 hours (144 days + 2 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 c8 b0 00 e0 Error: UNC at LBA = 0x0000b0c8 = 45256 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 00 c8 b0 00 e0 08 2d+06:51:21.985 READ DMA ef 10 02 00 00 00 a0 08 2d+06:51:21.985 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 2d+06:51:21.981 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 2d+06:51:21.981 SET FEATURES [set transfer mode] SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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. syslog.zip