thr3ads.net - freebsd stable - ATA failure with 4.6.2 & 250GB drive? [Oct 2003]

If this information is useful, please help other people find it:
Share via:

Scott Mitchell

2003-Oct-13 02:10 UTC

ATA failure with 4.6.2 & 250GB drive?

Hi all,

Just installed a Maxtor 250GB PATA drive in one of our servers, to be used
as a backup staging area.  This was actually a replacement for an identical
drive that appeared to have died after a month of service.

Anyway, 2 days after this drive was installed I start seeing this in the
daily logs:
> ad1s1e: hard error reading fsbn 850845887 of 425422912-425422943 (ad1s1 bn
850845887; cn 52962 tn 180 sn 17) trying PIO mode
> ad1s1e: hard error reading fsbn 850845887 of 425422912-425422943 (ad1s1 bn
850845887; cn 52962 tn 180 sn 17) status=59 error=40
> ad1s1e: hard error reading fsbn 850845887 of 425422912-425422943 (ad1s1 bn
850845887; cn 52962 tn 180 sn 17) status=59 error=40
> ad1s1e: hard error reading fsbn 850845887 of 425422912-425422943 (ad1s1 bn
850845887; cn 52962 tn 180 sn 17) status=59 error=40...

Several hundred of these are appearing every day, although the backup jobs
do seem to be completing OK, and I'm not seeing any _write_ errors, only
these identical read errors.  I might be reading these messages wrong, but
errors on block 850845887 seem a bit suspicious when the drive only has
490234752 blocks.

So, do I really have another bad drive here?  Or do I just need to upgrade
this machine to get a newer ata driver?  RELENG_4_6 appears to have support
for 48-bit ATA addressing, so I wasn't expecting any problems, but maybe
there's something else I need?  Any advice much appreciated - this is a
production machine so I don't want to take it out of service for an upgrade
unless I really need to, but equally I would like this disk to work.

Attached: dmesg.boot and output of 'atacontrol cap', fdisk and disklabel
for the offending drive.

Cheers,

	Scott

-- 
==========================================================================Scott
Mitchell           | PGP Key ID | "Eagles may soar, but weasels
Cambridge, England       | 0x54B171B9 |  don't get sucked into jet
engines"
scott at fishballoon.org | 0xAA775B8B |      -- Anon
-------------- next part --------------
Copyright (c) 1992-2002 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
	The Regents of the University of California. All rights reserved.
FreeBSD 4.6.2-RELEASE-p26 #1: Thu Oct  9 09:44:39 BST 2003
    rsm@kokako:/usr/obj/usr/src/sys/KOKAKO
