FlamongOle

Not going to go through all the themes, but you can change the background colors under Configuration, Layout and Tray Allocation, depending on how you wanna change the colors.

No cards listed under "Unit ID for Dashboard(Multiple):"? Need to select GPU there at least. I'm running an A310 myself with ReBar and things shows up in my dashboard. But my dashboard shows over 100% (like 150% etc) when doing multiple transcodes.

GitHubFeature request: Able to see drive firmware · Issue #455...From spasmonaut @ unraid forums: I would love to be able to see drive firmware as another point of data that could be pulled in to make it very simple to see, at a glance, which of my drives would ... This request is completed, but due to design changes in Unraid 7.2 it will be released once that is released. Unraid 7.2 will be required for Disk Location moving forward next version.

You don't need the disklocation-2024-edition. The others must be there. There's a cleanup function under "System" tab as well for obsolete files.

https://github.com/olehj/disklocation/issues/455

That should be updated automatically once the SMART update has been run. If the drive is/has been in standby (must be active for minimum 5 minutes), it won't be updated. "Force SMART" should update it regardless, including rest of the drives - this will wake them all up. "SMART" will only get SMART data from active drives.

Good to know! These extra cables are for redundancy or transfer speeds? I will see if I MAYBE can add something to make this work in a future version, depending on if it's easy to detect and parse or not.

Maybe you're affected by this? Just a guess.

I don't know how these things interact or work, I just find it strange that it creates duplicated devices. Disk Location 2024 does not check for this as it works differently than the 2025 version. I'm not sure if a bypass would be a thing to add either as it might cause some weird side effects.

I did a bit more digging, and it looks like something is reported multiple times: All devices with path 1:X:X:X and 8:X:X:X matches the exact same drive state (ACTIVE/IDLE/STANDBY) when putting them up side by side for comparison. E.g.: 1:0:0:0 -> 8:0:0:0 ... 1:0:14:0 -> 8:0:14:0 ... 1:0:32:0 -> 8:0:32:0 This will create a conflict as it sees itself double. I don't know WHY this happens, but this is kernel level or so. Are the drives passed through VM or something like that? It looks like your drives are assigned multiple times: PATH 1:0:0:0 and 8:0:0:0 are /dev/sdd (sg3) AND /dev/sdaj (sg37) it also matches the serial numbers. This has to be the issue and why Disk Location don't wanna add it because of that conflict. I didn't think this would be possible, so maybe you know what's going on with your server. And please share if you know why this happens or why you need it (if).

I see that all the drives are marked as unassigned, and that there's several PATH differences from the drives with what's stored in the temporary files. Are none of the drives listed for assignment under "Tray Allocations"? You might need to assign them if that's the case. I'm not sure why all drives are marked as unassigned. Does /tmp/disklocation exists, and does it contain files. Can those files be edited, or has it been mounted as read-only or something? Please check these: ls /tmp/disklocation/smart (should countain one json file per drive) cat /tmp/disklocation/powermode.json (should contain a list of drive states with PATH) Have you tested for faulty RAM? /tmp folder are mounted in the memory. Maybe a proper power off (with plugging out the cord) for some minutes will solve things too (if you have faulty files/write permission issues etc). If none of the above gives any clue or solves it, I would probably go to System -> then select Reset "all" (NOT wipe). Then restore a backup you know worked followed by "Force SMART+DB". If the backup doesn't work and you have tried several, then I guess you must start from scratch (you can still keep benchmarks, backups etc, so no "wipe" will be required).

you could try to go to Disk Location -> System, then click "Enable debugging", then click "Disable debugging" right away. Download the debug file and send that one. It will expose serial numbers and comments etc. related to the plugins, no content whatsoever.

It won't be implemented unless it's implemented in Unraid itself. Disk Location uses Unraid's info.

Do you see anything related to Disk Location in the PHP Logs found here: Tools -> PHP settings

Brilliant! :)

Anyone know where or if I can edit the "Featured Replies"/"Recommended" posts? Earlier I could remove old obsolete recommendations "tag". I don't want to delete the entire post. I have tried to look for it and search for it, but I can't really find it.

Which version did you have, and which do you run now? It shouldn't be any difference in how it gathered devices, only how it's stored (in case of database migration). USB drives where never really supported to begin with, but if it works, then great! I have way too less information from you that I can help any further. So the only suggestion I have so far is: did you try to Force SMART+DB? Did you also check the first post and recommended posts?

Need to Allow editing of Unraid config in "Configuration" tab.

It will update every 5 minutes, typically. Warnings cleared from Unraid doesnt matter here.

Update 2025.06.03 - my birthday release 🥳 gettin' old 😅 Commit #452 - MINOR: Issues where tray 0 can't be assigned. Check if tray is 0 or null and not just "empty". Minor bug fixed in Tray Allocations where the default selector would select 0 instead of "--" for unassigned devices. @JohnnyGrey try this one ;)

Update 2025.06.01 Commit #450 - MINOR: Old variables used in benchmarking causing old values to be used if it shouldn't exists. Some benchmark results from "previous" run could be used for new devices with earlier dates not existing. Clear variables before each run to make sure it won't use data from different devices.

The auto function only happens since Overhaul '25. It doesn't matter if it's auto or manual, both counts as valid backups and dates.

Note: It should be silent without [], the brackets traditionally shows it is optional to use it ;) It might however still work regardless. And to just point out, it is possible to fetch the output to post that into notifications via shell variable :P But you maybe want something more "useful" than just "Backup created." :P

Update 2025.05.30 Commit #448 - IMPROVEMENT: Added help text for how to add own backup cycle via scheduler/crontab. Minor "Help" updates in Configuration and System tab. Added a slight difference between "silent" and non-silent output. Also updated the Help on Dashboard tab.

Make sure you have read all Help text. Here you need to increase the size of the blocks. They do not scale itself. Check if you have heat map enabled or not. Heat map overrides custom colors. Otherwise: device colors > group colors > default colors