Hi folks; New one... I've got a 2 x SATA system here I'm playing with in preparation to move over production to 5.x. These drives have been working under 4.x for quite some time - they're 250GB Maxtor disks.... ad4: 239372MB <Maxtor 6B250S0/BANC1980> [486344/16/63] at ata2-master SATA150 ad6: 239372MB <Maxtor 6B250S0/BANC1980> [486344/16/63] at ata3-master SATA150 The first disk runs nice and happy. The second does too, provided that the load isn't too high. If it is, then I start to get DMA transfer errors, such as the following: ad6: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> LBA=543191 GEOM_MIRROR: Request failed (error=5). ad6[READ(offset=278048256, length=102400)] GEOM_MIRROR: Device m0: provider ad6 disconnected. ad6: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> LBA=300463 ad6: TIMEOUT - READ_DMA retrying (2 retries left) LBA=90863 ad6: FAILURE - READ_DMA timed out ad6: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> ad6: TIMEOUT - READ_DMA retrying (2 retries left) LBA=120663 ad6: FAILURE - READ_DMA timed out I'm having a lot of trouble believing this is an actual disk problem. Among other things, its happening at different places - not always at the same block. The above (after the first one) are all being provoked with a "dd if=/dev/ad6s1 of=/dev/null bs=100k". Anyone else seeing this with a -STABLE build from the last few days, and only on a secondary (and/or SATA) channel? Note that this disk can be reintegrated into the mirror, and it will rebuild happily. Its only when I put a real working load on it that things act up. -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://www.spamcuda.net SPAM FREE mailboxes - FREE FOR A LIMITED TIME! http://genesis3.blogspot.com Musings Of A Sentient Mind
On Wed, 19 Jan 2005 15:13:01 -0600, Karl Denninger <karl@denninger.net> wrote:> I've got a 2 x SATA system here I'm playing with in preparation to move > over production to 5.x. > > These drives have been working under 4.x for quite some time - they're 250GB > Maxtor disks.... > > ad4: 239372MB <Maxtor 6B250S0/BANC1980> [486344/16/63] at ata2-master SATA150 > ad6: 239372MB <Maxtor 6B250S0/BANC1980> [486344/16/63] at ata3-master SATA150 > > The first disk runs nice and happy. > > The second does too, provided that the load isn't too high. If it is, then I > start to get DMA transfer errors, such as the following: > > ad6: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> > LBA=543191 > GEOM_MIRROR: Request failed (error=5). ad6[READ(offset=278048256, > length=102400)] > GEOM_MIRROR: Device m0: provider ad6 disconnected. > ad6: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> > LBA=300463 > ad6: TIMEOUT - READ_DMA retrying (2 retries left) LBA=90863 > ad6: FAILURE - READ_DMA timed out > ad6: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> > ad6: TIMEOUT - READ_DMA retrying (2 retries left) LBA=120663 > ad6: FAILURE - READ_DMA timed out > > I'm having a lot of trouble believing this is an actual disk problem. Among > other things, its happening at different places - not always at the same > block.I've got a few 1U Supermicro boxes running dual SATA drives: ad4: 78167MB <Maxtor 6Y080M0/YAR51HW0> [158816/16/63] at ata2-master SATA150 ad6: 78167MB <Maxtor 6Y080M0/YAR51HW0> [158816/16/63] at ata3-master SATA150 I've run into all sorts of problems with every one, and changing the IDE channel settings in the BIOS always fixes it. Which really annoys me, because I setup a new box, run it for a couple weeks, then the drives start getting flaky under load. Then I go change the setting in the BIOS (that I always forget to do on initial setup) and it's dead stable for months at a time. I've had the exact same problem with FreeBSD 5.3 and OpenBSD 3.5 as well.
At 04:13 PM 19/01/2005, Karl Denninger wrote:>I'm having a lot of trouble believing this is an actual disk problem. Among >other things, its happening at different places - not always at the same >block.If you have the drives on a RELENG_5 box, try /usr/ports/sysutils/smartmontools/ Its quite handy to sort of various drive issues as well as to monitor for ongoing errors via the daemon. ---Mike