You could try using SpinRite.
http://www.grc.com
It now works with all filesystems and is up to version
6.
Mark
--- Tuc <[EMAIL PROTECTED]> wrote:
> > > Problem is, unless it fails the Dell Power on
> IDE test, they won't
> > > replace it. :-/ Guess I just keep backing it up
> until it fail
> > Problem is, unless it fails the Dell Power on IDE test, they won't
> > replace it. :-/ Guess I just keep backing it up until it fails totally.
>
> Get a Dell diagnostic disk for your system, and run the hard drive test. It
> ought to see the problems, which you can then report back to D
Tuc wrote:
[ ...and SMART status... ]
So is there something I should do?
Get a new hard drive, this one is not going to live much longer.
Problem is, unless it fails the Dell Power on IDE test, they won't
replace it. :-/ Guess I just keep backing it up until it fails totally.
Get a Dell diagn
>
> Tuc wrote:
> > ad0: FAILURE - READ_DMA status=51 error=40
> LBA=11291
> > ad0: FAILURE - READ_DMA status=51 error=40
> > LBA=112977803
> > ad0: FAILURE - READ_DMA status=51 error=40
> > LBA=112977835
> [ ...and SMART status... ]
> > So is there something I should do?
>
> Get a new
Tuc wrote:
ad0: FAILURE - READ_DMA status=51 error=40
LBA=11291
ad0: FAILURE - READ_DMA status=51 error=40
LBA=112977803
ad0: FAILURE - READ_DMA status=51 error=40
LBA=112977835
[ ...and SMART status... ]
So is there something I should do?
Get a new hard drive, this one is not going to live
> ### Test 1:
> # smartctl -a ad0 | more
>
> ### Test 2:
> # smartctl -t offline ad0
>
> # smartctl -a ad0 | more
>
> ### Test 3:
> # smartctl -t long ad0
>
> # smartctl -a ad0 | more
>
Ok, done. (Oh, BTW, I was having errors like :
ad0: FAILURE - READ_DMA status=51 error=40
LBA=1129
On Sat, Oct 23, 2004 at 07:18:29PM -0500, David Fleck wrote:
> On Sun, 24 Oct 2004 [EMAIL PROTECTED] wrote:
> >On Sat, Oct 23, 2004 at 05:26:27PM -0500, David Fleck wrote:
> >>Is this likely a one-time thing, or a symptom of creeping disk death?
> >> (The 'hard error' messages only started after t
On Sun, 24 Oct 2004 [EMAIL PROTECTED] wrote:
On Sat, Oct 23, 2004 at 05:26:27PM -0500, David Fleck wrote:
Is this likely a one-time thing, or a symptom of creeping disk death?
(The 'hard error' messages only started after the reboot.)
You could try /usr/ports/sysutils/smartmontools to run S.M.A.R
On Sat, Oct 23, 2004 at 05:26:27PM -0500, David Fleck wrote:
> Oct 23 16:58:12 grond /kernel: ad0s1e: hard error reading fsbn 29926527 of
> 9843232-9843263 (ad0s1 bn 29926527; cn 1862 tn 214 sn 15) status=59
> error=40
>
> Is this likely a one-time thing, or a symptom of creeping disk death?
4.9-RELEASE-p11 system.
Experimenting with cdda2wav this morning, I managed to get my system into
a completely non-responsive state- no keyboard, mouse, or console
activity; the machine responded to about 20% of ping packets, with
many-second delays; attempts to ssh into the box failed. So I
p
10 matches
Mail list logo