Jaster

Yes, its after rebooting, but it already "crashed" the pool by dropping out the first drive. As said, I did replace cables, and changed the port. The Isse was still reoccuring. Right now I removed the drive, but this (of course) killed my pool. I keep having issues with corrupted cache over and over again. I'm wondering if it is the drives or BTRFS?

Hi Guys, I'm experiencing an SSD dropping out of the cache array. I checked/changed the cables, ports, etc. Keeps happening. Is that thing dead or do I have another issue? Diagnostics attached. knowlage-diagnostics-20190805-1837.zip

Hi Guys, I just had a cooler failure and relaized, there is no way to get notified about it. While hard disk temperatures can create notificaions, those for CPUs, GPUs, etc can not. Is there a way to achive this?

I changed my HBA but seem to have an issues with some older drives. It seems the serial is not recognized correctly/has changed due to the controller: Diagnostics are attached - can I just use "new config"? knowlage-diagnostics-20190803-2116.zip

anyone? any ideas?

Works. Thanks! But... what would be the file name for this container: mcr.microsoft.com-mssql-server-2017-latest.png does not do the trick

Hi Guys, Simple question; how can I set a docker Icon to an image on the array/localhost instead of putting it somewhere on the net?

Hi Guys, I'd like to run the MSSQL Docker on unraid but I have no idea what it is telling me after I try starting it: /opt/mssql/bin/sqlservr: Invalid mapping of address 0x14fc0f8c7000 in reserved address space below 0x400000000000. Possible causes: 1) the process (itself, or via a wrapper) starts-up its own running environment sets the stack size limit to unlimited via syscall setrlimit(2); 2) the process (itself, or via a wrapper) adjusts its own execution domain and flag the system its legacy personality via syscall personality(2); 3) sysadmin deliberately sets the system to run on legacy VA layout mode by adjusting a sysctl knob vm.legacy_va_layout. Hints? Ideas? Thanks!

Its 50kb supervisor and ~8kb the other logs. fresh setup, not much happening there.

ts logs.rar

ts logs.rar root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-teamspeak' --net='host' --log-opt max-size='10m' --log-opt max-file='1' --privileged=true -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -e 'UDP_PORT_9987'='9987' -e 'TCP_PORT_30033'='30033' -e 'TCP_PORT_10011'='10011' -v '/mnt/user/apps':'/unraid':'rw' -v '/mnt/user/apps/binhex-teamspeak':'/config':'rw' 'binhex/arch-teamspeak' supervisor log is included in the archive

Yes, I'm sure. I gave it an extra try right now for sever containers Here are some logs ts logs.rar Actually I did try host and bridge... Same story. There is one log line 2019-06-20 12:42:38.021304|INFO |CIDRManager | |updated query_ip_whitelist ips: 127.0.0.1/32, ::1/128, Which seems strange... would that not be a whitelist to local only?...

My port forwarding seems fine and works for several other dockers, etc. I can reach the TS server only from my local network using the ip, not the dns name of the server.

Keep receiving the same error

Hi Guys, I can't forward the ports. I do have forwarding for several other dockers setup and running (via duckdns), but I just can't get that one to get going. The server runs on local network, but can't reach it via duckdns or my public ip. Any Suggestions?