Timecounter "i8254"  frequency 1193182 Hz
CPU: Pentium III/Pentium III Xeon/Celeron (696.41-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x683  Stepping = 3
 
Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>
real memory  = 536805376 (524224K bytes)
avail memory = 517312512 (505188K bytes)
Preloaded elf kernel "kernel" at 0xc04d9000.
Pentium Pro MTRR support enabled
md0: Malloc disk
Using $PIR table, 12 entries at 0xc00fdf00
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Intel 82443GX host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
pcib2: <Intel 82443GX (440 GX) PCI-PCI (AGP) bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib2
pcib3: <PCI to PCI bridge (vendor=1011 device=0023)> at device 15.0 on
pci1
pci2: <PCI bus> on pcib3
fxp0: <Intel Pro 10/100B/100+ Ethernet> port 0x3000-0x303f mem
0xf4200000-0xf42fffff,0xf4300000-0xf4300fff irq 5 at device 7.0 on pci2
fxp0: Ethernet address 00:02:b3:16:7d:b9
inphy0: <i82555 10/100 media interface> on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
ahc0: <Adaptec aic7896/97 Ultra2 SCSI adapter> port 0x2000-0x20ff mem
0xf4100000-0xf4100fff irq 11 at device 12.0 on pci0
aic7896/97: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs
ahc1: <Adaptec aic7896/97 Ultra2 SCSI adapter> port 0x2400-0x24ff mem
0xf4101000-0xf4101fff irq 11 at device 12.1 on pci0
aic7896/97: Ultra2 Wide Channel B, SCSI Id=7, 32/253 SCBs
fxp1: <Intel Pro 10/100B/100+ Ethernet> port 0x2800-0x283f mem
0xf4000000-0xf40fffff,0xf4102000-0xf4102fff irq 10 at device 14.0 on pci0
fxp1: Ethernet address 00:d0:b7:89:92:a7
inphy1: <i82555 10/100 media interface> on miibus1
inphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
isab0: <Intel 82371AB PCI to ISA bridge> at device 18.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel PIIX4 ATA33 controller> port 0x2860-0x286f at device 18.1
on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
uhci0: <Intel 82371AB/EB (PIIX4) USB controller> port 0x2840-0x285f irq 10
at device 18.2 on pci0
usb0: <Intel 82371AB/EB (PIIX4) USB controller> on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
intpm0: <Intel 82371AB Power management controller> port 0x1040-0x104f irq
9 at device 18.3 on pci0
intpm0: I/O mapped 1040
intpm0: intr IRQ 9 enabled revision 0
smbus0: <System Management Bus> on intsmb0
smb0: <SMBus general purpose I/O> on smbus0
intpm0: PM I/O mapped c00 
pci0: <Cirrus Logic GD5480 SVGA controller> at 20.0
pcib1: <Intel 82443GX host to AGP bridge> on motherboard
pci3: <PCI bus> on pcib1
orm0: <Option ROMs> at iomem
0xc0000-0xc7fff,0xc8000-0xcd7ff,0xcd800-0xce7ff,0xce800-0xcf7ff on isa0
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
pcf0: can't reserve irq, polled mode.
pcf0: <PCF8584 I2C bus controller> at port 0x320-0x321 irq 5 on isa0
iicbus0: <Philips I2C bus> on pcf0 addr 0xaa
iicsmb0: <I2C to SMB bridge> on iicbus0
smbus1: <System Management Bus> on iicsmb0
smb1: <SMBus general purpose I/O> on smbus1
iic0: <I2C general purpose I/O> on iicbus0
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/8 bytes threshold
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
ad0: 19595MB <QUANTUM FIREBALLP LM20.5> [39813/16/63] at ata0-master
UDMA33
ad1: 239372MB <Maxtor 7Y250P0> [486344/16/63] at ata0-slave UDMA33
acd0: CDROM <TOSHIBA CD-ROM XM-6702B> at ata1-master PIO4
Waiting 15 seconds for SCSI devices to settle
pass5 at ahc0 bus 0 target 6 lun 0
pass5: <ESG-SHV SCA HSBP M13 0.02> Fixed Processor SCSI-2 device 
pass5: 3.300MB/s transfers
da0 at ahc0 bus 0 target 0 lun 0
da0: <IBM IC35L036UCD210-0 S5BA> Fixed Direct Access SCSI-3 device 
da0: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled
da0: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C)
da1 at ahc0 bus 0 target 1 lun 0
da1: <IBM DDYS-T36950M S96H> Fixed Direct Access SCSI-3 device 
da1: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled
da1: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C)
da2 at ahc0 bus 0 target 2 lun 0
da2: <IBM DDYS-T36950M S96H> Fixed Direct Access SCSI-3 device 
da2: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled
da2: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C)
da3 at ahc0 bus 0 target 3 lun 0
da3: <IBM DDYS-T36950M S96H> Fixed Direct Access SCSI-3 device 
da3: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled
da3: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C)
da4 at ahc0 bus 0 target 4 lun 0
da4: <IBM DDYS-T36950M S96H> Fixed Direct Access SCSI-3 device 
da4: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled
da4: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C)
Mounting root from ufs:/dev/ad0s1a
-------------- next part --------------
ATA channel 0, Slave, device ad1:

ATA/ATAPI revision    7
device model          Maxtor 7Y250P0
firmware revision     YAR41BW0
cylinders             16383
heads                 16
sectors/track         63
lba supported         268435455 sectors
lba48 supported         490234752 sectors
dma supported
overlap not supported

