RageInvader

I'm getting these messages every few hours, although mine are happening on my Sata Controller (SAS2LP-MV8) followed by at a errors, and its causing parity errors, have reseated every cable and my card to the board, and still getting errors. Mar 24 07:21:16 Ness kernel: dmar: DRHD: handling fault status reg 3 Mar 24 07:21:16 Ness kernel: dmar: DMAR:[DMA Write] Request device [04:00.0] fault addr ff67e000 Mar 24 07:21:16 Ness kernel: DMAR:[fault reason 05] PTE Write access is not set Mar 24 07:21:16 Ness kernel: dmar: DRHD: handling fault status reg 3 Mar 24 07:21:16 Ness kernel: dmar: DMAR:[DMA Write] Request device [04:00.0] fault addr ff67e000 Mar 24 07:21:16 Ness kernel: DMAR:[fault reason 05] PTE Write access is not set Mar 24 07:21:16 Ness kernel: dmar: DRHD: handling fault status reg 3 Mar 24 07:21:16 Ness kernel: dmar: DMAR:[DMA Write] Request device [04:00.0] fault addr ff67f000 Mar 24 07:21:16 Ness kernel: DMAR:[fault reason 05] PTE Write access is not set Mar 24 07:21:16 Ness kernel: dmar: DRHD: handling fault status reg 3 Mar 24 07:21:16 Ness kernel: dmar: DMAR:[DMA Write] Request device [04:00.0] fault addr ff67f000 Mar 24 07:21:16 Ness kernel: DMAR:[fault reason 05] PTE Write access is not set Mar 24 07:21:16 Ness kernel: dmar: DRHD: handling fault status reg 3 Mar 24 07:21:16 Ness kernel: dmar: DMAR:[DMA Write] Request device [04:00.0] fault addr ff67f000 Mar 24 07:21:16 Ness kernel: DMAR:[fault reason 05] PTE Write access is not set Mar 24 07:21:46 Ness kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Mar 24 07:21:46 Ness kernel: sas: trying to find task 0xffff8802233da200 Mar 24 07:21:46 Ness kernel: sas: sas_scsi_find_task: aborting task 0xffff8802233da200 Mar 24 07:21:46 Ness kernel: sas: sas_scsi_find_task: task 0xffff8802233da200 is aborted Mar 24 07:21:46 Ness kernel: sas: sas_eh_handle_sas_errors: task 0xffff8802233da200 is aborted Mar 24 07:21:46 Ness kernel: sas: ata10: end_device-1:3: cmd error handler Mar 24 07:21:46 Ness kernel: sas: ata7: end_device-1:0: dev error handler Mar 24 07:21:46 Ness kernel: sas: ata8: end_device-1:1: dev error handler Mar 24 07:21:46 Ness kernel: sas: ata9: end_device-1:2: dev error handler Mar 24 07:21:46 Ness kernel: sas: ata10: end_device-1:3: dev error handler Mar 24 07:21:46 Ness kernel: ata10.00: exception Emask 0x0 SAct 0x4 SErr 0x0 action 0x6 frozen Mar 24 07:21:46 Ness kernel: ata10.00: failed command: READ FPDMA QUEUED Mar 24 07:21:46 Ness kernel: ata10.00: cmd 60/00:00:10:bb:f6/04:00:fa:00:00/40 tag 2 ncq 524288 in Mar 24 07:21:46 Ness kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Mar 24 07:21:46 Ness kernel: ata10.00: status: { DRDY } Mar 24 07:21:46 Ness kernel: ata10: hard resetting link Mar 24 07:21:46 Ness kernel: sas: ata11: end_device-1:4: dev error handler Mar 24 07:21:46 Ness kernel: sas: ata12: end_device-1:5: dev error handler Mar 24 07:21:46 Ness kernel: sas: ata13: end_device-1:6: dev error handler Mar 24 07:21:46 Ness kernel: sas: sas_form_port: phy0 belongs to port3 already(1)! Mar 24 07:21:48 Ness kernel: drivers/scsi/mvsas/mv_sas.c 1430:mvs_I_T_nexus_reset for device[0]:rc= 0 Mar 24 07:21:49 Ness kernel: ata10.00: configured for UDMA/133 Mar 24 07:21:49 Ness kernel: ata10.00: device reported invalid CHS sector 0 Mar 24 07:21:49 Ness kernel: ata10: EH complete Mar 24 07:21:49 Ness kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1

Hey, I'm having a problem I just can't figure out how to fix... My uTorrent runs on a MacMini, which I use automator to either extract or copy the .mkv file to my unRAID server into Filebot's /input folder. But Filebot will sometimes start processing the file before the MacMini has finished extracting or copying the file, thus leading to the resulting file, that has been moved to Plex's folder being corrupt. Here is the following settings in filebot.conf SETTLE_DURATION=03:00 MAX_WAIT_TIME=59:00 MIN_PERIOD=00:10

To use plexconnect on your unRAID server you will have to change the port for unRAIDs webGUI. The Apple TV will only use port 80 and 443 for receiving its content.

Ahh yes that explains why after the restart it was cyberghosts fork, as I couldn't get the variable working either. The reason i'd prefer to pick any fork as, I have actually forked CyberGhost's fork and changed a few things and would love to use it.

Ok, building on docker for the PlexConnect. (it's Pending since 15 minutes, hopefully it will build soon!). I added a GHOST variable. If present, it will use the Cyberghost84 fork. I'll reply again when the build will be complete. Hey, the new docker is working great pulls CyberGhost84's fork. Could I be a pain and suggest you change it so that you provide the variable "FORK" and then type in the url for the fork you want to use... would mean you could use any fork. Just a Thought. Many Thanks

Ok, building on docker for the PlexConnect. (it's Pending since 15 minutes, hopefully it will build soon!). I added a GHOST variable. If present, it will use the Cyberghost84 fork. I'll reply again when the build will be complete. Fantastic, look forward to it. still been using the Plugin currently, as I prefer Cyberghosts Fork

Love your PlexConnect docker, but I liked using CyberGhost84's PlexConnect fork as the Views are much better. Is there anyway I could change which fork is downloaded? Thanks.