• Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About Cobragt88

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. IT UPDATED to a newer version. as well on the first boot after the kernel panic. It has not crashed sense Friday knock on wood. As you said the Nvidia driver caused the problem hopefully this new version fixes the problem. Also plex uses the Nvidia driver for transcoding i can not remove it. Thxs for the advise will keep you posted if it happens again. Oh btw it was completely locked up I had no chance to get the diag when it happened.
  2. not sure what happened but here is the diag file. It's been over 12 hours sense the error but I thought I'd pass this on too see if its something to do with my setup or a Linux problem
  3. Sweet worked like a champ. No errors so far. Thanks for this.
  4. Hi, Thanks for a great stable docker app, just wanted to know if an update was coming soon as I keep getting notices when I login to the web UI that there is a new version of the controller software. Would be nice when I click dismiss and don't show me this notice again that it doesn't come back, it does that's the only problem I'm having minor. thanks again for all this great work on this great docker. Is it possible to update to 6.0.36?
  5. when you go too add the vm iso it does not show the iso your looking for, it only shows old ones you have used? This is on beta 30 it didn't happen on beta 29.
  6. So everyone not sure if this is a bug but I thought i'd post it. I increased a vdisk by mistake & like normal I was going to use command line to resize the vdisk. I get this this error now.... /mnt/user/domains/Windows Server 2019# qemu-img resize vdisk2.img 30G WARNING: Image format was not specified for 'vdisk2.img' and probing guessed raw. Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted. Specify the 'raw' format explicitly to remove the restrictions. qemu-img: Use the --shrink option to
  7. hmmm. OK so i switched the one VM to 5.0 from 3.0. Is there a way to clear the log minus doing a full reboot?
  8. Ok here is the log at 100%. root@LoweNAS:~# df -h /var/log Filesystem Size Used Avail Use% Mounted on tmpfs 384M 384M 0 100% /var/log root@LoweNAS:~# du -sm /var/log/* 1 /var/log/ 1 /var/log/ 0 /var/log/btmp 0 /var/log/cron 0 /var/log/debug 1 /var/log/dmesg 0 /var/log/docker.log 0 /var/log/faillog 0 /var/log/lastlog 1 /var/log/libvirt 0 /var/log/maillog 0 /var/log/messages 0 /var/log/nfsd 1 /var/log/nginx 0 /var/lo
  9. Thought I'd bring this up, my routing table is wrong or is this the new behavior of 6.9? I don't have any /25 networks. So why did it add a /25? Also can't delete those /25 either. On 6.8.3 there was a no /25 networks on my routing table.
  10. Got a small problem with beta 25. My log file gets to 100% in a few days. This never happened before on 6.8.3. Just thought i'd say something, other than that, I don't have any problems with this version.
  11. Hello first great docker app. Got a minor bug that I thought I'd pass on. Anytime I try too add the private torrent tracker Torrentday it gives me an error. "Request to Jackett Server Failed". From the log file : at Jackett.Server.Middleware.CustomExceptionHandler.Invoke(HttpContext httpContext) in /home/vsts/work/1/s/src/Jackett.Server/Middleware/CustomExceptionHandler.cs:line 70 System.Exception: Error parsing JS challenge HTML in red. That seems to be every time I try too add The Tracker as an Indexer. If required more logs I can.
  12. saw it briefly on the main console screen when I logged in. What's the best command to detect any xfs errors on any disks? FYI I was able to fix the xfs errors on disk 8. Seems all is back to normal now.
  13. Hi was hoping I can get some help fixing the xfs errors. Thanks