• Content Count

  • Joined

  • Last visited

  • Days Won


ashman70 last won the day on December 28 2018

ashman70 had the most liked content!

Community Reputation

70 Good

About ashman70

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

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

  1. Just installed this and when I try to run the command scrutiny-collector-metrics run in the Scrutiny console I get: command not found Am I doing something wrong?
  2. So upgrade. Delete the existing Plex docker Install the new Plex docker - select driver to latest? Reboot Is that what you are saying?
  3. Quick question: I am currently running unRAID 6.8.2 with a P2000 for transcoding in Plex. I am using the liuxserver Plex docker which is currently running without issue. I am running the unRAID version with the baked in Nvidia drivers. If I want to upgrade to unRAID 6.9x do I have to anything for Plex or simply upgrade?
  4. I am currently running on 6.82 and everything is working well. I run a bunch of dockers, no VM's but my main concern is plex. I have an Ndivia P2000 in my server for hardware transcoding, so I am running the version of Plex that has the Nvidia drivers baked into it. I read something about 6.9 having the Nvidia drivers included now in the unRAID OS. Do I just go ahead with the normal upgrade process to 6.9 or is there anything I have to do for Plex?
  5. So in this case, do I just let it finish the read-check and then will it automatically begin a party check if the drive passes the read-check? Or will I have to bring it back online? Can I cancel the read-check, stop and restart the array, hopefully brining the drive back online and starting a parity check?
  6. This morning I swapped out an 8TB drive for a 14TB drive. I did it the usual way. Stopped the array. Removed the 8TB drive from the list of drives in unraid. Started the array with no drive in its slot in unraid. Stopped the array, physically removed the disk Added the new 14TB drive Selected it from the available drives and added it to the slot where the 8TB drive had been. Started the arrray Now the 14TB drive is showing as disabled and for some reason unRAID is doing a read check? The 14TB drive is a brand new recently shucked dr
  7. Still getting permission denied when trying to download Big Sure option 2 ****************************************************************************** Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet? The scheme stores pixel data offscreen on the VNC viewer side for faster retrieval. It should work with any VNC viewer. Try it by running: x11vnc -ncache 10 ... One can also add -ncache_cr for smooth 'copyrect' window motion. More info: [services.d] starting app... [app] sta
  8. It doesn't work for me at all, which is too bad as I'd like to try it. Jazz if you Google:macOS Product: 001-86606, you will see it is indeed Big Sur
  9. Hi Steve1977, did you install the macinabox docker in the past few days? I am unable to get it working at all.
  10. Still getting this error, this is under unRAID 6.82, I tried upgrading to 6.9RC2 but it broke my VM which I need. /Macinabox/ line 273: /Macinabox/tools/FetchMacOS/BaseSystem/SharedSupport.dmg: Permission denied
  11. No I am actually on unRAID 6.82 do you think that matters? Updated to 6.9RC2 - getting this error? /Macinabox/ line 273: /Macinabox/tools/FetchMacOS/BaseSystem/SharedSupport.dmg: Permission denied
  12. I think I figured it out, issue on my end, trying method 2 now. But now I see this in the docker log?: Macinabox/ line 273: /Macinabox/tools/FetchMacOS/BaseSystem/SharedSupport.dmg: Permission denied Tried again and got this: 2021-01-02 10:59:42,451 Network Request: Fetching 2021-01-02 10:59:43,091 Selected macOS Product: 001-86606 /Macinabox/ line 273: /Macinabox/tools/FetchMacOS