• Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About DingHo

  • Rank


  • Gender
  • Location

Recent Profile Visitors

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

  1. @Shonky Thanks Shonky, best of luck.
  2. @Shonky Thanks for the update. I too attempted rebuilding the docker image, with no effect. I think I was able to chase down a cause for my problem, however not sure it applies to anyone but my particular case, and probably not to unRAID in general. When Plex was running its scheduled tasks, it was getting 'stuck' on some music files in one of my libraries. While stuck it would read like crazy on the cache drive, even though the songs are on the array. I could reproduce the issue several times by setting the scheduled task and the watching it get stuck. My temporary solut
  3. @JorgeB and @itimpi , Thank you both. I'm currently copying data off the bad drive. Can anyone confirm, I can shuffle around the drive order when I make a new config before rebuilding parity?
  4. Thanks @JorgeB Here's my plan moving forward, please help me do a sanity check: 1) Stop Array. New Config. Add the Unassigned Device (previous parity drive) as Disk 11 (encrypted). 2) Copy Disk 2 to Disk 11. 3) Stop Array. Tools, New Config. Remove Disk 2. (Can I put the other disks in any order at this point?) 4) Order New Parity Drive 5) Finish encrypting other disks while I wait. 6) Add new drive and parity sync.
  5. Hello, I'm in the process of encrypting my array, following SpaceInvader One's guide, so I'm currently operating without parity to speed things up. I received the popup notification "Offline uncorrectable is 1" for Disk 2, which I successfully encrypted and copied data to/from without errors yesterday. Today, while copying data with unBALANCE between two other disks I received the above error. SMART shows 1 Current Pending Sector. I then ran an extended SMART test (attached) and nothing appears to have changed. On the Main WebGUI page, Disk 2 still has
  6. You may need to resort to a VM to get that to work. Best of luck.
  7. Hi @rcrh, it is in fact only a music server. If you search for 'photos' in community applications you'll find plenty of photo servers. Good luck!
  8. Curious if anyone has made any progress on this issue. I'm still encountering it on a fairly regular basis, even after updating to 6.9.2.
  9. @jonp With your permission, I'll take a crack at generating a transcript with Google Speech-toText. I have an 96kb/s 44.1kHz MP3 of the podcast. If you're interested to provide a FLAC, it would improve the accuracy.
  10. Another thing I noticed during my last incident, when I ran 'docker stats', I could see that the netdata container was marked 'unhealthy' I never had netdata running previously when this happened, I just turned it on recently to try and figure this issue out. So I don't think this specific docker is the cause. Also, from the 5 diagnostics top files I have accumulated while this occurs: MiB Mem : 7667.6 total, 117.7 free, 6593.1 used, 956.7 buff/cache MiB Mem : 7667.6 total, 131.4 free, 6260.4 used, 1275.8 buff/cache Mi
  11. I think I'm having the same issue. I posted previously about it (link to thread with multiple diagnostic files below). Here's what I've found... iowait causes all 4 CPUs to peg at 100%, system becomes mostly unresponsive iotop -a shows large amount of accumulating READS from the cache disk (at >300MB/S), specifically, loop2 restarting a docker container via command line will fix the problem (for example, docker restart plex, or docker restart netdata) I can not figure out a pattern to when this happens. Mover or TRIM is not running. No one watching a plex movie
  12. Sorry, I misunderstood. If I restart only the plex docker, it goes back to normal operation. I haven't tried disabling/re-enabling the docker service and VM service.
  13. @JorgeB thanks for the reply. Is there anyway to check besides disabling docker/VMs? As this doesn’t occur predictably, and sometimes not for many days, I’d be without many services unless I built another system to take over network duties. thanks again.
  14. Occurred again today. I noticed the cache drive was being read at a very high rate while CPUs were pegged to 100% again. Attached new diags. Any help appreciated. scour-diagnostics-20210503-0959.zip