iamnypz

Members
  • Content Count

    20
  • Joined

  • Last visited

Community Reputation

0 Neutral

About iamnypz

  • Rank
    Newbie

Recent Profile Visitors

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

  1. I have the same issues. VMs been rock solid on 6.8.3 and upgraded to 6.9.1 and then 6.9.2 and the load is generally low on the VM but super laggy after about 24hrs of uptime on the VM and/or the unRAID server. I have no GPU passtrough though. Edit: At glance, it seems like changing the scaling governor actually helps. Strange. Never been an issue for me earlier. Had it schedueled for "power save" from 0100-1600hrs and "performance" 1600-0100 hrs. Changing it to "on demand" reduced VM lag as it seems.
  2. Hi, I just upgraded to 6.9.2 and I get theese errors as well. Haven't changed anything regarding network. Log as follows:
  3. Nvidia's Virtualization Unlocked On Gaming GPUs via Hack | Tom's Hardware
  4. Wow, how could I have missed that? Fixed it! takk så mye!
  5. As of today/night, my Organizr is broken. I get a "fatal error" on the webpage and nothing shows for some reason (see attached image). When i look at the logs, the two lines i marked with red colour stands out. Could it be some PHP error? If so, how do I resolve it? GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... sed: can't move '/etc/php7/php-fpm.d/www.confncLMpB' to '/etc/php7/php-fpm.d/www.conf': Resource
  6. Update: By adding "vfio-pci.ids=1b39:0001" to the Syslinux Configuration as below i managed to get the drive visible for passthrough when I edit a VM But still no soup as I want to use the PCIe card as a unassigned device and run my VMs and dockers on it
  7. Hi, Just bought a PCIe accelerator card as described above (link) and i can't use the drive. I may be over my head on this one BUT as far as i know, the driver was included per customer req in unRAID 6.6.0 The card shows up in system devices as follows: But i can't find it as a drive in the WebGUI using unassigned drives or as a choice when i assign drives to the array. From syslog: Any ideas? Do i have to compile drivers manually?
  8. Hi! I'm trying to troubleshoot this issue as well. Had it for like a month or two. Transcode of anything fails within 24hrs of restart of the docker. Though i want to point out that i'm not using this docker, instead i'm using linuxserver.io's docker. Seems like a Plex issue?
  9. I deleted the docker image under settings->docker and now it works. Try it!
  10. It jus doest that i guess. Same happened to me. Change hostname in line 94 in telegraf.conf (se attached pic)
  11. Funny thing. This just happend to me as well, and i can't get it working again. Super frustrating. On unRAID 6.8.3 got both eht0 and eth1 bonded and briged and the only options in grafana now is "eth0" and "all". When i look into the influxdb that's the only entries as well, so i guess the telegraf docker is f****? edit: Spelling
  12. What I love most: being able to extend the array one drive at the time! what i woule like to be added: Multiple arrays! happy new year to ya’ll!
  13. Hi guys! Haven't been able to update Nextcloud in a while due to this error, any ideas why it appears? At first, I wasn't able to even see the upgrade screen since I got the "Step 4 is currently in process. Please reload this page later" error. I found a site that recommends removing the "nextcloud-data/updater-randomstring/.step"-file wich I did and then could proceed. But then this error comes up! Worth mentioning is that the data folder (including "nextcloud-data/updater-randomstring/.step" ) is on a FreeNAS server. The share is mounted in unRAID (NFS) with
  14. FYI, I found this today, doing some research. So 66C isn't BANANAS but high - yes Did a parity rebuild tonight with server case closed on the same parity drive and without Disk 4 and as far as i know, the temperature were < 58C so the airflow (and thus me) were to blame in the first case. http://knowledge.seagate.com/articles/en_US/FAQ/193771en