FlamongOle

Nah, not really made for this kind of configurations anyway

Then I assume it's still bugged. Just uninstall it, then install it again.

No, just update it, it should redirect to the newest one then. This is the fix for it being stalled at 2025.02.08

Maybe, won't promise anything

You'll see them both in the layout. It uses ID's to have a static point of reference. The layouts are dynamic and I don't want to use that. If you don't like it, fork it and make your own

Update 2025.03.18 Commit #411 - MAJOR: Benchmark page would divide by zero if fastest and slowest speed was equal, added -/+ 50 to the fastest and slowest values if they are equal. You can try now @idean

-> right/(top/bottom) Otherwise -read- what it says, it's not Tray's, it's Tray ID's.

Update 2025.03.17 Commit #409 - MINOR: Some NVMe drives will show 0 Kelvin as warning and critical temperatures, if values are not found, NULL will be set and SSD values should be used. @FriendlyFire you can try this update, then run Update SMART+DB. @idean Make also sure you run the last version of Disk Location, otherwise I need the part of the PHP log mentioned above (Tools -> PHP Settings -> "View log"; find entries related to Disk Location).

Please go to Tools - PHP Settings, then open the log and find anything related to Disk Locations. Thanks!

Does the warning and critical match the value set in global ssd disk config? What crit and warn values do you expect, what is defined by unRAID, and where is the numbers found? I'm not sure if optane behaves different or not than regular nvme devices. Maybe unRAID falls back to SSD if nvme is not found. Disk Location just uses 0 as "not found" if I remember correctly. Gonna be drunk this weekend, so look into it later. 😜

Try to Force SMART+DB if you haven't. The warning and critical is stored in the DB as I don't want to pull that info every refresh. It is in Kelvin yes, 0 means not found/stored really and it's converted to C or F. Might do something about it later.

Update 2025.03.12 Commit #407 - MINOR: Obsolete files function listing wrong entries. Found a minor flaw where the obsolete files function would include the backup list into the array if no obsolete files were detected. This would just list "0" and do no harm, neither delete the backups as it was an non-parseable array by the function. Commit #405 - IMPROVEMENT: Removed a few History tags that would just become empty as it won't contain any data. If they are selected, an error message will popup and a red border around the faulty area. Commit #404 - MINOR: Commit not found. Reported by user @SickPup404, not found. Just kidding 😛 Tray count wrong in some count directions if bypassed trays are enabled. Rewrote the tray numbering function. FOR USERS WITH STUCK UPDATES: Tried to work around a possible flaw where the plugin would not automatically update, it might at some point been headed to the 2024-edition branch instead of the master branch. New installation file in 2024-edition branch will point it back to the master branch, hopefully. Alternatively, re-installation of the plugin might be required if it continues to be stuck on version 2025.02.08. Re-installations/removal will NOT remove any configuration.

There's been several updates about this, so hard to know without any PHP error log and not knowing which version that was installed. Feel free to check the PHP log if there's anything in there about this plugin. Otherwise, not much I can do.

It has nothing to do with the folders, just uninstall it, then install it again

@Squid since you're "here" 😛 Do you detected any issues with the versions or some configs with Disk Location in CA? Looks like several users have issues with automatic updates from 2025.02.08 specifically. I just updated the CA xml for last plugin update version (but usually that didn't/doesn't matter).

I don't know why disklocation-2024-edition folder exists if you never installed it manually. However, it is safe to delete. disklocation and diskalocation-master are both required. disklocation-master must be there to enable crontabs after reboots etc. disklocation is the main folder for settings. Everything under disklocation are settings etc. and won't be touched during uninstall, these can only be removed manually or reset in the System tab or Recovery.

Config's always untouched. not sure why it stops at the 2024-edition version as I think it should use the newest date available at all times. I guess I should check some stuff.

This case has several posts already, you'll find answers just 1 or 2 pages back 😛

Ye, it's probably for the best to enable it by default, but I understand why it isn't right now. Would be a hell lot of messages popping up everywhere before plugin and Unraid devs got it all sorted out Haha ye exactly. PHP has been ugly/lazy that way. But even then, there's always some sneaky ones that hid themselves until someone did something you didn't account for Then you add some new ones, removes some old ones, and suddenly there's more of them. I do look at the log files from time to time to see if there's something popping up. But usually the users finds them first haha.

It never saw the light, and 6.12 is still supported. The PHP log has usually been on, but as it turns off automatically during reboots, I sometimes forget to turn it one during development It shouldn't be any warnings I am aware of now, but the plugin is fairly large and have hell lot of different outcomes, usecases and systems, so hard to fetch them all at once.

Update 2025.03.04 Commit #402 - MINOR: Fixed that in some instances and configurations, the benchmark save would trigger an error resulting in an incomplete settings.json file.

You don't need to go to the terminal to delete things anymore, Disk Location Recovery can do it for you, also restore backups etc. I would be interested in the settings.json file after you save it, if you don't mind, please send it to me after you press "save". I will look into this. Nevermind, found the issue.

You have likely manually installed the 2024-edition, this won't be updated. To get the new update, just uninstall the plugin, then install it via CA again. Config should remain, or have been backed up.

Update 2025.03.03 Commit #400 - IMPROVEMENT/MINOR: Added cronjob to use NVME data for warning and critical temperatures (this will be collected during a Force SMART+DB update). This should now follow Unraids default settings. @s11 I was mistaken about the last conversation about this, nvme hot and max was not part of the global variable at all, so had to fetch the data myself. This version should be more correct!

Update 2025.02.27 Commit #396 - IMPROVEMENT: Some Help text was outdated and has now been fixed and cleared up, also added some more info for some configurations. Commit #395 - MINOR: Temperature column not shown. If the temperature is listed to display on e.g. Information tab, it was not shown due to faulty variable name request. The hot/max values are now only displayed in formatted html outputs (Information tab) but not in exported TSV as it can't function when it's outside the Unraid GLOBALS.