guyinco6nito

One extra update: Problem: The NextPVR docker container was running as root. All of the video files created were owned by root, and my user didn't have permissions to delete them. Fix: Run docker as the user of your choice! First find the ID of your username by launching the terminal and running "id your username". It'll return a number (e.g. 1001) and the group to which your user belongs (e.g. users, with a group number of 100). Next add one more "Extra Parameter" for the docker container saying: "--user 1001:100" and apply the settings. Now the NextPVR Docker container will create the recordings with the permissions already set! If you're doing this to fix it, you might need to update permissions on your config by running: chown -R 1001:100 /mnt/user/appdata/nextpvr

I tried those steps but they didn't work for me, so I ended up using the official NextPVR build with the steps below, posted for posterity: As far as prerequisites: You need Docker running on a properly working cache pool per the guide here: https://docs.unraid.net/unraid-os/using-unraid-to/run-docker-containers/overview/ Know the directory you want to save your recorded video files in your Array. They are accessed through /mnt/user (e.g. /mnt/user/BigPool/DVR-incoming) Know the directory to your "appdata" folder that lives on your Cache Pool (usually /mnt/user/appdata/) Once that's ready: Open up the unraid terminal (link is the >_ symbol at the top) and create the directories you want to use with the command: mkdir /mnt/user/appdata/nextpvr Next go to the Unraid -> Docker tab Go to Add Container Switch to Advanced mode Set the name as NextPVR Set the repository as: nextpvr/nextpvr_amd64 Enter the extra parameters: --volume /mnt/user/appdata/nextpvr:/config --volume /mnt/user/BigPool/DVR-incoming:/recordings --volume /mnt/user/BigPool/DVR-incoming:/buffer --restart unless-stopped --publish 16891:16891/udp --publish 8866:8866 Next set up those paths to map to your actual array (so your config and recordings have a more permanent home than the temporary docker image) At the bottom, click on "Add another Path, Port, Variable, Label or Device" Leave the config type as "Path" Set the name as "config" Set the container path as /mnt/user/appdata/nextpvr Set the host path as /mnt/user/appdata/nextpvr Leave Read/Write permissions and Click Add! Now again click on "Add another Path, Port, Variable, Label or Device" Set the name as "recordings" Set the container path as /mnt/user/BigPool/DVR-incoming Set the host path as /mnt/user/BigPool/DVR-incoming Click Add Click Apply Now NextPVR will be running and you can load up the page at: http://*your unraid server*:8866 (it'll see any network tuners and be ready to go! You can also drop your config and database into the /mnt/user/appdata/nextpvr folder on the Unraid server, you just might need to enable the share to do so) Happy watching! -guyinco6nito

Thanks much for those clarifications! I think I've realized what I was missing. A formatted drive isn't really empty, it just has an empty filesystem with no known addresses pointing anywhere in the wilderness of 1s and 0s on the drive. If the Parity drive is to truly protect against hardware failure, it has to know and calculate each and every bit of every data drive. Preclearing/Initializing the drive (the feature that I thought I was looking for) would achieve that by writing 0s to every single part of the drive and then confirming them all as being zeroed, which would put more wear and tear on the drives than just mapping the unaddressed nonsense in there and achieving parity. Have good ones!

Hello, I'm building a new array from scratch and I have gone in and erase all of the disks before creating it. Is there a way to disable the 36+ hour parity check? I know that all the drives have zeroes on them, so the parity must just be zero, why do I need spending a day and a half to read 100% of an empty drive? Have I misunderstood what the Parity-Sync does? Thanks for any tips you can provide! -Dan Metzger