On 8/9/2011 11:33 AM, Jeppe Øland wrote: > About a year ago, I switched to running the full pfSense 2.0 (beta > something at the time) on a Kingston SS100S2/8G embedded SSD. > > Since then, every 3 months or so I noticed (in connection with > installing a new release) that the filesystem was corrupted, and I > have had to format the drive some 3 times in that year! > > I believe I read somewhere that some of the earlier beta/RC's had > filesystem corruption issues, so I guess that *could* be the issue. > > I have also noticed that the system log occasionally has this line: > ad4: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4892879 > (The LBA is fixed ... it only changes if I reformat/reinstall).
If the LBA id fixed, that usually (but not always) points to an issue with the disk itself. If it's random, then one might suspect the controller/cables/memory/etc. Doing a full read/write test on the drive might be helpful. I'm not sure about that model and how it reports things, but the S.M.A.R.T. data might be useful. Though a good report from SMART doesn't always mean everything is fine and dandy, if it shows issues it's generally correct. > Does anybody have more information about this issue. > Is there a problem with the motherboard? > Is the drive crap? (Kingston support isn't exactly helpful). > Are there known problems with AHCI or NCQ? I'd lean more toward blaming the drive, given the symptoms. Unless you are seeing a bunch of kernel panics/random sudden unclean reboots, you shouldn't be getting filesystem corruption. Jim --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] Commercial support available - https://portal.pfsense.org
