Re: Bad disk or kernel (ATA Driver) problem? - SOLVED
Sam Leffler wrote: I have had spectacularly bad luck with Maxtor SATA drives. I've already RMA'd 4 of 8 drives and have 2 more waiting to go back. 1 was DOA, the rest failed completely while in operation (typically locking up the machine). These were all Maxtor DiamondMax Plus 9 6Y160M0 160GB Serial ATA drives. After testing for power, cables, disk controller, motherboard, and other potential reasons I've decided the drives were just faulty and have switched to another vendor. I have a pair of 6Y200M0 drives in my machine. They absolutely _hated_ the SiI 3112 controller I had them on (the one built-in on the motherboard). Lots of timeouts and the occasional untraceable random lockup. I moved them over to a Promise SATA controller and they seem much happier. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bad disk or kernel (ATA Driver) problem? - SOLVED
Michael R. Wayne wrote: On Wed, Jan 19, 2005 at 09:36:05PM -0600, Karl Denninger wrote: What 'other vendor' have you found that makes RELIABLE SATA disks in the high capacity (e.g. 200-300gb) arena? WD now makes a SATA RAID line. HIGHLY recommended by 3ware. I read with some alarm about trouble with SuperMicro servers and ATA, because that is my new box. I'll chime in a data point saying that I have not seen any errors with the SuperMicro 1U and my 250G Western Digital SATA drives: atapci0: port 0x4000-0x400f,0x4020-0x4023,0x4028-0x402f,0x4024-0x4027,0x4030-0x4037 mem 0xfc30-0xfc3001ff irq 26 at device 2.0 on pci3 ata2: channel #0 on atapci0 ata3: channel #1 on atapci0 atapci1: port 0x4010-0x401f,0x4038-0x403b,0x4040-0x4047,0x403c-0x403f,0x4048-0x404f mem 0xfc300400-0xfc3005ff irq 27 at device 3.0 on pci3 ata4: channel #0 on atapci1 ata5: channel #1 on atapci1 atapci2: port 0x2060-0x206f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci2 ata1: channel #1 on atapci2 acd0: CDROM at ata1-master UDMA33 ad4: 238475MB [484521/16/63] at ata2-master SATA150 ad6: 238475MB [484521/16/63] at ata3-master SATA150 The vendor (ASA) were initially reluctant to send me this box because they were keen to issues with FreeBSD's SATA chipset compatability, but I did some research and convinced them not to fret. I am saving money and probably some hassle by replacing 3ware with gmirror. My cheat sheet is posted at http://dannyman.toldme.com/2005/01/24/freebsd-howto-gmirror-system/ . Thanks, -danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bad disk or kernel (ATA Driver) problem? - SOLVED
# [EMAIL PROTECTED] / 2005-01-20 15:26:21 -0800:
> Karl Denninger <[EMAIL PROTECTED]> wrote:
>
> > Seagate's have been getting very poor performance reviews of late.
>
> Do you have any URLs? While I haven't been following disk drives
> closely, I haven't seen anything that points at "very poor" performance
> ("average"/boring performance, yes, but nothing really bad).
I had a Barracuda IV or V that the Samsung I bought as a replacement
outperforms (e. g. opening a Maildir in mutt) by an order of
magnitude. I had to wait *minutes* to get into some of my larger
maildirs with the Seagate whereas now it's a matter of seconds.
A test at xbitlabs.com
(http://www.xbitlabs.com/articles/storage/display/21hdd-160_18.html)
relates large performance differences between Seagate disks to
firmware revisions. If you buy a drive with the right firmware,
you'll get decent performance. If you miss, you'll suffer greatly.
--
FreeBSD 4.10-STABLE
10:19AM up 3:02, 4 users, load averages: 0.00, 0.01, 0.00
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bad disk or kernel (ATA Driver) problem? - SOLVED
Stein M. Sandbech wrote: [ ... ] I'm having problems with this disk just after startup, and it seem to me its related to temperature. Occationally, when starting up with disk @ room temperature I usually get a handfull of the checksum errors listed below. If it been sitting in the car for a while and temp is down to 15C or below, it wont start at all. Just giving a lot more of the CRC errors, and usually a kernel panic. I sometimes heated the disk with a hairdryer ;-) This drive should be RMA'ed, looks like it has some major TCAL problems. -- -Chuck ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bad disk or kernel (ATA Driver) problem? - SOLVED
On Jan 20, 2005, at 22:09, Michael R. Wayne wrote: On Wed, Jan 19, 2005 at 09:36:05PM -0600, Karl Denninger wrote: What 'other vendor' have you found that makes RELIABLE SATA disks in the high capacity (e.g. 200-300gb) arena? WD now makes a SATA RAID line. HIGHLY recommended by 3ware. FYI, Im using a Maxtor 6B200M0 200GB Serial ATA disk in a Shuttle XPC. FreeBSD 5.3R. I'm having problems with this disk just after startup, and it seem to me its related to temperature. Occationally, when starting up with disk @ room temperature I usually get a handfull of the checksum errors listed below. If it been sitting in the car for a while and temp is down to 15C or below, it wont start at all. Just giving a lot more of the CRC errors, and usually a kernel panic. I sometimes heated the disk with a hairdryer ;-) The normal procedure is now to start the PC and stop the boot process, and let the system heat up by itself, 5mins usaually. Any got similar experiences with the Maxtor SATA's? If this is the norm, I'd rather stay away from these Maxtor products... --- Jan 9 16:35:43 biosphere kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=209417132 Jan 9 16:35:43 biosphere kernel: ad4: FAILURE - WRITE_DMA status=51 error=84 dma=0x02LBA=209417132Jan 9 16:35:43 biosphere kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=209679308 Jan 9 16:35:43 biosphere kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=210203692 Jan 9 16:35:43 biosphere kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=210203692 Jan 9 16:35:43 biosphere kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=209941484 Jan 9 16:35:43 biosphere kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=209941484 Jan 9 16:35:43 biosphere kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=209950124 Jan 9 16:35:43 biosphere kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=209950124 Jan 9 16:35:43 biosphere kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=209941484 Jan 9 16:35:47 biosphere kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=302277292 Jan 9 16:35:47 biosphere kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=302099020 Jan 9 16:35:55 biosphere kernel: ad4: TIMEOUT - READ_DMA retrying (2 retries left) LBA=302077068 Jan 9 16:35:55 biosphere kernel: ad4: FAILURE - READ_DMA timed outJan 9 16:35:59 biosphere kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=210465708 Jan 9 16:36:00 biosphere kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=221218956 -- Best Regards Stein Morten ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bad disk or kernel (ATA Driver) problem? - SOLVED
Karl Denninger <[EMAIL PROTECTED]> wrote:
> Seagate's have been getting very poor performance reviews of late.
Do you have any URLs? While I haven't been following disk drives
closely, I haven't seen anything that points at "very poor" performance
("average"/boring performance, yes, but nothing really bad).
Thanks.
--
Darryl Okahata
[EMAIL PROTECTED]
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Agilent Technologies, or
of the little green men that have been following him all day.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bad disk or kernel (ATA Driver) problem? - SOLVED
On Thu, Jan 20, 2005 at 08:17:40AM -0800, Darryl Okahata wrote: > Karl Denninger <[EMAIL PROTECTED]> wrote: > > > These two are DiamondMax10s - let's hope that this doesn't apply to that > > line as well. > > Out of curiosity, why didn't you consider Seagate ? The recent > Maxtors that I have, if run 24x7, seem to die just after the warranty > expires (for me, just over a year). I'm now switching back to Seagate, > as they now have a nice 5-year warranty, but I don't have much > experience with these new drives. The Maxtors I'm getting have 3-year warranties. Seagate's have been getting very poor performance reviews of late. of course a drive that pukes is worse than one that is slow! -- -- Karl Denninger ([EMAIL PROTECTED]) Internet Consultant & Kids Rights Activist http://www.denninger.netMy 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.comMusings Of A Sentient Mind ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bad disk or kernel (ATA Driver) problem? - SOLVED
On Wed, Jan 19, 2005 at 09:36:05PM -0600, Karl Denninger wrote: > > What 'other vendor' have you found that makes RELIABLE SATA disks in the > high capacity (e.g. 200-300gb) arena? WD now makes a SATA RAID line. HIGHLY recommended by 3ware. /\/\ \/\/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bad disk or kernel (ATA Driver) problem? - SOLVED
Karl Denninger <[EMAIL PROTECTED]> wrote: > These two are DiamondMax10s - let's hope that this doesn't apply to that > line as well. Out of curiosity, why didn't you consider Seagate ? The recent Maxtors that I have, if run 24x7, seem to die just after the warranty expires (for me, just over a year). I'm now switching back to Seagate, as they now have a nice 5-year warranty, but I don't have much experience with these new drives. -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bad disk or kernel (ATA Driver) problem? - SOLVED
On Wed, Jan 19, 2005 at 07:37:34PM -0800, David G. Lawrence wrote: >Yeah, the 6Y series Maxtor is particularly bad. More than half of all > of them that I've had (a few dozen in total) have gone bad. The 7Y series > is a slightly better, but still well short of an acceptable failure rate. >On the other hand, the Hitachi 7K250 and 7K400 series SATA drives have > worked quite well for us, with failure rates in the low single digits. > Seagate SATA drives also seem to be reliable, although they don't perform > very well. > > -DG I have some associates that have had major problems with Deskstars in server use, which is why I didn't consider them originally. They moved them all to desktop machines where they're getting reasonable life from them - albiet at a pricepoint that didn't make sense compared to the Seagates and WDs of smaller capacity. Often this kind of thing is part and parcel of one given model though, which means that unless you're talking the same line/model/whatever, it may not apply, and some of the issues are firmware related - so a production change can make a formerly unacceptable unit "ok" somewhere - or the reverse. This really bites - while I used to have issues with disks now and then when I ran my ISP, it was typically a rare bad lot once in a while. Products with this kind of failure rate just never made it out - now it seems that the manufacturers will throw whatever they can into the market, hoping they survive until the warranty runs out, and there's a trend towards shortening warranties to one year as well! I wonder if someone could go after these guys on their "MTBF" claims which all appear to be WILDLY optimistic. Ah well, if I can't get the Maxtors to work reasonably well I guess I can try the Deskstar 250s... Thanks for the datapoints guys... (rant off!) -- -- Karl Denninger ([EMAIL PROTECTED]) Internet Consultant & Kids Rights Activist http://www.denninger.netMy 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.comMusings Of A Sentient Mind ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bad disk or kernel (ATA Driver) problem? - SOLVED
> I have had spectacularly bad luck with Maxtor SATA drives. I've already > RMA'd 4 of 8 drives and have 2 more waiting to go back. 1 was DOA, the > rest failed completely while in operation (typically locking up the > machine). These were all Maxtor DiamondMax Plus 9 6Y160M0 160GB Serial > ATA drives. After testing for power, cables, disk controller, > motherboard, and other potential reasons I've decided the drives were > just faulty and have switched to another vendor. Yeah, the 6Y series Maxtor is particularly bad. More than half of all of them that I've had (a few dozen in total) have gone bad. The 7Y series is a slightly better, but still well short of an acceptable failure rate. On the other hand, the Hitachi 7K250 and 7K400 series SATA drives have worked quite well for us, with failure rates in the low single digits. Seagate SATA drives also seem to be reliable, although they don't perform very well. -DG David G. Lawrence President Download Technologies, Inc. - http://www.downloadtech.com - (866) 399 8500 TeraSolutions, Inc. - http://www.terasolutions.com - (888) 346 7175 The FreeBSD Project - http://www.freebsd.org Pave the road of life with opportunities. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bad disk or kernel (ATA Driver) problem? - SOLVED
On Wed, Jan 19, 2005 at 07:18:08PM -0800, Sam Leffler wrote: > I have had spectacularly bad luck with Maxtor SATA drives. I've already > RMA'd 4 of 8 drives and have 2 more waiting to go back. 1 was DOA, the > rest failed completely while in operation (typically locking up the > machine). These were all Maxtor DiamondMax Plus 9 6Y160M0 160GB Serial > ATA drives. After testing for power, cables, disk controller, > motherboard, and other potential reasons I've decided the drives were > just faulty and have switched to another vendor. > > Sam These two are DiamondMax10s - let's hope that this doesn't apply to that line as well. I'm going to be royally POd if so. One RMA is already issued and that one is going back - hopefully the replacement is good. If not, I will not be amused BTW I've had relatively bad luck with recent WD drives - which is why I decided to try the Maxtors. My experience with WDs is that in a server they last about a year before locking up with unrecoverable errors which cannot be cleared except by a power cycle. The lockup extends to the host bus; it appears that the microcode is holding either DREQ or DACK on the cable and as such that entire PATA bus is locked out. I've sent two back in the last six months with the exact same problem - WD has been replacing them, but this failure mode is very ugly as it takes down the machine that they're in at the time, RAID or no RAID. What 'other vendor' have you found that makes RELIABLE SATA disks in the high capacity (e.g. 200-300gb) arena? -- -- Karl Denninger ([EMAIL PROTECTED]) Internet Consultant & Kids Rights Activist http://www.denninger.netMy 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.comMusings Of A Sentient Mind ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bad disk or kernel (ATA Driver) problem? - SOLVED
I have had spectacularly bad luck with Maxtor SATA drives. I've already RMA'd 4 of 8 drives and have 2 more waiting to go back. 1 was DOA, the rest failed completely while in operation (typically locking up the machine). These were all Maxtor DiamondMax Plus 9 6Y160M0 160GB Serial ATA drives. After testing for power, cables, disk controller, motherboard, and other potential reasons I've decided the drives were just faulty and have switched to another vendor. Sam ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bad disk or kernel (ATA Driver) problem? - SOLVED
On Wed, Jan 19, 2005 at 03:06:04PM -0800, Jon Simola wrote: > On a different box (Supermicro SuperServer 5013C-T, P4SCE BIOS v1.2c): .. > A pair of Maxtor 80GBs, the BIOS is set for "Enhanced", up to 6 drives > (4 IDE + 2 SATA). > Crazy as though it seems, I wasn't kidding about changing the BIOS. > The other 2 settings are "SATA only" and "Auto". When the drives > started flaking out (timeouts on reads) I would go into the BIOS and > cycle through the BIOS settings. After changing it once or twice, > things would be fine for months at a time. After swapping the "suspect" drive around in an attempt to get the failure to move to the other disk in the pair I actually got a failure on the OTHER channel (in other words, the problem followed the DISK) That got followed up with a soak test with DOS-based diags, which eventually spat out a hard failure code. It took some effort, since the problem doesn't appear on a quick test nor does it show up at the same block all the time - indeed, the block where it finally pukes is all over the place. Back to Maxtor it goes - it appears that FreeBSD's driver (and the bios, etc) is not at fault here, and was indeed reporting a "real" failure. I guess the mirroring code in 5.3-STABLE actually works :-> -- Karl Denninger ([EMAIL PROTECTED]) Internet Consultant & Kids Rights Activist http://www.denninger.netMy 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.comMusings Of A Sentient Mind ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
