Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 21 Sep 2002 18:19:13 +1000
From:      Neal Nelson <neal@nelson.name>
To:        "DOROVSKOY,IGOR (A-Portsmouth,ex1)" <igor_dorovskoy@agilent.com>
Cc:        "'neal@nelson.name'" <neal@nelson.name>, freebsd-hardware@freebsd.org
Subject:   Re: Disc Problems
Message-ID:  <20020921081913.GA344@server>
In-Reply-To: <0D9185CE635BD511ACA50090277A6FCF038809DE@axcs18.cos.agilent.com>; from igor_dorovskoy@agilent.com on Fri, Sep 20, 2002 at 23:44:48 %2B1000
References:  <0D9185CE635BD511ACA50090277A6FCF038809DE@axcs18.cos.agilent.com>

next in thread | previous in thread | raw e-mail | index | archive | help
I've never had a floppy provided with any of the hard discs that I've 
bought. However, I went to the Western Digital web site and downloaded 
a programme that makes a bootable floppy. It needs Windows 
unfortunately, so I used my Wifes laptop.

The diagnostics seem to have done the job and the disc is again working 
fine.

Flushed with success I went to the Seagate web site and downloaded 
their diagnostics (for a previously failed drive), which also made a 
boot floppy but needed Windows to run. This is all very annoying. I 
don't see why they can't just have an image for downloading.

Anyway, the Seagate diagnostics just told me that the drive is dead and 
don't seem to try and fix things. Ah well, it was worth a try. One out 
of two dead discs recovered isn't too bad.

On 2002.09.20 23:44 "DOROVSKOY,IGOR (A-Portsmouth,ex1)" wrote:
> Boot from floppy disk provided by your disk maker and go to
> diagnostics (exact name maybe different for different hdd vendors)
> and run the test. In most cases this procedure will fix your disk
> drive.
> 
> Regards,
> Igor.
> 
> > -----Original Message-----
> > From: Neal Nelson [mailto:neal@nelson.name]
> > Sent: Tuesday, September 17, 2002 9:21 PM
> > To: freebsd-hardware@freebsd.org
> > Subject: Disc Problems
> >
> >
> > I'm having problems with one of my discs when I do a cvsup
> > (on -STABLE
> > as of last week). I get the following:
> >
> > ad4: READ command timeout tag=0 serv=0 - resetting
> > ata2: resetting devices .. done
> > ad4: READ command timeout tag=0 serv=0 - resetting
> > ata2: resetting devices .. done
> > swap_pager: indefinite wait buffer: device: #ad/0x20021,
> > blkno: 15992,
> > size: 57344
> > ad4: READ command timeout tag=0 serv=0 - resetting
> > ata2: resetting devices .. done
> > ad4: READ command timeout tag=0 serv=0 - resetting
> > ad4: trying fallback to PIO mode
> > ata2: resetting devices .. done
> > ad4s1e: hard error reading fsbn 28844015 of 13795232-13795359
> > (ad4s1 bn
> > 28844015; cn 10900 tn 41 sn 32) status=59 error=40
> > ad4s1e: hard error reading fsbn 28844127 of 13795344-13795415
> > (ad4s1 bn
> > 28844127; cn 10901 tn 1 sn 18) status=59 error=40
> > spec_getpages:(#ad/0x20024) I/O read failure: (error=5) bp
> 0xc383e75c
> > vp 0xc8515c00
> >                 size: 36864, resid: 36864, a_count: 36864, valid:
> 0x0
> >                 nread: 0, reqpage: 0, pindex: 374, pcount: 9
> > vm_fault: pager read error, pid 378 (cvsup)
> > pid 378 (cvsup), uid 1003: exited on signal 6 (core dumped)
> > Sep 18 11:17:21 server /kernel: pid 378 (cvsup), uid 1003: exited on
> 
> > signal 6 (core dumped)
> >
> > I've tried changing cables, so I assume that it's my hard
> > disc at fault.
> >
> > Does anyone have any ideas before I go out and replace the
> > disc? I had
> > to do the same less than a year ago and I'm accumulating a nice
> stack
> > of dodgy discs.
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-hardware" in the body of the message
> >
> 
> 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020921081913.GA344>