smoothvirus

Members
  • Posts

    4
  • Joined

  • Last visited

Everything posted by smoothvirus

  1. I did a little more research and discovered that the computations for Parity 1 and Parity 2 are different and that you can't have a Parity 1 without a Parity 2. I bit the bullet and just replaced my Parity 1 drive drive with the larger 20 TB drive. Fortunately no errors but it was a fun day (26 hours) to run unprotected as the Parity 1 drive rebuilt itself.
  2. I'm jumping in on this topic as I'm in the middle of the same process but taking a different approach. I didn't want to remove my one parity drive and then rebuild a new parity drive as that would put my array at risk. I followed this process, please tell me if there is a problem. I currently have 1 4 TB parity drive and my array is filling up. I leveraged the black Friday deals and bought two 20 TB drives and have an extra 14 TB drive as well. I added the 14 TB drive to the data array and one 20 TB drive as "Parity 2". My plan is to restart the system and let Parity 2 build parity. Once that is done, I will add the 2nd spare 20 TB drive to the data array (now that I have a 20 TB Parity 2 drive) and move the 14 TB drive that was formerly Parity 1 to the data array. Restart the system and the array will come back on line with 1 parity drive in the Parity 2 position. Any issues with that approach? Thanks for the help!!
  3. The contents in appdata/binhex-plexpass are all the configuration data from your previous install. If you redownload the container and make sure your content parameter and config parameter are the same as your previous installation it will detect your previous install. Just to be on the safe side, I would make a copy of the data inside binhex-plexpass directory. In the terminal you can run the command: cp -R /mnt/user/appdata/binhex-plexpass /mnt/user/appdata/binhex-plexpass-backup That will make a copy of the previous install information in case you need it. Once you've got the new docker container running you can delete it with the command: rm -R /mnt/user/appdata/binhex-plexpass-backup
  4. I recently had corruption issues on my flash drive. When I run fix common problems I get an error that my /boot/config/plugins/dockerMan/templates-user/my-binhex-plex-pass.xml is corrupted. When I looked at the file it was corrupted. Is there a way to put down a fresh my-binhex-plex-pass.xml without removing the Plex docker container? I don't want to reconfig plex as this is a significant undertaking. In looking at my-binhex-sonarr.xml is seems like it would be pretty straightforward to recreate the file. Any help would be appreciated. Thanks