jaylo123

Members
 View Profile  See their activity

  • Posts

    85

  • Joined

 Content Type 

Posts posted by jaylo123

    Downgraded back to 6.6.7 due to Sqlite corruption

    in General Support

    Posted

    On 10/11/2019 at 4:51 AM, nuhll said:

    can anyone clarify if that only happens if your appdata is not on cache (or lets say the docker is not on cache?)

    I can verify that my Plex sqlitedb has not had an issue ever since I moved it to my SSD cache drive and off of my spinning disks in the main array.  I did this before I even knew about this thread / posts on Reddit about this issue.  I rebuilt and rebuilt, but every day or two the database would become malformed.  It's been up and stable for weeks now.

     

    Shame, I lost a lot of user data, and since the backups were stored on the spinning disks they, too, were toast.  My fault, I should have kept better backups, but it is what it is.

    Blacklist an IOMMU group in syslinux.cfg?

    in General Support

    Posted · Edited by Jason Harris

    Hello,

     

    I'm seeing a ton of errors around IOMMU, VFIO and my onboard Intel GPU.  I don't necessarily want to disable it in case I need console access to my Unraid server.  The errors are around PTE read errors:

      

    Dec 26 20:48:43 unraid kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 6fae4000 [fault reason 06] PTE Read access is not set
Dec 26 20:48:43 unraid kernel: DMAR: DRHD: handling fault status reg 2
Dec 26 20:48:43 unraid kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 6fae5000 [fault reason 06] PTE Read access is not set
Dec 26 20:48:43 unraid kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 6fae5000 [fault reason 06] PTE Read access is not set
Dec 26 20:48:43 unraid kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 6fae5000 [fault reason 06] PTE Read access is not set
Dec 26 20:48:43 unraid kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 6fae5000 [fault reason 06] PTE Read access is not set
Dec 26 20:48:43 unraid kernel: DMAR: DRHD: handling fault status reg 2
Dec 26 20:48:48 unraid kernel: dmar_fault: 5102159 callbacks suppressed

     

    Rinse, repeat.

     

    Now, the "correct" fix is to disable the onboard GPU in my BIOS.  However, I would lose all console access from the local system if I do this, as my actual GPU is an Nvidia GRID M60, and it's working just fine.  So I need the GPU to work during POST, but after the OS takes over I couldn't care less if it is functional.

     

    So instead, I would like to just blacklist the 00:02.0 device entirely from loading at boot time.  What can I pass along on the kernel line in syslinux.cfg that will just disable this device from loading into an IOMMU group / VFIO group / just shut it the heck down?