hermy65
-
Posts
273 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by hermy65
-
-
5 minutes ago, GilbN said:
use command
SELECT DISTINCT "ID_SERIAL" FROM (SELECT * FROM "diskio" WHERE time >= now() - 10s)Would rather not expose my db to the internet but if i need to i can to use your link above. I did run the command via console and got the result below which makes me assume its not pulling serial data but that wouldnt explain why the drives arent visible in the top bar of the dashboard (i assume):
-
8 hours ago, falconexe said:
New Query: SELECT DISTINCT("ID_SERIAL") FROM (SELECT * FROM "diskio" WHERE $timeFilter)
@falconexe @GilbN Well, maybe we found an issue?
There is data under diskio but im not seeing any serials
-
1 hour ago, GilbN said:
Connect to you database using this and run the variable command there. http://influxui.s3-website-us-east-1.amazonaws.com/ It works locally.
Or exec into the container and run it that way.
That will atleast confirm that there is data in the dB.
Have you tried to remove and re add the datasource in grafana.
@GilbN which command am i supposed to be running? Didnt see it mentioned unless i missed something.
-
46 minutes ago, falconexe said:
Also, in this image your data source should NOT BE "unRAID", it should be the variable "$Datasource_Telegraf".
Yeah i changed it back to the variable after posting that image. Still no luck though unfortunately...time to start it all on fire i guess
-
2 minutes ago, falconexe said:
1.5 is driven by variables. Set your datasource variable in the dash.
Then go back to the drive variables, and set the query to use the VARIABLE for Data source "$Datasource_Telegraf". You'll need to do this on all of the drive variables.
You should see all your drives appear under the "Preview of values" section at the bottom. Try that and let me know.
Yeah thats how i had it setup originally with my datasource at the top and everything as your last screenshot shows. Attaching the image i put on my first post again, in case i missed something.
-
Just now, falconexe said:
If that was the issue, make sure you restart the 3 main dockers (InfluxDB, Telegraf, and Grafana). Then go back into the drive variables, and hopefully your disks are now showing up in the bottom preview area. I thought I read 1.3, but if you are going from 1.2 to 1.5, that is a DRASTIC departure from what the UUD was back in September ha ha.
I already had that enabled, and my disks do show up in the bottom panel in the smart health section but im guessing that doesnt tell us if diskio is working.
-
21 minutes ago, falconexe said:
Hey man. Long time....
Hmm very odd. First thing I would do is check to make sure your variables have the correct data source assigned.
When you look at the content of any of the drive variables, you should see your drives listed in the bottom once the query runs. If they show up in the variable itself, they should show up in the drop downs.
The refresh setting should also be on Dashboard Load in Version 1.5. So you can try clearing your browser history/cookies, and reloading the dashboard. If it worked in 1.2 it will work in 1.5 because nothing changed with this variable except the name.
Let me know if that helps.
So i went through and i *assume* i updated it correctly but still no go after clearing cache, etc.
-
@falconexe Looking good my man! I just bumped from 1.2 to 1.5 and am running into an issue that im hoping you can point me in the correct direction on. In 1.5 im not able to select any drives at the top of the dashboard (Flash (Boot) Drives, Cache Drive(s), etc). On 1.2 and 1.5 all of my disks, serials, etc pull through towards the bottom of the dashboard but im not able to select anything at the top. Anything i should be looking for to try to figure this one out?
-
@JorgeB bummer, that did not work. Followed your steps, there was no existing data overwritten warning. Started it back up and it says unmountable for the cache array
-
@JorgeB also, i assume if we blow this away i just add the new drive then tell it to format the cache array since its unmountable or whats the correct process here?
-
@JorgeB just your standard vms, appdata, docker image, etc.
My question for you then is since the new SSD is still showing as unmountable in the unassigned devices but does give me the option to preclear it...should i do that? What is to say wiping out the cache and starting over would get that other one working?
Edit: Also, i still have the drive i pulled sitting in unassigned devices, if i put that back in will that break anything? Or is it better to put the new drive back in the array, wipe the cache array, then copy data from the old drive.
-
@JorgeB yes the pool mounts, or at least appears to without that new disk in. But if i look at the docker tab it tells me that docker isnt started, my vms arent available, etc
-
@JorgeB removed it and started it and looking in unassigned devices it doesnt show that its mountable, can preclear it though.
-
-
@JorgeB Is it normal for this to happen for that drive? It is a brand new drive.
-
@JorgeB You were correct as always sir, ran it again after moving that last 70GB and it looks like it completed. Diagnostics are attached.
-
@JorgeB Interesting. I just manually checked and im seeing about 335GB used out of 1TB. After that i moved another 70GB off of it so literally the only thing left on cache is my plex folder and my docker image which both of those total about 240. Im running the command now, will see what happens this time.
-
@JorgeB Having issues getting this to work, keeps saying im out of space when there is almost 600GB available
-
@JorgeB Done, attached are new diagnostics plus a screenshot of the popup i got.
storage-diagnostics-20201221-1047.zip
-
-
@trurl attached
storage-diagnostics-20201221-0900.zip
Also, i stopped and started thee array before making the OP so i could get the exact message from the popup but it didnt come up this time. Below is a picture of my cache pool, sdc is the new drive that i put in that did not rebuild.
-
Needed to upgrade 2 of the 4 SSDs i had in my cache pool so i swapped in the first one and it did the standard BTRFS rebuild or whatever it is supposed to do. Once that completed i stopped the array and put the second one in, this time when it came up though it did a parity check for some reason and never actually did the BTRFS rebuild or whatever it is and now when i start the array it was telling me i had a missing cache drive but referenced the new drive as the missing one even though its in the array.
So my question is, what do i do so i can get the BTRFS function to do what it is supposed to do?
-
All of a sudden today my unraid box has been seriously sluggish so i rebooted and when it came back up it took 20+ minutes to start up just my containers. My machine isnt underpowered so it shouldnt be this slow, im running dual xeon e5-2630v4s and 64gb of ram. Prior to today i had uptime of ~200 days without any issue so this is definitely not normal for my rig. Diagnostics are attached
Edit: Im also seeing slowdown now when accessing/modifying existing containers too
-
26 minutes ago, GilbN said:
Is there an advanced option?
If there is, im unable to find it.
Ultimate UNRAID Dashboard (UUD)
in User Customizations
Posted
Interesting, never saw mention of it working locally. I ran all the commands you gave but never got a result from any of them. Here is what my telegraf config looks like in the [[inputs.diskio]] section
# Read metrics about disk IO by device [[inputs.diskio]] ## By default, telegraf will gather stats for all devices including ## disk partitions. ## Setting devices will restrict the stats to the specified devices. # devices = ["sda", "sdb"] ## Uncomment the following line if you need disk serial numbers. # skip_serial_number = false # ## On systems which support it, device metadata can be added in the form of ## tags. ## Currently only Linux is supported via udev properties. You can view ## available properties for a device by running: ## 'udevadm info -q property -n /dev/sda' device_tags = ["ID_SERIAL"] # ## Using the same metadata source as device_tags, you can also customize the ## name of the device via templates. ## The 'name_templates' parameter is a list of templates to try and apply to ## the device. The template may contain variables in the form of '$PROPERTY' or ## '${PROPERTY}'. The first template which does not contain any variables not ## present for the device is used as the device name tag. ## The typical use case is for LVM volumes, to get the VG/LV name instead of ## the near-meaningless DM-0 name. # name_templates = ["$ID_FS_LABEL","$DM_VG_NAME/$DM_LV_NAME"]