ShangHangin

Members
  • Posts

    96
  • Joined

  • Last visited

Everything posted by ShangHangin

  1. Found my problem...I had not set one of the library transcode caches to /temp (hand left as default .) Delete the docker, which cleaned up the docker image (dropping about 20% usage), reinstalled and restarted....all is good! TDARR is filling up my docker container. I had installed TDARR the other day, and everything was running find - transcoding for a couple days. I then had a power outage and after a restart, during parity check, I got a docker image space usage error. I stopped TDARR and the image stopped filling. After the parity check was complete, I restarted TDARR - and more filling. I have attached the TDARR log files. Advice appreciated. TDARR
  2. I have changed a re-seated cables on the one drive I had the issue. Have reset the counters, run a parity check, no issues (an a test of one). Will continue to monitor.
  3. Thanks - check and changed the cable, no increase in the error count. Seems corrected - will monitor. Any way to clear the error count so that is does not keep popping up as an error?
  4. Diagnostics attached. Advice appreciated. SH hal-9000-diagnostics-20201006-0638.zip
  5. I have a question on UDMA CRC error count. I have one drive that the error count increases at every parity check. When I run an extended SMART test (attached), the results return as a "Pass". Should I be concerned? I have pre-cleared unassigned drives I can swap into the array if there is a concern. Thanks in advance. SH hal-9000-smart-20201005-1134.zip
  6. I have a disk with UDMA CRC error count warning. Have run a SMART test which passed. Should I be concerned or just monitor? Thanks in advance. SH. hal-9000-smart-20200608-1145.zip
  7. Extended test attached hal-9000-smart-20200401-0306.zip
  8. Diagnostics and Extended SMART Test Reports attached. Thanks for any guidance. SH hal-9000-diagnostics-20200330-0842.zip hal-9000-smart-20200330-2223.zip
  9. Hello Community, I have read errors on one of my disks. I have attached the SMART report (ran the short version) which shows no errors. Also attached the system log that does show the disk error. 1. Should I be concerned? 2. Actions to take? I am somewhat challenged to put my hands on my server, as I am in the USA and my server is in my house in China (yes, I am a Covid refugee). I am accessing my server using Zero Tier. Thanks for the advice. SH hal-9000-smart-20200330-2223.zip hal-9000-syslog-20200330-1435.zip
  10. When I updated to Unraid 6.8.1, it broke binhex-plex. All my dockers restarted cleanly, but this one - got a "Execution Error" dialogue box. Upon restoring to 6.8.0, everything worked fine. I am running transcoding in an Nvidia GPU. Sorry I did not pull log files, as I was short on time. Any thoughts?
  11. I am having issues with Plex not updating the library when new files are added or a manual library scan. I deleted and reinstalled the docker, thinking there was something corrupt there, no difference. I have attached the Plex log and system log. Thanks in advance for the assistance. SH Plex Media Server.log.zip hal-9000-syslog-20191207-1335.zip
  12. Thanks. I appreciate the quick reply...I am a linux newbie...I am back on the road to file system conversion completion with your assistance
  13. I am in the process of converting my file system from RFS to XFS. The first 3 disks went perfectly - I hit disk four and had an rsync error (as in the attached photo). I am looking for some guidance as to how to correct this issue and keep moving.
  14. Binhex - love your stuff. I have a plex question...is there a way to have plex meta-data scraping through VPN, while the streaming non-VPN. I live in a region that blocks access to theTVDB thus cannot get show metadata. I am running Binhex-deluge with privoxy, bh-SABnzd, Sonar, Radar, etc... If this is not possible, then routing all plex traffic through VPN. Any thoughts appreciated. Thanks - SH.
  15. I am not sure what is the issue - below is the error message for the WebIU log . DownloadedEpisodesImportService Import failed, path does not exist or is not accessible by Sonarr: /downloads/complete/<tvshow name> 5:40am Per my physical drive mapping: /mnt/cache/downloads/Downloads/ which is mapped to /data for Sonar and SAB. I have no path named /downloads/complete/ - All my container paths for download data are named /data - nowhere do I have a container named /downloads If I do a manual import via the Sonar WebUI, it maps to /data/complete/ I have no issues. I am not sure why the autoprocessing tries /downloads/complete. SAB saves its files to /data/complete - the files are there. (As a side note, for some reason when using Chrome on a Mac, the Sonar UI never gets beyond the bouncing ball - this is a new phenomenon I have not seen before. Safari has no issue. ) Thanks in advance for the support. SH
  16. Sonar in outer space. I am not sure what is happening - this is a new problem after everything had been working well. Sonar starts, the web GUI comes up partially and all I see is the bouncing ball left to right. I can never get fully into Sonar. I believe I have all the mapping correct - Below is the log from Sonar - I get the import failed issues mentioned in the above posts - but it was working before. Created by...___. .__ .__\_ |__ |__| ____ | |__ ____ ___ ___| __ \| |/ \| | \_/ __ \\ \/ /| \_\ \ | | \ Y \ ___/ > <|___ /__|___| /___| /\___ >__/\_ \\/ \/ \/ \/ \/https://hub.docker.com/u/binhex/2018-03-27 20:32:36.286253 [info] Host is running unRAID2018-03-27 20:32:36.314044 [info] System information Linux 78df25834de1 4.14.13-unRAID #1 SMP PREEMPT Wed Jan 10 10:27:09 PST 2018 x86_64 GNU/Linux2018-03-27 20:32:36.345453 [info] PUID defined as '99'2018-03-27 20:32:36.377563 [info] PGID defined as '100'2018-03-27 20:32:36.446291 [info] UMASK defined as '000'2018-03-27 20:32:36.476325 [info] Permissions already set for volume mappings2018-03-27 20:32:36.510804 [info] Starting Supervisor...2018-03-27 20:32:36,674 CRIT Set uid to user 02018-03-27 20:32:36,674 INFO Included extra file "/etc/supervisor/conf.d/sonarr.conf" during parsing2018-03-27 20:32:36,677 INFO supervisord started with pid 72018-03-27 20:32:37,678 INFO spawned: 'sonarr' with pid 422018-03-27 20:32:37,679 INFO reaped unknown pid 82018-03-27 20:32:38,004 DEBG 'sonarr' stdout output:[Info] Bootstrap: Starting Sonarr - /usr/lib/sonarr/NzbDrone.exe - Version 2.0.0.51632018-03-27 20:32:38,462 DEBG 'sonarr' stdout output:[Info] AppFolderInfo: Data directory is being overridden to [/config]2018-03-27 20:32:38,741 DEBG 'sonarr' stdout output:[Info] Router: Application mode: Interactive2018-03-27 20:32:38,741 INFO success: sonarr entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2018-03-27 20:32:40,300 DEBG 'sonarr' stdout output:[Info] MigrationLogger: *** Migrating data source=/config/nzbdrone.db;cache size=-10485760;datetimekind=Utc;journal mode=Wal;pooling=True;version=3 ***2018-03-27 20:32:40,471 DEBG 'sonarr' stdout output:[Info] MigrationLogger: *** Migrating data source=/config/logs.db;cache size=-10485760;datetimekind=Utc;journal mode=Wal;pooling=True;version=3 ***2018-03-27 20:32:40,498 DEBG 'sonarr' stdout output:[Info] OwinHostController: Listening on the following URLs:2018-03-27 20:32:40,499 DEBG 'sonarr' stdout output:[Info] OwinHostController: http://*:8989/2018-03-27 20:32:40,695 DEBG 'sonarr' stdout output:[Info] NancyBootstrapper: Starting Web Server2018-03-27 20:33:17,255 DEBG 'sonarr' stdout output:[Error] DownloadedEpisodesImportService: Import failed, path does not exist or is not accessible by Sonarr: /downloads/complete/Homeland.S07E07.720p.WEB.H264-DEFLATE[rarbg]
  17. Squid - thanks. Was planning the reboot after I complete my parity check after the unclean power down. The cache drive is on my maintenance list to replace along with a conversion of the entire array to XFS. Once done, will confirm all is happy and close the thread. SH UPDATE: Confirmed and operational - thanks Squid!
  18. I have had the same issues after an unclean shut down (power outage). Through the Unraid IU Settings>Dockers have deleted the img file and tried to restart the dockers - no luck - Docker tab - "Docker Service failed to start" I have attached my diagnostics. I assume the docker image was corrupted by the unclean shutdown. Thanks for the support hal_9000-diagnostics-20180304-0945.zip
  19. @trurl Sorry for my poor choice of words regarding parity. As I plan to increase drive sizes during the conversion process, my planned first step is to upgrade the Parity drive and let unRaid rebuild on the larger disk. After that is complete, then move onto to the file system change process by using a blank drive (pre-cleared) formatted to XFS, and copying data over following the "Mirror each disk with rsync, preserving parity" process. I plan to use this process because I have a mix of user share and excluded drive. I hope I am on the right track.
  20. @Lev Yes, I have come so far yet have a long journey ahead of me. Since I have been using unRaid, I have never had an issue with RFS. Most likely luck, but I continue to be "Grasshopper" like in the ways of Linux. Many thanks for your sage advice - more options to consider in my quest.
  21. Thanks for the comments. I am planning to move forward on this. From a planning standpoint, I am going to first upgrade my Parity drive, re-establish parity, then roll through the drives in the following order. For most drives, the new "destination" drive is larger than the current drive. In the end, I will have 3 "leftover" 2GB drives. Let me know if you see any holes in the plan or any "gotchas" to the conversion.
  22. I am going to be expanding my array starting with a replacement of my parity drive and swapping out a few drives along the way. I am running 6.3.5 RFS. I have a 21TB array made up of 3- 3GB drives, 6-2GB drives, 500MB cache. My plan was to bump the parity to a 4GB, replace a couple of the older 2GB with 4GBs, move one of the 2GB's as a cache drive. My question to the experts: Is it worth going through the trouble to convert to the XFS file system? If so, is this the time to do it? I look for thoughts from the community. Thanks,
  23. I think I have a controller problem. Switched location, same controller - no luck; moved to another controller - success. Have new controller on order (replacing Marvel controller with an LSI). Not sure why the updated version is more "sensitive" as everything was working prior to the upgrade.
  24. Diagnostics attached hal_9000-diagnostics-20170826-1149.zip
  25. I am still looking for assistance as to why my cache drive is not recognized. The device is physically present as can be seen by the device listing below. Am I missing something when I did the upgrade from 5.0.5->6.3.5 Please advise. ----------------------------- root@HAL_9000:/dev/disk/by-id# ls -l total 0 lrwxrwxrwx 1 root root 9 Aug 26 09:39 ata-ST2000DL001-9VT156_5YD2ZP9B -> ../../sdl lrwxrwxrwx 1 root root 10 Aug 26 09:39 ata-ST2000DL001-9VT156_5YD2ZP9B-part1 -> ../../sdl1 lrwxrwxrwx 1 root root 9 Aug 25 17:22 ata-ST2000DL001-9VT156_5YD6CTMD -> ../../sde lrwxrwxrwx 1 root root 10 Aug 25 17:22 ata-ST2000DL001-9VT156_5YD6CTMD-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 Aug 25 17:22 ata-ST2000DL001-9VT156_5YD6FSNN -> ../../sdf lrwxrwxrwx 1 root root 10 Aug 25 17:22 ata-ST2000DL001-9VT156_5YD6FSNN-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 Aug 25 17:22 ata-ST2000DL003-9VT166_6YD0H04A -> ../../sdd lrwxrwxrwx 1 root root 10 Aug 25 17:22 ata-ST2000DL003-9VT166_6YD0H04A-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 Aug 25 17:22 ata-ST2000DM001-9YN164_W2F02JC5 -> ../../sdg lrwxrwxrwx 1 root root 10 Aug 25 17:22 ata-ST2000DM001-9YN164_W2F02JC5-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 9 Aug 26 09:54 ata-ST500DM002-1BC142_S2A2X477 -> ../../sdh lrwxrwxrwx 1 root root 10 Aug 26 09:54 ata-ST500DM002-1BC142_S2A2X477-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 9 Aug 26 09:52 ata-WDC_WD20EARX-00PASB0_WD-WMAZA7957124 -> ../../sdj lrwxrwxrwx 1 root root 10 Aug 26 09:52 ata-WDC_WD20EARX-00PASB0_WD-WMAZA7957124-part1 -> ../../sdj1 lrwxrwxrwx 1 root root 9 Aug 25 17:22 ata-WDC_WD30EZRX-00D8PB0_WD-WCC4N1060268 -> ../../sdb lrwxrwxrwx 1 root root 10 Aug 25 17:22 ata-WDC_WD30EZRX-00D8PB0_WD-WCC4N1060268-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 Aug 26 09:55 ata-WDC_WD30EZRX-00D8PB0_WD-WMC4N0F377PE -> ../../sdk lrwxrwxrwx 1 root root 10 Aug 26 09:55 ata-WDC_WD30EZRX-00D8PB0_WD-WMC4N0F377PE-part1 -> ../../sdk1 lrwxrwxrwx 1 root root 9 Aug 25 17:22 ata-WDC_WD30EZRX-00SPEB0_WD-WCC4E1038872 -> ../../sdc lrwxrwxrwx 1 root root 10 Aug 25 17:22 ata-WDC_WD30EZRX-00SPEB0_WD-WCC4E1038872-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 Aug 25 17:22 ata-WDC_WD30PURX-64P6ZY0_WD-WMC4N0M2Z7ED -> ../../sdi lrwxrwxrwx 1 root root 10 Aug 25 17:22 ata-WDC_WD30PURX-64P6ZY0_WD-WMC4N0M2Z7ED-part1 -> ../../sdi1 lrwxrwxrwx 1 root root 9 Aug 25 17:22 usb-Sony_Storage_Media_AB2211108174003136-0:0 -> ../../sda lrwxrwxrwx 1 root root 10 Aug 25 17:22 usb-Sony_Storage_Media_AB2211108174003136-0:0-part1 -> ../../sda1 lrwxrwxrwx 1 root root 9 Aug 25 17:22 wwn-0x1088186779592314881x -> ../../sdi lrwxrwxrwx 1 root root 10 Aug 25 17:22 wwn-0x1088186779592314881x-part1 -> ../../sdi1 lrwxrwxrwx 1 root root 9 Aug 25 17:22 wwn-0x11129719321484480513x -> ../../sdb lrwxrwxrwx 1 root root 10 Aug 25 17:22 wwn-0x11129719321484480513x-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 Aug 26 09:52 wwn-0x12643206672075083777x -> ../../sdj lrwxrwxrwx 1 root root 10 Aug 26 09:52 wwn-0x12643206672075083777x-part1 -> ../../sdj1 lrwxrwxrwx 1 root root 9 Aug 26 09:39 wwn-0x13115951031382986752x -> ../../sdl lrwxrwxrwx 1 root root 10 Aug 26 09:39 wwn-0x13115951031382986752x-part1 -> ../../sdl1 lrwxrwxrwx 1 root root 9 Aug 25 17:22 wwn-0x17191845585664233473x -> ../../sdc lrwxrwxrwx 1 root root 10 Aug 25 17:22 wwn-0x17191845585664233473x-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 Aug 25 17:22 wwn-0x17964091599503773696x -> ../../sdf lrwxrwxrwx 1 root root 10 Aug 25 17:22 wwn-0x17964091599503773696x-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 Aug 25 17:22 wwn-0x2270452567899131904x -> ../../sdg lrwxrwxrwx 1 root root 10 Aug 25 17:22 wwn-0x2270452567899131904x-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 9 Aug 25 17:22 wwn-0x2557260717170380800x -> ../../sdd lrwxrwxrwx 1 root root 10 Aug 25 17:22 wwn-0x2557260717170380800x-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 Aug 25 17:22 wwn-0x3640111702948728832x -> ../../sde lrwxrwxrwx 1 root root 10 Aug 25 17:22 wwn-0x3640111702948728832x-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 Aug 26 09:55 wwn-0x4059813130583560193x -> ../../sdk lrwxrwxrwx 1 root root 10 Aug 26 09:55 wwn-0x4059813130583560193x-part1 -> ../../sdk1 lrwxrwxrwx 1 root root 9 Aug 26 09:54 wwn-0x5858697946123489280x -> ../../sdh lrwxrwxrwx 1 root root 10 Aug 26 09:54 wwn-0x5858697946123489280x-part1 -> ../../sdh1