geekllem Posted March 9, 2016 #1 Posted March 9, 2016 Hola a todos, os explico mi problema a ver si alguien me puede ayudar. Tengo un Buffalo Terastation TS58000D. Al cual le he puesto el XPEnoboot DS3615xs5.2-5644.5 y el ultimo software disponible: DSM_5.2-5644 Update-5. Mi problema es que el NAS es muy ruidoso y veo que el ventilador no para de funcionar. Cuando utilizaba el firmware original de Buffalo no hacia nada de ruido. Dentro del Panel de control, en el apartado Hardware y alimentacion, hay una opcion que pone: Modo de velocidad del ventilador (fan speed mode), pero no puedo seleccionar ningun valor, esta vacia. He probado varias cosas: 1) Archivo scemd.xml Leyendo varios foros, veo que este es el archivo que en teoria controla el tema del ventilador. Lo he editado para ver que valores hay, pero lo que mas me sorprende es que hay diferentes opciones para cada hardaware (hw_version=Synology-DX5, Synology-DX510, Synology-DX1211, Synology-RX1211rp, etc), pero no esta la opcion que instala el Xpenoboot DS3615. He editado el fichero y copiando los valores de otro hardware he añadido estas versiones: hw_version=Synology-DS3615xs hw_version=Synology-DS3615xs-j hw_version=Synology-DS-3615xs Pero no ha funcionado, sigue haciendo ruido y no se para. La edicion de este archivo la he hecho en: /usr/syno/etc/scemd.xml y /usr/syno/etc.defaults/scemd.xml Puedo entender que el menu del control panel aparezca vacio, ya que no tiene valores de configuracion. Alguna idea? 2) He revisado la BIOS al arrancar el NAS, pero no hay ninguna opcion configurable del ventilador. Es una bios de Aptio American Megatrends, version 2.14.1219 3) He seguido lo explicado de este post: viewtopic.php?f=2&t=2565 instalado el mktemp, el lm-sensors etc..etc.. pero nada de nada. sigue haciendo ruido... Bueno despues de este rollo de mensaje, felicitar al que haya llegado hasta el final.. y a ver si alguien puede ayudarme. Muchas gracias de antemano. Quote
geekllem Posted May 15, 2016 Author #2 Posted May 15, 2016 Al final lo he resuelto con la tercera opcion... me habia saltado algun paso... Este post es la clave... viewtopic.php?f=2&t=2565 basicamente: instalamos bootstrap (para poder usar ipkg) mkdir /volume1/@tmp cd /volume1/@tmp wget http://ipkg.nslu2-linux.org/feeds/optware/syno-i686/cross/unstable/syno-i686-bootstrap_1.2-7_i686.xsh chmod +x syno-i686-bootstrap_1.2-7_i686.xsh sh syno-i686-bootstrap_1.2-7_i686.xsh Actualizamos los paquetes ipkg update ipkg upgrade tambien hay que instalar perl ipkg install perl y bash ipkg install bash Hay que añadir este texto al final del archivo /root/.profile if [[ -x /opt/bin/bash ]]; then exec /opt/bin/bash fi En el mismo archivo .profile hay que añadir # a dos lineas. #PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin:/usr/local/sbin:/usr/local/bin #export PATH Se instalan los paquetes necesarios ipkg install mktemp ipkg install lm-sensors Creamos un script de arranque S99fancontrol.sh en /usr/syno/etc/rc.d/ #!/bin/bash # Use the same head in fancontrol script # # S99fancontrol.sh - startup script for fancontrol # # This goes in /usr/syno/etc/rc.d and gets run at boot-time. FANCONTROL=/opt/sbin/fancontrol case "$1" in start) if [ -x "$FANCONTROL" ] ; then echo "start fancontrol" $FANCONTROL & fi ;; stop) echo "stop fancontrol" kill -TERM `cat /var/run/fancontrol.pid` > /dev/null 2>&1 logger -p daemon.error "$0 stop fancontrol" sleep 1 ;; *) echo "usage: $0 { start | stop }" >&2 exit 1 ;; esac ponemos permisos: chmod 755 /usr/syno/etc/rc.d/S99fancontrol.sh ahora probamos los sensores: sensors me sale lo siguiente: coretemp-isa-0000 Adapter: ISA adapter Core 0: +55.0°C (crit = +100.0°C) Core 1: +57.0°C (crit = +100.0°C) it8721-isa-0a10 Adapter: ISA adapter in0: +3.02 V (min = +1.34 V, max = +0.79 V) ALARM in1: +2.83 V (min = +2.93 V, max = +0.92 V) ALARM in2: +1.97 V (min = +1.54 V, max = +2.36 V) +3.3V: +3.26 V (min = +2.30 V, max = +3.67 V) in4: +1.20 V (min = +2.23 V, max = +1.13 V) ALARM in5: +2.22 V (min = +2.76 V, max = +0.74 V) ALARM in6: +1.44 V (min = +1.46 V, max = +0.78 V) ALARM 3VSB: +3.26 V (min = +1.66 V, max = +3.89 V) Vbat: +2.88 V fan1: 2064 RPM (min = 108 RPM) fan2: 2045 RPM (min = 10 RPM) fan3: 0 RPM (min = 19 RPM) fan4: 0 RPM (min = -1 RPM) temp1: -70.0°C (low = -104.0°C, high = -50.0°C) sensor = thermal diode temp2: -70.0°C (low = +51.0°C, high = +0.0°C) sensor = thermal diode temp3: +39.0°C (low = -110.0°C, high = -95.0°C) ALARM sensor = thermal diode intrusion0: ALARM tengo 2 ventiladores y voy a usar el sensor de temperatura 3. Si el comando sensors no os da informacion, probar con el siguiente parametro para detectar que sensores teneis: sensors-detect en mi caso sale: # sensors-detect revision 5946 (2011-03-23 11:54:44 +0100) # System: Buffalo TeraStation # Board: USI SUGI 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 Intel digital thermal sensor... Success! (driver `coretemp') Intel AMB FB-DIMM 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'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... Yes Found `ITE IT8721F/IT8758E Super IO Sensors' Success! (address 0xa10, driver `it87') Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor'... 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 # DMI data unavailable, please consider installing dmidecode 2.7 # or later for better results. 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): YES 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): YES Using driver `i2c-i801' for device 0000:00:1f.3: Intel ICH10 modprobe: chdir(3.10.35): No such file or directory Failed to load module i2c-i801. Next adapter: ITE 9135(9006) Generic (i2c-0) Do you want to scan it? (YES/no/selectively): YES Adapter cannot be probed, skipping. 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 `it87': * ISA bus, address 0xa10 Chip `ITE IT8721F/IT8758E Super IO Sensors' (confidence: 9) Do you want to overwrite /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. Seguimos... vamos a crear los archivo de configuracion: sensors -s y ahora creamos: /etc/fancontrol pwmconfig si nos dice: /bin/sh: pwmconfig: not found probemos asi: bash pwmconfig si ahora funciona es que tenemos mal puesto las cabeceras ... Cabecera de /usr/syno/etc/rc.d/S99fancontrol.sh: #!/bin/sh y de /opt/sbin/fancontrol y /opt/sbin/pwmconfig: #!/opt/sbin/bash el pwmconfig creara un archivo parecido a este: aqui en mi caso, controlo los ventiladores con el sensor 3 de temperatura. y la configuracion esta creada para controlar 2 ventiladores el archivo esta en: /etc/fancontrol # Configuration file generated by pwmconfig, changes will be lost INTERVAL=2 DEVPATH=hwmon0= hwmon1= DEVNAME=hwmon0=coretemp hwmon1=it8721 FCTEMPS=hwmon1/device/pwm1=hwmon1/device/temp3_input hwmon1/device/pwm2=hwmon1/device/temp3_input FCFANS= hwmon1/device/pwm1=hwmon1/device/fan1_input hwmon1/device/pwm2=hwmon1/device/fan2_input MINTEMP=hwmon1/device/pwm1=20 hwmon1/device/pwm2=20 MAXTEMP=hwmon1/device/pwm1=60 hwmon1/device/pwm2=60 MINSTART=hwmon1/device/pwm1=8 hwmon1/device/pwm2=8 MINSTOP=hwmon1/device/pwm1=10 hwmon1/device/pwm2=10 MINPWM=hwmon1/device/pwm1=10 hwmon1/device/pwm2=10 MAXPWM=hwmon1/device/pwm1=165 hwmon1/device/pwm2=165 Reiniciamos y listo... Quote
C0mec0c0s Posted July 5, 2021 #3 Posted July 5, 2021 Muchísimas gracias! Voy a probarlo porque tengo el mismo problema que tu, espero que funcione porque te has dado un buen curre. Saludos! Quote
C0mec0c0s Posted July 6, 2021 #4 Posted July 6, 2021 Genial, me ha funcionado todo perfectamente, ya puedo controlar los ventiladores desde DSM. Muchas gracias!! Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.