Everything posted by FlamongOle
-
[PLUGIN] Disk Location
Overhaul '25 update: 2025.02.12-2205 RC2 Dashboard selection is fixed and tested, actual selectors are now visible via Help function. Changed some operations in cronjob to prevent powermode-function to not operate as expected. @SShadow I could not find any issue with the Backup function here. Try this version and see if it's still an issue. Also check if you have /boot/config/plugins/disklocation/backup folder existing. If it is, try to create a file in it: "touch testfile" or something. Also check if you have any other files or folder other than dates and if they contain anything else than disklocation.*.gz files: ls -la /boot/config/plugins/disklocation/backup/* I have some old obsolete folder in there, and it still works. But I would like to know if there might be something conflicting there. There should only be one file per date-folder. I am grateful for your testing involvement! Thanks @SShadow @mr2toyou @PeterHS
-
[PLUGIN] Disk Location
Currently investigating this, there's things here which was parsed wrong. There should be more available, and also listed. Working on it!
-
[PLUGIN] Disk Location
Thanks, I have adjusted something in the cronjob, maybe it will solve it.
-
[PLUGIN] Disk Location
was that after coming from 2024-edition or after devel-upgrade? SMART(+DB) should regenerate the powermode file, hard to say what really happened there. It's also executed by crontab every 5 minutes and should update itself, and as long as you did SMART+DB it should also match each other. I'm gonna have a look if I find anything
-
[PLUGIN] Disk Location
Overhaul '25 update: 2025.02.11-2218 RC2 Fixed "heat map" to be working again, it used an old variable. Also fixed so that N/A temp is colored as N/A.
-
[PLUGIN] Disk Location
On other hand, you use "Heat map" and not "Disk Type"? Looks like "Heat map" does not work at all. Gonna look into that.
-
[PLUGIN] Disk Location
No, the SMART errors are now just moved in the SMART section of the plugin instead. This will make it use SMART settings defined in Unraid config. I decided to not include it this time as it's more of a clutter anyway. (these: Reallocated Sector, Reported Uncorrectable, Command Timeout, Current Pending Sectors, Offline Uncorrectable incl. whatever you might have included from Unraid config). But, "nvme_used" (Percentage used) still exists, just under another tag called "endurance" which is valid for both SSD and NVMe. Power On Time still exists, but two different formats: powerontime which gives you a calculated time "4 years 3 months" etc.. and powerontime_hours which gives you raw hours. Load Cycles still exists, but not included by default (loadcycle). Press "help" button, and entire list will show up of what you can choose per table.
-
[PLUGIN] Disk Location
I just tested them, they work here. But it might take up to 5 minutes before you'll see if it's in standby or not, it's background-caching. You can double check when you hover the LED if it says "device spun down" or "device is active" or something similar. Server-side cache (nothing you can change)
-
[PLUGIN] Disk Location
Are the temps below the warning threshold? There's two settings, warning and critical. Ideally you would be below both. The settings are adjusted in per disk settings, or globally under Settings -> Disk Settings I just tested both, and they work here. Make sure the settings are adjusted correctly and report back.
-
[PLUGIN] Disk Location
Overhaul '25 update: 2025.02.11-1751 RC2 Same as previous, just git merge fixed. @SShadow @PeterHS @mr2toyou If this release seems fine, then the I will likely pull request it to master branch on 14.02 and release it as stable then.
-
[PLUGIN] Disk Location
Ah, I see the merge resolve is in the way. I'll see if I can fix it soon
-
[PLUGIN] Disk Location
I notice you use devel, anything bugged so far, or did everything go smooth?
-
[PLUGIN] Disk Location
Yes, they can be individual or global. I just grab the data, nothing else for temps
-
[PLUGIN] Disk Location
Unraid disk config
-
[PLUGIN] Disk Location
Overhaul '25 update: 2025.02.10-2201 RC2! See main post about additional changes. The previous warning about crashing with devel-release is now invalid. It will fallback to default if something is wrong, and it will also tell you what's wrong. As this is Release Candidate 2, I would like to have a few more testers. Mostly from stable users, but also devel users. This would normally be released as stable, but I don't want to rush anything, just in case. Please go to the post below for instructions. Please post here about the experience and how it went, both good and bad! Added a Seagate HDD check in System tab due to a fraud likely caused by some miners. https://www.heise.de/en/news/Fraud-with-Seagate-hard-disks-Dozens-of-readers-report-suspected-cases-10259237.html https://www.tomshardware.com/pc-components/hdds/seagates-fraudulent-hard-drives-scandal-deepens-as-clues-point-at-chinese-chia-mining-farms https://www.techspot.com/news/106706-used-seagate-drives-sold-new-traced-back-crypto.html
-
[PLUGIN] Disk Location
This will allow or disallow editing of Unraid config files via this plugin. E.g. acknowledgement of all drives at once, or editing warranty dates etc. When setting this to "NO", the options are not editable via the plugin.
-
[PLUGIN] Disk Location
Overhaul '25 update: 2025.02.08-1936! See main post about additional changes. IMPORTANT! For current devel-testers: This update might crash current devel installs (won't affect real upgrades later), fix: edit file /boot/config/plugins/disklocation/settings.json then search and replace all "nvme_used" to "endurance", or just remove "nvme_used"
-
[PLUGIN] Disk Location
Yes, unraid/server boot. It was several things involved which is now fixed and forced. Good to hear!
-
[PLUGIN] Disk Location
Overhaul '25 update: 2025.02.07-2352! See main post about additional changes:
-
[PLUGIN] Disk Location
Update 2025.02.08 (2024-edition) Commit #370 - MINOR: Blank displayinfo on update in some occasions, likely due to empty config without pulling the default config. @edival try to update and see if it fixes it.
-
[PLUGIN] Disk Location
Overhaul '25 update: 2025.02.07-1551! See main post about additional changes.
-
[PLUGIN] Disk Location
You will not loose any data by uninstalling. Just uninstall and install it again. Even by installing devel keeps the old config, also backs it up. Use "master"/CA for stable release. 2024-edition is for future if some wants to stay on this system and not the new one. 2024-edition is not compatible with CA and must be manually installed. Newest version won't fix the issue right away, you must do a force update all. New version will do that when booting your system next time and then it should prevent these things from happening. Overhaul '25 have an additional check added in place for this now (last update)
-
[PLUGIN] Disk Location
I updated devel (2025.02.06-0014) once again, please update it (regular way via Plugins if it's already installed). If you see any changes, good (red text is good in this regard). If nothing, then yes, logs would be fine. Please do following: Go to System tab If "Delete debug file" is visible, click that. Click "Enable" Then just click "Disable" right away, no need for refresh or anything (log file will increase size quite drastically every refresh) Then download the file and send to me as private message, WARNING! serial numbers, comments etc. are exposed! Also, which warnings/critical messages do you get?
-
[PLUGIN] Disk Location
You must do a Force Update All, if you have installed the newest stable version, this should now be fixed as Force Update All is executed at boot. What you see here is a misalignment between drives and drive PATH. Some of these LEDs might even be for wrong drives. I think I will adjust how this detecting works by using a different method. But for Overhaul '25.
-
[PLUGIN] Disk Location
The SMART tab will only show drives if it find anything reported as errors defined by Unraid config. If you see none, that means none of your drives have like reallocated sectors etc. I'm a bit more curious of why you had flashing backgrounds. That would happen if there's no SMART data available, but this was detected and should put a big red message about what you need to do. I can not reproduce it either, so I must do some more investigations of that.