Jump to content

reggierat

Members
  • Content Count

    226
  • Joined

  • Last visited

Community Reputation

0 Neutral

About reggierat

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. As an IT professional, i love that Unraid is so easy to use, when i get home from work the last thing i need is anything complex at my home. I would love to see built in check summing and snapshotting for the file system as a standard feature (eventually)
  2. And fixed.. good old BIOS update to the rescue After trying a different graphics card with stock unraid and also unraid-nvidia it became obvious this wasn't a driver issue (thanks for listening)
  3. Just to follow up on the sleep issue i've been having. - Removed video card and confirmed sleep works correctly with 6.7.2 and 6.8 - Tested each build of Unraid Nvidia which contains a different Nvidia driver - issue is present in all drivers - Enabled and disabled anything and everything in the bios i thought might be relevant - Observed the system when it receives magic packet, video card fans spin up and then power off , system hangs and never wakes from sleep - All of the above was performed with the array stopped so never experienced an unclean shutdown
  4. Gotcha, no, definitely no flash up
  5. could you explain what you mean by this?
  6. I realise this is a bit of a stretch, but is anyone running unraid nvidia + the s3 sleep plugin successfully? My server crashes running the above combo when putting itself to sleep. Not really expect much support on this one though
  7. Now i realise this is probably outside the bounds of what is supportable, but i have noticed since moving to unraid nvidia that the sleep plugin causes an unclean shutdown when attempting to put the server to sleep. I have tested this with unraid nvidia 6.7.2 and 6.8, stock unraid the sleep plugin correctly puts the server into s3 sleep and i'm able to easily wake it. Is this worth investigating or do i just give up on s3_sleep?
  8. meant to post this log ffmpeg-transcode-f8c29a34-f835-456b-863a-0be833796c17_1.txt
  9. I've attempted to transcode several different files yes ffmpeg-transcode-76b50670-df09-4a11-9afc-87a88e8ef71b_1.txt
  10. What i mean is, the notes in the top of the template with instructions to add the extra parameter were missing
  11. root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='emby' --net='bridge' -e TZ="Australia/Sydney" -e HOST_OS="Unraid" -e 'NVIDIA_VISIBLE_DEVICES'='GPU-2c8cd41b-4bf5-73dc-1eff-96d27d64113b' -e 'PUID'='99' -e 'PGID'='100' -p '8096:8096/tcp' -p '8920:8920/tcp' -p '1900:1900/udp' -p '7359:7359/udp' -v '/mnt/user/Movies/':'/movies':'rw' -v '/mnt/user/TV Shows/':'/tv':'rw' -v '/mnt/user/Music/':'/music':'rw' -v '/mnt/user/appdata/emby':'/config':'rw' --runtime=nvidia 'linuxserver/emby' 9cd52be25d822572dc4e5b54e16033f144f0afcddf59d438768d1e9224966f29 Still hitting the CPU ffmpeg-transcode-069afe13-e1b1-438b-b6db-b01a2e627c6e_1.txt
  12. I found it confusing, as i had it in their previously. Then i deleted the container and added it back and the info was missing from the template
  13. root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='emby' --net='bridge' -e TZ="Australia/Sydney" -e HOST_OS="Unraid" -e 'NVIDIA_VISIBLE_DEVICES'='GPU-2c8cd41b-4bf5-73dc-1eff-96d27d64113b' -e 'PUID'='99' -e 'PGID'='100' -p '8096:8096/tcp' -p '8920:8920/tcp' -p '1900:1900/udp' -p '7359:7359/udp' -v '/mnt/user/Movies/':'/movies':'rw' -v '/mnt/user/TV Shows/':'/tv':'rw' -v '/mnt/user/Music/':'/music':'rw' -v '/mnt/user/appdata/emby':'/config':'rw' 'linuxserver/emby' 69b8eaa2900c8a47ae13dfb6fd0b19acdf3db7e05a015f5b0b24f9b88977525c