Jump to content

bigsing

Members
  • Content Count

    104
  • Joined

  • Last visited

Community Reputation

0 Neutral

About bigsing

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  1. Thanks to everyone for the responses, i'll be replacing the drive.
  2. My scheduled parity check completed yesterday with no errors. Today i received an alert for Current_Pending_Sector and Offline_Uncorrectable increases on one of my data drives. Attached is the extended SMART test, should i be replacing this drive? WDC_WD80EMAZ-00WJTA0_7SHASSUD-20190303-1435.txt
  3. Is your issue specific to VideoSort or Post Processing scripts in general? For the container to load the scripts your ScriptDir property (found under Settings > Paths) needs to be set to the location the scripts reside. For example my ScriptDir is set to /config/ppscripts which translates to /mnt/user/appdata/nzbget/ppscripts
  4. I fixed this by using the permissions plugin in the config.yaml file. Insure the permissions plugin is listed in the plugins section at the top and include a permissions section further down in the file similar to the below. permissions: file: 666 dir: 777
  5. Done - https://github.com/linuxserver/docker-beets/issues/32
  6. I'm attempting to install the PlexUpdate plugin, but it requires the requests package be installed via pip. I see that the pip packages installed are defined in the dockerfile, could this possibly be added to the dockerfile?
  7. @johnnie.black thanks for your help! I was able to get a clean parity build then mount the old disk with unassigned devices and copy the files back over to the array. Only one file ended up being corrupted. Running another parity check now just to make sure everything is in order.
  8. The array is not 100% unchanged, so that's not an option. I've reviewed the contents of the drive and was able to move the important files to another drive without issue.The items that remain i can replace if needed. In this case, i think re-syncing parity with a new disk 4 and then copying everything over is the best approach. How do i add a new disk 4 without a rebuild occurring on it when i start the array?
  9. Diagnostics File is attached. I was attempting to upgrade my parity drive from a 3TB to 8TB and encountered 384 errors on Disk 4. I ran an extended SMART test which subsequently failed, so i'm expecting I need to look at replacing the drive. The WebGUI shows that parity is valid, but will i be able to successfully rebuild the disk since the errors occurred during the parity rebuild? In retrospect i should have ran a check before upgrading the parity drive, but at least i know i won't make that mistake again. What should my next steps be? joey-diagnostics-20180330-0017.zip
  10. I recently purchased a LSI 9201-16i off eBay. The cards BIOS version is 8.00.00.00-IT would I gain anything from updating this? As far as testing the card, I plugged the card into my test bench and verified that each SAS port recognizes 4 drives when using a reverse breakout cable. The drives i tested with included 2x250GB, a 1TB HDD, and 1 SSD. I also ran a parity check and verified that an 8TB drive was recognized successfully after booting unraid.
  11. Yep, I meant forward breakout cables. Sent from my Pixel using Tapatalk
  12. I recently purchased a LSI 9201-16i off eBay. I plugged the card into my test bench last night and verified that each SAS port recognizes 4 drives when using a reverse breakout cable. The drives i tested with included 2x250GB, a 1TB HDD, and 1 SSD. I was going to run a parity check as well, but is there any other testing I should do before I consider moving this card from my test bench into my main server? Also the cards BIOS version is 8.00.00.00 would I gain anything from updating this?
  13. I have the same problem after CA Backup runs on Monday morning. The system is unresponsive and I have to hard reboot. I'll turn on troubleshooting mode this weekend to see if I can capture anything. Sent from my XT1254 using Tapatalk
  14. bigsing

    Norco 4224 Thread

    Link fixed Sent from my XT1254 using Tapatalk