Biomatrix

Members
  • Posts

    9
  • Joined

  • Last visited

Everything posted by Biomatrix

  1. Sorry, my Typing was bad. I have used the plugin on an other hardware. I have hit apply a few times - output of the command requested : root@Fermentor:~# more /boot/config/plugins/gpustat/gpustat.cfg VENDOR="nvidia" GPUID="GPU-5c634d50-acf3-3243-6e8c-ff426f210ea4" TEMPFORMAT="C" DISPCLOCKS="1" DISPENCDEC="1" DISPPCIUTIL="1" DISPTEMP="1" DISPFAN="1" DISPPWRDRAW="1" DISPPWRSTATE="1" DISPTHROTTLE="1" DISPSESSIONS="1" UIREFRESH="1" UIREFRESHINT="1000" DISPMEMUTIL="1" DISP3DRENDER="1" DISPBLITTER="1" DISPVIDEO="1" DISPVIDENH="1" DISPINTERRUPT="1" DISPEVENT="1" DISPVERTEX="1" DISPTEXTURE="1" DISPSHADEREXP="1" DISPSEQUENCER="1" DISPSHADERINTER="1" DISPSCANCON="1" DISPPRIMASSEM="1" DISPDEPTHBLK="1" DISPCOLORBLK="1" DISPGFXTRANS="1" but I will say I did update to RC3 today - and then did this process : changed Vendor to : Change Me Hit Apply changed Vendor to : NVIDIA Hit Apply and everything is fixed. I did do this in RC2, but it didn't really help. I am not sure why it works now. but consider my issue solved.
  2. I wish that was it, but this USB device, and server never had the old hard installed.. it shows only a single card, and that's the current (new) card (pictures show that only a single option is there anyway)
  3. hello! don't know if this is the right way to report this, but I do not get any population of the plugin with my new GPU (Nvidia T600) nvidia-smi -q -x -i 0 :
  4. so, I am closing this - I have not experenced even a studder since I removed those 2 items,
  5. UPDATE : so I have disabled 2 user scripts that I brought over from my older box. disabling them seems to have fixed it (so far) Nvidia was the last peice that wasn't really disabled - so I did these scripts first... I don't even know if they are nessary anymore? Nvidia-Persistance-First #!/bin/bash nvidia-smi --persistence-mode=1 Nvidia-Power-Reduction #!/bin/bash gpupstate=$(nvidia-smi --query-gpu="pstate" --format=csv,noheader); gpupid=$(nvidia-smi --query-compute-apps="pid" --format=csv,noheader); if [ "$gpupstate" == "P0" ] && [ -z "$gpupid" ]; then nvidia-smi -pm 1; fuser -kv /dev/nvidia*; fi; Either way; I will come back in another day or two to report if nothing else.
  6. yea... new syslog - this is where it crashes/reboots after 5 hours of idle... Jan 30 05:24:16 Fermentor emhttpd: read SMART /dev/sde Jan 30 05:25:16 Fermentor kernel: sd 11:0:3:0: attempting task abort!scmd(0x00000000de361d93), outstanding for 60341 ms & timeout 60000 ms Jan 30 05:25:16 Fermentor kernel: sd 11:0:3:0: [sde] tag#1003 CDB: opcode=0x4d 4d 00 40 00 00 00 00 00 04 00 Jan 30 05:25:16 Fermentor kernel: scsi target11:0:3: handle(0x000d), sas_address(0x5000c50084f99f3d), phy(7) Jan 30 05:25:16 Fermentor kernel: scsi target11:0:3: enclosure logical id(0x50030480091bdf7f), slot(7) Jan 30 05:25:16 Fermentor kernel: scsi target11:0:3: enclosure level(0x0000), connector name( ) Jan 30 05:25:16 Fermentor kernel: sd 11:0:3:0: task abort: SUCCESS scmd(0x00000000de361d93) Jan 30 05:30:14 Fermentor kernel: Linux version 5.14.15-Unraid (root@Develop) (gcc (GCC) 11.2.0, GNU ld version 2.37-slack15) #1 SMP Thu Oct 28 09:56:33 PDT 2021 Jan 30 05:30:14 Fermentor kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot Jan 30 05:30:14 Fermentor kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Jan 30 05:30:14 Fermentor kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Jan 30 05:30:14 Fermentor kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Jan 30 05:30:14 Fermentor kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Jan 30 05:30:14 Fermentor kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. Jan 30 05:30:14 Fermentor kernel: signal: max sigframe size: 1776 Jan 30 05:30:14 Fermentor kernel: BIOS-provided physical RAM map: So... i'm going down the line; going to disable Nvidia. Memory tested good - all 384GB of it... LOL can redo a test again. there was no change in the system from the previous 64GB ram, to this 384GB from the dell, the crashes happened then too. I do apprecate everyone!
  7. you know what - I don't know. I've only recently built this server; and have been chasing little issues(had zero issues on my dell) I can't say it's consistantly with a Parity, because sometimes I come back when i've started a partity to a clean run... but it's worth a shot for sure. I will attempt this and come back with more (or less?) information!
  8. so, this has happened before, I thought I fixed it with removal of CPU FREQ plugin... but it seems I have not. in this particular instance - I left the server doing a Parity check, and came back to the main showing 8 of the 10 disks in the array as "missing" - hard reboot brought everything back. attached is the last diagnostic that was on the Flash, as well as the syslog. (mirrored to flash until it gets stable) last time I touched the server was Jan 28 - around 17:30 hr the manual/forced reboot was around Jan 29; 11:30 Hr syslog fermentor-diagnostics-20220128-1817.zip