FlamongOle

Community Developer
  • Posts

    542
  • Joined

  • Last visited

Everything posted by FlamongOle

  1. Currently no. Your observation is correct. For now you can still increase the global to have it like "worst case scenario" if it bothers you. I might look into Unraids settings and use those directly at a alter point.
  2. Just to add some more here, if it's under ZFS filesystem, it won't see it as it uses info from the zpool status. I must be under Unraid array.
  3. Should be no change with that. Idle is the same as active, disk spinning. Standby is spun down. It won't show instantly if it's spun up or down as it might take up to 5 minutes to gather new data. And that is a recent intended change. This plugin works semi-independent of Unraid disk statuses.
  4. Update 2024.03.22 Commit #307 - MINOR: Just a minor cleanup in the javascript handling and code of the Locate script. Added also a check if the device is assigned or unassigned so that the Locate works if there's unassigned devices in the list, which is kind of the point. Thanks to @warwolf7 who patiently explained the situation well enough for me to finally get the problem
  5. Aha, Ill have another look tomorrow or so
  6. I tried both, and things around it, but whatever I did, it would not start the locate script, nor the blinking of the disk visualization. Next release will revert the "-1" change, as it wont accept "Stop" click on the last device. Also cleaned up where the script was loaded twice in different positions. But it won't change your error code, which I don't seem to get myself. For curiosity, which browser do you use? It works without problem on Chrome, Vivaldi, Firefox for me.
  7. Update 2024.03.21b b) Fixed a minor issue when fixing #309 below. Commit #309 - BUG: If the disklocation.conf wasn't created (which is expected in some cases), the recent install scripts would fail. Now it will check if that file exists before it tries to pull out information from it, otherwise use default location of the database. Commit #307 - ISSUE: Yet again changed a bit of the javascript based upon information from warwolf7 (I hate javascript). This should fix the issues during boot of the server, did not know it would stall the entire server if a plugin install would fail. However, deleting the "disklocation" folder should almost never be necessary and will also delete the database and backups created. Deleting the .plg file would be enough in this case. You can always restore them from an Unraid backup, if you have, you should have... The javascript change is minor and I could not get @warwolf7 line working, so instead did a simple "-1" in the loop to skip the empty array. I hate javascript.
  8. Update 2024.03.20 Commit #307 - ISSUE: Cleaned up the javascript for the Locate functions, should hopefully work better overall now. Tested with Chromium based browsers and Firefox. @warwolf7 you can try now with this update. Hopefully, that'll fix it.
  9. Update 2024.03.19 Commit #305 - IMPROVEMENT: Skip updating devices during install if database version is matching the current database version. This will make the update faster for existing install, except if the database is getting an upgrade. Commit #304 - IMPROVEMENT: Prioritize using ZFS data over Unraid if it's not a traditional Unraid array. Only visible for the device and dashboard page (e.g. Device is ONLINE (ZFS) instead of ACTIVE (Unraid)). This will also use the "zfs pool" name, instead of "unraid type" which defaulted to "Cache"
  10. This plugin is rather dependent on Unraid as it uses variables from it. I guess the "easiest" solution is to run Unraid in a VM with all the drives accessible through it. There's no real arranging of these segments, it's all just automatically CSS aligned where the browser seem to make it fit.
  11. First of all, make sure you have the newest update. Otherwise, it's not guaranteed that it will work as it depends on the drive and backbones, HBA or Raid cards etc. Even the blinking time can vary as it depends on how quickly SMART responds from the drives/devices. It can be instant, so the LED won't even turn on or blink too fast to notice (dunno how these work). SSD/NVMe won't typically work.
  12. Can be caused by the database corruption that is now hopefully fixed. I can't look more into this unless I have more data on exactly when that happened. If new cases comes up with that issue, I will know if the new implementation works or not. But thanks for reporting it.
  13. Looks like it resolved after a reboot, dunno why or what happened there.
  14. Update 2024.03.10 Commit #302 - ISSUE: Some forms relied on header("Location") to redirect after submitting a form (it's slightly faster). In case there's an error somewhere (might be anywhere in the system printing out a header), use also html meta refresh as a backup to get back to the page.
  15. Update 2024.03.09 Commit #300 - ISSUE: Fixed an issue where the "Locate" button would not turn on the blinking feature on the drive LED. Also clean a bit up in the cronjob script. 300 commits and over 5 years of bugs... yey celebration 🥳
  16. Update 2024.03.08 Happy International Women's Day! 🥳 Commit #298 - Made sure to clean up temporary files during uninstall and reset the database lock file during an upgrade.
  17. No specific reason why that should happen.. but it should list device by device as before, then when that's done it will write into the database. Nothing that really changed a lot to not make this not work like before. If it's stuck for so long, take a look if the lock.db file exists in /tmp/disklocation/, if it does, delete it and check if the install continues. Might be that I should delete the temp lock file during upgrade, so I will add that now.
  18. Update 2024.03.07 Commit #296 - Added background blinking (blue) on a device during "Locate" click, if assigned. Commit #290 - Changed how the background task store the SMART input to the database, collect all info before writing it instead of writing it per device as found. Should probably not "brick" any servers out there GL;HF ❤️
  19. The "Apps" would use the same link, so no advantage over manual install in that regard in case you wonder. But both works Thanks for reporting back!
  20. Sorry, but I do have a life besides writing Unraid plugins I'm now correcting bugs on my laptop in a hotel directly on GitHub on work travel after work.
  21. Update 2024.03.06c <- make sure it says "c" and NOT "b" before updating. Commit #294 - BUG: Check for ZFS before executing functions based on it. (reported by @malaki86) Commit #293 - BUG: Deactivated the database lock as it seem to have caused some serious issues. #290 will be incomplete again. Please check if this helps the issue, I'm not home at the moment and can't test it myself. Sorry for the inconvenience etc. and so on Thanks for people who contribute and provide with proper information, wonderful to see people are using the plugin To some others, I would just recommend to read the license, especially §15-§17 😘 https://github.com/olehj/disklocation/blob/master/COPYING
  22. Update 2024.03.06 Commit #291 - MINOR: Some group names got swapped under selection forms are now fixed. Commit #290 - ISSUE: To prevent database corruption, a forced lock has been implemented during an update. This will also delay page loading if the updater runs in the background. If it will take more than 2 minutes, the lock file will automagically delete itself so it won't prevent Unraid to function normally. It can also be manually deleted under /tmp/disklocation/db.lock if required. Commit #289 - IMPROVEMENT: Made the plugin recognize multiple ZFS pools. Defaulting to Unraid status. Pool names are displayed as "Unraid info" if it exists. Also optimized the code a bit to respond faster. With the #290 fix, I suggest the users using "hourly" updates to consider using "daily" (or later/rarer) instead as it might interrupt your work too often if you are "using" Unraid GUI frequently.
  23. Might be, renaming or deleting the database will solve the problem and you might be able to restore an old backup if those were created (unless you deleted the entire folder in /boot. Why it happens, is another story yet to be discovered. One way to find out is to send me the database so I can have a look what happened or not, but it contains all the information from the drives, like full serial numbers etc.
  24. root@Odin:~# /usr/local/emhttp/plugins/user.scripts/startSchedule.php hourly bash: /usr/local/emhttp/plugins/user.scripts/startSchedule.php: Permission denied root@Odin:~# php /usr/local/emhttp/plugins/user.scripts/startSchedule.php hourly /usr/local/emhttp/plugins/user.scripts/backgroundScript.sh "/tmp/user.scripts/tmpScripts/dynu_updater_hourly/script" >/dev/null 2>&1/usr/local/emhttp/plugins/user.scripts/backgroundScript.sh "/tmp/user.scripts/tmpScripts/pfsense_firewall/script" >/dev/null 2>&1 Noticed that I got a permission error in the logs from the User Scripts plugin, it looks like Unraid does not accept the #!/usr/bin/php anymore. I had to add "php" in front of the startSchedule.php in the crontab file to make it work. Can someone test this, I wanna know if it's just my system or a bug/glitch..