Confusing smartd messages

[Rodney W. Grimes]

> Another problem issue is that flash memories also exhibit the charge
> drain problem.
> They cannot be read indefinitely without occasional rewrite, as every
> read drains a minuscule amount of the charge.
> 
> I often wished I knew of some OS/driver function/mechanism which can
> rewrite respective refresh media on a mounted+running system and could
> be, for example, run via cron.
> 
> Such would not only be very useful to fix pending sectors without
> stopping a running machine, but also for keeping embedded machines'
> flash memories reliably charged over the years.

It would be nice to have this feature, should not be too hard
to implement just a matter of locking the device from start
of read to end of write.

> 
> On 7/5/18, Wojciech Puchar <wojtek at puchar.net> wrote:
> >>> okay.  What's the recommended action at this point?     -- George
> >>
> >> In my experience it is begin of disk death, even if overall status is
> >> PASSED. It could work for month or may be half a year after first
> >> Offline_Uncorrectable is detected (it depends on load), but you best bet
> >> to replace it ASAP and throw away.
> > well my disk had this and live happily for 3 years.
> >
> > It JUST means that some sectors are unreadable which may be a reason that
> > at some some write got wrong because of hardware problem. But this problem
> > may be - and possibly were - powerdown while writing, or power spike.
> >
> > the media itself could be fine. the best action in such case is to force
> > rewrite whole drive with some data.
> >
> > with gmirror it is as easy as first checking second drive for no errors,
> > then forcing remirror.

-- 
Rod Grimes                                                 rgrimes at freebsd.org