Subject: Re: disk errors
To: Brian A. Seklecki <lavalamp@spiritual-machines.org>
From: Wolfgang Rupprecht <wolfgang@wsrcc.com>
List: netbsd-users
Date: 05/28/2002 12:32:24
> Hmmm...Can you include the errors from syslog? From your other post, It
> sounds like you're dealing with typical ATA/IDE issues.
May 26 10:25:56 capsicum /netbsd: wd0e: device timeout reading fsbn 784016 of 784016-784047 (wd0 bn 9267344; cn 9193 tn 12 sn 44), retrying
May 26 10:25:56 capsicum /netbsd: wd0e: device timeout reading fsbn 784016 of 784016-784047 (wd0 bn 9267344; cn 9193 tn 12 sn 44), retrying
May 26 10:25:56 capsicum /netbsd: wd0e: device timeout reading fsbn 784016 of 784016-784047 (wd0 bn 9267344; cn 9193 tn 12 sn 44), retrying
May 26 10:25:56 capsicum /netbsd: wd0e: device timeout reading fsbn 784016 of 784016-784047 (wd0 bn 9267344; cn 9193 tn 12 sn 44), retrying
May 26 10:25:56 capsicum /netbsd: wd0e: uncorrectable data error reading fsbn 784025 of 784016-784047 (wd0 bn 9267353; cn 9193 tn 12 sn 53), retrying
May 26 10:25:56 capsicum /netbsd: wd0e: uncorrectable data error reading fsbn 784025 of 784016-784047 (wd0 bn 9267353; cn 9193 tn 12 sn 53)
May 26 10:26:47 capsicum /netbsd: wd0e: device timeout reading fsbn 784016 of 784016-784031 (wd0 bn 9267344; cn 9193 tn 12 sn 44), retrying
May 26 10:26:47 capsicum /netbsd: wd0e: device timeout reading fsbn 784016 of 784016-784031 (wd0 bn 9267344; cn 9193 tn 12 sn 44), retrying
May 26 10:26:47 capsicum /netbsd: wd0e: device timeout reading fsbn 784016 of 784016-784031 (wd0 bn 9267344; cn 9193 tn 12 sn 44), retrying
May 26 10:26:47 capsicum /netbsd: wd0e: device timeout reading fsbn 784016 of 784016-784031 (wd0 bn 9267344; cn 9193 tn 12 sn 44), retrying
May 26 10:26:47 capsicum /netbsd: wd0e: uncorrectable data error reading fsbn 784025 of 784016-784031 (wd0 bn 9267353; cn 9193 tn 12 sn 53), retrying
May 26 10:26:47 capsicum /netbsd: wd0e: uncorrectable data error reading fsbn 784025 of 784016-784031 (wd0 bn 9267353; cn 9193 tn 12 sn 53)
[and just for reference, the boot info for the disk]
May 26 12:09:33 capsicum /netbsd: wd0 at pciide0 channel 0 drive 0: <ST380021A>
May 26 12:09:33 capsicum /netbsd: wd0: drive supports 16-sector PIO transfers, LBA addressing
May 26 12:09:33 capsicum /netbsd: wd0: 76319 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 156301488 sectors
May 26 12:09:33 capsicum /netbsd: wd0: 32-bit data port
May 26 12:09:33 capsicum /netbsd: wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
May 26 12:09:33 capsicum /netbsd: wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 4 (Ultra/66) (using DMA data transfers)
May 26 12:09:34 capsicum /netbsd: warning: double match for boot device (wd0, wd1)
May 26 12:09:34 capsicum /netbsd: boot device: wd0
May 26 12:09:34 capsicum /netbsd: root on wd0a dumps on wd0b
This is a system that has been in continuous use for 1.5 years and has
never has this kind of flagrant errors before. (This is an ASUS A7V
based on the VIA chipsets.)
-wolfgang
--
Wolfgang Rupprecht <wolfgang@wsrcc.com> http://www.wsrcc.com/wolfgang/
Coming soon: GPS mapping tools for Open Systems. http://www.gnomad-mapping.com/