It probably is the disk dying.  I'm kinda surprised the driver
handles it as well as it does.

	-- Lennart

Tracy Di Marco White wrote:
> In message <409286FB.1000100@augustsson.net>, Lennart Augustsson writes:
> 
>>The code for that driver is just not very good.  E.g., it lacks
>>most error recovery.
>>But that said, I don't mind if it's uncommented.
> 
> 
> I'll uncomment it, then.
> 
> We have a couple archos at home, we get errors a lot from one.  I
> assumed it was the disk dying, is it the driver having problmes?
> If it is the driver having problems, can someone help me improve it?
> 
> -Tracy
> 
> wd1: soft error (corrected)
> wd1e: device fault writing fsbn 28688 of 28576-28703 (wd1 bn 28751; cn 28 tn 8 sn 23), retrying
> wd1e: device fault writing fsbn 28656 of 28576-28703 (wd1 bn 28719; cn 28 tn 7 sn 54), retrying
> wd1e: device fault writing fsbn 28656 of 28576-28703 (wd1 bn 28719; cn 28 tn 7 sn 54), retrying
> wd1: soft error (corrected)
> wd1e: device fault writing fsbn 29307088 of 29307080-29307087 (wd1 bn 29307151; cn 29074 tn 8 sn 55), retrying
> wd1: soft error (corrected)
> <....>
> wd1e: device fault writing fsbn 14879792 of 14879784-14879791 (wd1 bn 14879855; cn 14761 tn 12 sn 11), retrying
> umass0: Phase Error, residue = 4096
> wd1e: device fault writing fsbn 14879792 of 14879784-14879791 (wd1 bn 14879855; cn 14761 tn 12 sn 11), retrying
> wd1: soft error (corrected)
> umass0: Phase Error, residue = 0
> wd1e: device fault writing fsbn 14416 of 14368-14495 (wd1 bn 14479; cn 14 tn 5 sn 52), retrying
> umass0: Phase Error, residue = 8192
> wd1e: device fault writing fsbn 14384 of 14368-14495 (wd1 bn 14447; cn 14 tn 5 sn 20), retrying
> wd1: soft error (corrected)
>