Re: ATA Woes.
On 7/19/05, Wilko Bulte <[EMAIL PROTECTED]> wrote: > On Tue, Jul 19, 2005 at 11:22:01AM -0700, Jon Simola wrote.. > > I've now failed 4 of 10 SATA drives (Maxtor and WD) > > in 1U rackmounts, and am moving on to trying the WD Raptor SATA drives > > (which claim to be low-end server). > > Properly cooled? Yeah, they're in the Supermicro 811 chassis with hotswap SATA sleds. There's a decent amount of air flowing over the drives, and SMART says they're running about 26C. Compared to my 10Krpm SCSI array that I've burned my fingers on, frequently. -- Jon Simola Systems Administrator ABC Communications ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATA Woes.
Jon Simola wrote: On 7/19/05, Tony Byrne <[EMAIL PROTECTED]> wrote: I'm totally confused. I don't know enough about SMART to know whether I'm looking at real failing drives or some bug exposed by the interaction between drive firmware, hd controller and FreeBSD. What I've recently learned the hard way is that desktop drives have no place in a server. I've now failed 4 of 10 SATA drives (Maxtor and WD) in 1U rackmounts, and am moving on to trying the WD Raptor SATA drives (which claim to be low-end server). I have to agree with this opinion, I recently had a WD1600JD SATA fail within a couple months of installation, and the warranty replacement failed within a week. First drive failed autodetection and made servo ticking noises. Second drive had many bad sectors. Add this to the pile of dead 3yr-old 40GB WD drives from all the workstations around here. I install SATA drives in duplicate and triplicate for this reason. Preferably in removable bays with a fan. I assume they're bad out of the box... I write them full of zeros with DD, then read it all back, then do it again. If I don't get read errors then I install them. Joe Koberg joe at osoft dot us ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATA Woes.
Tony Byrne wrote: Hello Wilko, Tuesday, July 19, 2005, 7:35:40 PM, you wrote: WB> On Tue, Jul 19, 2005 at 11:22:01AM -0700, Jon Simola wrote.. What I've recently learned the hard way is that desktop drives have no place in a server. I've now failed 4 of 10 SATA drives (Maxtor and WD) in 1U rackmounts, and am moving on to trying the WD Raptor SATA drives (which claim to be low-end server). WB> Properly cooled? I can't speak for Jon, but the two disks that 'failed' sequentially on me in the last 48 hours took turns in a housing that had fans installed to draw air over the drive. Smartctl reported the drive temp. as 26 Deg.C. I don't think it's a problem of proper cooling or bad drives. I have a _desktop_ box with an 80G WDC drive in it, brand new. It installs WinXP and Linux just fine. It will not get through writing the superblocks for FreeBSD during the install _unless_ I boot the install kernel in "save" mode. This is installing 5.4-RELEASE, _and_ 5-Stable (several different snapshots, the most recent 8 July). This is a PATA drive, nothing special about it. The CPU is an AlthonXP 2200, mb has the VIA KT266A chipset. Out of the box, I'm having a lot of trouble installing 5.anything on this configuration. These same READ_DMA errors appear to be occurring with both SATA and PATA drives. (The drive checks out as fine. I'm about to run WDC diagnostics on it again.) John -- John T. FarmerOwner & CTOGoldSword Systems [EMAIL PROTECTED] 865-691-6498 Knoxville TN Consulting, Design, & Development of Networks & Software ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re[2]: ATA Woes.
Hello Wilko, Tuesday, July 19, 2005, 7:35:40 PM, you wrote: WB> On Tue, Jul 19, 2005 at 11:22:01AM -0700, Jon Simola wrote.. >> What I've recently learned the hard way is that desktop drives have no >> place in a server. I've now failed 4 of 10 SATA drives (Maxtor and WD) >> in 1U rackmounts, and am moving on to trying the WD Raptor SATA drives >> (which claim to be low-end server). WB> Properly cooled? I can't speak for Jon, but the two disks that 'failed' sequentially on me in the last 48 hours took turns in a housing that had fans installed to draw air over the drive. Smartctl reported the drive temp. as 26 Deg.C. Regards, Tony. -- Tony Byrne ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATA Woes.
On Tue, Jul 19, 2005 at 11:22:01AM -0700, Jon Simola wrote.. > On 7/19/05, Tony Byrne <[EMAIL PROTECTED]> wrote: > > > Jul 19 13:01:48 roo kernel: ad0: FAILURE - READ_DMA > > status=51 error=40 LBA=288810495 > > Jul 19 13:01:59 roo kernel: ad0: FAILURE - READ_DMA > > status=51 error=1 LBA=288810495 > > Jul 19 13:02:05 roo kernel: ad0: FAILURE - READ_DMA > > status=51 error=40 LBA=288810495 > > Jul 19 13:02:16 roo kernel: ad0: FAILURE - READ_DMA > > status=51 error=40 LBA=288810495 > > Jul 19 13:04:36 roo last message repeated 4 times > > > I'm totally confused. I don't know enough about SMART to know whether > > I'm looking at real failing drives or some bug exposed by the > > interaction between drive firmware, hd controller and FreeBSD. > > What I've recently learned the hard way is that desktop drives have no > place in a server. I've now failed 4 of 10 SATA drives (Maxtor and WD) > in 1U rackmounts, and am moving on to trying the WD Raptor SATA drives > (which claim to be low-end server). Properly cooled? -- Wilko Bulte [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATA Woes.
On 7/19/05, Tony Byrne <[EMAIL PROTECTED]> wrote: > Jul 19 13:01:48 roo kernel: ad0: FAILURE - READ_DMA > status=51 error=40 LBA=288810495 > Jul 19 13:01:59 roo kernel: ad0: FAILURE - READ_DMA > status=51 error=1 LBA=288810495 > Jul 19 13:02:05 roo kernel: ad0: FAILURE - READ_DMA > status=51 error=40 LBA=288810495 > Jul 19 13:02:16 roo kernel: ad0: FAILURE - READ_DMA > status=51 error=40 LBA=288810495 > Jul 19 13:04:36 roo last message repeated 4 times > I'm totally confused. I don't know enough about SMART to know whether > I'm looking at real failing drives or some bug exposed by the > interaction between drive firmware, hd controller and FreeBSD. What I've recently learned the hard way is that desktop drives have no place in a server. I've now failed 4 of 10 SATA drives (Maxtor and WD) in 1U rackmounts, and am moving on to trying the WD Raptor SATA drives (which claim to be low-end server). -- Jon Simola Systems Administrator ABC Communications ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATA Woes.
Hello Tony, Tuesday, July 19, 2005, 10:37:40 AM, you wrote: TB> Folks, TB> I'm seeing something very unusual on one of our FreeBSD 5.4 Stable TB> boxes which I'm having a hard time getting to the bottom of. Further information from my server logs: Jul 19 13:01:48 roo kernel: ad0: FAILURE - READ_DMA status=51 error=40 LBA=288810495 Jul 19 13:01:59 roo kernel: ad0: FAILURE - READ_DMA status=51 error=1 LBA=288810495 Jul 19 13:02:05 roo kernel: ad0: FAILURE - READ_DMA status=51 error=40 LBA=288810495 Jul 19 13:02:16 roo kernel: ad0: FAILURE - READ_DMA status=51 error=40 LBA=288810495 Jul 19 13:04:36 roo last message repeated 4 times With this disk it appears to be the same LBA each time. How can I translate that LBA offset into something indicating the file affected? I installed the *other* disk into a Windows box an ran the Western Digital Drive Tools SMART test on it. It found some sectors needing reallocation and successfully performed the reallocation. The tests (both short and long) now pass, but the drive's SMART Status remains at 'fail'. When I examine the attributes, the Raw Read Error Rate is flagged. I'm totally confused. I don't know enough about SMART to know whether I'm looking at real failing drives or some bug exposed by the interaction between drive firmware, hd controller and FreeBSD. Regards, Tony. -- Tony Byrne ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ATA Woes.
Folks, I'm seeing something very unusual on one of our FreeBSD 5.4 Stable boxes which I'm having a hard time getting to the bottom of. You may recall that a few weeks ago I posted regarding a server that was having trouble with WRITE_DMA and READ_DMA timeouts on it's SATA disk. We finally decided to migrate to a new disk, so we purchased a brand new Western Digital 250GB SATA drive and transferred the data across, before removing the old drive. We got about two days of trouble free access to this new disk before it too started throwing READ_DMA problems. This time they were error 40. Running SmartCtl on the disk showed a number of errors and there were specific files on the disk that could not be read. We moved the disk to a desktop box to confirm the problem and noted that fsck couldn't fix the errors on the drive. Assuming a dud drive, we purchased a replacement and this time we spurned SATA in favour of a PATA drive (Western Digital 200GB). We installed the drive yesterday using a brand new UDMA cable. Imagine my surprise when I came in this morning to find that this new drive was also now suffering from UNCORRECTABLE READ_DMA failures and SmartCtl confirmed that the drive wasn't happy. What are the odds of getting two dud disks from two separate batches of drives from, a reputable brand? The server itself is a 1U high rack mount installed in an AC'd machine room. It is powered from a UPS. There is space around the drive and a pair of fans draw air over the drive casing, to the casings are cool to the touch. The motherboard is an Intel S875PWP3 equipped with an Intel ICH5 chipset. Is there any known problem with using WD SATA / PATA disks with FreeBSD 5.4 Stable with the above mainboard? Is it possible that a FreeBSD bug is causing problems with these drives, including the problems reported by SmartCtl? Regards, Tony. -- Tony Byrne ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
