FlamongOle

Use custom colors, no ETA on implementation yet.

nope But can you tell me what flash2 was? Usually "flash" is the Unraid USB memory, flash2 would then be like a mirror or so, or just another USB drive? Maybe you use Unraid 7.3 already with the system on disks instead? Reason I ask is if flash2 is a typical device name in Unraid somehow, or if it's sort of "hidden" behind "flash" and that's why it didn't acknowledge it.

These values are not stored within Disk Location, but in an Unraid file. I would be interested in the debug file and your /var/local/emhttp/monitor.ini You can also try to "Acknowledge all" under SMART if you enable "Allow editing of Unraid config" under Disk Location -> Configuration. Unless you already tried that.

New drives must be added under "Tray Allocations", after they are added and saved, they should not dissappear. Doesn't matter what content is on the disks, it only care about the hardware itself.

I don't know why this would continue to fail. It looks like all drives are spun down and this would be the reason why temps are not showing. I probably need a new debug file from this.

I can't replicate this, so need a debug file in that case. Make sure the drives are not in standby mode, then temps are not monitored. It does not use same data as Unraid, but probes itself. Any specific controllers used for drives?

This is rather intentional as it gives more flexibility for various layouts. If you just wanna add an empty section, you can add number "11" and hide it. Or just create a new group consisting of just 1 tray, move it in between, then hide that.

@Free Man The colors goes in this priority: disk > group > common If "disk" has a custom color, then it will override both "group" and "common", regardless what the others are set to. If "group" has a custom color but "disk" doesn't, "group" color will be chosen over "common" To reset color per disk or group, the "common empty color" should be used to reset. That is whatever the "empty" color is specified as, not the original Disk Location color, unless if that's being used.

I think I see what's going on here now, and don't have time to fix this for some time (few months even maybe). Anyway, some of the drives has been marked as "removed" earlier then re-added. Typically this duplication should not happen and I am not sure why or how that happened right now. When re-adding drives, it should change the status from "removed" to "in use". Removed drives won't have SMART status saved and thus why it says "FAILED". To fix this, you might need to either wait for a fix someday, or you can: go to System tab create a backup delete "devices" (only select "devices", you want to keep rest of the configurations you made, probably, but "History" devices will be wiped. redo "SMART+DB" go to "Tray Allocations" assign devices to the slots again profit, hopefully :p

Need a debug file for that one, anything in common with disks in 2-13, like same controller or so? Temperature N/A is expected if the drives are spun down.

As "heat map" is selected, it will use the temperature thresholds set by Unraid (or the disks if SSD's). Yellow is your "normal" temperatures, "red" is the critical temperatures. It might run hot, it might be that the values are set too low. You can set global disk temperature thresholds and per disk in Unraid. Disk Location will use these data, but it's not related to the plugin itself. If you hover the red "LEDs", or go to Information tab, you might see the current temperatures and the thresholds if it's configured that way.

What does the "SMART" tab in Disk Location say? For all I know, this might be colors specified by you. Feel free to post me the "Configuration" and "SMART" tab.

Update 2026.02.19 Commit #486 - FEATURE: Edit color for SMART Errors/Overview now possible by selecting "SMART color theme" to "Custom" under Configuration tab. It will use the defined colors specified for data type or heat map colors. Commit #489 - IMPROVEMENT: Added updated help text for tray assignment count direction.

Update 2026.02.13 Commit #491 - BUG: Benchmark did show only the first set number of results, and not the last as intended. Commit #489 - BUG: Tray assignment count direction could fail tray numbering if row/col is 1. If count order was selected to be "left/bottom" or "right/top" when rows or columns were set to 1, it would fail the counting. As these does not make any difference than selecting "left/top" or "right/bottom", the two others are removed from the selection if rows or columns are set to 1. Commit #487 - BUG: Read/written values could be carried over from another device in some situations, values should now return "null" if values doesn't exists. @CtznSnips this should help avoiding the problem in the future.

Ah, this is a weird bug. But easy to work around: If you have only 1 column, set "Tray assignment count direction" to either "left/top" or "right/bottom" the two others are mainly only meaningful if you have more than 2 columns and then it works. You can see it at the bottom, once the assignment is wrong, you will likely see something like disk order: 1 0 0 0 0, instead of 1 2 3 4 5 etc.

Ye, that should be doable I guess. But it's not a priority right now. The dates can be copied from Unraid itself as this plugin doesn't store most of that data anymore. Check out this file: /boot/config/disk.log

Not much I can do with that info. Have you adjusted the start count to be "1" and not "0"? If it can't save, there's something conflicting, like trying to assign 5 if it doesn't exists but in your case could be 4. I don't have your config, so can't test.

No ways to split the "bay", I see no reason for it either. Don't think of this to directly copy the looks of your server, rather where you find the disks. 2 HDD's in one bay: create 2 bays instead of just 1. Easy to try different configurations, just create a new group and play with it until you're satisfied, no need to change the one you have until you find the one that fits your purpose. I hope it makes sense enough :P

No, visible via mouseover if configured so

You must add 6x8 or 12x4 depending on the layout you want. No ways to assign two drives into same number/slot.

You can't add more than one drive per assigned slot. Rather add multiple slots if you do dual drives per slot.

Can you try "right/bottom"? I wonder if the "left/top" has a weird bug for 1 column, but works for 2 or something (can't be bothered testing it again). But "right/bottom" should do the same for your setup, but runs the calculation slightly different. Please report back if it solves it. Otherwise, I will look at it when I find time and motivation.

I dunno when I will have time to look at this, but please send me a debug file. Thanks!

@neatgz The locate button is only looping a SMART request and will only activate the activity LED. It doesn't always work, depending on the drive and manufacturer etc. "storcli" isn't installed by default in Unraid, and I don't want to include that in the plugin. If it's installable via a plugin, then that's great, but I can't test the functionality myself as I don't have the hardware to test this. Maybe in the future I can add something. What I need to know is the actual output of: storcli /call/eall/sall show all | grep -B5 -i "your serial number" If the output can be in JSON, that's even better. I also need to know how to detect if /ex part is required or not, if ever. storcli /cx[/ex]/sx start locate I understand the "/c0/s2" - but what is /e[x]? The ledctl would be straight forward to add as an option, as it uses only default drive paths, but which package is that in? I can't test it myself, but seems easy enough.

Thanks! It works just as before, thanks Only minor thing is that it says "SettingsReadings" (see screenshot from previous post by @joshua777 ) And that the cogwheel is misplaced on the Dashboard (there's an updated guide for new 7.2 dashboard). But no rush, works otherwise as expected!