kenshinx34

Members
  • Posts

    27
  • Joined

  • Last visited

Everything posted by kenshinx34

  1. Second try is a charm. I tore it all down, removed all the configs. Rebuilt it from scratch and it works great. Thanks!
  2. Could you explain the click on icon method for adding ram? I feel really dumb. I would just ssh in and update the /bin/run.conf
  3. I gave mine 4gb of ram and nothing I still get the same error as I did before.
  4. Here's a screenshot for reference. I'm currently running updated unraid with the most current docker build of crashplan.
  5. I also have the same issue with Crashplan becoming disconnected after 1 minute or so. It just started since this last update. Any ideas?
  6. If I really don't want to add a cache, is it necessary? or am I fine just doing it to the normal array and just lose the speed and performance gains?
  7. I'm going to ask a dumb question that I couldn't find the answer to anywhere, but I'm sure exists. Feel feel to just point me to a link. Why should we put the docker setup on the cache drive? Is it a performance reason (faster speeds)? Is it so we aren't constantly spinning up and down multiple drives in the array? Is it so we don't constantly write data to the disk & parity? Is there any harm in putting in on the array? If we do use a cache drive what's the risk of the cache dying with the docker/crashplan data on it? Do you automatically have the cache set to backup to your array at night? Again, I apologize if this has been asked before. I just would like to understand a bit better the proper use of the cache drive before I sacrifice a sata port for cache disk. -Eric
  8. This is probably just a crazy coincidence. I have never had RAM ever go bad on me. I updated to 6.1.8 on both of my Unraid servers and in the same week I had two completely different Unraid builds RAM go bad. Can an OS corrupt RAM, or is this just some crazy coincidence? One stick of RAM is 2yrs + old, and the other is <6months. One is 2GB, the other is 8GB. I get correlation does not imply causation, it just seems too hard to ignore that two completely different machines, with entirely different workloads, hardware specs would go bad after the same upgrade within a week of one another. Has anyone had file corruption with bad ram? Would parity checks catch this?
  9. Totally the memory. I am an idiot. How much should I worry about the files that I copied over? If they copied okay what do you think the chances of corruption are/were?
  10. I'm making the move as well to Windows 10. Since v6.1.* I've had nothing but problems, docker won't stay alive for more a day, and I can't even copy large files off without unraid dying (I suspect a kernel issue but no one has replied to my forum post). I've used unraid for years and years and really like it, but I can't deal with the instability.
  11. Well unraid is just about unusable now. I'm really surprised no one has replied to this post.
  12. Also the CPU is at max 15% utilized so it is not taxed at all and airflow is great.
  13. Hey All, I'm a long time Unraid user and have not had this type of error before. When transferring files, at some point during the transfer Windows experiences "an unexpected network error". After receiving this error I could no longer ping Unraid, SSH, connect to shares, or pretty much anything. It was clear that Unraid was still on, but nothing was responding. The only way to get it out of this was to hard power it off. This obviously isn't good and forces a parity check each time. I'm currently running the latest build of Unraid 6.1.7. Docker is not running and the only other plugin I have running is Sleep (other than the stock plugins). The drives are all reporting clean SMART stats, and the pool is 6 drives (10TB total) with about 70% utilization. Here's my system build: M/B: ASUSTeK Computer INC. - M4A88T-M CPU: AMD Athlon II X3 450 @ 3200 HVM: Disabled IOMMU: Disabled Cache: 384 kB, 1536 kB Memory: 6144 MB (max. installable capacity 16 GB) Network: eth0: 1000Mb/s - Full Duplex Kernel: Linux 4.1.15-unRAID x86_64 OpenSSL: 1.0.1q After digging deeper and tailing syslog during a transfer here's what I found (see the attached two logs). At first I thought it had something to do with AFP so I disabled the share with the apple shares. Still the same issue. The transfers range anywhere from 50GB to 250GB which is big, but has never been a problem in the past. This machine has been incredibly stable (uptimes of 8 months no problem). I haven't made any hardware changes recently either. Any help would be awesome! First.txt Second.txt
  14. I just installed the Crashplan & Crashplan Desktop docker images and am having an issue with a "Bus error" *** Running /etc/my_init.d/config.sh... Current default time zone: 'America/Los_Angeles' Local time is now: Sat Jan 2 18:10:29 PST 2016. Universal Time is now: Sun Jan 3 02:10:29 UTC 2016. cp: cannot stat ‘/root/wallpapers/*’: No such file or directory /etc/my_init.d/config.sh: line 17: 30 [b]Bus error[/b] /usr/bin/supervisord -c /opt/supervisord.conf Now here's the strange part. I spent the last week troubleshooting a docker/owncloud problem where a "Bus error" was an issue while trying to run an update within docker/owncloud. I would say this was just my problem as it seems no one else has stumble across it from the lack of Google answers. However these are on two completely separate unraid builds that are both experiencing "Bus errors". Here's my Unraid version and build information: Version: 6.0.1 Model: N/A M/B: ASUSTeK Computer INC. - M4A88T-M CPU: AMD Athlon(tm) II X3 450 @ 3200 HVM: Disabled IOMMU: Disabled Cache: 384 kB, 1536 kB Memory: 6144 MB (max. installable capacity 16 GB) Network: eth0: 1000Mb/s - Full Duplex Kernel: Linux 4.0.4-unRAID x86_64 OpenSSL: 1.0.1o Uptime:29 days Also after checking my main unraid log I would get the following line repeating while the docker containers were running Jan 2 18:18:12 Server kernel: BTRFS warning (device loop0): csum failed ino 19263 off 10285056 csum 3357241515 expected csum 2995147020 With some Googling here's what I've found so far although I'm not sure how to use it: https://lime-technology.com/forum/index.php?topic=40960.30 Any help would be great!
  15. Could you elaborate more? Do you mean having owncloud access other folders on unraid, or folders on your desktop where app is installed.
  16. After I tried to update I can't seem to get this screen to go away and go back to the login screen. I've tried: [*]Waiting [*]toggling maintenance mode on and off in the config manually (which will put it into maintenance mode, but toggling it off brings it right back) [*]going into docker itself to run occ (however it seems as if the owner / executable-ness needed to be fixed up) [*]After changing the permissions of occ and /config/config.php to run occ, I received a "Bus error" and can't seem to get farther than that. [*]Restarting the docker image I did notice that the config.php has version 8.0.4.2 and that the version.php file has 8.1.4. Any help would be AWESOME. I've been working on this for a few hours and am at a loss at this point. Thanks!
  17. Okay I made the changes to my syslinux.cfg on the correct lines this time! Where do I look to verify that it is only using 4095? Here's my syslog! Thanks! New_Text_Document_3.txt
  18. I was in the process of completing the other items listed when I last posted. -Sorry I've completed the following: #2 (Switching BIOS AHCI) #3 (wasn't needed as #2 changed the hdx to sdx) #4 I added that line to the 'syslinux.cfg' file to change the amount of RAM but didn't see on the syslog where to check that. I've attached the latest syslog since these changes (to verify the correct amount of RAM), and will be trying a large file transfer today to see how it goes! I appreciate the help! syslog_after_fixes.txt
  19. Alright I swapped the cable and no more error. That's the strangest thing in the world. I would have thought that a cable either worked or wouldn't work! I didn't realize that could have an effect like it did. I'm still getting a hang when I try to copy large files over (it says network no longer available), but now it doesn't lock up the server, I just have to retry the copy. I'll do some testing and see if I can rule out my router, computer and other stuff but for now here's the smart test... I ran a long smart test on the drive in question and here's the info: Linux 3.9.6p-unRAID. root@Tower:~# smartctl -a -d ata /dev/hdc 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 === Device Model: WDC WD30EZRX-00MMMB0 Serial Number: WD-WCAWZ2926157 Firmware Version: 80.00A80 User Capacity: 3,000,592,982,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sat Sep 14 16:25:21 2013 PDT 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: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (49680) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off supp ort. 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 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 153 152 021 Pre-fail Always - 9333 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 284 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 092 092 000 Old_age Always - 6182 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 - 50 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 28 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 817 194 Temperature_Celsius 0x0022 125 111 000 Old_age Always - 27 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 - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 1012 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged 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. root@Tower:~# smartctl -d ata -tlong /dev/hdc 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 OFFLINE IMMEDIATE AND SELF-TEST SECTION === Sending command: "Execute SMART Extended self-test routine immediately in off-line mode". Drive command "Execute SMART Extended self-test routine immediately in off-line mode" successful. Testing has begun. Please wait 255 minutes for test to complete. Test will complete after Sat Sep 14 20:43:29 2013 Use smartctl -X to abort test. root@Tower:~# smartctl -d ata -a /dev/hdc > smartctl.txt root@Tower:~# smartctl -d ata -a /dev/hdc 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 === Device Model: WDC WD30EZRX-00MMMB0 Serial Number: WD-WCAWZ2926157 Firmware Version: 80.00A80 User Capacity: 3,000,592,982,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sun Sep 15 06:45:49 2013 PDT 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: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (49680) 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 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 153 152 021 Pre-fail Always - 9350 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 285 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 092 092 000 Old_age Always - 6196 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 - 50 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 28 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 820 194 Temperature_Celsius 0x0022 119 111 000 Old_age Always - 33 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 - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 1012 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 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 without error 00% 6190 - 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.
  20. Alright, currently updated to 5.0 final. Unraid no longer freezes, however it is showing some worrying messages in the syslog. This is pretty much the main message I see repeated throughout my syslog: Sep 12 23:08:15 Tower kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } Sep 12 23:08:15 Tower kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC } Sep 12 23:08:15 Tower kernel: hdc: possibly failed opcode: 0x35 "hdc" is my parity drive, should I be nervous that my data is being corrupted? My parity checks come out clean, but if I have a dying parity drive I wonder if that could corrupt everything. I've attached the full log: New_Text_Document_2_2.txt
  21. WARNING: NEW USER I have been running a configuration for the past year which has been extremely stable (>100 days) without a shutdown, error or anything. Lately I've been trying to transfer ~300Gb of data to my "Tower" and in the process it will become unavailable. After cancelling the transfer I cannot connect to the network share, or ping the tower. However, it is still on. I've hooked up a monitor to it when this happens to see the command line and it only sometimes displays an image. I haven't made any changes recently or messed with the drive configuration. Each hard shutdown requires a parity check which takes ~18 hours. Sometimes I'll also have trouble accessing the web interface, however in this circumstance I can still Telnet into it. Here's my setup: unRAID Version: unRAID Server Plus, Version 5.0-beta14 Motherboard: ASUSTeK - M4A88T-M Processor: AMD AthlonTM II X3 450 - 3.2 GHz Cache: L1 = 384 kB L2 = 1536 kB L3 = 0 kB Memory: 6912 MB - DIMM1 = 1333 MHz DIMM2 = 1333 MHz DIMM3 = 1333 MHz Network: 1000Mb/s - Full Duplex Simple Features 1.0.5 I guess my question is that I don't know where to start troubleshooting. Any help would be appreciated. I also have logs I can post, but I'm not sure which log files are relevant. Thanks!
  22. I just installed simplefeatures. I highly recommend the S3 sleep if you mobo has the WOL cabability. S3 sleep will shut down all fans and drives. I keep my box in a confined space and the box only draws about ~1watt when in S3 sleep as opposed to 60watts when running, and 150 when everything is at full tilt. Hope that helps!