Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

17 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. This plugin is only built for stable releases. However, it's likely you missed the past change where the plugin was divided in two sections: "Disk Location" which is found under "Tools" "Disk Location (Configuration)" which is found under "Settings"
  2. Make sure the drives output SMART with minimum of "model name" and "serial number" per drive. If the serial number is hidden or just zeroes, this will fail and probably overwrite each drive of the same model name showing only the last one. Check if your controllers can bypass the SMART data. Maybe your raid controllers can enable some settings in this regards. Do a smart check(smartctl -i /dev/sgX) for each drive listed in "lsscsi -u -g"
  3. Update 2019.09.27 Commit #108 - BUG: Missing bracket in CSS file, caused color error for the LEDs
  4. Update 2019.09.26 Commit #105 - FEATURE: Add force removal of drives stuck in database for any reason under a new tab called "Drives" under Configuration. This has slimmed down the "Information" page and leaves that with just the info without the controll/ operation buttons. Some bugfixes applied to these buttons as well. Commit #104 - IMPROVEMENT: Unclear tray assigning because of TrayID assignment in some cases, made it more clear with added information. @Melocco try this new feature, hope it works @tgrdn maybe the tray allocation is better and made more clear now with the new update
  5. Alright, I see multiple drives have the same name. It's hard to figure out what happened here, what can maybe cause this issue is replacement of multiple drives and assigning them to slot before force scan has been made (or reboot if hot-swapping just partly works) to make sure the drives ends up in the correct list (flag). I would probably delete the database and start over, that is the easy solution at least. If you know how to deal with terminal and SQLite, you can set the flag to "r" for the removed disks manually (might be needed to clear out/null the "devicenode" as well). Just make a backup of the existing one before you edit it. Or just wait long enough until I bother making a "Remove disk" button.
  6. Did you try to "Force rescan all"? This should remove old drives and add them into the "Information" view instead as a history reference
  7. Hi I see you as well do the same mistake as many others, under the configuration of tray allocations, you assign devices based upon ID's and NOT the actual number you define. Else the colors seems to match all pictures as far as I can tell. The configuration will always show 1,2,3,....-> regardless of your settings, it is also stated under "Help" (click that button). Example: You add a group of 5 drives and want it to count backwards so it looks like: 5|4|3|2|1 In the configuration, because it is based upon ID, it will show as: 1|2|3|4|5 Meaning; you set the drive '1' to be the first drive from the left side physically seen. The devices does not rearrange if you suddenly choose to use another count properties, it will only show different numbers and the drives are stuck in place because of its ID.
  8. Ah, and to make clear, the dates are only transferred if the drives are part of the Unraid array. It does not work with unassigned devices as this doesn't seem to really store the data per disk. It looked like it stored the last input you stored for -all- of the unassigned devices as one common unit. The plugin does not use that data because of that, and you have to specify those manually via the plugin.
  9. Make sure you haven't specified a custom color for the drive, just choose any default colors and it should reset to standard scheme. At least make sure of it, I dunno why else it should behave like that
  10. I dunno why you SSD shows like that, it might be lacking some information. Model name and serial numbers are required and has to be unique when it's combined, so make sure it's not blank or contains some odd characters or whatever. If "Force Scan All" does not work, it might be because the old name/serial numbers and rest of the data are still showing as the old disk. This is something the system itself handles and the only way I know to fix this is by a reboot of the server. At least this is often the case with hot-swapping as far as I have experienced. If it shows even after a deleted database, there's nothing I can do.
  11. Under "Set warranty date entry", be sure that "Unraid" is selected. And then store the dates via Unraid page. You might have to force scan all disks, so try that as well.
  12. Are you sure you have selected the correct config for this? It has to use the "Unraid date" and not "self specified ISO"
  13. It's not a bug, it's a feature In all seriousness, the allocation configuration is NOT tray number, it is just a tray ID. So assign them after the ID. It is also written if you click the "Help" button in Unraid.
  14. First of all, get Unraid 6.7.2 or above and update the plugin to the newest version. Then you add three groups, 5+4+5 slots, first and last vertical, the middle horizontal with standard count 1->5 on all. Then you can adjust pixel sizes to make a difference for 3,5 and 2,5 manually. Something like this:
  15. First of all I see that two has the same path (20:0:0:0), this might cause some issues. So I suggest you run a "Force Scan All" under Configuration->Tray Allocation, this will rescan all drives and also wake them up from standby to get all SMART data. It will also purge invalid configs which might happen when replacing drives or controllers, or maybe other configurations. Else it might be that these drives simply don't trigger the HDD light when SMART data is requested, like most/all of the SSD's out there. No fix for that in this case.