smaka510

Members
  • Posts

    61
  • Joined

  • Last visited

  • Days Won

    1

smaka510 last won the day on October 17 2017

smaka510 had the most liked content!

Recent Profile Visitors

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

smaka510's Achievements

Rookie

Rookie (2/14)

9

Reputation

  1. I gave up on it. I'm using plex kodi connect.... does the same thing, but you have to have a plex server.
  2. I am at a complete loss as to how to get Kodi-headless working... Here is what I have done so far: 1. install the docker 2. install mariadb and create user/pass 3. configure advancedsettings.xml on the headless server with IP/Port/user/pass on the docker 4. copy over sources.xml from kodi client to the kodi server 5. enter headless IP/Port/user/pass in kodi clent advancedsettings.xml 5. restart the docker..... Nothing happens.... what did i miss? how is everyone getting this to work?
  3. I am not able to get this working and dont know why. I thought I missed something and went through the entire setup 4 times. I missed nothing. I've been at this for days. Before I give up on it, can anyone help? FYI - I have Mojave in a VMWare Workstation VM (vmdk). This is what I used to perform all the steps in the guide. I read that a USB incompatability is the cause and usbinjectall.kext may be needed to fix this. I dont know what to do from here. in some cases the vm will start clover and select the install option, then it will reboot (this happens over and over) OR in other cases I can boot clover just fine... when I select the installation an apple logo shows a progress bar then I get this.
  4. I have the same problem. boots to clover, when I select the install option the vm reboots. this loops over and over. i thought I missed something so i went through the entire process 4 times. i missed nothing. before i give up on this, can anyone help?
  5. I figured it out. not sure how, but sleep was set to "30 min". I don't remember changing this in my VMs, but I will take the easy fix. This still does not explain the high cache usage.
  6. No replies yet? I did more digging and found old vdisks from VMs I no longer have still sitting in the "./domains" folder. I deleted these and freed up another 100gb. I tried looking at the log files but do not know what to look for. Can anyone help me with this?
  7. Hello all, My VMs keep pausing. This seems to be due to high disk usage, but I don't know what is causing it. - I stopped all tv show recordings to the cache - installed a dedicated SSD for plex transcoding - deleted all "cache only" shares - changed "min free space (cache)" to 2gb. - thought the docker image might be full so I expanded it to 150gb. I have 2 Kingsont 250gb SSDs in raid 0 (btrfs). My main page shows over 150gb free space, this could be wrong maybe? Not sure what else to do. Please see the attached logs. thank you maximus-diagnostics-20181029-0733.zip
  8. ** Update ** I have been able to get this working again. I'm not sure why Mellanox moved the "protocol". If you are using Mellanox Connex-x cards that support Infinity Band (IB) and cannot figure out how to change the virtual protocol from Ethernet to IB try the following. note: IB mode requires a subnet manager run otherwise IB will not work. Also Both ends (host/server/switch) must be configured this way. 1. Open the device manager 2. find your mellanox card and go to properties 3. select the "Protocol" tab and toggle between IB and Eth as desired. If you do not see the "Protocol" tab try the following: 1. in the device manager look for your mellanox NIC under "system devices" 2. open properties and select the "Protocol" tab 3. toggle between IB and Eth as needed.
  9. I made the mistake of re-imaging my windows 10 PC and found this impossible to get working again. The key to this working with mellanox VPI cards is your ability to toggle between "Infinity Band (aka IB)" and "Ethernet (aka eth)". I don't know what Mellanox did with the drivers but the "Port Protocol" tab in the device manager is gone. I found another driver for this in the device manger under "system devices" instead of "Network Adapters". This has the "Port Protocol" tab, but everything is greyed out. Mellanox no longer supports X-2 cards so getting help from them is out the window. This is so frustrating Do yourself a favor when you get this working.... Export your FUNCTIONAL Windows 10 drivers and save them in a place you can get to them later.
  10. I cant get this to work at all. it never scans my library. I add artist manually and try searching but it never gets a torrent. How did you get this to find a torrent??
  11. I rebooted the server and everything came back. All is well.
  12. my unraid server stopped responding so I rebooted. when it came back up all my plugins, dockers and VMs are missing. the tabs for these are not even present in the web UI. I went to "dockers" in the settings menu and noticed that it is turned off. I tried to enable it using the path "/mnt/user/appdata/" but it says this path does not exist. I am looking at the path as we speak. No changes where made everything was working fine. All shares and data are still present and if I look in the "appdata" folder the data for all my dockers is still present. Not having my VM's running breaks all of my automatons in a bad way. I don't know what to do (Linux is foreign to me). Can someone please explain why this happened
  13. my unraid server stopped responding so I rebooted. when it came back up all my plugins, dockers and VMs are missing. the tabs for these are not even present in the web UI. I went to "dockers" in the settings menu and noticed that it is turned off. I tried to enable it using the path "/mnt/user/appdata/" but it says this path does not exist. I am looking at the path as we speak. No changes where made everything was working fine. All shares and data are still present and if I look in the "appdata" folder the data for all my dockers is still present. Not having my VM's running breaks all of my automatons in a bad way. I don't know what to do (Linux is foreign to me). Can someone please explain why this happened
  14. I gave up on this particular docker and started using another Guacamole docker. All is well now.