ehm... no.
Replacing your power supply was a coincidence. The disk was going
bad and reallocated the bad areas. By the time you replaced the
power supply it was simply done.
To make sure all ares have been touched (and potentially fixed)
simply read the whole disk like:
dd if=/dev/rwd0c of=/dev/null bs=1m
Or something.
On Sep 16, 2005, at 8:06 AM, <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
wrote:
Hi
I have two harddisks:
wd0 at pciide0 channel 0 drive 0: <Maxtor 91360U4>
wd0: 16-sector PIO, LBA, 12982MB, 26588016 sectors
wd0(pciide0:0:0): using PIO mode 4, DMA mode 2
wd1 at pciide0 channel 1 drive 0: <IC35L080AVVA07-0>
wd1: 16-sector PIO, LBA, 78533MB, 160836480 sectors
wd1(pciide0:1:0): using PIO mode 4, DMA mode 2
and as I copied some large files from wd0 to wd1 I get the
following
errors. Do I need a new harddrive?
wd0(pciide0:0:0): timeout
type: ata
c_bcount: 65536
c_skip: 0
pciide0:0:0: bus-master DMA error: missing interrupt, status=0x20
wd0f: device timeout writing fsbn 7565664 of 7565664-7565791
(wd0 bn
12664128; c
n 12563 tn 9 sn 57), retrying
wd0: soft error (corrected)
wi0: host encrypt not implemented for 802.3
wd0(pciide0:0:0): timeout
type: ata
c_bcount: 65536
c_skip: 0
pciide0:0:0: bus-master DMA error: missing interrupt, status=0x20
wd0f: device timeout writing fsbn 7619104 of 7619104-7619231
(wd0 bn
12717568; c
n 12616 tn 10 sn 10), retrying
wd0: soft error (corrected)
wd0(pciide0:0:0): timeout
type: ata
c_bcount: 65536
c_skip: 0
pciide0:0:0: bus-master DMA error: missing interrupt, status=0x20
wd0f: device timeout writing fsbn 7693584 of 7693584-7693711
(wd0 bn
12792048; c
n 12690 tn 8 sn 24), retrying
wd0: soft error (corrected)
wi0: host encrypt not implemented for 802.3
wd0(pciide0:0:0): timeout
type: ata
c_bcount: 65536
c_skip: 0
pciide0:0:0: bus-master DMA error: missing interrupt, status=0x20
wd0f: device timeout writing fsbn 7961472 of 7961472-7961599
(wd0 bn
13059936; c
n 12956 tn 4 sn 36), retrying
wd0: soft error (corrected)
wd0(pciide0:0:0): timeout
type: ata
c_bcount: 65536
c_skip: 0
...
i had this same problem with a SATA drive i have. i couldn't
figure out what was going wrong for quite a bit, but swapping
out the power supply fixed it in my case.
i think the first PS i had installed was giving enough juice
to the drive.
cheers,
jake