Feature                      Support  Enable    Value   Vendor
write cache                    yes	yes
read ahead                     yes	yes
dma queued                     no	no	0/00
SMART                          yes	yes
microcode download             yes	yes
security                       yes	yes
power management               yes	yes
advanced power management      yes	no	0/00
automatic acoustic management  yes	yes	254/FE	192/C0
-------------- next part --------------
******* Working on device /dev/ad1 *******
parameters extracted from in-core disklabel are:
cylinders=30515 heads=255 sectors/track=63 (16065 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=30515 heads=255 sectors/track=63 (16065 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165,(FreeBSD/NetBSD/386BSD)
    start 63, size 490223412 (239366 Meg), flag 80 (active)
	beg: cyl 0/ head 1/ sector 1;
	end: cyl 1023/ head 254/ sector 63
The data for partition 2 is:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>
-------------- next part --------------
# /dev/ad1s1c:
type: ESDI
disk: ad1s1
label: 
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 30514
sectors/unit: 490223412
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0		# milliseconds
track-to-track seek: 0	# milliseconds
drivedata: 0 

8 partitions:
#        size   offset    fstype   [fsize bsize bps/cpg]
  c: 490223412        0    unused        0     0       	# (Cyl.    0 - 30514*)
  e: 490223412        0    4.2BSD     2048 16384    89 	# (Cyl.    0 - 30514*)

Mark Willson

2003-Oct-13 03:11 UTC

head link

ATA failure with 4.6.2 & 250GB drive?

I encountered a similar problem a while back, which turned out to be
caused by a bad IDE cable.  Worth a shot?

-mark

> From owner-freebsd-stable@freebsd.org Mon Oct 13 10:12:59 2003
> Date: Mon, 13 Oct 2003 10:09:10 +0100
> From: Scott Mitchell <scott+freebsd@fishballoon.org>
> To: freebsd-stable@freebsd.org
> Subject: ATA failure with 4.6.2 & 250GB drive?
>
>
> --YiEDa0DAkWCtVeE4
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
>
> Hi all,
>
> Just installed a Maxtor 250GB PATA drive in one of our servers, to be used
> as a backup staging area.  This was actually a replacement for an identical
> drive that appeared to have died after a month of service.
>
> Anyway, 2 days after this drive was installed I start seeing this in the
> daily logs:
>
> > ad1s1e: hard error reading fsbn 850845887 of 425422912-425422943
(ad1s1 bn 850845887; cn 52962 tn 180 sn 17) trying PIO mode
> > ad1s1e: hard error reading fsbn 850845887 of 425422912-425422943
(ad1s1 bn 850845887; cn 52962 tn 180 sn 17) status=59 error=40
> > ad1s1e: hard error reading fsbn 850845887 of 425422912-425422943
(ad1s1 bn 850845887; cn 52962 tn 180 sn 17) status=59 error=40
> > ad1s1e: hard error reading fsbn 850845887 of 425422912-425422943
(ad1s1 bn 850845887; cn 52962 tn 180 sn 17) status=59 error=40
> ...

Scott Mitchell

2003-Oct-14 01:57 UTC

head link

ATA failure with 4.6.2 & 250GB drive?

On Mon, Oct 13, 2003 at 10:09:10AM +0100, Scott Mitchell
wrote:> Hi all,
> 
> Just installed a Maxtor 250GB PATA drive in one of our servers, to be used
> as a backup staging area.  This was actually a replacement for an identical
> drive that appeared to have died after a month of service.
> 
> Anyway, 2 days after this drive was installed I start seeing this in the
> daily logs:
> 
> > ad1s1e: hard error reading fsbn 850845887 of 425422912-425422943
(ad1s1 bn 850845887; cn 52962 tn 180 sn 17) trying PIO mode
> > ad1s1e: hard error reading fsbn 850845887 of 425422912-425422943
(ad1s1 bn 850845887; cn 52962 tn 180 sn 17) status=59 error=40
> > ad1s1e: hard error reading fsbn 850845887 of 425422912-425422943
(ad1s1 bn 850845887; cn 52962 tn 180 sn 17) status=59 error=40
> > ad1s1e: hard error reading fsbn 850845887 of 425422912-425422943
(ad1s1 bn 850845887; cn 52962 tn 180 sn 17) status=59 error=40
> ...
OK, swapped out the cable (from an 80- to 40-wire one, as it happened,
although that should make no difference on a UDMA33 controller).  Same
errors appeared again while the backups were running.

Some more information on how this drive is being used - we're dumping two
vinum RAID5 volumes onto it, one local and one remote, writing to the
backup disk over NFS.  Both dumps kick off at 0300, with the remote one
finishing at 0305 last night.  The first ATA error appeared in the logs at
0325, while the local backup was still running.  The last error was logged
at 0355, but the backup itself didn't finish until nearly 0500.

Anyone have any more ideas on how to diagnose this?  It does occur to me
that the daily periodic run also kicks off at 0301 but that is usually all
done before 0330.

Cheers,

	Scott

-- 
==========================================================================Scott
Mitchell           | PGP Key ID | "Eagles may soar, but weasels
Cambridge, England       | 0x54B171B9 |  don't get sucked into jet
engines"
scott at fishballoon.org | 0xAA775B8B |      -- Anon

DavidB

2003-Oct-14 11:13 UTC

head link

ATA failure with 4.6.2 & 250GB drive?

Kevin Oberman wrote:
>> Date: Tue, 14 Oct 2003 09:55:54 +0100
>> From: Scott Mitchell <scott+freebsd@fishballoon.org>
>> Sender: owner-freebsd-stable@freebsd.org
>>
>> On Mon, Oct 13, 2003 at 10:09:10AM +0100, Scott Mitchell wrote:
>>
>>> Hi all,
>>>
>>> Just installed a Maxtor 250GB PATA drive in one of our servers, to 
>>> be used
>>> as a backup staging area.  This was actually a replacement for an 
>>> identical
>>> drive that appeared to have died after a month of service.
>>>
>>> Anyway, 2 days after this drive was installed I start seeing this
in
>>> the
>>> daily logs:
>>>
>>>
>>>> ad1s1e: hard error reading fsbn 850845887 of
425422912-425422943
>>>> (ad1s1 bn 850845887; cn 52962 tn 180 sn 17) trying PIO mode
>>>> ad1s1e: hard error reading fsbn 850845887 of
425422912-425422943
>>>> (ad1s1 bn 850845887; cn 52962 tn 180 sn 17) status=59 error=40
>>>> ad1s1e: hard error reading fsbn 850845887 of
425422912-425422943
>>>> (ad1s1 bn 850845887; cn 52962 tn 180 sn 17) status=59 error=40
>>>> ad1s1e: hard error reading fsbn 850845887 of
425422912-425422943
>>>> (ad1s1 bn 850845887; cn 52962 tn 180 sn 17) status=59 error=40
>>>
>>>
>>> ...
>>
>>
>> OK, swapped out the cable (from an 80- to 40-wire one, as it happened,
>> although that should make no difference on a UDMA33 controller).  Same
>> errors appeared again while the backups were running.
>>
>> Some more information on how this drive is being used - we're
dumping
>> two
>> vinum RAID5 volumes onto it, one local and one remote, writing to the
>> backup disk over NFS.  Both dumps kick off at 0300, with the remote one
>> finishing at 0305 last night.  The first ATA error appeared in the 
>> logs at
>> 0325, while the local backup was still running.  The last error was 
>> logged
>> at 0355, but the backup itself didn't finish until nearly 0500.
>>
>> Anyone have any more ideas on how to diagnose this?  It does occur to
me
>> that the daily periodic run also kicks off at 0301 but that is 
>> usually all
>> done before 0330.
>
>
>
> It's a real drive problem, but possibly not a terminal one. (I had the
> same issue on one of my drives a few months ago and it's fine now.)
>
> The problem is that the system is getting an error trying to read this
> area of the disk. It's an unmapped bunch of bad blocks. The system
> gets an unrecoverable error trying to read these blocks and that is
> what you see reported. Since it can't read "good" data, it
does not
> relocate the bad data, but just leaves it there and reports errors
> every time it tries to read the data.
>
> First, any files containing data stored in these blocks are probably
> toast. Or, at least garbled. Sorry.
>
> The fix/workaround is to move the file(s) involved so that the damaged
> blocks are marked free and relocated to spar space on the drive. You
> can try to figure out just which file(s) use those blocks. There
> might even be a reasonable way to do this...I just don't know what it
> is.
>
> Another "fix"is to simply copy the drive onto another and then
copy it
> back. dd(1) will do the trick as will dump/restore. (I'd suggest the
> dump/restore to copy the data out and dd to copy it back if the disks
> have identical geometries.) Once the data is restored to the original
> disk, the bad blocks will have been re-directed by the drive and will
> no longer trouble you.
>
> Modern disks are pretty smart at error recovery, but some failures are
> too sudden for the drive to be able to deal with them without losing
> data. 

Regarding a fix:

I had similar read error message not long ago when dumping to tape, 
wondered what they could mean. So I went to the hard drive 
manufacturer's website and download a DOS tool to scan/repair the 
harddrive.

Just to note an issue:  I had one bootdisk for to check my harddrive 
which was an Hitachi (HGST) drive in my laptop and one for the Western 
Digital which was the drive of concern. For some reason I used the 
software utility from Hitachi on the WD, which was a good thing, because 
it reported bad blocks and wouldn't fix them because it recognized that 
it wasn't their drive. Then I used the bootdisk I had created for the WD 
utility and ran it, (this is why it was a good thing) it did the scan 
reported NO issues, checked its logs to see if it had logged fixing any 
problems. The utilities logs said the drive had no issues.
Just to double check I re-ran the HGST tool and it didn't find any bad 
blocks.  Hmm. Those knuckle-heads at Western Digital made the utility to 
fix the bad blocks silently.  I find this under-handed because you might 
not find a disk going bad until the disk is totally failing. Hmm. wonder 
if this helps get it past the warranty before the drive completely fails.
[ya know when 1:bad blocks show up, 2:you clean 'em up 3:return to step1 
that the drive will die the death in the near future]

So you can get utilities from the manufacturer usually {atleast WD, 
HGST, and Seagate} to do some subset of turn on and off S.M.A.R.T., 
exercise the harddrive, scan for errors, repair errors, low-level 
format, ....

If you don't mind booting from a DOS bootdisk to run the tool.  WD is a 
little confusing which to grab.  But note as I found out some 
manufacturer's might silently repair certain issues.

Hope this help,
David

Dan Strick

2003-Oct-14 18:26 UTC

head link

ATA failure with 4.6.2 & 250GB drive?

> FWIW, I have had _major_ problems (ie drive failure) when trying to use
> an 80 wire cable on a UDMA33 board with  an ATA66 drive - I would recommend
> never using 80 wire cables on controllers that don't support UDMA66 or
> better. The reverse, using 80 wire cables on UDMA66 (or better) controllers
> with ATA33 drives is ok, however, and I've done that successfully.
The only difference between 40 and 80 wire ATA cables are the extra 40
wires which are all connected to ground and pin 34 in the host connector
which is not connected to the conductor in an 80 wire cable.  The ANSI
ATA/ATAPI-5 standard says that "80-conductor cable assemblies may be used
in place of 40-conductor cable assemblies to improve signal quality ..."
(section 4.2.2.1).

Unless someone can suggest a specific mechanism for the drive failures,
I would expect that your correlation between drive failures and using
80 conductor cables with UDMA33 controllers was just coincidence.

Dan Strick
strick@covad.net

freebsd stable - Oct 2003 - ATA failure with 4.6.2 & 250GB drive?

ATA failure with 4.6.2 & 250GB drive?

ATA failure with 4.6.2 & 250GB drive?

ATA failure with 4.6.2 & 250GB drive?

ATA failure with 4.6.2 & 250GB drive?

ATA failure with 4.6.2 & 250GB drive?