Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by olehj

  1. Update 2020.09.24 Commit #156 - IMPROVEMENT: Changed how the devices are displayed in the dashboard, devices and tray allocations. Should now align itself automagically where it fits best.
  2. Update 2020.09.09 Commit #152 - FEATURE: Added an option to start tray count from 0 or 1. Commit #151 - IMPROVEMENT: Adjusted the design to fit to the default Unraid scheme better. Commit #150 - FEATURE: Added shortcut for Tools and Settings page as people were confused and couldn't find the pages. Commit #149 - IMPROVEMENT: Removed disk status from Dashboard widget as it was rather faulty anyway.
  3. Sorry for a very late answer, but I realize this won't be so easy to do as there's data that needs to be generated per drive etc. for it to be stored in the database, even for historical purpose. Remember, my plugin does not include "First Install", "Recent Install" or "Last Seen" It requires the previous device nodes like "sdX" and LUN - they all can contain bogus info, or if you remember it all you can of course type them in. Else it must have a unique HASH per device, which consists of "model_name"+"smart_serialnumber" in SHA256 (no leading or trailing spaces, or newlines): Note: the most important thing is that they have a unique HASH, but you should never include them in the plugin then at a later point. If you go with accuracy, please bear in mind that "Family name" should -not- be included like "Seagate IronWolf" and "Western Digial Red", but the "Model name" like "ST8000VN0022-*" and "WDC WD30EFRX-*" echo -n "<model name><serial number>" | sha256sum You can then copy and backup before you open the SQLite database: cp /boot/config/plugins/disklocation/disklocation.sqlite /boot/config/plugins/disklocation/disklocation.bak sqlite3 /boot/config/plugins/disklocation/disklocation.sqlite inside SQLite, you have to type in this per device you want to add: INSERT INTO disks(device,luname,model_family,model_name,smart_serialnumber,smart_capacity,smart_powerontime,smart_loadcycle,status,purchased,comment,hash) VALUES('sdx','4000ee42314ff43','Western Digital Red', 'WDC WD30EFRX-XXXX', 'WD-WCCF00', '3000000000', '8008', '1337', 'r', '2019-12-31', 'Test disk', '7164c219729d0483dd6f053a6ee1553b9579ad4f2f3a6cfdc68716ede3ac92eb'); capacity = bytes status = 'r' // removed date = ISO format YYYY-MM-DD I can recommend to create a notepad list of "INSERT" commands before injecting them all into the database. Quit database with: .quit Good luck.
  4. I'll look into it in winter sometime.. just too hot and busy at work at the moment to bother implementing anything at all. Project still alive though... ish.
  5. 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.
  6. 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.
  7. 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.
  8. 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.
  9. 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; }
  10. No, it will only use ISO-format and I will never change that as it is boring to convert dates 😛
  11. 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.
  12. 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.
  13. Ye, the settings was moved to a "sub-plugin" to keep things separate and cleaner not too long ago.
  14. 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
  15. I might add that later, right now Im busy doing nothing and play left 4 dead 2
  16. Did you go under "Settings" and go on "Disk Location" from there? These tabs exists under "Tools" only
  17. Check if any of the drives have a "FAIL" SMART status. The "Information" tab should point it to the related drive as well.
  18. Update 2020.03.30 Commit #145 - BUG: Wrong checksum for disklocation.sh cronjob script.
  19. I can't seem to find anything wrong here. Can you verify that the "/boot/config/plugins/disklocation/disklocation.sqlite" exists at all after installation? And that for some reason this is not mounted as read-only for whatever reason. You can try the new version which fixes another issue as described in the next post:
  20. Try to delete the entire plugin and reinstall it, looks like something went wrong during download. Maybe you have to delete the database also under /boot/config/plugins/disklocation/disklocation.sqlite if the "Settings -> Disk Location -> System" does not exists or shows any database
  21. Update 2020.03.18 Not really anything new, but now licensed under GNU GPL version 3.
  22. Hi The screenshots are outdated, and the information was given in the forum at some point. Though I will update the first post later. The plugin is divided into two sections: Tools -> Disk Location: This is the visible and configured section of your system Settings -> Disk Location: This is where you configure your system. "Force Scan All" button under "Tray Allocations" will help solve most of the problems.
  23. Update 2020.03.06 Commit #142 - IMPROVEMENT: Differ between SATA SSD, NVMe, and rotational devices. Commit #141 - MINOR ISSUE: Checking for SSD only if rotation rate is not reported, some drives should show rotation rates again (ex. Toshiba drives). "Force Scan All" might be needed to update all the devices. @S80_UK fixed.. probably.
  24. Update 2020.03.04 Commit #139 - FEATURE: Added the ability to turn off scanning of device during a plugin update. If it's disabled it will rely on manual updates (Force Scan All) and S.M.A.R.T update schedules. (This will make updates and reboots faster though) Commit #138 - FEATURE: Added possibility to adjust the size of the preview/dashboard layout. @CorneliousJD something for you 😛