Re: READ_DMA timed out on Promise FastTrak100
-- quoting [EMAIL PROTECTED] -- However, when I boot FreeBSD, the system reports READ_DMA errors on the second drive, and the array reports a degraded state. I can still mount it, and both drive lights flash when accessing the volume. I had similar problems with my SATA RAID controller, lots of DMA errors. Looks like a bug in 5.3 -- or is it fixed now? I solved this issue in disabling DMA via sysctl... HTH! Greetings, Matthias -- Marge, tell Bart I just want to drink a nice glass of syrup like I do every morning. -- Homer Simpson Lisa the Vegetarian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: READ_DMA timed out on Promise FastTrak100
-Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Auftrag von Matthias F. Brandstetter Gesendet am: Freitag, 28. Januar 2005 13:58 An: freebsd-questions@freebsd.org Betreff: Re: READ_DMA timed out on Promise FastTrak100 -- quoting [EMAIL PROTECTED] -- However, when I boot FreeBSD, the system reports READ_DMA errors on the second drive, and the array reports a degraded state. I can still mount it, and both drive lights flash when accessing the volume. I had similar problems with my SATA RAID controller, lots of DMA errors. Looks like a bug in 5.3 -- or is it fixed now? I solved this issue in disabling DMA via sysctl... I am using a Promise FastTrak100 and I have no problems at all. I tried FreeBSD5.3 Release and the most current RELENG_5. So, no kernel bug, as far as I can tell. Norbert Koch ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: READ_DMA timed out on Promise FastTrak100
[EMAIL PROTECTED] wrote: However, when I boot FreeBSD, the system reports READ_DMA errors on the second drive, and the array reports a degraded state. I can still mount it, and both drive lights flash when accessing the volume. Googling returns a lot of information relating to hardware: http://www.google.ca/search?q=%22FAILURE+-+READ_DMA%22+freebsd I was originally running 5.3-RELEASE-p5 (SMP, dual P3). I built and booted 5.3-STABLE SMP, and although everything else looks fine, the READ_DMA error is unchanged. I have verified the seating of cables and cards. Does anyone have any pointers? What else should I try? Thanks in advance. My suggestions would begin with replacing your cables (obviously with UDMA100-style/80-conductor)... I know the promise cables have that nifty PROMISE branded ribbon that looks like one is supposed to use to remove the cable from the drive, but I've seen that thing cause some trouble (like ruining the drive connectors). Failing that, if you can take the drive out of the machine (new cable, new card, new system), and run the manufacture's _extensive_ drive tests on it, I think you'll find all is not well. Cheers, Derek ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
