On Tue, 24 Apr 2007 11:53:56 +0200, Bill Maas wrote: >Unusual System Events >=-=-=-=-=-=-=-=-=-=-= >Apr 15 01:00:39 soekris2 /bsd: wd0a: id not found reading fsbn 367868 >of 367868-367871 (wd0 bn 367932; cn 365 tn 0 sn 12), retrying >Apr 15 01:00:40 soekris2 /bsd: wd0: soft error (corrected) > >I'm not sure what this is about, but it might be the first hint at a >wearing out CF. Apparently something to do with corrupted disk blocks >(according to various *BSD lists). I've been having these warnings quite >regularly for a couple of weeks now. CF is about a year old, brand >"Kingston Technology". The "soft error" indicates that it's nothing to >worry about anyway, so I won't, for now.
Y'know, Kingston is a brand I trust very much - for RAM. It is also the only brand CF that I've had trouble with. Qualify that: I don't buy Bamboo Charlie components for anything critical, so the only CFs I've used have been Sandisk (rugged, zero failures, but slow in bench access speed and write speed testing), Apacer (zero failures, rugged in my year long "log it to death" test, faster than Sandisk) and Kingston. The Kingston was trouble very early in testing. I don't have all the details to hand but I now think we may have had a bad batch because all of the samples had a common problem and it's not like Kingston to do lousy QA. We chose Apacer because they're fast, have had zero failures in service or torture and the price was attractive as well. BTW unless you need atime time stamps you would be well advised to mount your CF partitions noatime if you care about avoidable wear. Otherwise every time you access a file in almost any way the timestamp is deleted and rewritten. Go well, Rod/ "Write a wise saying and your name will live on forever." - Anonymous _______________________________________________ Soekris-tech mailing list [email protected] http://lists.soekris.com/mailman/listinfo/soekris-tech
