Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

15 Good

About olehj


  • Gender
  • URL
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yes, this happens now because LUN is ignored when scanning through drives. Earlier it was used to detect if the drive was an actual drive, but some drives doesn't even have LUN's so it had to be removed. At least you can choose to show it or not 😛
  2. Update 2019.07.12 Commit #100 - MINOR ISSUE: Fixed a non-numeric value warning message. Fixed padding for empty trays.
  3. Yes, it is per group basis.
  4. Delete it under "System Files"
  5. Probably just an undefined variable, nothing to care about. The configuration is now located under Unraid "Settings" tab, while the plugin view is under "Tools"
  6. Under "System Files" you can delete the database - you have to set up everything again, but it might help.
  7. Then I suggest deleting the database and redo it, if that doesn't help, then I don't know what causes this. It should simply not be possible unless custom colors has been saved.
  8. The drives you assign has to be recognized as "Data" drives by Unraid and connected to the device node. There's nothing which can interfere with the main colors, sure you haven't stored some custom colors for disk 11 and 14? Do you use a different card for these drives, than the other drives - like raid card or something. Maybe lsscsi doesn't pick up the device nodes and then won't find the function it is assigned for. For Unraid/main colors, it uses only device node and not the scsi generic device node. I have no documentation about what Unraid stores if it does not get the device node name.
  9. Update 2019.07.10 Commit #98 - IMPROVEMENT: Added color list for color selection under the "Configuration" tab.
  10. Did you make sure that: - You changed the "Data" color under the "Configuration" tab and not the "Custom color" under "Tray Allocations" - Does not try to use the same color for "Custom color" as for those pre-defined under "Configuration"? Custom colors works as an override and can not be the same as "Parity" "Cache" "Data" "Empty" or "Unassigned" pre-defined colors. Try to change 11 and 14 to f.eks. #FF0000 to see if it saves and uses those values, to reset to colors, you can use the predefined colors and it will automatically ignore it and use the pre-defined instead.
  11. Update 2019.07.07 Commit #94 - MINOR ISSUE: Some disks fail because of missing LUN. Skipping LUN during device validation, add LUN from SMART instead. @shaunmccloud I am just way too nice 🥴 Do a "Force Scan All" to get all disks updated, the installer/updater only care about spinning disks (non-standby)! New devices may appear (like USB drives and SATA/RAID controllers) as they might provide SMART information... do whatever you want with them or just ignore them. Devices without SMART "serial number" and "model name" will be skipped, and they play a vital role in the database system - this will not be changed.
  12. Because of the output above, I assume it can't detect the disk to assign the color to. It will fail hitting the device nodes as the output is outside the specifications of what the plugin can handle at the moment. I might ditch the entire LUN in the future as I mainly don't use that anymore if I remember correctly.
  13. [4:0:0:0] disk ATA SPCC Solid State Disk _ /dev/sdc /dev/sg3 There's the problem, for some odd reason, this "disk" does not get a LUN like the others, and falls back to "ATA SPCC Solid State Disk _" for whatever reason. I'm sorry I can't help you further here. I dunno why it hasn't received any LUN's though. Has it been inserted with the server on, like hot swap? I dunno if that might be a problem or the SATA SSD controller itself. If a reboot doesn't help, then I dunno how to fix this. I never had that issue with any of the disks I had
  14. what's the output of "lsscsi -u -g" ?