• Posts

  • Joined

  • Last visited

1 Follower

About olehj

  • Birthday June 3


  • Gender
  • URL
  • Location

Recent Profile Visitors

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

olehj's Achievements


Enthusiast (6/14)



  1. You're missing the point. DL is not supposed to care about the "real" size. But rather what's written/labeled on the physical drive itself. It is rather used for manual identification. This plugin is an organizer for where each individual disks are located, so having the labeled disk size is more usable than the formatted usable size. It would be easy to check the actually size of the formatted info - or just use what ever written in the Unraids variable array, but that is not the intention of use and will never be implemented. It's all about the physical hardware, not the logical data.
  2. Disk Location uses the size reported from the SMART itself, and has nothing to do with the partitions or the format. The content is not interesting for this plugin as it is to detect what kind of drive that might be broken, or rather for identification in general.
  3. Hmmmm... does it work if you choose "dark mode" on Unraid? I always use dark mode and don't really think about these things. You can choose another color for the default "unassigned" devices too though.
  4. Thanks and cheers Back in the days it was auto-scanning drives after every change, but it was quite slow on larger systems. It's not optimal, but for now the safest and fastest option I can come up with. Maybe I will look more into it whenever I have time. I have success with two PCI-E SSD cards with bifurcation on a SuperMicro X9 motherboard: ASUS HYPER M.2 X16 PCI-E 3.0 with 4* Kingston NV1 SuperMicro AOC-SLG3-2M2 with 2* Intel 660p SSD Not sure if multiplexer cards would work, or server cards etc. with raid built in and so on.. but if you go bifurcation which I believe would work quite fine on your Dell, then that's the way I would probably choose. But I'm no expert in that area.
  5. request, please use github for trackability
  6. And what's the problem? You make sure to read that TrayID is not the same as the chosen numbering of the trays?
  7. never removed? check above commands if they get detected or not?
  8. Some RAID cards might do weird stuff, can't guarantee they all will work with this plugin. Do you see all the drives with this command: lsscsi -u -b If no: nothing I can do. If yes, run this command on a drive that shows up in the plugin and one which doesn't: smartctl -x --json /dev/sg<X> where <X> is a drive number found from "lsscsi" command. Post these in a text file or on pastebin etc. From the smart output, it has to post a "model name" and a unique "serial number" from each drive as a minimum.
  9. Cool, thanks. It will be included in the next update.
  10. I don't see this warnings myself, but please try to replace the "!isset" with "!is_numeric" instead, and see if that helps? Do not reboot, this will just reinstall plugins and all changes you have manually done.
  11. Try to write "0" (zero without quotes) instead of "null" on that line and see if it disappears, then I'll update that on next release
  12. Update 2022.06.10 Commit #185 - BUG: json output of smartctl varies between SCSI protocols, checking for multiple variables instead. @jlficken
  13. Update 2022.06.07 Commit #182 - BUG: Picked up wrong array from SMART data, Commit #182 should work now (hopefully). Added additional debugging lines and made NVMe drives be ignored from the standby check during scanning. @BlinkerFluid try now, thanks!
  14. No reboots required. Can you check using SMART that "model name" and "serial number" is different from drive to drive, and not the same as getting info from the drive controller? Made sure the plugin is actually updated, and refreshed page before running "force scan"? You could also try to delete the database (back it up first just in case if you have put some work into it).
  15. Update 2022.06.05 Commit #182 - BUG: With SCSI enclosures/SAS drives, SMART data behaves slightly different and ignores the drives as the plugin couldn't find them. Added new variables required to detect disks in enclosures. @BlinkerFluid