MrGrumpie

Sorry I don't get that. I can see the server if I put in \\tower in my browser or input the IP address. Windows won't let me add a network share though...

Anyone?

Yes, the shares are all set to export with puiblic security. I'm stumped, there's no reason I can see why I can't add a network share, I can navigate perfectly to it from the web browser.

Hi all, hoping someone can help with what seems like a minor issue. I've just reinstalled windows 11. the server is working fine on my network, can watch movies etc, but in windows whilst I can navigate to the gui via the web browser, I can't map a network drive. Tower shows in Network on my PC, but when I double click it I get the following error message: \\TOWER is not accessible. The network address is invalid. Which I don't understand...as it clearly is. I have network set to Private and the network discovery + file & printer sharing turned to "on". Any ideas?

Hi all, I have a Terramaster F5-221 server running unraid, and I can't get fan control to work. Basically my fans have to be on all the time ("Full on" in bios" otherwise they are completely off regardless of temperatures. (other options in BIOS are "automatic" and "PWM manually"). I've installed PERL, dynamix fan control and dynamic system temp. In fan control is disabled and there is no fan controller detected. I've run sensors-detect from the console and this is what I get: root@Tower:~# sensors_detect -bash: sensors_detect: command not found root@Tower:~# sensors-detect # sensors-detect version 3.6.0 # System: retsamarret 000-F5221-FBA002-0001 [Default string] # Board: retsamarret Default string # Kernel: 4.19.107-Unraid x86_64 # Processor: Intel(R) Celeron(R) CPU J3355 @ 2.00GHz (6/92/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): YES 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 17h thermal sensors... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Hygon Family 18h thermal 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): YES 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 `ITE IT8613E Super IO Sensors' Success! (address 0xa20, driver `to-be-written') 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): YES 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): 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): YES Using driver `i2c-i801' for device 0000:00:1f.1: Broxton (SOC) Module i2c-dev loaded successfully. Next adapter: SMBus I801 adapter at f040 (i2c-0) Do you want to scan it? (yes/NO/selectively): 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) Driver `to-be-written': * ISA bus, address 0xa20 Chip `ITE IT8613E Super IO Sensors' (confidence: 9) Note: there is no driver for ITE IT8613E Super IO Sensors yet. Check https://hwmon.wiki.kernel.org/device_support_status for updates. Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): YES Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors for initialization at boot time. You should now start the lm_sensors service to load the required kernel modules. Unloading i2c-dev... OK root@Tower:~# Help! The fan noise is driving me up the wall now as the server is in my home office.

Hi all, I have a Terramaster F5-221 server running unraid, and I can't get fan control to work. Basically my fans have to be on all the time ("Full on" in bios" otherwise they are completely off regardless of temperatures. (other options in BIOS are "automatic" and "PWM manually"). I've installed PERL, dynamix fan control and dynamic system temp. In fan control is disabled and there is no fan controller detected. I've run sensors-detect from the console and this is what I get: root@Tower:~# sensors_detect -bash: sensors_detect: command not found root@Tower:~# sensors-detect # sensors-detect version 3.6.0 # System: retsamarret 000-F5221-FBA002-0001 [Default string] # Board: retsamarret Default string # Kernel: 4.19.107-Unraid x86_64 # Processor: Intel(R) Celeron(R) CPU J3355 @ 2.00GHz (6/92/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): YES 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 17h thermal sensors... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Hygon Family 18h thermal 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): YES 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 `ITE IT8613E Super IO Sensors' Success! (address 0xa20, driver `to-be-written') 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): YES 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): 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): YES Using driver `i2c-i801' for device 0000:00:1f.1: Broxton (SOC) Module i2c-dev loaded successfully. Next adapter: SMBus I801 adapter at f040 (i2c-0) Do you want to scan it? (yes/NO/selectively): 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) Driver `to-be-written': * ISA bus, address 0xa20 Chip `ITE IT8613E Super IO Sensors' (confidence: 9) Note: there is no driver for ITE IT8613E Super IO Sensors yet. Check https://hwmon.wiki.kernel.org/device_support_status for updates. Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): YES Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors for initialization at boot time. You should now start the lm_sensors service to load the required kernel modules. Unloading i2c-dev... OK root@Tower:~# Help! The fan noise is driving me up the wall now as the server is in my home office.

Weird....put my server back together and it's working now....

Hi, diagnostics file attached. I've noticed a couple of other things as well: When I reboot, the server always boots the first time into the BIOS. The boot settings have the USD drive as the bootable option, when I exit and restart from the bios (without making any changes) the server usually boots into unraid - I don't get this behaviour? Also, the server boots at 1pm every day when it's switched off....have I messed up a setting somewhere? Finally, re: the main issue around connectivity, during the day I often get alerts on my Mesh network that Tower has joined the network, and 5 minutes (or half an hour) later, I get a message to say it's disconnected. This will happen repeatedly, sometimes with minutes between connecting and disconnecting. My initial thought was that the network adaptor has failed, but surely there would be no connection at all with the network if this were the case? tower-diagnostics-20210719-1828.zip

Anyone?

I'm a little baffled, so wondering if anyone has any ideas. Just moved house, set up my new network. Tower is hard wired to my router. Was working fine this morning, but I shut down my server earlier. When I re-booted the server, whilst it looks to be running fine on the local monitor, I can't access the shares or the tower gui from the network. I've rebooted the server several times, also rebooted the router, bypassed a network switch etc. My mesh network (Deco) can see Tower when it comes online, but otherwise I can't see it anywhere or access anything. I also can't see Tower in "network" on my windows 10 PC (how do I get the syslog without removing the USB drive from my server and inserting it into my PC?) Thanks Matt

Hi all Just wondering, for those of you that have full tower cases, what SATA cable lengths are you using? Thanks Matt