-
Posts
549 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by FlamongOle
-
Did you "force scan all"? if you have a lot of drives, all of them will likely spin up and take some time per device to complete the scan.
-
Sadly no. Might be something to add in the future, but no ETA or really any time atm.
-
Did you update the plugin(s) to the newest version? Otherwise it's a false negative and should work. I think this plugin works from 6.9.0 and above, but haven't tested. I don't know why you're getting this message.
-
Thanks mate, appreciate!
-
Update 2023.07.17 Commit #224 - MAJOR ISSUE: Fixed a Dashboard crash when all drives were spun down. Try now guys, hopefully this'll fix it. Sorry for the delay, haven't been home for a while. @Mat W @krh1009 @Revan335 (USB drives are mainly not supported) @SShadow
-
Can you share a screenshot of your Disk Location configuration tab? Also, just for debugging, have you tried to be on the Dashboard for like 5 minutes or more? Just speculating in performance issues rather than crashing the dashboard. I might need a diagnostic file here, but I don't really like to ask about them. But more PHP logs might be useful too.
-
I can't make any sense of this yet. I released a C version, but doubt it does much good. I have to debug this later one day. Is there any problems loading any other pages on the plugin configuration?
-
Update 2023.07.08b Commit #220 - MAJOR ISSUE: Fixed a Dashboard crash when all drives were spun down. Fixed also some other minor PHP deprecations. Please update and give me feedback if this update solves the problem @SShadow @Mat W @Walter S I have made some few more changes, and I tried to replicate the problem without success. I tried to create new database with just two of the drives. Then spun them down and made several adjustments to the variables without crashing the dashboard on Unraid 6.12.2.
-
Update 2023.07.08 Commit #220 - MAJOR ISSUE: Fixed a Dashboard crash when all drives were spun down. Fixed also some other minor PHP deprecations. Please update and give me feedback if this update solves the problem @SShadow @Mat W @Walter S Thanks for reporting the issue at Github @Walter S
-
Feed me the info posted on github, and I will try to have a look at it ASAP. But I will be quite busy the next weeks, but it will really help me debugging it faster as I don't have a setup I currently can put all drives to standby.
-
It's been reported problems with maybe a similar controller here: https://github.com/olehj/disklocation/issues/191 Raid P410 controller, maybe it suffers from the same thing. If it's not reachable with the commandos I gave and cant provide unique serial numbers, then I can't do anything about it.
-
New smaller update to prevent faulty upgrades. Hopefully this fixes some issues.
-
Then that's the reason, maybe there's a setting to change serial number on the controller or whatever system that is. Maybe bypass logical volumes if possible and run the drives directly? the plugin heavily depend on unique serial numbers, and I never thought this would even be possible.
-
Does the logical volumes generate two unique serial numbers? you can probably check that with smartctl -x /dev/sdb smartctl -x /dev/sdc
-
Hmm, technically the plugin should uninstall itself before it install itself during upgrade. So don't know what's going on there, I'll have a look at it later
-
It should work ye, is it updated to the newest plugin release? Haven't seen what happens with an upgrade from 6.11 -> 6.12 yet, just separate installs. But don't think that should matter. The dashboard for 6.11 should just be ignored, and the other one loaded. It might be located somewhere else on the dashboard than before. Maybe you even need to unhide it by default if they did any changes recently to the RC. Otherwise, try to reinstall the plugin. Database should remain intact.
-
What does this command output: lsscsi -b -g
-
I going to move both buttons if I move them, but maybe I'll look into it. The heat map overrides all custom colors. The names for the main color definitions also renames accordingly when you toggle between "Disk Type" and "Heat Map". Rather toggle "Temperature LED" and "Warning/Critical Flash" if you want some indication on a "Disk Type" view. There's no way to have them both as it defines the background color.
-
About the buttons, never really knew the best place to put them.. any suggestions?
-
Sorry, I can't replicate this. Check if you didn't mess up with choosing "heat map" and thinking custom colors would work. You have a "reset colors" button in the configuration too.
-
Was a typo in the variable, fixed with 2023.04.22
-
Did you force scan all recently? I know this was a bug at initial release. I might look into it soon, but too drunk now.
-
New update, fixes the issue above. Might apply to several out there, who knows?
-
This post continues at https://github.com/olehj/disklocation/issues/188
-
New minor update, should fix the above problem as well.
