FlamongOle

Community Developer
  • Posts

    533
  • Joined

  • Last visited

Everything posted by FlamongOle

  1. 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.
  2. 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.
  3. 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.
  4. Looks like it resolved after a reboot, dunno why or what happened there.
  5. 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.
  6. 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 🥳
  7. 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.
  8. 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.
  9. 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 ❤️
  10. 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!
  11. 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.
  12. 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
  13. 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.
  14. 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.
  15. 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..
  16. I would love this to be fixed as well. Proton is about the only provider I wanna use these days.
  17. TSV stands for Tab Separated Value. TSV file is a flat file, which uses the Tab character to delimit data and reports one time-series per line. CSV stands for Comma Separated Value. CSV file is a flat file, which uses the comma (,) character to delimit data and reports one observation per line. https://wikis.ec.europa.eu/display/EUROSTATHELP/Which+are+the+available+formats#:~:text=TSV stands for Tab Separated,reports one observation per line. So: yes, it is TSV
  18. Update 2024.02.23b Commit #287 - BUG: Setups without "Disk Utilities" could not see "Disk Location", added an extra page file containing the required contents.
  19. I'm seeing what's going on now. I thought "Disk Utilities" was a default Unraid section, but it was created by "Pre-clear" plugin. You can still access the plugin via "Plugins", then I'll sort something out soon-ish.
  20. Both of my servers shows up in Tools -> Disk Utilities. Reboots will "never" be required
  21. Hm, I experienced an odd behavior. Not sure what it was as it didn't provide any info/errors in the logs I could retrieve. The pages just stopped loading and Unraid was blank after the menu. It has happened a few times occasionally, but disappeared by itself somehow. Today I just tried to manually delete one plugin after the other, and once I manually deleted "community.applications" from "/usr/local/emhttp/plugins" Unraid webpages worked again. I can't reproduce the problem as deleting the plugin (after the manual deletion), and reinstalling it solved the problem. Maybe a database glitch or some other background updates? If this happens again, where can I fetch the log manually? I can only access the server via the terminal.
  22. Update 2024.02.23 Commit #285 - IMPROVEMENT: Moved the plugin to "Tools" instead of "Settings" as it makes more sense. Renamed "Force Scan All" to "Force Update All" and added "Update Active" button to update active (spinning) devices only. Updated the output format of update buttons and CLI. Commit #284 - BUG: Cache size from commit #277 caused drives to spin up, moved the check to the correct location so it won't spin up devices unless a "Force Update All" has been executed. If you have already used the "removed date", the dates have been overwritten by the "current date" during a "Force Update All". If all the dates are recent and you want to delete them, run this command to reset the changes. It won't affect anything regardless, just for optics: sqlite3 /boot/config/plugins/disklocation/disklocation.sqlite -cmd "UPDATE disks SET removed='' WHERE status='r'" ".quit"
  23. Yes you are right, it will be fixed soon. It was added in the wrong section of the script.