splnut
Members-
Posts
216 -
Joined
-
Last visited
Converted
-
Gender
Undisclosed
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
splnut's Achievements
Explorer (4/14)
2
Reputation
-
Unraid Forum 100K Giveaway
splnut replied to SpencerJ's topic in Unraid Blog and Uncast Show Discussion
The GUI is amazing! I would love to see fail over protection with vms and docker containers. -
Sorry if this is a dumb question, but I tried to install this docker on Ubuntu and got the following message. Can someone point me in the right direction? 2017-03-22 13:59:22,474 DEBG 'start-script' stdout output: [warn] 'tun' module not available, you will not be able to connect to ruTorrent or Privoxy outside of your LAN [info] Synology users: Please attempt to load the module by executing the following on your host:- 'insmod /lib/modules/tun.ko' 2017-03-22 13:59:22,480 DEBG 'start-script' stdout output: [warn] 'iptable_mangle' module not available, you will not be able to connect to ruTorrent or Privoxy outside of your LAN [info] unRAID users: Please attempt to load the module by executing the following on your host:- '/sbin/modprobe iptable_mangle' [info] Synology users: Please attempt to load the module by executing the following on your host:- 'insmod /lib/modules/iptable_mangle.ko'
-
Ok. I have tried to swap the sata cable and power connector twice. I have also swapped out the additional sata card as this issue started when I added 2 new drives to the array. tower-diagnostics-20170315-1134.zip tower-diagnostics-20170315-0939.zip tower-smart-20170315-1156 (1).zip
-
Here is the smart report after rebooting. Should it be safe to unassign/reassign again? smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.9.10-unRAID] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Green Device Model: WDC WD40EZRX-00SPEB0 Serial Number: WD-WCC4E4CL8734 LU WWN Device Id: 5 0014ee 2b5df2df9 Firmware Version: 80.00A80 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2 (minor revision not indicated) SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Fri Mar 10 15:21:00 2017 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: (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: (52380) 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: ( 524) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x7035) 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 - 6 3 Spin_Up_Time 0x0027 200 176 021 Pre-fail Always - 7000 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1878 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 195 192 000 Old_age Always - 264 9 Power_On_Hours 0x0032 085 085 000 Old_age Always - 11572 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 168 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 57 193 Load_Cycle_Count 0x0032 141 141 000 Old_age Always - 179801 194 Temperature_Celsius 0x0022 119 112 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 - 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 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. tower-diagnostics-20170310-1518.zip
-
I recently added 2 new drives to my array. One of the drives was connected to a Marvell 9250 controller and fell offline and caused the disk to be disabled. I took this chance to remove all the sata cables and reconnect/reposiiton them. Upon reboot, my parity disk was disabled. I shut down the server, reset the sata cable and powered back up. After checking the SMART report, I decided to unassign and reassign the parity disk. Partiy rebuilt and everything was fine. After about 3 days, the parity disk is disabled again and I can no longer check the smart report through the GUI (or through terminal). How can I check the SMART report of this drive? Following the wiki (http://lime-technology.com/wiki/index.php/Console#Console_Commands_for_Hard_Drives), results in the following error: tower-diagnostics-20170310-1423.zip
-
I was having issues when I tried using a mix of linuxserver and binhex containers. Since the mappings are different (/downloads vs /data), the different apps were having issues with post processing. So I switched everything over to binhex without an issue.
-
splnut started following Network will not auto reconnect and Disk is unmountable
-
I thought I read somewhere that they are working on PHP with their Dockers. Plus this isn't officially supported yet. Mine quit working and I assume it's related to that.
-
Shows as an INTEL in the System Devices. I did just get a new 4 port pci card that I plan on installing this week to see if that changes anything. 00:1a.0 USB controller [0c03]: Intel Corporation C600/X79 series chipset USB2 Enhanced Host Controller #2 [8086:1d2d] (rev 06) 00:1d.0 USB controller [0c03]: Intel Corporation C600/X79 series chipset USB2 Enhanced Host Controller #1 [8086:1d26] (rev 06)
-
I am trying to pass through a wireless receiver for an xbox 360. I have tried 2 different adapters with multiple VM's (i440fx/Q35, Windows/linux, etc) . When the device is passed through to a VM, I receive the following error continuously (247 times per second). Jan 15 23:34:27 Tower kernel: usb 2-1.3.2: reset full-speed USB device number 9 using ehci-pci Jan 15 23:34:27 Tower kernel: usb 2-1.3.2: usbfs: usb_submit_urb returned -28 Jan 15 23:34:27 Tower kernel: usb 2-1.3.2: usbfs: usb_submit_urb returned -28 Jan 15 23:34:27 Tower kernel: usb 2-1.3.2: usbfs: usb_submit_urb returned -28 Jan 15 23:34:27 Tower kernel: usb 2-1.3.2: usbfs: usb_submit_urb returned -28 Jan 15 23:34:27 Tower kernel: usb 2-1.3.2: usbfs: usb_submit_urb returned -28 Jan 15 23:34:27 Tower kernel: usb 2-1.3.2: usbfs: usb_submit_urb returned -28 Jan 15 23:34:27 Tower kernel: usb 2-1.3.2: usbfs: usb_submit_urb returned -28 Jan 15 23:34:27 Tower kernel: usb 2-1.3.2: usbfs: usb_submit_urb returned -28 Jan 15 23:34:27 Tower kernel: usb 2-1.3.2: usbfs: usb_submit_urb returned -28 Jan 15 23:34:27 Tower kernel: usb 2-1.3.2: usbfs: usb_submit_urb returned -28 Jan 15 23:34:27 Tower kernel: usb 2-1.3.2: usbfs: usb_submit_urb returned -28 Jan 15 23:34:27 Tower kernel: usb 2-1.3.2: usbfs: usb_submit_urb returned -28 Jan 15 23:34:27 Tower kernel: usb 2-1.3.2: usbfs: usb_submit_urb returned -28 Jan 15 23:34:27 Tower kernel: usb 2-1.3.2: usbfs: usb_submit_urb returned -28 Jan 15 23:34:27 Tower kernel: usb 2-1.3.2: usbfs: usb_submit_urb returned -28 Jan 15 23:34:27 Tower kernel: usb 2-1.3.2: usbfs: usb_submit_urb returned -28 The device appears to work correctly in the VM, although some issues have arose. VM's are unable to reboot (the VM just shuts down), and they randomly stop running. I have not attempted to pass through an entire controller, since I have only 1 at the moment. Any suggestions? tower-diagnostics-20170117-1035.zip
-
Just installed it and added some movies. Adding a large collection of movies is tedious as you have to approve each movie. Currently I am unable to use it as I can't get jackett to work as a provider.
-
Maybe http://greenleaf-technology.com
-
I was having the same issues as others. I just updated to the latest version and it find my server immediately. Great job.
-
Install the Plex app. When you connect to the VM using the cast function, you will have an option to "Open Remote". Personally, I passed through a ir receiver.
-
not started yet, still finishing off some work to do with base image update, aur helper and zombie reaping issues, but i should be able to take a look at it this week. Good progress with this guys, should have something for you to look at late tonight/tomorrow evening. Give it 30 mins, still building All done, please edit your existing container and add in a port and define as container port number 3000 (host port can we whatever you want). You will then need to add in an variable, key should be "ENABLE_FLOOD" value should be "yes" to enable. It's not working for me either. 2016-11-16 04:42:07,882 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47390023970184 for <Subprocess at 47390023486712 with name flood-script in state RUNNING> (stdout)> 2016-11-16 04:42:07,882 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 47390023968168 for <Subprocess at 47390023486712 with name flood-script in state RUNNING> (stderr)> 2016-11-16 04:42:07,882 INFO exited: flood-script (exit status 0; expected) have you added in the port and the variable?, otherwise it will default to disabled. For some reason I had to delete the container and download it again. Flood is loading now. THANKS!
-
not started yet, still finishing off some work to do with base image update, aur helper and zombie reaping issues, but i should be able to take a look at it this week. Good progress with this guys, should have something for you to look at late tonight/tomorrow evening. Give it 30 mins, still building All done, please edit your existing container and add in a port and define as container port number 3000 (host port can we whatever you want). You will then need to add in an variable, key should be "ENABLE_FLOOD" value should be "yes" to enable. It's not working for me either. 2016-11-16 04:42:07,882 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47390023970184 for <Subprocess at 47390023486712 with name flood-script in state RUNNING> (stdout)> 2016-11-16 04:42:07,882 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 47390023968168 for <Subprocess at 47390023486712 with name flood-script in state RUNNING> (stderr)> 2016-11-16 04:42:07,882 INFO exited: flood-script (exit status 0; expected)