skinsvpn

Members
  • Posts

    46
  • Joined

  • Last visited

Everything posted by skinsvpn

  1. I replaced a failed disk and during the rebuild I got a notification for read errors. I now see a drive that is skyrocketing read errors and the rebuild estimate is now at 289 days. A few more days than expecting. The drive with read errors is at 40k and counting so possibly a loose cable? Can I just cancel the rebuild to investigate and begin again?
  2. You were correct, the docker image wouldn't start with the 18.20 drivers. Guess that card is older than I realized. Thanks for the response though!
  3. lxnd, I am getting the following message in the logs: amdgpu_device_initialize: DRM version is 2.50.0 but this driver is only compatible with 3.x.x. Safe to take that message to mean my card in unsupported? (Radeon HD 7870)
  4. 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: subtitles = en Parameter: pushbullet = ***** Parameter: pushover = ***** Parameter: exec = /bin/ash /config/filebot_verify_suball.sh '{f}/' Parameter: music = y Parameter: artwork = y Parameter: ignore = idx|\.sub Parameter: movieFormat = {fn =~ /2160p/ ? "4k_movies" : "movies"}/{n.replaceFirst(/^(?i)(The|A|An)\s(.+)/, /$2, $1/).ascii()} ({y})/{n.replaceFirst(/^(?i)(The|A| An)\s(.+)/, /$2, $1/).ascii()} {"("+fn.matchAll(/despecialized|extended|uncensored|remastered|remaster|4k.remaster|unrated|uncut|directors.cut|director.s.cut|spe cial.edition|criterion.collection|theatrical|remux/)*.upperInitial()*.lowerTrail().sort().join(", ").replaceAll(/[._]/, " ")+")"} {"[$vf $vc $ac $af]"} Parameter: seriesFormat = tv_shows/{n.replaceFirst(/^(?i)(The|A|An)\s(.+)/, /$2, $1/).ascii()} ({y})/Season {s.pad(2)}/{n.ascii()} - {s00e00} - {t.ascii()} {"("+ fn.matchAll(/despecialized|extended|uncensored|remastered|remaster|4k.remaster|unrated|uncut|directors.cut|director.s.cut|special.edition|criterion.collection|re mux/)*.upperInitial()*.lowerTrail().sort().join(", ").replaceAll(/[._]/, " ")+")"} {"[$vf $vc $ac $af]"}{"."+lang} Parameter: musicFormat = music/{n.replaceFirst(/^(?i)(The|A|An)\s(.+)/, /$2, $1/).ascii()}/{album.ascii()} ({y})/{album.ascii()} - {media.PartPosition}{pi.pad(2) } - {t.ascii()} ({kbps}) Argument[0]: /mnt/disks/whatbox/Rick.and.Morty.S04E07.1080p.WEBRip.x264-BTX Ignore video extra: /mnt/disks/whatbox/Rick.and.Morty.S04E07.1080p.WEBRip.x264-BTX/Sample/rick.and.morty.s04e07.1080p.webrip.x264-btx.sample.mkv Read archive [rick.and.morty.s04e07.1080p.webrip.x264-btx.rar] and extract to [/mnt/disks/whatbox/Rick.and.Morty.S04E07.1080p.WEBRip.x264-BTX/rick.and.morty.s04e 07.1080p.webrip.x264-btx/Rick.and.Morty.S04E07.1080p.WEBRip.x264-BTX] Extracting files [/mnt/disks/whatbox/Rick.and.Morty.S04E07.1080p.WEBRip.x264-BTX/rick.and.morty.s04e07.1080p.webrip.x264-btx/Rick.and.Morty.S04E07.1080p.WEBRip.x 264-BTX/rick.and.morty.s04e07.1080p.webrip.x264-btx.mkv] Input: /mnt/disks/whatbox/Rick.and.Morty.S04E07.1080p.WEBRip.x264-BTX/rick.and.morty.s04e07.1080p.webrip.x264-btx/Rick.and.Morty.S04E07.1080p.WEBRip.x264-BTX/ric k.and.morty.s04e07.1080p.webrip.x264-btx.mkv Group: {Series=rick and morty} => [rick.and.morty.s04e07.1080p.webrip.x264-btx.mkv] Get [English] subtitles for 1 files Looking up subtitles by hash via OpenSubtitles No matching subtitles found: /mnt/disks/whatbox/Rick.and.Morty.S04E07.1080p.WEBRip.x264-BTX/rick.and.morty.s04e07.1080p.webrip.x264-btx/Rick.and.Morty.S04E07.108 0p.WEBRip.x264-BTX/rick.and.morty.s04e07.1080p.webrip.x264-btx.mkv Rename movies using [TheMovieDB] Auto-detect movie from context [/mnt/disks/whatbox/Rick.and.Morty.S04E07.1080p.WEBRip.x264-BTX/rick.and.morty.s04e07.1080p.webrip.x264-btx/Rick.and.Morty.S04E07. 1080p.WEBRip.x264-BTX/rick.and.morty.s04e07.1080p.webrip.x264-btx.mkv] [MOVE] from [/mnt/disks/whatbox/Rick.and.Morty.S04E07.1080p.WEBRip.x264-BTX/rick.and.morty.s04e07.1080p.webrip.x264-btx/Rick.and.Morty.S04E07.1080p.WEBRip.x264-B TX/rick.and.morty.s04e07.1080p.webrip.x264-btx.mkv] to [/mnt/user/media/tv_shows/Rick (2003)/Season/Rick - - [1080p x264 AAC 2ch].mkv] Processed 1 files groovy.lang.MissingPropertyException: No such property: seriesInfo for class: net.filebot.web.Movie groovy.lang.MissingPropertyException: No such property: seriesInfo for class: net.filebot.web.Movie at Script1$_run_closure69$_closure112$_closure117.doCall(Script1.groovy:355) at Script1$_run_closure69$_closure112.doCall(Script1.groovy:355) at Script1$_run_closure69.doCall(Script1.groovy:352) at Script1.run(Script1.groovy:332) at net.filebot.cli.ScriptShell.evaluate(Unknown Source) at net.filebot.cli.ScriptShell.runScript(Unknown Source) at net.filebot.cli.ArgumentProcessor.runScript(Unknown Source) at net.filebot.cli.ArgumentProcessor.run(Unknown Source) at net.filebot.Main.main(Unknown Source) Error (o_O) AMC call from custom script in user scripts: docker exec FileBot /opt/filebot/filebot -script fn:amc --output '/mnt/user/media/' \ --log-file amc.log \ --action move \ --conflict index -non-strict \ --db TheMovieDB \ --def subtitles=en \ --def pushbullet=$pushbullet_token \ --def pushover=$pushover_userkey:$pushover_apitoken \ "exec=/bin/ash /config/filebot_verify_suball.sh '{f}/'" \ music=y artwork=y \ ignore='idx|\.sub' \ 'movieFormat='"$movie_format" \ 'seriesFormat='"$series_format" \ 'musicFormat='"$music_format" \ "$file_name"
  5. 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.
  6. 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? https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui tower-diagnostics-20200520-0908.zip
  7. 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?
  8. 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?
  9. Does the invalidslot command work immediately? There is no output from the command in the terminal.
  10. 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...
  11. 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
  12. 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
  13. 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 9 Power_On_Hours -O--CK 047 047 000 - 38832 10 Spin_Retry_Count -O--CK 100 100 000 - 0 11 Calibration_Retry_Count -O--CK 100 100 000 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 234 192 Power-Off_Retract_Count -O--CK 200 200 000 - 175 193 Load_Cycle_Count -O--CK 175 175 000 - 77941 194 Temperature_Celsius -O---K 113 108 000 - 39 196 Reallocated_Event_Count -O--CK 120 120 000 - 80 197 Current_Pending_Sector -O--CK 200 198 000 - 31 198 Offline_Uncorrectable ----CK 200 198 000 - 0 199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0 200 Multi_Zone_Error_Rate ---R-- 200 190 000 - 2 I would assume that this builds confidence in using disk1 in its current state to rebuild disk7? Then move on and replace disk1.
  14. Extended test in progress. Would a screenshot be sufficient after or is a diagnostic file still best?
  15. 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: tower-diagnostics-20200517-1733.zip tower-diagnostics-20200517-1733.zip
  16. I actually do have a fairly recent diagnostics file. April 29. tower-diagnostics-20200429-0800.zip
  17. 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.
  18. One thing I should add is that the dying drive was placed into a Disabled state by unraid.
  19. No, the array has not been started. Are you saying I should place the potentially failing drive back in the array and rebuild once I've replaced the the fried drive with a new one? Then replace the failing drive? Thanks makes sense to me. Unfortunately I powered down once I saw that the to be discovered as fried drive was missing. I assumed I had bumped a sata cable or something simple. This means the important info in the logs are gone correct? I've attached the latest at least. tower-diagnostics-20200506-1653.zip
  20. So I had a disc that was giving SMART errors and I wanted to replace it before it went belly up. While swapping it out I had a drive possibly short and actually melt the sata data connector (one of those kapton over the 3.3v pins drives). The worst part being that I only have one parity. I have the functioning but old drive I can pull data off of but what would be the best sequence for me to take here to get back up and running. My last off-site backup was about a month ago so I should lose too much data either way but I'd obviously prefer to lose none.
  21. I'm about to replace the cpu in my server with something more powerful but equal cores. Do I have to undo all CPU pinning prior to the upgrade and then reapply or just leave everything as is through the upgrade?