• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About skinsvpn

  • Rank

Recent Profile Visitors

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

  1. I'm having issues with my AMC script when processing tv shows. It appears as though AMC is forcing the title to be a movie but also recognizes to place it in the tv_shows folder. Has anyone experienced this situation? Unraid version: 6.8.3 Latest version of docker image (I don't know exactly how to verify this other than run a check for updates and ensure it states "latest") filebot -v output: FileBot 4.9.1 (r7372) JDK8 / OpenJDK Runtime Environment 1.8.0_242 / Linux 4.19.107-Unraid (amd64) Log: Run script [fn:amc] at [Thu May 21 09:53:11 EDT 2020] Parameter: s
  2. So unraid has completed rebuilding both drive and I haven't found anything of note that is causing me issue at this time. Back in business! Thank you to everyone that helped me through this. It is truly appreciated.
  3. I got a notification that Parity sync / Data rebuild was completed and that Disk 7 has returned to normal operation but disk7 shows as "Unmountable: No file system." I've read on other posts in similar situations that I may need to run a filesystem check. Would it be correct to Stop the array and run a filesystem check on disk7 while in maintenance mode using the process from the wiki in the link below?
  4. Clearing up one more question since I think it may technically have been done out of order. My disk7 was replaced and the new drive placed into the disk7 slot on the Main page prior to starting these instructions but without ever restarting the array anytime after. So there was a replacement in the disk7 slot on Main when the first step "-Tools -> New Config -> Retain current configuration: All -> Apply" was run. Could this cause a potential issue?
  5. Ok, just for my sanity, which is a slow process so thank you for your patience here, my GUI was on the Plug-Ins tab to uninstall the plugin that was giving an error when I ran the invalidslot command. Is going to the Main tab goign to trigger the same effect as a refresh? Should I go to the main tab and rerun the command?
  6. Does the invalidslot command work immediately? There is no output from the command in the terminal.
  7. May 19 08:07:44 Tower emhttpd: import 30 cache device: (sdc) SPCC_Solid_State_Disk_AA000000000000000807 Did I need to run invalidslot with a 30 for parity? Edit: why did i think the cache was my parity? not enough coffee maybe...
  8. I am getting the following error immediately when running the mdcmd cmd Warning: Division by zero in /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php on line 62 This is a copy from my terminal for what I ran exactly root@Tower:~# mdcmd set invalidslot 7 29
  9. I've been looking for the correct usage for invalidslot and found this recent post of yours Just so I don't botch anything, my understanding is that above the 1 is the disk being rebuilt and 29 is the parity correct? Since I need to rebuild disk7 then make disk1 enable I would run: mdcmd set invalidslot 7 29
  10. Extended test passed Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 38832 - ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 190 189 051 - 690643 3 Spin_Up_Time POS--K 154 147 021 - 9275 4 Start_Stop_Count -O--CK 097 097 000 - 3583 5 Reallocated_Sector_Ct PO--CK 187 187 140 - 187 7 Seek_Error_Rate -OSR-K 200 200 000 - 0
  11. Extended test in progress. Would a screenshot be sufficient after or is a diagnostic file still best?
  12. So I finally got my replacement drive and replacement cables in. If I was understanding correctly I need to first get my disabled drive back online then rebuild the fried drive. Do I start with the 'Trust My Array' procedure in the wiki to get the disabled drive back? My latest diag:
  13. I actually do have a fairly recent diagnostics file. April 29.
  14. Looking at my previous notifications I got a message saying the reallocated sector count is 17 then a message followed saying the drive is now disabled. I would have to connect the drive to execute this plan so if I connected it now and got another diagnostic would it contain the necessary info? To complicate things I had to order a new sata breakout cable (since that connector melted...) so until that arrives I don't have the capability of reconnecting without removing another drive. Not sure if that would make finding that specific drives info in the logs more difficult.
  15. One thing I should add is that the dying drive was placed into a Disabled state by unraid.