Community Developer
  • Posts

  • Joined

  • Last visited


Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Carpe_Diem's Achievements


Newbie (1/14)

  • Superstar Rare

Recent Badges



  1. Dejo aquí el script que creó onetx para tal efecto
  2. This is great, but... You just made obsolete my 2 weeks old video tutorial!!! XD I found the usermod workaround by myself, and posted it as part of my guide. No longer needed, it seems. Now seriously, thank you for your container. Lots of users from the Spanish community have started to use Borg recently thanks to your container. Keep on with your great work! 👏
  3. That solved the problem. Thanks! I have now realized that there are community themes inspired on infinity gems, i need to try them! 😍
  4. Suddenly, login themes stopped working. Might this be related to some broken links? I seem to be able to access the .css on my browser (ie and I get the .css without problems. Same with the imported url But when I run the script, I get the default login screen (yes, I hace DISABLE_THEME="false" in the script). What I can't understand is that the theme login screen was working flawlessly for months, and suddenly it works no more. It's related to some problem on my server? (running v6.9.2)
  5. Buenas a todos. Desde la comunidad de UnRAID ES hemos creado un canal de youtube para tener centralizados los tutoriales. Todos los tutoriales futuros se lanzarán en dicho canal. Esperamos que sea de utilidad para toda la comunidad 😁 😁
  6. Hi. As admin in several NAS communities, I've seen how more and more QNAP users are deciding to get rid of their QNAP units for several reasons. Some of them are switching to UnRAID and they want to use the same hardware they already have (their QNAP units). You can get UnRAID up and running in most QNAPs, no big deal, but the hwmon driver used by QNAP in their MOBO is not recognized in UnRAID, which lead to fans not being detected and thus, being unable to control fan speed and drive temperature. One of the QNAP users in Reddit developed this driver kernel module that works fine with most QNAP units. The problem is that compiling it in UnRAID is not possible (or at least I have not been able to), so you must use another Linux OS like Ubuntu, with same kernel version that current UnRAID release, and compile it, so rinse and repeat for each new kernel update. It also becomes a new binary, that is not integrated in the OS and cannot be used with already existing plugins, like Dynamix autofan. If this driver were to be compiled and included in future releases, It would increase the number of people switching to UnRAID. It should also require minimum work for UnRAID developers. So, how can we request this feature to be included? Thanks!
  7. Genial trabajo @Nelo3D Muchas gracias!
  8. Muchas felicidades Eugeni!!! Confianza más que merecida, por todo lo que estás haciendo por la comunidad
  9. Un saludo a todos de parte de la comunidad de UnRAID ES. Yo por mi parte intentaré ser un poco más activo por aquí, siempre que me lo permita mi tiempo 😁
  10. Since I tried performing a safe reboot (that means no plugins, no docker) and the issue still persist, if smartctl is to be blamed, then it must be an OS smartctl process (perhaps the temperature probe?). In any case, UnRaid should ignore those smartctl queries when counting for time without IO usage to spin down. The fact that the drives are not immediately awaken after spin down means that smartctl (or whatever process it is) does not really "keeps awake" the drives, but Unraid just fails to ignore those IO and keep counting time.
  11. Just to note: Autofan is not always the culprit. I have exactly this same behavior, and even after rebooting in safe mode (all plugins disabled), drives do not spin down. I also get 341B/s read metrics on all drives simultaneously, whick Unraid seems to register even when the drives are manually spinned down. I just reverted to 6.8.3 and this feature started working perfectly fine again.
  12. Can confirm, same behavior: Current setup is 3 HDD with no parity, + SSD cache. I have docker with telegraf working, and also Dynamix fan control, but they are NOT the issue. Drives refuse to scheduled spin down, even with docker disabled and plugins disabled (safe boot). When they are manually spinned down, they remain in that state until woke up. In Dashboard, all three disk show constant read activity of exactly 341B/s or 682B/s (same in all drives at same time), but this is a "fake" read, because dashboard still shows that read activity with drives manually spinned down, which is of course, impossible. It seems to me that this is a bug where unraid is getting fake read activity, and so, it does not automatically spin down drives. Docker/Grafana and plugins cannot be blamed, as problem persist with no plugins and docker disabled. This behavior was not present with 6.8.3 (automatic spin down worked perfectly fine)