[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: filesystem damage



On Fri, 7 Mar 2025 at 00:41, Dan Purgert <dan@djph.net> wrote:
> On Mar 07, 2025, David wrote:

> > The wikipedia page [1] regarding "1 Raw_Read_Error_Rate" says:
> >   The raw value has different structure for different vendors and is often
> >   not meaningful as a decimal number. For some drives, this number
> >   may increase during normal operation without necessarily signifying errors.
>
> I've never seen spinning rust just increase read-errors for no reason,
> but since they were all ECC corrected, it's less concerning.

Hi, I found a blog post [1], which gives an example where
Seagate’s Seek Error Rate attribute consists of two parts —
a 16-bit count of seek errors in the uppermost 4 nibbles,
and a 32-bit count of seeks in the lowermost 8 nibbles.

The raw value in the blog example is 359872048, which
indicates zero errors :)

[1] https://www.disktuna.com/big-scary-raw-s-m-a-r-t-values-arent-always-bad-news/


Reply to: