5/6     http://h20565.www2.hp.com/portal/site/hpsc/template.PAGE/public/kb/docDisplay/?spf_p.tpst=kbDocDisplay&spf_p.prp_kbDocDisplay=wsrp-navigationalState%3DdocId%253Demr_na-c03747345-1%257CdocLocale%253D%257CcalledBy%253D&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken
        \_ seems like I get these every 6 months or so from HP.  Do all drives
           have these kind of issues and I only see the ones from HP because
           they are diligent about reporting/fixing these issues?  Or do they
           suck?   (It's not actually their drives so...)  Also, do I really
           need to bring down my production infrastructure and fix all this
           or is "rare" sufficiently rare (or sufficiently harmless) that I
           can ignore it?   -advice needed.  tnx.

5/6     http://goo.gl/KiIMT (shortened link from http://HP.com)
        seems like I get these every 6 months or so from HP.  Do all drives
         have these kind of issues and I only see the ones from HP because
         they are diligent about reporting/fixing these issues?  Or do they
         suck?   (It's not actually their drives so...)  Also, do I really
         need to bring down my production infrastructure and fix all this
         or is "rare" sufficiently rare (or sufficiently harmless) that I
         can ignore it?   -advice needed.  tnx.
         \_ no raid? can't update 1 at a time?