Dstubbs28

Members
  • Posts

    15
  • Joined

  • Last visited

Everything posted by Dstubbs28

  1. Where are the logs for UPS activity held?
  2. So, someone I suggested to use unraid misplaced his root password and told me about this. Please fix this, as it should not be that easy to gain full access to your entire server.
  3. Yes. I just realized that since this started happening I also now have a mariadb docker running, I have that running on 3307, but the default port is 3306. Could they be conflicting?
  4. My password no longer works on guac, tried the default un/pw as well (thinking config reset) and still nothing.... How do I fix this?
  5. My hardware worked fine before 6.6. Iommu groups were separated properly. Thats like someone telling a guy with a flat tire fresh out of the tire shop that he should of bought a better car
  6. Well thats part of the issue, with ACS on, off, multipurpose or downstream, the iommu groups remain the same.
  7. Upgraded to 6.6, I can no longer pass through my USB controller to my VM (which means no hotplugging) as the IOMMU group now stays locked no matter what ACS patch override mode I chose. My NVME drive is now in the same group as my PCIE usb card (1106:3483), which is a huge problem. I had an older bios before the upgrade, updated the bios once I saw the iommu groups are completely borked, no change. Anyone have any ideas how to remedy this? # for iommu_group in $(find /sys/kernel/iommu_groups/ -maxdepth 1 -mindepth 1 -type d);do echo "IOMMU group $(basename "$iommu_group")"; for device in $(\ls -1 "$iommu_group"/devices/); do if [[ -e "$iommu_group"/devices/"$device"/reset ]]; then echo -n "[RESET]"; fi; echo -n $'\t';lspci -nns "$device"; done; done IOMMU group 7 [RESET] 00:1b.0 PCI bridge [0604]: Intel Corporation Cannon Lake PCH PCI Express Root Port #19 [8086:a342] (rev f0) [RESET] 00:1b.3 PCI bridge [0604]: Intel Corporation Cannon Lake PCH PCI Express Root Port #20 [8086:a343] (rev f0) [RESET] 00:1b.4 PCI bridge [0604]: Intel Corporation Cannon Lake PCH PCI Express Root Port #21 [8086:a32c] (rev f0) [RESET] 02:00.0 USB controller [0c03]: VIA Technologies, Inc. VL805 USB 3.0 Host Controller [1106:3483] (rev 01) [RESET] 03:00.0 PCI bridge [0604]: Integrated Technology Express, Inc. IT8892E PCIe to PCI Bridge [1283:8892] (rev 71) [RESET] 05:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961 [144d:a804] IOMMU group 5 00:16.0 Communication controller [0780]: Intel Corporation Cannon Lake PCH HECI Controller [8086:a360] (rev 10) IOMMU group 3 00:12.0 Signal processing controller [1180]: Intel Corporation Cannon Lake PCH Thermal Controller [8086:a379] (rev 10) IOMMU group 1 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) [8086:1901] (rev 07) [RESET] 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) 01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 580] [1002:aaf0] IOMMU group 8 [RESET] 00:1c.0 PCI bridge [0604]: Intel Corporation Cannon Lake PCH PCI Express Root Port #5 [8086:a33c] (rev f0) [RESET] 06:00.0 Ethernet controller [0200]: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller D0/D1 (copper applications) [8086:105e] (rev 06) [RESET] 06:00.1 Ethernet controller [0200]: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller D0/D1 (copper applications) [8086:105e] (rev 06) IOMMU group 6 00:17.0 SATA controller [0106]: Intel Corporation Cannon Lake PCH SATA AHCI Controller [8086:a352] (rev 10) IOMMU group 4 00:14.0 USB controller [0c03]: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller [8086:a36d] (rev 10) 00:14.2 RAM memory [0500]: Intel Corporation Cannon Lake PCH Shared SRAM [8086:a36f] (rev 10) IOMMU group 2 [RESET] 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 630 (Desktop) [8086:3e92] IOMMU group 10 00:1f.0 ISA bridge [0601]: Intel Corporation H370 Chipset LPC/eSPI Controller [8086:a304] (rev 10) 00:1f.3 Audio device [0403]: Intel Corporation Cannon Lake PCH cAVS [8086:a348] (rev 10) 00:1f.4 SMBus [0c05]: Intel Corporation Cannon Lake PCH SMBus Controller [8086:a323] (rev 10) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller [8086:a324] (rev 10) 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (7) I219-V [8086:15bc] (rev 10) IOMMU group 0 00:00.0 Host bridge [0600]: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers [8086:3ec2] (rev 07) IOMMU group 9 [RESET] 00:1d.0 PCI bridge [0604]: Intel Corporation Cannon Lake PCH PCI Express Root Port #9 [8086:a330] (rev f0) [RESET] 07:00.0 Non-Volatile memory controller [0108]: Intel Corporation SSD 600P Series [8086:f1a5] (rev 03) dmserver-diagnostics-20180925-2237.zip
  8. Trying to set up duo... Ive put all the relevant info into guacamole.properties but I get the following error when logging into guac: I can curl ipinfo.io/ip so i know that the docker can at least access the outside world, and /var/log/* does not show any kind of errors (I dont know which one i should of checked, so I checked them all, none of them have any error relating to this...)
  9. This is awesome, and confirmed it worked for me. Thank you!
  10. Not with this kitten... Unless I want to have an 'ugly' solution.
  11. Sadly not a Bios option as thats a venue i already explored... I'll have to do the cp each boot then. (I do wish it was an unraid option though...) Thanks Saarg
  12. This option should be in /etc/acpi/acpi_handler.sh if I am not mistaken, but each time i edit this file, when the server is rebooted.. the file reverts to its original lines. Commenting out the lines in this file does indeed turn off the ability to short press the power button, but I want to make it permanent. (I have case with a pbutton on top, and I have cats) Thanks all!
  13. Yeah im not sure why hes so against a password.. its just a VNC server, and with no UN/PW all you have to do is be on the network to get root access. Mind you all you could really do is mess things up and not get data off it... but still I dont want some malicious person getting in and deleting all my stuff due to a lack of a pw on VNC.