truckerCLOCK
-
Posts
33 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by truckerCLOCK
-
-
If you go to setting and go to v0.3.4. It works fine for me.
-
4
-
1
-
-
On 4/9/2021 at 3:28 AM, FreeMan said:
I started having issues as soon as I updated my server to 6.9, and assumed that was the problem because I hadn't yet updated my backup server and it continued to run just fine. Now I'm getting no results on either server even though the backup is still on 6.8.x and the primary is on 6.8.1.
@dmacias are you still active on this project? If not, I'll move on to something else. This has been a great "ping" to know the servers are still up, and I'll miss it if it's gone...
Also having issues since 6.9.1 update. If not supported anymore it will be sadly missed.
-
I know this is pretty much an unsupported plug in but I was wondering if anyone still uses it and if you've upgraded to 6.9.1 without any issues?
-
On 2/9/2020 at 10:01 PM, Deke The Geek said:
Whew, what a thread! Thanks to OP and all who post here, but I've been unable to resolve my issue, so here goes:
I own four (4) LSI branded 9201-16e HBAs, and have been using two of them for a couple of years without incident. I was able to flash them (~4 mins IIRC) to P20 firmware without incident. The other two have just been sitting on a shelf awaiting their time in the sun 🙂
So I got my FreeDOS USB ready and started down a path to hell I've been on for the past couple days LOL
sas2flsh -o -list output:
Adapter Selected is a LSI SAS: SAS2116_1(B1)
Controller is not operational. A firmware download is required.
Enter firmware file name or quit to exit:
When I offer the P20 fw file, I get:
Firmware Image has a Valid Checksum.
Firmware Image compatible with Controller.
Valid NVDATA Image found.
Valid Initialization Image verified.
Valid Bootloader Image verified.
Chip is in FAULT state. Attempting Host Boot...
ERROR: Firmware Host Boot failed !
Due to error remaining commands will not be executed.
Unable to process Commands.
Exiting SAS2Flash.
Attempts to execute the flash command directly (sas2flsh -o -f 9201-16E.BIN) gives same error message.
Attempts to wipe card (sas2flsh -o -e 6 or any other number for that matter) result in same
I've tried sas2flsh v7, v16, and v20.
megarec commands fail as this is an LSI branded card
Is there any hope for my cards? I have two like this... TIA
EDIT: FYI, I've also tried on two different systems, both of which are able to flash the other two cards
2nd EDIT: I've tried the above commands with v8, v9, v10, v11, v12, v13, v13-5, v14, v15, v16, v17, v18, v19, and v20, all freshly downloaded from LSI website today. It doesn't appear to be an issue with the wrong version or anything... unless there are tools I'm not using that can fix this I may have a couple of useless cards 😕Hello I was wondering if you found a solution to this problem? I'm thinking of switching to a 16i card but have read similar stories about the firmware updates.
-
Just wondering if this plug-in is still being supported or if everyone is moving to Wireguard?
-
STOP button is not working. Had a problem with one of my disks so I stopped the array. When I started it back up could not get Openvpn to connect.Had to do a reboot to get it to connect.
-
On 10/26/2019 at 5:01 AM, David Bott said:
@peter_sm Thanks for the thought of modifying the actual openvpn server file you want to use. Before I tried that I took a closer look at the connection log, via your plug-in, and did see this line...
Sat Oct 26 07:36:18 2019 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 198.18.0.1,dhcp-option DNS 198.18.0.2,rcvbuf 493216,sndbuf 493216,explicit-exit-notify 5,comp-lzo no,route-gateway 172.21.92.1,topology subnet,ping 20,ping-restart 40,ifconfig 172.21.92.25 255.255.254.0,peer-id 0,cipher AES-256-GCM'
...so it seems that ping and ping-restart are part of it yet does not seem to solve the issue. BTW... I did also try adding the lines to the file to different settings, but after stopping and starting the OPENVPN client again, the same values showed up in the log. So it does not seems to be part of that file. So not sure where these settings are being set from as it dies not seem to be the server.ovpn files.
I did happen to notice also that it reads...
Sat Oct 26 07:36:17 2019 OpenVPN 2.4.6 x86_64-slackware-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on May 7 2018
Sat Oct 26 07:36:17 2019 library versions: OpenSSL 1.1.1c 28 May 2019, LZO 2.10...wondering if i does not need to be updated? (It may be current for all I know.)
Otherwise the plug-in does just perfect for what I wanted. Something that puts my UnRAID internet traffic through a VPN and it does that. Even updates for docker files or plugins all use the VPN. But the issue is, once you loose internet for X amount of time, it will not redo the tunnel and your entire server does not have access to the Internet. (You can still reach it from inside the network of course.) The GUI also stops working. (Side note....At least on mine, when I choose to STOP the OpenVPN service the says Stopping but then the screen becomes empty from the UnRaid Menu bar down. You need to click on SETTINGS and the OPENVPN Client option again to go back in and see if it stopped. No biggie...but just a heads up.)
But the big thing is it not coming back up. Sometimes I may not notice for days and have things stacked up to come down.
If you may care to look into this, I am happy to test. If not, I understand as it has not been touched in some time but is really the open option I have found that does the server as a client in one easy to setup, understand, and use plug-in.
You also mentioned "keepalive what I know is a server function" ... Just don't seem to see a setting for that anywhere.
Thank you again.
I know this is from last year but was wondering if anyone has found a fix for this? As I am experiencing the same problems. The plugin not reconnecting and having to restart the array to get it properly work. Spectrum has been doing alot of maintance\upgrades in my area so internet has been reseting thruout the day.
-
On 8/29/2019 at 7:12 AM, Frank1940 said:
For anyone who has never ending problems with SMB and Window 10, If you are using WIN10 PRO (or above), you can use NFS instead of SMB. You will need to be somewhat comfortable in the use of the command line in Windows (called Command Prompt in WIN10). Note that this will require that you mount your NFS share(s) as a mapped drive(s) in Windows. If you want to minimize the number of mapped drives, I would suggest using /mnt/user0 as the mount point. The following article describes the steps that are necessary.
https://graspingtech.com/mount-nfs-share-windows-10/
I have not yet tried this but it seems fairly straight forward. Enabling the NFS services will add another command to the Windows shell-- mount which is used to setting up the mapped drive on your Windows computer. Note that in the instructions, it is setting up the anonymous user as root which could be a potential security risk.
Thank you. I've been looking at doing this. Getting tired of Windows and all the updates screwing up my SMB shares.
-
On 8/27/2019 at 12:02 PM, itfcjim said:
Hi all,
Have installed this plugin onto my Unraid server running a SuperMicro X8DTE-F motherboard. When I hit DETECT nothing seems to happen. Is there anything special I need to do?
Many thanks
Uninstall this plug in. It hasn't work for awhile and doesn't seem to be supported anymore. It's been months with no updates or replys.
-
3 hours ago, iilied said:
system temp does not detect motherboard's (prime x470-pro) sensors when pressed, and yes perl is installed via nerd pack. any idea why?
There is a problem with this plug in after the 6.7.2 update. It's been a couple of months with no fixes or updates. Consider sys temp/fan control plug in dead.
-
11 hours ago, xtrips said:
Hello.
Pressing Detect for Autofan has no effect. What are the conditions to be met for this to work?
There is a problem with the System temp plug in after OS update. Read thru post. Others are having the same problems.
-
......🦗🦗🦗
Ok guess these plugins aren't being supported anymore.
-
On 5/14/2019 at 4:39 AM, trurl said:
Did you try going to the Settings for System Temps and make sure the sensors were still selected?
Yup. How could they change? Update to 6.7.0. nothing changes, settings still the same. No array temps. Shows "not used". Revert back to 6.6.7. temps show back up. Works fine. Update again to 6.7.0. No array temps. Shows "not used". Checked Nerd pack for updates. I'd say it's a problem with the plug in and makes fan auto control not work.
-
On 5/4/2019 at 5:44 PM, bengele said:
Dear all,
im realy stuck in the Fan Speed Plugin.
PWM controller is not found and at the same time i dont find temps of the Harddrives that are connected to the Mainbaord.
The Most weird thing is that i can access the Temps over the Main:
I did run sensors-detect but it found a sensor on "ID 0x8686"
root@ben-server:/boot/config/plugins# sensors-detect # sensors-detect revision 6284 (2015-05-31 14:00:33 +0200) # System: Gigabyte Technology Co., Ltd. Z270P-D3 [Default string] # Board: Gigabyte Technology Co., Ltd. Z270P-D3-CF # Kernel: 4.18.20-unRAID x86_64 # Processor: Intel(R) Core(TM) i7-7700T CPU @ 2.90GHz (6/158/9) This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 16h thermal sensors... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Intel digital thermal sensor... Success! (driver `coretemp') Intel AMB FB-DIMM thermal sensor... No Intel 5500/5520/X58 thermal sensor... No VIA C7 thermal sensor... No VIA Nano thermal sensor... No Some Super I/O chips contain embedded sensors. We have to write to standard I/O ports to probe them. This is usually safe. Do you want to scan for Super I/O sensors? (YES/no): Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... Yes Found unknown chip with ID 0x8686 Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Some systems (mainly servers) implement IPMI, a set of common interfaces through which system health data may be retrieved, amongst other things. We first try to get the information from SMBIOS. If we don't find it there, we have to read from arbitrary I/O ports to probe for such interfaces. This is normally safe. Do you want to scan for IPMI interfaces? (YES/no): Probing for `IPMI BMC KCS' at 0xca0... No Probing for `IPMI BMC SMIC' at 0xca8... No Some hardware monitoring chips are accessible through the ISA I/O ports. We have to write to arbitrary I/O ports to probe them. This is usually safe though. Yes, you do have ISA I/O ports even if you do not have any ISA slots! Do you want to scan the ISA I/O ports? (YES/no): Probing for `National Semiconductor LM78' at 0x290... No Probing for `National Semiconductor LM79' at 0x290... No Probing for `Winbond W83781D' at 0x290... No Probing for `Winbond W83782D' at 0x290... No Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): Found unknown SMBus adapter 8086:a2a3 at 0000:00:1f.4. Sorry, no supported PCI bus adapters found. Module i2c-dev loaded successfully. Next adapter: SMBus I801 adapter at f040 (i2c-0) Do you want to scan it? (YES/no/selectively): Client found at address 0x50 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Probing for `EDID EEPROM'... No Client found at address 0x52 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `coretemp': * Chip `Intel digital thermal sensor' (confidence: 9) Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): no To load everything that is needed, add this to one of the system initialization scripts (e.g. /etc/rc.d/rc.local): #----cut here---- # Chip drivers modprobe coretemp /usr/bin/sensors -s #----cut here---- You really should try these commands right now to make sure everything is working properly. Monitoring programs won't work until the needed modules are loaded. Unloading i2c-dev... OKThe command:
modprobe it87 modprobe: ERROR: could not insert 'it87': No such deviceor:
modprobe it87 force_id=0x8686Did also not work...
Im not a linux pro so i hope for help.
The only thing that i got to work in System Temps is the CPU Core :
Hope for help
mfg Bengele
Did this happen after you updated to 6.7.0?
-
Just updated to 6.7.0. Not able to monitor array temps. Mb and CPU show up fine. Using the coretemp nct6775 drivers. Revert back to 6.6.7 everything works fine.
-
So cooling the heatsink more isn't going to help keep the chip cool.....hmmm.
-
Great idea but I took a simplier route. I just purchased 2 mini 24 vdc fans and glued them to the heatsinks.
-
After the last update it does not want to run. I start the test. It shows " Internet bandwidth test started " then Done. It does nothing.
-
Hello I just updated to the newest release and also updated config files. Everything seems to be running fine but after checking the logs it shows errors. Should I be concerned?
Tue Jan 3 21:07:25 2017 WARNING: file 'ta.key' is group or others accessible
Tue Jan 3 21:07:25 2017 WARNING: file '/boot/config/plugins/openvpnclient/password.txt' is group or others accessible
Tue Jan 3 21:07:25 2017 OpenVPN 2.4.0 x86_64-slackware-linux-gnu [sSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Dec 29 2016
Tue Jan 3 21:07:25 2017 library versions: OpenSSL 1.0.2j 26 Sep 2016, LZO 2.09
Tue Jan 3 21:07:25 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]
Tue Jan 3 21:07:25 2017 UDP link local: (not bound)
Tue Jan 3 21:07:25 2017 UDP link remote: [AF_INET]
Tue Jan 3 21:07:25 2017 TLS Error: cannot locate HMAC in incoming packet from [AF_INET]
Tue Jan 3 21:07:27 2017 TLS Error: cannot locate HMAC in incoming packet from [AF_INET]
Tue Jan 3 21:07:31 2017 TLS Error: cannot locate HMAC in incoming packet from [AF_INET]
-
DO NOT UPDATE WITH P20 firmware..... I just updated my card Monday to the P20 firmware. Big mistake. All drives showing errors. Like 77,400 and higher numbers. Ran multiple self tests to make sure my drives weren't dying and all test show good. Came across some info bout people having the same problem. Flashed back to P19. No errors.
Speedtest.net for unRAID 6.1+
in Plugin Support
Posted
I have tried that app. It sadly is not the same.