marco, >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. >
i have had a lot of problems with this drive, and it correlated very strongly with the hardware to which it was attached. i probably should have posted the problems i had to misc, but i wasn't on the mailing list at the time. i had used this disk in conjunction with several different motherboards and PSes and found that whenever it was connected to a configuration with a particular PS, it would check the filesystems on boot and get these soft errors. in fact, the disk would have such a hard time reading data that it would spit me into kdb or not load the kernel at all (no boot prompt). i was very worried that the disk was corrupted and that i had lost my data. despite all the signs pointing to the disk being damaged, as soon as i put it in a configuration that didn't involve aforementioned PS, it would boot fine, fsck the filesystems and correct the errors. from there on out, i didn't get any soft errors until i changed back to the anomalous PS. i confirmed this on a couple of different working setups, and when i reverted to the setup with the suspect PS it would give the soft errors and not boot correctly. perhaps the PS was doing damage to the disk? how can i test if the disk is/was damaged? the drive has been working just fine ever since i swapped the PS. here's the dmesg chunks with the disk in question: # dmesg|grep wd0 wd0 at pciide0 channel 0 drive 0: <ST3200822AS> wd0: 16-sector PIO, LBA48, 190782MB, 390721968 sectors wd0(pciide0:0:0): using BIOS timings, Ultra-DMA mode 6 dkcsum: wd0 matched BIOS disk 80 root on wd0a >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
