• Posts

  • Joined

  • Last visited

ShinseiTom's Achievements


Newbie (1/14)



  1. I've started running into this issue ever since the latest large update (I guess to v7? The one that completely changed the webui theme) Basically, after a random but long (this last time was 4 days) amount of time Grafana goes back to the login screen. This is what I assume is the error messages related to it: t=2020-12-06T03:10:23-0600 lvl=eror msg="Failed to send usage stats" logger=metrics err="Post \"\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" t=2020-12-06T04:06:20-0600 lvl=eror msg="Failed to look up user based on cookie" logger=context error="user token not found" t=2020-12-06T04:06:20-0600 lvl=eror msg="Failed to look up user based on cookie" logger=context error="user token not found" Unfortunately, the Grafana devs don't seem to be seeing the same issues on any of their systems so it's probably some kind of "quirk" of the multitudes of personal-run instances and circumstances. Doesn't help us that have the issue though, and definitely shouldn't be happening and didn't in the past. According to a response near the end of this github issue, increasing that "token_rotation_interval_minutes" value to something large (like 7 days) helps mitigate the issue somewhat. But I too can't find the config file (custom.ini? since supposedly we're not to modify grafana.ini) mentioned in their documentation. Is there a way to modify that config setting using the docker setup variables, or at the very least find and modify the config file used through the container's console? Would changing the "GF_PATHS_CONFIG" environment variable to point to a modified config in it's appdata be enough?
  2. Thanks, I was on 0.5, that was the update that killed it. At the time I posted, that reddit response wasn't quite there yet, must have been off by mere minutes based on timestamps! However, it's been updated again and now has a button to redirect to the login page on that unauthorized page! I hoped it would get fixed pretty fast. Now I need to check if my homescreen user problems are fixed.
  3. Dont know if this is just me or not, but I can't use DashMachine at all since the recent update. I just get an "Unauthorized" page when I try to open the site. Tried completely wiping and restarting but still got the same, Firefox and Edge. Sucks, just got it setup with icons and everything.
  4. Unfortunately/fortunately, no. My specific issue might not ever be resolved, simply because I moved on from that setup. Too much of the box's hardware changed all at once, and I've not had any issues since. In fact, the only thing remaining of the old box is the case, usb, and some of the drives! Moved from a 2500k with 12GB ram to an 1800x with 32GB ram. New power supply, obviously different motherboard, double the drives, an nvme drive, SAS card, 10Gb SFP+ card (nice!). I also don't have Plex running over the network anymore, so no sustained hours-long thousand-files network reading. So yeah, unless I decide I want a second Unraid box and I run it on the 2500k for some reason, probably not going to figure it out... not that I was having any luck with the current logging anyway.
  5. Alright, another crash with an error I could catch. Had been stable 8 days, was in the middle of a network copy of a few large (10+gb) files.
  6. So, this is an interesting coincidence. I had recently used the advanced option to add the iDRAC 6 docker image to unraid. And it just almost works. It connects, get the needed java libraries/whatever from the iDRAC, but then it fails to actually login I guess? It just gives an unhelpful "Connection failed." in the log. Unfortunately this version does the same thing (as I expected, since it's literally the same thing from domistyle). I know the idrac is working. It's not using anything crazier than a static ip. It's not super out of date, though it's not the newest version. It is just using the default cert. I resorted to setting up a WinXP virtual machine on Unraid instead and it connects just fine and can run the remote control/display part. The only true "fix" to the issue on his github that a user relayed was "reset iDRAC". Which I really just do not want to have to bother doing. So if anybody finds a fix or workaround to this error it would be wonderful. But I have a feeling it's a Dell issue somewhere in their crap that for some reason gunks up what this docker image is doing but doesn't to a normal XP os.
  7. chkdsk didn't return any issues with the drive. But it was indeed plugged in to a USB3 slot. I'll swap it to USB2 and continue monitoring.
  8. Ok, finally the system crashed but kept an error on-screen on the attached monitor. I feel like I know what the issue is, though I'm still puzzled by why it would only crash at a certain time at night. I hope this is the same issue and not something new. So, the error: "whole bunch of gibberish with hex locations and whatnot" FAT-fs (sda1): FAT read failed (blocknr 1941) FAT-fs (sda1): unable to read inode block for updating (i_pos 12544047)
  9. So, I hadn't responded in a while since it was actually stable for a while (didn't have remote plex pointed at it). Decided to point the remote Plex at it again, which seemed to work... for a couple days. Decided to do the update to 6.8.1. Probably should have left well enough alone, crashed again. Last thing in the syslog before the crash is what I assume is a mover entry: Jan 15 05:49:26 ShinseiUNRAID kernel: mdcmd (71): spindown 1 Jan 15 06:00:02 ShinseiUNRAID crond[1652]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null So, I'm going to leave the Plex connected for now and see if it crashes again. If it does, well I'm kinda feeling let down. This was supposed to be the replacement for my Synology NAS but this instability for Plex over the network kinda kills that use.
  10. Yep, which is the same for me. Plex is completely separate hardware from my Unraid box, only connected by networking. Plex isn't crashing, the worst it gets is the connection fails when Unraid crashes/freezes. Well, it was completely separate at least. I spun up the Plex docker I had for messing around and pointed it at all the "local" files (mounted the /user/public/Plex folder on the array to /unraid in the docker, and created 7 libraries pointed at 7+tb of media) and let it run uninterrupted since my last post. No crashes or anything despite load, and even my weekly scheduled Parity check ran last night at the same time. It's still running right now, I believe it's creating the interval screenshots for JoJo's. Now, the unraid box doesn't have nearly the grunt as my external Plex server (stock 2500k vs R610 dual-quad xeon) so maybe that has some to do with it, but the only big difference in what Unraid is doing is that it's not reading over the network to get the files.
  11. 1. PSU is definitely hooked up alright, I tried replugging all the power (and other cables) once. I've never run into a power supply that only died when under heavy hdd reads. I could see one of the hdd being somehow bad and not reflecting that in SMART, but that wouldn't crash the whole system surely? Unraid also finishes Parity checks just fine after each reboot I have to do, and that's stressfull on both the cpu and hdd for long periods of time. 2. Yes, it crashed/froze every time between 3-8, when my Plex server (on another computer) is set to do deep scans of files. And it only started restarting/freezing when I pointed Plex to the new copies of the library on the array and it stopped when I unlinked those libraries. Nothing external writes to Unraid as far as I know, only VM/Docker/Plugins. SSD Trim and Mover are set to run daily, at 4AM and 6AM respectively though, so I could see them possibly interacting? 3. No, for most of the failures it was in a closet with a closed door. Doesn't get hot either. As far as I can tell no issue with the power button. 4. I have one connected now, but that was in effort to eliminate possible power issues and only done right before my first post. I don't have power issues usually (hence the previous 90+ days continuous runtime before these issues), but to be sure I hooked it up anyway. As for my Plex server, I have no issues with it otherwise. Been running fine pointed at the NAS I was trying to replace. It only reads from my unraid box, nothing is being written far as I know when you point a library somewhere. I did notice that when Plex does a deep scan of music files it has a shit-ton of handles/streams open though. The list in the Unraid Active Streams plugin goes crazy, probably 100+ entries at times. Not sure about Maria, it's not ignored far as I can tell. Up-to-date too.
  12. Ok, so I ran the system without Plex hitting it for a week while on vacation. And what do you know, no lockups or restarts. So heavy read loads are what's causing it, though I know it can be not technically it's fault. Syslog was already mirrored to boot days before I posted here, and it appeared to have caught nothing. I remember reading it and there was just a big blank timespan without any kind of information after what looks like normal lines. I'll attach the current syslog while I try to cause a new failure. I'm sure you already know this, but searching for "microcode: microcode updated" line will help find the times where the server was restarted (though some of them are normal restarts as I tried stuff). I'll also attach the current diagnostics after it's been running a while. Power supply is brand new bought for the Unraid build in July. It's also incredibly overkill for Unraid at 650W. My Unraid server pulls from 60-160W depending on load. syslog.7z
  13. I recently bought a key of unraid after testing for around 120 days, with one stretch of 90+ days uptime at the end (so the trial didn't end). As you can see, it was rock-solid stable no problems, except it was slow as crud since I was using 12 old SAN 500 GB drives. Hot (so hot, 40+ idle!), loud, slow, low capacity, but great for testing. I had it in a 2:2:8 setup, parity cache data. Even had a super old pci raid card for the extra sata ports. Did what I wanted, if slow, so great! I decided to buy a key and new hardware on black Friday, and it got reconfigured into 4 4TB drives 1 parity 3 data, and 2 1TB SSD for cache. Ditched the raid card for now. Everything was (and kinda is?) working great! Speeds, temps, loudness, capacity, all great jumps. I'm now held back by my 2500k and gigabit nic more than anything else. And then it started restarting or freezing literally every night in the 3-8am time-frame. Every morning I'd check and it would be sitting there at the array not started (because I turned off autoinit), OR it would be completely unresponsive even to ping and if a monitor+m/k was physically plugged in that would also be unresponsive. So first I thought it might be power or heat, as I moved it into a closet on an old power strip when I reconfigured the hardware. Just ruled that out, connected to UPS it had same issue and heat was never an issue that I could see from the stats. Also nothing else is affected by flickers around the house. Then I tried mirroring the syslog to flash, but there's nothing in there but a gap from when it fails (I assume) until I start it back up. Then I tried upgrading to the just-released 6.8.0, thinking maybe I had some kind of weird software error. No change. Finally, maybe basic hardware, so I ran a memtest (since everyone gets so hot and bothered by it on these forums) for 24+hours, got 11 successes no errors/fails. No SMART errors either So then I started doing all kinds of stuff, plugins and whatnot to see what was going on in that 3-8am timespan. Think I tracked it down to Plex (on a completely different computer) scheduled to deep scan files in that timespan. It would have tons of files open on Unraid at the same time (from looking at the active streams plugin) as it scanned the copied contents of my NAS I setup after getting the new hardware. Since it died most often after 6, when mover starts, maybe something with that too? Failed as early as 3:45am though, so it's definitely not all. TLDR: It appears my separate Plex server kills my Unraid with tons of network reads as it deep-scans files in libraries I pointed to look at the Unraid array share. I'd rather not turn the deep-scan feature off, and this is probably not really Plex's fault. I've done memtest and tried to look in a mirrored syslog file. What do I need to do to get more technical data to look through as syslog doesn't seem to cut it? Diagnostics? Motherboard: ASRock Z77 Pro4 CPU: 2500k Ram: 4GB + 8GB DDR3 (bad setup but it's a friends hand-me-down while he uses my old 1800x computer, huge upgrade for him) No add-in cards 4 WD Red 4TB drives, 2 Samsung 870 evo SSD Also, will probably be unresponsive or slow for next week, sorry if I don't immediately respond. Been trying to fix this for the last two+ weeks before I go on vacation, but finally ran out of patience/exhausted my knowledge. Creating this thread so that I don't forget anything while on vacation! I'm also going to use it as a sorta "test", as I've disconnected my Plex server from Unraid and I'm going to see if it crashes any while I'm gone.
  14. I've not been using Unraid very long, still in the trial phase. I like it since it's so much simpler to use than FreeNAS or similar. So maybe I'm doing something incredibly wrong with this image and MariaDB, but I get just abysmal performance and tons of problems despite following the tutorial as best as I can tell. I first had really bad problems getting Nextcloud to use the db correctly. I'm still not sure it really is using it right. I was doing the initial setup, and it was timing out with a 504 error. But it definitely was connecting and adding tables with data, so I don't know what the issue is. I tried wiping the dockers and their data and completely restarting a few times. Then I tried just doing the Nextcloud setup twice in a row. User/pass already exists (despite being on the initial setup page). So I used a different combo and it finally went through, but only if I logged in using the first time's combo. Ok.... Then I went through the normal setup on a desktop, and it is technically working... but it's just f'ing terribly slow. I know it's not a bandwidth issue, if I throw one large file in there it downloads/uploads super fast just fine. But throw in a folder with even a few hundred small files and it just grinds to a halt. Less than one file per 5 seconds is transferred. And I can hear the drives super thrashing, constantly. Nothing else running on the server does this. It's not a bad drive as I've even tried moving around mapped folders to get it working better. Cache doesn't help. Just straight-up moving the files to the server in an open share is super-fast (for tons of tiny files to non-ssd) and finishes in literal seconds. I'm obviously screwing something up with one of these docker images, but I don't know what. Does anyone have any tips?