Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

21 Good

About olehj

  • Rank
    Advanced Member
  • Birthday June 3


  • Gender
  • URL
  • Location

Recent Profile Visitors

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

  1. It should be displayed under both for different purpose. The plugin is only tested on stable releases (current: 6.8.3). Try to reinstall, I see no reason why this shouldn't work.
  2. I have run unraid with this setting to "No" with cache enabled since January 3rd, and it works. But yes, Unraid documentation is pretty appalling. But using the "Help" function at the "Global Share Settings" would give you some hints about what happens. From the help function: Soooo, I would say: just try. Doubt you'll loose any real functionality.
  3. Shouldn't care about SAS vs SATA drives, it's rather the HBA/Raid card. There's several posts here about these issues and howto debug it.
  4. No problem. Even "Unassigned devices" plugin doesn't use the same scheme of things (they still use PNG images). Rather blame Unraid for insanely poor guidelines and documentation for plugins.
  5. Heh, does it really matter though? It mainly uses the scheme from Unraid itself, just that I don't see Unraid actually uses "green-blink" as a blinking green LED 😛 Not having any plan at the moment to change that though.. unless the majority start requesting it. I try to avoid any more configurations and options than it currently has to keep it somewhat simpler. Best thing you can do so far is to add your own CSS in your browser (if it supports it, maybe via addon): .green-blink { color: lightgray; animation: none; animation-timing-function: unset; font-size: 8pt; cursor: help; }
  6. No, it will only use ISO-format and I will never change that as it is boring to convert dates 😛
  7. If you use unassigned devices, you must use the internal plugin dates - I think that was some "bugs" with Unraid, or the incompatibility with Unassigned devices. I know I had similar problem earlier, and that's the reason I included that in the plugin as well. If you use Unraid array dates, be sure to NOT use the plugin for the dates, but set under each device where you read the SMART data. Things entered here will override what's stored in the database for the plugin. Also make sure that all the drives are recognized as different drives, model name and serial number should be present and the last one unique.
  8. Most likely it bugged out and created two or more cronjob files for the same task, I did experience this myself, but not sure why yet. What you can try: Press "SAVE" while it is chosen as "Disabled" before you choose anything else. It might fix it. Reinstall the plugin, do wait for it to complete - it might take a while depending on how many drives you have and if "Disk Location plugin on update scan" is "on". This can be turned off for faster installation and no scanning. Manual way: Check if the files exists in /etc/cron.* type in terminal: ls -la /etc/cron.*/disklocation.sh and delete them manually.
  9. Ye, the settings was moved to a "sub-plugin" to keep things separate and cleaner not too long ago.
  10. Yes, it can be done manually, save your data and I provide you with some SQL insertions later when I bother It is manual, and eventually have to be done everytime if you delete the database. So keep a backup after you added them all. I provide the details later, but as I said earlier in the last post.. Im busy doing nothing and playing left 4 dead 2 at the moment 😛 I just need a coding break, but will support this further later
  11. I might add that later, right now Im busy doing nothing and play left 4 dead 2
  12. Did you go under "Settings" and go on "Disk Location" from there? These tabs exists under "Tools" only
  13. Check if any of the drives have a "FAIL" SMART status. The "Information" tab should point it to the related drive as well.
  14. Update 2020.03.30 Commit #145 - BUG: Wrong checksum for disklocation.sh cronjob script.