jrfbal

Hello, I'm getting the same issue. I'm on Unraid 7.3.1. When I open the web UI I get the following error: 15:34:48 Scanning hard drives Lucee 6.1.1.75-SNAPSHOT Error (expression) Message can not set Element at position [0] Detail Index -1 out of bounds for length 1 Stacktrace The Error Occurred in /var/www/ScanControllers.cfm: line 818 called from /var/www/ScanControllers.cfm: line 799 Java Stacktrace lucee.runtime.exp.ExpressionException: can not set Element at position [0] at lucee.runtime.type.wrap.ListAsArray.setE(ListAsArray.java:268) at lucee.runtime.type.wrap.ListAsArray.set(ListAsArray.java:413) at lucee.runtime.type.wrap.ListAsArray.set(ListAsArray.java:418) at lucee.runtime.type.util.ArraySupport.set(ArraySupport.java:312) at lucee.runtime.util.VariableUtilImpl.set(VariableUtilImpl.java:433) at lucee.runtime.PageContextImpl.set(PageContextImpl.java:1724) at lucee.runtime.PageContextImpl.us(PageContextImpl.java:1291) at scancontrollers_cfm$cf.call_000077(/ScanControllers.cfm:818) at scancontrollers_cfm$cf.call(/ScanControllers.cfm:799) at lucee.runtime.PageContextImpl._doInclude(PageContextImpl.java:1046) at lucee.runtime.PageContextImpl._doInclude(PageContextImpl.java:940) at lucee.runtime.listener.ClassicAppListener._onRequest(ClassicAppListener.java:63) at lucee.runtime.listener.MixedAppListener.onRequest(MixedAppListener.java:42) at lucee.runtime.PageContextImpl.execute(PageContextImpl.java:2725) at lucee.runtime.PageContextImpl._execute(PageContextImpl.java:2712) at lucee.runtime.PageContextImpl.executeCFML(PageContextImpl.java:2683) at lucee.runtime.engine.Request.exe(Request.java:45) at lucee.runtime.engine.CFMLEngineImpl._service(CFMLEngineImpl.java:1160) at lucee.runtime.engine.CFMLEngineImpl.serviceCFML(CFMLEngineImpl.java:1117) at lucee.loader.engine.CFMLEngineWrapper.serviceCFML(CFMLEngineWrapper.java:97) at lucee.loader.servlet.CFMLServlet.service(CFMLServlet.java:42) at javax.servlet.http.HttpServlet.service(HttpServlet.java:623) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:199) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:168) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:168) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:482) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:130) at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:660) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93) at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:761) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:346) at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:383) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:936) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1791) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52) at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1190) at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63) at java.base/java.lang.Thread.run(Unknown Source)

Hello After extensive tests with a Windows installation and moving cables around, it stopped happening. Not really sure what was the cause but might have been a not well connected cable causing the PSU to drop power or something. It's been running fine for the past 5 days even after manual restarts. Thank you for the attention

Hello, I had this working on Unraid v6, but since NerdPack is no longer supported on v7, is there any other method? Thank you

Hello, I've been running Unraid since August 2024 without any problems, and started having a lot of issues when I updated the server on 11/01. The update went smoothly and the server was running fine for 24 hours, but after I rebooted the server on the 12th it became unusable. The server is always rebooting without any warning. I've noticed this because the server would not come back online after I've requested the reboot through the UI. When I connected the monitor, it was stuck on a loop where it would reboot at some point during the booting process (seems that it was triggered when the graphics would change to the high resolution mode. I've shut down the server, hard rebooted, and eventually came back up, but it would only stay up for 15 minutes until it happened the same behaviour. I've tested the RAM and it seemed fine. Both the motherboard and PSU were purchased in August, so I would be surprised if this is a hardware issue, but I can install Windows or other OS on a separate drive to stress test the server. I'm attaching the log files, and what I've noticed that there are some entries right before everything breaks: Unraid kernel: usb 1-11-port2: disabled by hub (EMI?), re-enabling... I've tried unplugging all the USB devices, and the server managed to stay up for almost two hours. I closed the case, rebooted and the server got stuck again in the same boot loop. What might be causing this issue? Can it be some change in Unraid v7 or is this hardware failure that happened at the same time as the update? Thank you for your help syslog-192.168.1.8.log unraid-diagnostics-20250113-2231.zip unraid-diagnostics-20250113-2218.zip unraid-diagnostics-20250113-2214.zip

Thanks for your input. I have left the computer in the Bios screen for half an hour and never seen any suspicious values, neither in Unraid without the drivers installed. I've opened an issue on github and I've seen some other issues with the same sensor (it8625e).

I just experienced a hard lock and I think it might be related to the drivers. Even through a monitor and keyboard I could not interact with the system. I've removed the drivers now. You can find attached the diagnostics after the system came back up. unraid-diagnostics-20240826-1104.zip

Hello, I've uninstalled autofan, rebooted, installed the ITE drivers and rebooted, and after some minutes I'm already getting wrong reads on the motherboard sensor (-30C), even though the value seemed correct when the system started (like 40C). Yesterday without the ITE drivers installed it seemed that the value was always something believable. I'm attaching the diagnostic files. Thank you for your help. unraid-diagnostics-20240826-0950.zip

Hello, I've recently installed Unraid for the first time and I'm having issues with the sensors and making Dynamix Auto Fan Control work reliably. Out of the box I just get temperature report for the motherboard and the CPU. I ran sensors-detect, and it identified: Found `ITE IT8625E Super IO Sensors' Success! (address 0xa20, driver `to-be-written') I've installed the ITE IT87 Driver and all looked great. The sensors showed up, I could define the fan speed according to the temperature, etc. The idea was to have the Motherboard control the CPU fan while Auto Fan Control would control the case fans near the hard drivers. And this was working. However, with no reason that I could find, sometimes the sensors would become totally wrong (the Motherboard would show temperature of -30C and I've had a shutdown due to "Unraid kernel: thermal thermal_zone0: acpitz: critical temperature reached, shutting down", even though I'm sure that the temperature was not reached and this sensor is not related to the ITE8625E Sensor), the fan speeds would show wrong values (like 70000rpm) for one of the fans, and most critical, sometimes the CPU fan (not controlled by Auto Fan Control) would stop spinning and show as 0 rpm while the CPU reached 100C. A reboot would not fix this and the only way would be to enter Bios, change the Fan setting to Manual, then back to auto and save the changes. I've uninstalled the drivers a few hours ago and so far none of these issues are happening (even though I currently don't have monitoring on the fan speeds or fan control), but at least the motherboard temperature is always showing correctly. Is this a known issue and is there any workaround for this? I currently cannot provide any logs since I removed the drivers, but if anyone is available to take a look into this I can redo the configuration and provide logs. Motherboard: Biostar B760M-SILVER CPU: i5-12600K Thank you