Jump to content

Christopher

Members
  • Content Count

    35
  • Joined

  • Last visited

Community Reputation

2 Neutral

About Christopher

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. Yes! Thanks for the correction. I updated my original post.
  2. I'm having an issue where my Plex Server no longer being recognized. Plex is seeing my server as a new instance with a message on top saying, "An unclaimed media server has been found on your network. Claim it now". My Libraries are missing because it think it's a new server. Here's what led up to this below... 1) I had several cache drive BTRFS errors in my log. Docker apps to would stop or not respond. 2) Searched the forums and found post with similar issues. I tried a few things to fix it with no success. 3) I decided to recreate my cache drive. I disabled docker and VM and moved all cache folders/files to the array. 5) I cleared my cache configuration and deleted partitions on those my 4 cache SSDs. 6) I setup the 4 SSD drives as cache again and formatted. 7) Copied all files back to the cache array. Restarted server. 9) Deleted my docker.img 10) Enabled docker. Docker created new empty docker.img 11) Installed Plex from previous Apps. Config pointed to original folders 12) Started Plex Any ideas? Is there a way to get Plex to see this as my original instance? If I proceed with this new instance and add existing libraries, will Plex automatically use the existing database/files in my config folder? If I proceed with this how will it effect my Tautulli database? Your help is appreciated!
  3. Thanks for your pgAdmin4 template. Do you have any plans to upgrade from pgAdmin4 version 2.1 to the latest 3.4?
  4. +1. Maybe unRaid can have an option to login with basic http authentication or a forms login page. Sonarr has this option.
  5. I figured it out. I assumed the default user in the container was jovyan so I didn't set it. After reading the docs again, I explicitly set the NB_USER and now it works. Extra Parameters: --user root -e NB_USER="jovyan" -e NB_UID="1000" -e NB_GID="100"
  6. I'm trying to mount a local unRAID appdata folder to the working folder in docker container jupyter/scipy-notebook. The container runs and works fine except my work is not being saved to my volume mount. I believe the problem has to do with incorrect values in the "Extra Parameters" section for the User Id and Group Id. I've tried 99 and 0 as values. Can anyone help me get this working? Your help is appreciated! Thanks! Documentation for volume mounts on this image: https://jupyter-docker-stacks.readthedocs.io/en/latest/using/recipes.html#host-volume-mounts-and-notebook-errors Docker Options for this Image: https://jupyter-docker-stacks.readthedocs.io/en/latest/using/common.html#Docker-Options My Configuration:
  7. http://slickdeals.net/f/7980175-5tb-toshiba-7200rpm-3-5-hdd-ph3500u-1i72-139-99-fs-walmart-toshiba-com-5tb-seagate-enterprise-capacity-7200rpm-hdd-st5000nm0024-159-99-fs-rakuten?v=1&src=SiteSearch
  8. A Friend let me borrow a smaller drive and I was able to complete the process. Thanks for you help!
  9. The parity drive I want to use to restore disk13(3TB) is 4TB. I would like to replace disk13(3TB) with a new drive but my only spares are 5TB. Is there anyway I can make the 5TB appear to be 4TB or 3TB? This is just temporary so I can rebuilt disk13. Thanks, Christopher
  10. Thanks for the info bjp999! Here's the reason why I want to do this: [*]Initial state of my server was perfect. I had just done a parity check and all was well. [*]I upgraded my parity drive from 4GB to 5GB, Unraid started building parity. [*]In the morning I saw disk13 was redballed and parity build did not complete. Nothing has been copied/deleted/edited to the server since. I did not trust my old parity because events happened between steps 1 and 2 that wasn't sure about and I don't recall the details of. So I used reiserfsck to recover disk13 data and it restored about 2/3 of it. I copied the restored data to a local disk on my PC. Now I want to try to rebuild disk13 from my old parity. I realize that it the parity info might be invalid. But I wanted to give it a shot. Once I rebuild it I want to do an md5 comparision with the reiserfsck recovered data. Can you point me to the procedure? Thanks, Christopher
  11. My system currently doesn't have a parity drive. I want to install an old parity drive and have unraid trust it. When I start the array with the old parity drive I want this think everything is normal. Can someone point me to the link for this procedure? Thanks, Christopher
  12. Your right on both points. Thank you very much for your explanation! -Christopher
  13. I'm not having any serious issues I need help with. I just want to understand how the following works: 1) I used reiserfsck to recover data from a disk13 2) reiserfsck recovered 2/3 of the files and created a lost+found folder. 3) I followed the 'Trust My Array' procedure to reset my entire array. 4) I reassigned all the disks to the same slots minus the parity drive. I matched all serials to the old slot and triple checked against a screenshot. Yes, i'm unprotected. 5) I started the array. 6) Now my disk13 shows the original file structure with 100% of the files. I tested a few files that were missing after the reiserfsck rebuild and they work fine. My assumption was that disk13 would still show the reiserfsck rebuilt folder/file structure even after the 'Trust My Array' procedure. How did 100% my original disk13 folder/file structure return after the "reiserfsck --rebuild-tree /dev/md13" rebuilt and created 2/3 the original folder/file structure? Thanks, Christopher
  14. I went ahead and restarted the server and now disk13 is no longer showing as unformatted but still has a red ball. The reiserfsck tool recovered about 2/3 of my files. I've copied the recovered files using terracopy to a drive on my PC. I want to attempt to rebuild the disk13 by putting my old parity drive in. I know that my new parity is not correct. To do this I need to remove the disk13 red ball. Unraid will not let me put back my old parity drive with a red ball. The reason I didn't do a rebuild initially was because the events leading up to disk13 failure were obscure in my mind. Therefore I didn't trust my old parity drive. The reason I want to do a parity(old) rebuilt after a reiserfsck recovery: I want to md5 compare reiserfsck recovered files with parity(old) rebuilt files. If I see that the md5 matches for all or most files, then this give me confidence in the parity(old) rebuilt disk13 data. I found this information below but I wanted to confirm with you before I move forward. Also I have Unraid version 5.0.6. Whats the best way to remove the redball and put my old parity drive back? http://lime-technology.com/wiki/index.php/Make_unRAID_Trust_the_Parity_Drive,_Avoid_Rebuilding_Parity_Unnecessarily Thanks, Christopher
  15. I'm pretty sure I didn't check it but you never know. Here's the df output. md13 is the only one not mounted. I read in another thread that the "unformatted" label in the webgui should really read "unmounted". So the array is in normal mode with all disks mounted except md13. Perhaps reiserfsck didn't complain because the device it was operating on was already unmounted? I've attached a few webgui screenshots. Should I stop the array and then restart the server? Thanks, Christopher