On Wed, 15 Jun 2005, Greg Oster wrote:

> Teemu Rinta-aho writes:
>> p4# tail dmesg
>> wd0a: error reading fsbn 268435392 of 268435392-268435519 (wd0 bn 268435455;
>> cn
>> 266305 tn 0 sn 15), retrying
>> wd0: (id not found)
>> wd0a: error reading fsbn 268435392 of 268435392-268435519 (wd0 bn 268435455;
>> cn
>> 266305 tn 0 sn 15), retrying
>> wd0: (id not found)
>
> You need to find out what's causing these errors...  RAIDframe will
> not be happy if the underlying devices are reporting problems...
> (The above sector is at the 128GB mark on the disk... I wonder if
> there is something special about that?)

 	Its a seagate disk isn't it? Some seagate disks can only access
 	the last 'pre LBA48' sector via LBA48. There is a quirk table
 	in NetBSD, but really NetBSD should try LBA48 on that sector
 	if non LBA48 fails.

-- 
 		David/absolute       -- www.NetBSD.org: No hype required --