Antoine Rincent

Members
  • Posts

    15
  • Joined

  • Last visited

Recent Profile Visitors

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

Antoine Rincent's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Ahhh thank you so much I didn't know, I thought MB Temp was the motherboard's chipset temperature! Thanks again!
  2. When I click on the pulldown I only get CPU and MB temps... could it be because there's an options mismatch? Thanks again for your help!
  3. Thanks for your answer! I'm not sure how to use coretemp, when I'm using the sensor command in the terminal to access these (following the logic in this writeup), I only can see one temperature for the CPU Temperature, could you detail the process a tad more? Thanks a lot!
  4. Hi everybody! I have a very noobish question, but can't find a straight answer to anywhere, I have an unRAID machine running on an AMD 1700x cpu, with an aio water cooler and I noticed that whenever I was pushing the CPU (80+% CPU usage), the temperatures would rise up to about a 90°C plateau. I've found online reports that mentionned that the CPU/Motherboard (an asus crosshair hero 6) has a +20°C offset on the CPU for control purposes, and was wondering if the temperature reported by unRAID (using the Dynamix System Temperature plugin) was the temperature with or without that offset. I've tried maxing out my fan curves in the motherboard's BIOS and even then, I plateau at roughly 85°C, hence why I'm starting to wonder if it's actually plateau-ing at 65°C, which would make much more sense from that CPU with the amount of cooling it's getting. Thanks a lot!
  5. Hi! I've been using a low power Ubuntu VM on my unRAID machine for a while now, and it unexpedly stopped booting up, when I access it (through VNC remote), I just get a black screen, and all search results return about everything relating to GPU passthrough but this isn't my issue as I'm not using one in this VM. I believe the problem might stem from the fact that I made this VM have access to two shares of my unRAID machine, which was quite an hassle to setup because apparently it isn't officially supported behavior, but I'm unsure. I'm too much of a noob in both ubuntu and unRAID to be able to figure out what the issue is. I've tried to SSH to it from my PC, and the connection timed out as if the VM wasn't connected to my network, even though according to my router it has an IP and an accurate uptime, so I'm wondering what's going on! Here are the logs, pasted as text since they're short, but if you'd prefer a file I'd be happy to oblige! Thank you so much for your help! -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=utc,driftfix=slew \ -global kvm-pit.lost_tick_policy=delay \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 \ -device pcie-root-port,port=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 \ -device pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 \ -device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 \ -device pcie-root-port,port=0x14,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 \ -device pcie-root-port,port=0x15,chassis=6,id=pci.6,bus=pcie.0,addr=0x2.0x5 \ -device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x7.0x7 \ -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x7 \ -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,addr=0x7.0x1 \ -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,addr=0x7.0x2 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.4,addr=0x0 \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/Synology Sync/vdisk1.img","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-1-storage"}' \ -device virtio-blk-pci,scsi=off,bus=pci.5,addr=0x0,drive=libvirt-1-format,id=virtio-disk2,bootindex=1,write-cache=on \ -fsdev local,security_model=passthrough,id=fsdev-fs0,path=/mnt/user/Antoine/ \ -device virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=antoine,bus=pci.1,addr=0x0 \ -fsdev local,security_model=passthrough,id=fsdev-fs1,path=/mnt/user/Musique/ \ -device virtio-9p-pci,id=fs1,fsdev=fsdev-fs1,mount_tag=musique,bus=pci.2,addr=0x0 \ -netdev tap,fd=34,id=hostnet0,vhost=on,vhostfd=35 \ -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:72:ed:6b,bus=pci.3,addr=0x0 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=36,server,nowait \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device usb-tablet,id=input0,bus=usb.0,port=1 \ -vnc 0.0.0.0:0,websocket=5700 \ -k fr-ca \ -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pcie.0,addr=0x1 \ -device virtio-balloon-pci,id=balloon0,bus=pci.6,addr=0x0 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2020-12-14 14:22:08.714+0000: Domain id=1 is tainted: high-privileges 2020-12-14 14:22:08.714+0000: Domain id=1 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0)
  6. Yeah! I've limited the RAM to 4 Gb, but my container hasn't gone above 3.3 for the time being
  7. Going to latest right away worked flawlessly, just had to change the tag in the docker container settings and bam, that was it, what I meant is that the downgrades aren't working perfectly, but no matter, latest works fine for me, except for the memory leak but it isn't too bad an issue for my installation
  8. After downgrading back to 5.9 it worked well, but since I wanted the newer features I just used the latest tag, and tried to downgrade to LTS from there, but it wouldn't work either, if you find a good way to do so, please say so, but for now I'm running on the latest version
  9. Hey guys! I'm a newbie with using the unifi controller, but wanted to update mine, right now I'm using the 5.9 tag, and wanted to upgrade to the LTS tag, as I saw above that 5.11 was pushed on it, and I'm a big believer in the "set it and forget it" mentality, I changed the tag in the docker container and it all worked perfectly, but once trying to go in, I was greeted with the error message "we do not support upgrading from 5.9.xyz", did I forget a step, or do I need to restart from a blank slate? I reverted back to the 5.9 tag and it works like before. Browsing the unifi forum I found that people recommend pushing a certain command in the cloudkey once SSH'd into it, but I'm unsure if it would be the same for the docker container version of the controller and wanted to make sure before bricking it! Thanks a lot!
  10. Hi! Might be a dumb question, but how do you upgrade to 5.11? In the docker documentation I only see it going up to 5.9 or latest, do you simply change the name of the repository to linuxserver/unifi-controller:5.11 ? Also, will doing only this and reloading the docker container be sufficient to update the controller, or is there more to do too afterwards? I'm a huge newbie to docker and unifi so sorry again if these are stupid questions! Thanks!
  11. Turns out the issue was due to a pop-up blocker keeping the login page from showing up at launch of the webUI, dumb mistake, but an easy fix, thanks anyways!
  12. I'm allowing myself to give a quick bump, I'm guessing that the issues I have where Plex's web UI gets stopped at a blank page is an error caused on the Plex side of things, and not on the Docker side of things, as in the log file it says "Starting Plex Media Server. done." ? Any help is appreciated, thanks!
  13. Sorry for my mistake! Here it is : root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='plex' --net='host' --cpuset-cpus='9,11,13,25,27,29' --privileged=true -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'VERSION'='docker' -e 'NVIDIA_VISIBLE_DEVICES'='' -e 'TCP_PORT_32400'='32400' -e 'TCP_PORT_3005'='3005' -e 'TCP_PORT_8324'='8324' -e 'TCP_PORT_32469'='32469' -e 'UDP_PORT_1900'='1900' -e 'UDP_PORT_32410'='32410' -e 'UDP_PORT_32412'='32412' -e 'UDP_PORT_32413'='32413' -e 'UDP_PORT_32414'='32414' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/Movies/':'/movies':'rw' -v '/mnt/user/TV Shows/':'/tv':'rw' -v '/mnt/user/Musique/':'/music':'rw' -v '':'/transcode':'rw' -v '/mnt/user/Anime/':'/anime':'rw' -v '/mnt/user/appdata/plex/':'/config':'rw' 'linuxserver/plex' 509b5dead9fef8b90d3a7afdfb86d0959e1967ade32f6b0d9c5be72f4ef7843b The last two lines of my log file are : Starting Plex Media Server. [services.d] done.
  14. Hi! I was hoping I could get some help on setup, I've setup the Plex docker container with the different librairies, the logs seem normal, but when I connect to the WebUI, I just get an empty page with the Plex logo at the center, and nothing else, when it's loading I get more of the "normal" Plex UI with the different bars of the menu appearing for +/- 1s., then it all just disappears and stays on the "Plex" logo, would this be an issue with Plex as is, or rather an issue with the container? I tried using the plexinc docker container and had the same behavior, if that can help! Thanks a bunch!