tronyx

Members
  • Posts

    37
  • Joined

  • Last visited

About tronyx

  • Birthday 05/16/1986

Converted

  • Gender
    Male
  • URL
    https://tronflix.app
  • Location
    Pennsylvania, USA
  • Personal Text
    Have you tried turning it off and on again?

Recent Profile Visitors

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

tronyx's Achievements

Newbie

Newbie (1/14)

5

Reputation

  1. Anyone else having their Telegraf container not start w/ the following errors? ERROR: Unable to lock database: Permission denied ERROR: Failed to open apk database: Permission denied I believe it is an issue with this command now for some reason: /bin/sh -c 'apk update && apk add smartmontools nvme-cli && telegraf' EDIT: Looks like pinning the image to the 1.19.2-alpine tag fixed it so they must've broken something.
  2. *sigh* We don't see it anywhere. Rox was simply making sure you were, in fact, browsing to organizr.domain.com and not just domain.com. Just a measure of validation, that's all.
  3. We didn't see it, but Rox asked you because people have done that before and, since nothing is standing out as obvious to us as to what the issue could be, we're asking everything we can think of. Either your containers are not up to date or you have another Nginx instance running either in another container or installed natively on the System that is running Docker. root@suladan:~# docker exec -it organizr nginx -v nginx version: nginx/1.20.1 root@suladan:~# docker exec -it swag nginx -v nginx version: nginx/1.20.1
  4. Yes, we did, but you didn't answer the question. Are you LITERALLY browsing to organizr.domain.com or are you replacing domain.com with your ACTUAL domain? Also, those error pages show Nginx version 1.18. Both the SWAG and Organizr containers are running Nginx version 1.20 so you're either VERY out of date or you're running something else that is using Nginx.
  5. That is a directory, not a file, but yes, it exists already, or at least it should. If not, create the directory.
  6. That should be it, per the docs.
  7. No, the command is this: touch /boot/config/modprobe.d/amdgpu.conf That will create an empty file called amdgpu.conf in the /boot/config/modprobe.d/ directory. You will need to create the correct file that corresponds to your GPU type. If it is an Intel integrated GPU, like with my issue, you will need to create the i915.conf file instead of the amdgpu.conf file. This will cause it to overwrite the file that exists to blacklist the driver.
  8. What command? The doc outlines creating a file on the flash drive which is persistent between reboots.
  9. After upgrading to 6.9, I followed the docs to whitelist the i915 driver, as they're now blacklisted by default, as outlined HERE. Then I removed the original entry I had made to the /boot/config/go file to get things working with 6.8.3, and rebooted.
  10. I removed them as they are no longer needed, per the 6.9 docs. Also, please see my edited reply above as I found the real issue and resolved it.
  11. For anyone else that may encounter the same issue, I was able to resolve my issue on 6.9 by removing the nomodeset commands in my /boot/syslinux/syslinux.cfg file, like so: root@Morgoth:~# cat /boot/syslinux/syslinux.cfg default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append initrd=/bzroot label unRAID OS GUI Mode kernel /bzimage append initrd=/bzroot,/bzroot-gui label unRAID OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label unRAID OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest I do not remember explicitly adding them myself previously, but it is very possible that I did to get things working on 6.8.3.
  12. Was running 6.8.3 with functional iGPU/QS transcoding w/ Plex. Upgraded to 6.9 this morning and now the /dev/dri directory is missing. Found the section in the Wiki that explains the drivers being blacklisted, created the necessary file to whitelist it ( /boot/config/modprobe.d/i915.conf ), rebooted the server, but /dev/dri is still missing. Removed the original lines I had previously added to the go file in 6.8.3 and rebooted, but still no dice. The Server had been rebooted several times before with no issues and nothing has changed within the BIOS settings. My Server is essentially useless at the moment, so any help would be greatly appreciated. Mobo: Supermicro X11SCH-F CPU: Intel Xeon E-2246G Everything points to the fact that it SHOULD be working: root@Morgoth:~# lsmod | grep -i 'i915' i915 1712128 0 iosf_mbi 16384 1 i915 drm_kms_helper 163840 1 i915 drm 356352 2 drm_kms_helper,i915 intel_gtt 20480 1 i915 video 45056 1 i915 i2c_algo_bit 16384 2 igb,i915 backlight 16384 3 video,i915,drm i2c_core 45056 8 drm_kms_helper,i2c_algo_bit,igb,i2c_smbus,i2c_i801,i915,ipmi_ssif,drm root@Morgoth:~# modinfo i915 filename: /lib/modules/5.10.19-Unraid/kernel/drivers/gpu/drm/i915/i915.ko.xz license: GPL and additional rights description: Intel Graphics author: Intel Corporation Output of the above is the same on both 6.8.3 and 6.9. Although lspci -k doesn't show it is in use, like it used to on 6.8.3: 00:02.0 Display controller: Intel Corporation HD Graphics P630 Subsystem: Super Micro Computer Inc Device 1b11 Kernel driver in use: i915 Kernel modules: i915 Compared to 6.9: 00:02.0 Display controller: Intel Corporation CoffeeLake-S GT2 [UHD Graphics P630] Subsystem: Super Micro Computer Inc Device 1b11 Kernel modules: i915 Running modprobe i915, which should no longer be necessary anyway, doesn't make /dev/dri show up either. Doesn't seem to matter whether or not the array is started either. Diagnostics are attached in case they might be of any help. morgoth-diagnostics-20210302-1228.zip
  13. This is awesome! Thanks so much for putting it together. I don't suppose you'd be willing to share your dashboard for this for easy replication of the above panels?
  14. Pardon my ignorance here, but what is the benefit of this? Is this something that one *SHOULD* be doing? Are there any disadvantages to this?
  15. Been trying to get RDP-BOINC running with Rosetta@home since Sunday and every time I try to connect I receive a "this project is temporarily unavailable" message. I can connect to other projects fine, but I want to add the Rosetta one. Anyone seeing the same issue or have any suggestions?