November 18, 20169 yr Hi, I have an issue where my server is running very slow (mover is running about about 1GB every 20-30 mins) I can see these errors in my log which appear to be relating to a hard disk issue but the addresses do not match up to anything in my device list? Can someone throw me a bone please? Nov 18 12:05:06 UNRAIDSERVER kernel: DMAR: DRHD: handling fault status reg 3 Nov 18 12:05:06 UNRAIDSERVER kernel: DMAR: DMAR:[DMA Read] Request device [04:00.0] fault addr ffff0000 Nov 18 12:05:06 UNRAIDSERVER kernel: DMAR:[fault reason 06] PTE Read access is not set Nov 18 12:05:06 UNRAIDSERVER kernel: DMAR: DRHD: handling fault status reg 3 Nov 18 12:05:06 UNRAIDSERVER kernel: DMAR: DMAR:[DMA Read] Request device [04:00.0] fault addr fffe0000 Nov 18 12:05:06 UNRAIDSERVER kernel: DMAR:[fault reason 06] PTE Read access is not set Nov 18 12:05:06 UNRAIDSERVER kernel: DMAR: DRHD: handling fault status reg 3 Nov 18 12:05:06 UNRAIDSERVER kernel: DMAR: DMAR:[DMA Read] Request device [04:00.0] fault addr ffff0000 Nov 18 12:05:06 UNRAIDSERVER kernel: DMAR:[fault reason 06] PTE Read access is not set Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DRHD: handling fault status reg 3 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DMAR:[DMA Read] Request device [04:00.0] fault addr fffdc000 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR:[fault reason 06] PTE Read access is not set Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DRHD: handling fault status reg 3 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DMAR:[DMA Read] Request device [04:00.0] fault addr ffff8000 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR:[fault reason 06] PTE Read access is not set Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DRHD: handling fault status reg 3 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DMAR:[DMA Read] Request device [04:00.0] fault addr fffec000 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR:[fault reason 06] PTE Read access is not set Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DRHD: handling fault status reg 3 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DMAR:[DMA Read] Request device [04:00.0] fault addr ffff8000 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR:[fault reason 06] PTE Read access is not set Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DRHD: handling fault status reg 3 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DMAR:[DMA Read] Request device [04:00.0] fault addr fffd8000 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR:[fault reason 06] PTE Read access is not set Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DRHD: handling fault status reg 3 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DMAR:[DMA Read] Request device [04:00.0] fault addr ffff8000 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR:[fault reason 06] PTE Read access is not set Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DRHD: handling fault status reg 3 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DMAR:[DMA Read] Request device [04:00.0] fault addr ffff4000 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR:[fault reason 06] PTE Read access is not set Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DRHD: handling fault status reg 3 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DMAR:[DMA Read] Request device [04:00.0] fault addr ffff8000 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR:[fault reason 06] PTE Read access is not set Nov 18 12:05:09 UNRAIDSERVER kernel: DMAR: DRHD: handling fault status reg 3 Nov 18 12:05:09 UNRAIDSERVER kernel: DMAR: DMAR:[DMA Read] Request device [04:00.0] fault addr ffff4000 Nov 18 12:05:09 UNRAIDSERVER kernel: DMAR:[fault reason 06] PTE Read access is not set Nov 18 12:05:11 UNRAIDSERVER kernel: DMAR: DRHD: handling fault status reg 3 Nov 18 12:05:11 UNRAIDSERVER kernel: DMAR: DMAR:[DMA Read] Request device [04:00.0] fault addr ffff9000 Nov 18 12:05:11 UNRAIDSERVER kernel: DMAR:[fault reason 06] PTE Read access is not set unraidserver-diagnostics-20161118-1204.zip
November 18, 20169 yr Author Anyone got any ideas? I still have 360GB to shift before the mover finishes which will take weeks at this rate!
November 18, 20169 yr Quick google states to either disable IOMMU (if you're not passing through any cards to a VM), or change the IOMMU option in syslinux.cfg from "on" to be "pt". But I'm not a VM guy
November 18, 20169 yr My immediate impression from your listing of DMAR errors was that this was a typical Marvell controller issue, from an Intel based system with a Marvell SATA controller, and the usual advice is to add iommu=pt to the append line in the syslinux.conf file (often fixes it). And that may be the right advice after all, because of similar symptoms. But you don't have any Marvell chipsets. You also don't show a PCI device at exactly 04:00.0, but you do have an old Promise card at 04:01.0, which is so close it's probably *on* the same card. A little strange but I suspect the Promise card had an issue. Try the advice above. This didn't happen in your first syslog, and may not have happened here for quite awhile, so may be a sporadic issue. This diagnostics was odd, in that there was not a full syslog, and folders.txt shows that there wasn't one in /var/log either. The included 'syslog.txt' file is just a chopped tail of the whole, not from a syslog rotation either (no starting rsyslog line). Did you possibly delete the original syslog from /var/log?
November 18, 20169 yr Author Many Thanks for your reply, I will exchange that controller to see if that resolves the issue, I did indeed delete the previous log file as the UI wouldn't work and the system had ground to a halt with out of memory errors, deleting the log file cured that. I am stuck with the system trying to move 400GB of data which will take weeks at the speed it is going, how can I safely take down the server whilst the mover is running? Thanks Again
November 19, 20169 yr Author Quick google states to either disable IOMMU (if you're not passing through any cards to a VM), or change the IOMMU option in syslinux.cfg from "on" to be "pt". But I'm not a VM guy Hi mate, I disabled the VM to see if that cured the issue after googling found the same results this morning but it had no effect. Cheers
November 19, 20169 yr Author Ok, Swapped out the Promise card for a Via Chipset Card and all the errors have gone and system is flying again! Thanks for you help fellas
Archived
This topic is now archived and is closed to further replies.