• Content Count

  • Joined

  • Last visited

Everything posted by olehj

  1. That's entirely up to you, but Unraid is rather a continuous beta where versions doesn't really matter
  2. Rather create a common group for the 5*3.5" boxes. 5 columns and 3 rows and own group for the 2.5", guess that's the best you can do for now.
  3. Update 2021.03.03 Commit #161 - FEATURE: Formatting of the comment field has been added, read "Help" for more information under the "Tray Allocations" tab. @shEiD Commit #158 - BUG: NVME drives not detected with Unraid 6.9 because of changes in the output of lsscsi. From now on only Unraid 6.9 and above is supported. Older releases has to use the developer build without nvme support or previous Disk Location version. @Woutch @lovingHDTV
  4. This has been requested earlier, and there's no way I can make a layout that will match all the various builds out there. There's also no focus on removable media as this isn't really any intention of this plugin. In best case I might add some custom labeling on empty slots - someday.
  5. Can probably accept some easy formatting tools there for the future, but I am way too busy these days. So just stay tuned I guess 😛
  6. You do select a group ID as well? It requires both.
  7. It might be related. Anyway, a good place to start is "Force scan all" and if that does't work: delete the database and reinstall the plugin. And -wait- until the plugin says it's installed/done. It may take some time depending on how many drives it needs to check and wake up from standby.
  8. As said before, I do not support alpha/beta/rc versions. Mainly only the current stable (after I bother installing it myself obviously).
  9. That might be it, I'll have a look when Unraid 6.9 is stable
  10. Did you do a "Force Scan All"? Else I see no reason why it shouldn't work.
  11. Use "Purchased date" for that instead if you wanna adjust for warranty by the manufacturer date. Choose whatever makes it useful for you. Where I live, it's irrelevant what the manufacturer date is and what warranty they give as it's overruled by the laws here. Some others has to rely on the manufacturer date, so use that date instead of "purchase date". I won't add more as it will make the plugin itself more untidy 😛
  12. Problem is likely to be with "smartctl" not recognizing the drive. If "Force scan all" doesn't work, then only a new version will. Else not supporting non-stable Unraid releases.
  13. check if you have permission to write in that folder, else no idea
  14. Did you install the drives after the plugin? In case try to "Force scan all" to see if they get detected. Else they must be detected via "lsscsi -u -g" command and have SMART data output from "smartctl" command from the device detected by "lsscsi". If it's a new drive, it might need a newer version of smartctl, which comes with a new version of Unraid. Currently only "stable" is supported.
  15. Honestly don't care if you choose to use it or not, but I tried multiple browser in both Linux and Windows and different size settings without getting any results of what you show here. That the devices need to be scrolled to the side when viewing the "Device" tab is simply because it does -not- auto scale and uses fixed pixel size which you can configure yourself. It's not intended to be auto scaled, and it won't be either. The Dashboard is scaled by a set fraction (default divided by 10) of the regular sizes. Make sure to not use any custom CSS or browser extensions t
  16. Check if you don't have any extensions installed that messes up the layout. Haven't heard about this problem before, and I tested here with both Firefox, Chrome and Vivaldi. Try another browser for debugging. The sizes adjust well here for the Device tab, including the dashboard. I'm afraid I don't have a solution for you.
  17. What browser are you using? Not supporting anything else than Chrome and Firefox (and engines used by these). Also only support the latest Unraid stable release with the newest update of Disk Location. The size of the drives can be specified in the configuration, the width and height of the full size per array, and the divider for the small dashboard size(s).
  18. Then the other question is: did you type in the date manually by text? Or did you let the HTML5/web browser enter it for you by clicking the dates? The dates must be stored as ISO YYYY-MM-DD in the unraid variable. If somehow this got typed in manually, the database won't understand the input date.
  19. Next time, attach the screenshots directly to your post. And when using links, format it as such. Copypasta links are annoying. For the problem; did you "Force Scan All" after setting the dates? Do you see the dates under Settings -> Tray Allocations?
  20. As I said, avoid overrides. Create another group instead.
  21. Hard to say when I have no idea of how you want it to look like.. First of all, try "Help" function, by pressing... Help-button for Unraid. Other than that, the "override" use should be left alone for the most part (it's there mainly for compatibility for earlier versions, or special use cases). Rather add/use several groups. Else you specify <rows * columns> and leave "override" at blank (it will calculate itself). Override is used to add "+X amount of trays" to existing ones in that group, I don't think this would be so useful for most anymore. So ex
  22. 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.
  23. 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.
  24. 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):