Jump to content

emmcee

Members
  • Content Count

    89
  • Joined

  • Last visited

Community Reputation

1 Neutral

About emmcee

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. As luck would have it, today is my 6th anniversary - at least it was 6 years ago I received my licence key. While I’ve had a couple of issues over the years, they have been few and far between and almost always been answered quickly in the forum. And I’ve not lost a byte of data in that time! I come for the parity, but I stay for the community!
  2. I’ve had some success with the resilio sync docker as a replacement.
  3. I’m running linuxserver/plex with plexpass if it helps. Might be worth installing it to see if it works.
  4. Sorry. I thought I commented on the fix. I think this was related to that Plex error and iGPU passthrough. When I updated the Plex container the error went away and system has been up for 5 days. I think the 24 hour thing was due to people sitting down to watch Plex around 8PM.
  5. And it looks like Plex doesn't feel so good. From the plex container log: failed to open /data/jenkins/conan_build/290002784/conan/.conan/data/libva/2.1.0-40/plex/stable/package/81a2df5e16044d97d1b088b0e6c9598b5b17f233/lib/dri/hybrid_drv_video.so Failed to wrapper hybrid_drv_video.so failed to open /data/jenkins/conan_build/290002784/conan/.conan/data/libva/2.1.0-40/plex/stable/package/81a2df5e16044d97d1b088b0e6c9598b5b17f233/lib/dri/hybrid_drv_video.so Failed to wrapper hybrid_drv_video.so failed to open /data/jenkins/conan_build/290002784/conan/.conan/data/libva/2.1.0-40/plex/stable/package/81a2df5e16044d97d1b088b0e6c9598b5b17f233/lib/dri/hybrid_drv_video.so Failed to wrapper hybrid_drv_video.so failed to open /data/jenkins/conan_build/290002784/conan/.conan/data/libva/2.1.0-40/plex/stable/package/81a2df5e16044d97d1b088b0e6c9598b5b17f233/lib/dri/hybrid_drv_video.so Failed to wrapper hybrid_drv_video.so failed to open /data/jenkins/conan_build/290002784/conan/.conan/data/libva/2.1.0-40/plex/stable/package/81a2df5e16044d97d1b088b0e6c9598b5b17f233/lib/dri/hybrid_drv_video.so Failed to wrapper hybrid_drv_video.so failed to open /data/jenkins/conan_build/290002784/conan/.conan/data/libva/2.1.0-40/plex/stable/package/81a2df5e16044d97d1b088b0e6c9598b5b17f233/lib/dri/hybrid_drv_video.so Failed to wrapper hybrid_drv_video.so
  6. And right on cue it hangs again. Just before it hangs I see this in the syslog (I amreluctant to post itas it's not anonymised) May 22 20:26:38 Tower kernel: DMAR: DRHD: handling fault status reg 2 May 22 20:26:38 Tower kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 313000 [fault reason 05] PTE Write access is not set May 22 20:26:38 Tower kernel: DMAR: DRHD: handling fault status reg 2 May 22 20:26:38 Tower kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 315000 [fault reason 05] PTE Write access is not set May 22 20:26:38 Tower kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 316000 [fault reason 05] PTE Write access is not set May 22 20:26:38 Tower kernel: DMAR: DRHD: handling fault status reg 2 May 22 20:26:38 Tower kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 317000 [fault reason 05] PTE Write access is not set May 22 20:26:44 Tower kernel: [drm] GPU HANG: ecode 8:2:0x9bd7cfff, in Plex Transcoder [4974], reason: hang on vcs0, action: reset May 22 20:26:44 Tower kernel: i915 0000:00:02.0: Resetting vcs0 for hang on vcs0 May 22 20:26:52 Tower kernel: i915 0000:00:02.0: Resetting rcs0 for no progress on rcs0 May 22 20:26:52 Tower kernel: dmar_fault: 47723 callbacks suppressed May 22 20:26:52 Tower kernel: DMAR: DRHD: handling fault status reg 2 May 22 20:26:52 Tower kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 313000 [fault reason 23] Unknown May 22 20:26:52 Tower kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 314000 [fault reason 23] Unknown May 22 20:26:52 Tower kernel: DMAR: DRHD: handling fault status reg 2 May 22 20:26:52 Tower kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 315000 [fault reason 23] Unknown May 22 20:26:52 Tower kernel: DMAR: DRHD: handling fault status reg 2 May 22 20:26:52 Tower kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 316000 [fault reason 23] Unknown May 22 20:26:57 Tower kernel: dmar_fault: 31347 callbacks suppressed May 22 20:26:57 Tower kernel: DMAR: DRHD: handling fault status reg 3 May 22 20:26:57 Tower kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 313000 [fault reason 05] PTE Write access is not set May 22 20:26:57 Tower kernel: DMAR: DRHD: handling fault status reg 3 May 22 20:26:57 Tower kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 318000 [fault reason 05] PTE Write access is not set May 22 20:26:57 Tower kernel: DMAR: DRHD: handling fault status reg 3 May 22 20:26:57 Tower kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 31b000 [fault reason 05] PTE Write access is not set May 22 20:26:57 Tower kernel: DMAR: DRHD: handling fault status reg 2 May 22 20:27:02 Tower kernel: dmar_fault: 3344072 callbacks suppressed May 22 20:27:02 Tower kernel: DMAR: DRHD: handling fault status reg 2 May 22 20:27:02 Tower kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 116d1a000 [fault reason 23] Unknown May 22 20:27:02 Tower kernel: DMAR: DRHD: handling fault status reg 3 May 22 20:27:02 Tower kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 116d1d000 [fault reason 23] Unknown May 22 20:27:02 Tower kernel: DMAR: DRHD: handling fault status reg 2 May 22 20:27:02 Tower kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 116d21000 [fault reason 23] Unknown May 22 20:27:02 Tower kernel: DMAR: DRHD: handling fault status reg 2 May 22 20:27:14 Tower kernel: i915 0000:00:02.0: Resetting vcs0 for no progress on vcs0 May 22 20:27:14 Tower kernel: dmar_fault: 3249556 callbacks suppressed May 22 20:27:14 Tower kernel: DMAR: DRHD: handling fault status reg 2 May 22 20:27:14 Tower kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 313000 [fault reason 05] PTE Write access is not set May 22 20:27:14 Tower kernel: DMAR: DRHD: handling fault status reg 2 May 22 20:27:14 Tower kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 315000 [fault reason 05] PTE Write access is not set May 22 20:27:14 Tower kernel: DMAR: DRHD: handling fault status reg 2 May 22 20:27:14 Tower kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 316000 [fault reason 05] PTE Write access is not set May 22 20:27:14 Tower kernel: DMAR: DRHD: handling fault status reg 3 May 22 20:27:30 Tower kernel: i915 0000:00:02.0: Resetting rcs0 for no progress on rcs0, vcs0 May 22 20:27:30 Tower kernel: i915 0000:00:02.0: Resetting vcs0 for no progress on rcs0, vcs0 May 22 20:27:30 Tower kernel: dmar_fault: 1920976 callbacks suppressed May 22 20:27:30 Tower kernel: DMAR: DRHD: handling fault status reg 2 May 22 20:27:30 Tower kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 313000 [fault reason 05] PTE Write access is not set May 22 20:27:30 Tower kernel: DMAR: DRHD: handling fault status reg 2 May 22 20:27:30 Tower kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 315000 [fault reason 05] PTE Write access is not set May 22 20:27:30 Tower kernel: DMAR: DRHD: handling fault status reg 2 May 22 20:27:30 Tower kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 316000 [fault reason 05] PTE Write access is not set May 22 20:27:30 Tower kernel: DMAR: DRHD: handling fault status reg 2 May 22 20:27:35 Tower kernel: dmar_fault: 27784 callbacks suppressed May 22 20:27:35 Tower kernel: DMAR: DRHD: handling fault status reg 3 May 22 20:27:35 Tower kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 313000 [fault reason 05] PTE Write access is not set May 22 20:27:35 Tower kernel: DMAR: DRHD: handling fault status reg 2 May 22 20:27:35 Tower kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 317000 [fault reason 05] PTE Write access is not set May 22 20:27:35 Tower kernel: DMAR: DRHD: handling fault status reg 2 May 22 20:27:35 Tower kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 319000 [fault reason 05] PTE Write access is not set May 22 20:27:35 Tower kernel: DMAR: DRHD: handling fault status reg 2 May 22 20:27:42 Tower kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 May 22 20:27:42 Tower kernel: dmar_fault: 1239 callbacks suppressed May 22 20:27:42 Tower kernel: DMAR: DRHD: handling fault status reg 3 May 22 20:27:42 Tower kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 313000 [fault reason 05] PTE Write access is not set May 22 20:27:42 Tower kernel: DMAR: DRHD: handling fault status reg 2 May 22 20:27:42 Tower kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 317000 [fault reason 05] PTE Write access is not set May 22 20:27:42 Tower kernel: DMAR: DRHD: handling fault status reg 2 May 22 20:27:42 Tower kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 319000 [fault reason 05] PTE Write access is not set May 22 20:27:42 Tower kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 31a000 [fault reason 05] PTE Write access is not set May 22 20:27:48 Tower kernel: dmar_fault: 27637 callbacks suppressed May 22 20:27:48 Tower kernel: DMAR: DRHD: handling fault status reg 2 May 22 20:27:48 Tower kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 313000 [fault reason 05] PTE Write access is not set May 22 20:27:48 Tower kernel: DMAR: DRHD: handling fault status reg 2 May 22 20:27:48 Tower kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 317000 [fault reason 05] PTE Write access is not set May 22 20:27:48 Tower kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 318000 [fault reason 05] PTE Write access is not set May 22 20:27:48 Tower kernel: DMAR: DRHD: handling fault status reg 2 May 22 20:27:48 Tower kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 319000 [fault reason 05] PTE Write access is not set May 22 20:27:54 Tower kernel: dmar_fault: 3722 callbacks suppressed May 22 20:27:54 Tower kernel: DMAR: DRHD: handling fault status reg 2 May 22 20:27:54 Tower kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 313000 [fault reason 05] PTE Write access is not set May 22 20:27:54 Tower kernel: DMAR: DRHD: handling fault status reg 2 May 22 20:27:54 Tower kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 317000 [fault reason 05] PTE Write access is not set May 22 20:27:54 Tower kernel: DMAR: DRHD: handling fault status reg 2 May 22 20:27:54 Tower kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 319000 [fault reason 05] PTE Write access is not set May 22 20:27:54 Tower kernel: DMAR: DRHD: handling fault status reg 2 I found this which indicates it may be due to GPU. I'm passing the iGPU from my i7-5775c to the Plex docker - could that be related?
  7. Oh, very cool. I've rebooted and enabled that now. I'll post up if it hangs again.
  8. I've had an issue twice now since upgrading to 6.7 where the server just hangs. No network activity and nothing on the console if I plug in a monitor to HDMI. The power LED is still lit on the server but nothing else. When I restarted last night it did a parity check and it sent an email report about 4 hours ago, but I just sat down to watch something on plex and server is down again. Is there any way to get diagnostics in the case of no console/nmo network? I'm guessing not.
  9. The Open Files plugin will show you which processes have open files. I found this very useful to track down why my disks were spinning up.
  10. emmcee

    SSDs running hot

    It’s a new case, but airflow should be better as it’s much larger and the SSDs are beside a large vent. The old Kingston cache drive is still in there and is in and adjacent bay to the Crucial drives, but it idles 15deg cooler than the Crucials.
  11. emmcee

    SSDs running hot

    Looming at Grafna, it seems it hit 65deg C 3 times over the last 90 days. Not ideal, but still within spec for the SSD. I assume it will throttle if it gets any higher. It it would be great if we could set thresholds on each individual drive for warnings.
  12. Do you have any unassigned drives? It looks like they are monitored but there is no way to exclude them. I had this issue and disconnecting an unassigned drive fixed it.
  13. Yeah, I think I’ll swap in the spare and do some preclude runs on the drive and see what happens. I have a couple of months of warranty left anyway.
  14. Thanks Johnnie tower-smart-20190301-1001.zip