whoopn
Members-
Posts
20 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by whoopn
-
I'm seeing some behavior that I wasn't expecting, I'm trying to share some folders from Unraid through to a VM, the ones from my actual array I'm able to mount with the fstab commands below, but the one going to an unassigned device (that is mounted), I cannot write to the ones on the unassigned device. I've tried all manner of what should be unnecessary chown commands (file are all 777 right now). What am I missing? The exact same thing happened with a VM Unraid share from the cache drive...what am I missing? Additional info: There are hardlinks to the folder (no idea from where) cat /etc/fstab | grep virtio PS_Library /mnt/PS_Library 9p trans=virtio,version=9p2000.L,_netdev,rw 0 0 HousePhotos /mnt/HousePhotos 9p trans=virtio,version=9p2000.L,_netdev,ro 0 0 AppCacheData /mnt/AppDataCache 9p trans=virtio,version=9p2000.L,_netdev,rw 0 0 I can write to PS_Library all day long... Thanks for any assistance in advance!
-
Yes, I’ve reverted to 6.8.3 and have been up and running with no issues for 4 days, 6.9.1 would have crashed by now. Perhaps the UNRAID devs could compare what in the network stack changed and revert that change as it’s a regression. I think I speak for most unraid users that reliability is far more important than feature set. Reliability is the reason I’ve stayed on unraid.
-
I'm experiencing the exact same issue. On 6.8.3 I had ZERO issues, rock solid, I upgraded for NVIDIA GPU support so that is the only new thing. Yes I have br0 docker IP assignments, its never been a problem, even have VMs and Dockers sharing br0, no issues still. Limetech, this is a pretty serious issue, what do you need from me to investigate further? Are there logs I can upload? Thank you in advance!
-
Nevermind I'm an idiot
-
I had an issue where a drive was corrupted, and the xfs_repair tool was unable to find any suitable superblocks. Now I'd assume that a "good" disk would return something about good superblocks found and good magic numbers when you initially run it (xfs_repair -n /dev/sdX). However all of mine are returning bad superblocks and bad magic numbers. My question is two-fold: 1. Does it matter? 2. Is there some routine maintenance I should be running?
-
I'm not sure the data logger does that, its expecting the database to be created for it. Is there a way to create the database manually? Here are the instructions I am following: http://codersaur.com/2016/04/smartthings-data-visualisation-using-influxdb-and-grafana/ I appreciate your help BTW!
-
Will it create the database for me? This seems unsecure and different than other database technology i've used.
-
I get the following: { "error": "error parsing query: found AND, expected ; at line 1, char 40" } Do I need telegraf for this to work? I'm just using it as a database for grafana, my smartthings is going to spit data into the database
-
Still no go, this was me troubleshooting earlier before I changed the ports back to stock, should've changed my screenshot. I don't know what credentials to use, does it need any? What about creating a database? I haven't done that either.
-
Ok I must be missing something that everyone else seems to know already. I installed the Influx and Grafana dockers. Grafana works like a charm. Influx though I'm not sure if its up at all. I tried enabling the web interface but I still get a 404 I honestly don't care if I have a web interface but I have no idea how I'm supposed to interact with the db as a docker on unraid in any other way. What I'm really going for here is this page to complete successfully: I literally don't know what to fill in the fields with b/c I wasn't able to define any of these settings somewhere. I would really really appreciate any assistance as this is my first go at influx and grafana. I swear I'm not stupid, but I encounter issues like this and I have my doubts...
-
[Support] Linuxserver.io - Plex Media Server
whoopn replied to linuxserver.io's topic in Docker Containers
I have a question regarding the multiple IPs that are unavoidable on Docker (the host IP -in the 10.0.1.0 range- and the docker0 interface in the 172.16.1.0 range). How can I force plex to only work over a single interface? My TV's plex app wont work otherwise. I'd like to specify the 10.0.1.0 range to be used. I disabled docker0 and it worked great but NONE of my other docker apps work then. -
Ok so I was using rsync in mobaxterm to do this, that was causing the slowness. Direct copy with windows is far quicker, especially using the cache device.
-
I'm getting around 25MB/s sustained whether I use the cache drive or not. I've used the exact same machine before with the same drives on ZFS and was able to fill a 1Gb pipe all day long. On system it was around 250-300MB/s. Bumping everything to jumboframes (unsurprisingly) didn't change anything. Everything is going over two PCI-E cards save for the parity drive which is going directly to the onboard sata ports (its like an ICHR10 or whatever). Everything is reporting at least SATA 2.6 (3Gb/s) = 375MB/s (the drives can't even do that so anything more for a spinner is silly) Ideas? What information would be helpful? Attached is a screenshot of stuff.