S.M.A.R.T. log shows New Year's Eve 2024 as date (today: 2024-07-07)

  • Hi,


    how can I fix the wrong SMART date? It shows hundred of wrong data entries like:

    12/31/2024, 8:02:26 PM  smartd is exiting (exit status 0)

    ...

    12/31/2024, 7:43:37 PM  Device: /dev/disk/by-id/ata-ST12000VN0008-2YS101_WR8009B9 [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 83 to 77

    I collected these data example from 'Diagnostics -> System Logs -> Logs -> S.M.A.R.T.' at the OMV web interface.


    Thanks!


    _Michael_


    P.S. All other logs are showing the right date.

    Edited once, last by _Michael_: Correction of the data source and a little more information. ().

    • Official Post

    What is the output of

    date


    12/31/2024, 7:43:37 PM Device: /dev/disk/by-id/ata-ST12000VN0008-2YS101_WR8009B9 [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 83 to 77

    This is telling you, that there is an issue with your drive.

  • Hi macom, at CLI the command 'date' delivers the expected date (in the meantime I updated my initial post, see "P.S.").

    Quote

    This is telling you, that there is an issue with your drive.

    I usually use the SMART info from

    'Storage -> S.M.A.R.T. -> Devices'

    There is the "Status = Good" for all drives displayed. I can use the

    'Storage -> S.M.A.R.T. -> Devices -> Details -> Extended Information'

    but I have currently no idea to map the "ata-ST12000VN0008-2YS101_WR8009B9" with the there visible drive names. I.e. the info from

    'Diagnostics -> System Logs -> Logs -> S.M.A.R.T.'

    is currenlty not helpful for me.

    • Official Post

    There seems to be an issue with the timestamp of smart logs in OMV6. It is fixed in OMV7


  • Thanks a lot, so at least no date issue at my side.

    Would you please have a look to my collected (link) SMART data? Is there really a problem with my less than 1 year old Seagate IronWolf HDD? The GUI tells nothing but the collected details are much to much for my knowledge.

    • Official Post

    From the SMART data #5, #197 and #198 are looking good. I think most consider these three data as most relevant.

    RAW_READ_ERROR_RATE seems to be tricky to interpret.


    From here https://en.wikipedia.org/wiki/…_and_Reporting_Technology

    Quote

    Stores data related to the rate of hardware read errors that occurred when reading data from a disk surface. 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

    Maybe you need to do some research or test the drive with a Seagate tool.


    I have 3 Seagate drive, which have quite high numbers (I just noticed) whereas a WD drive has 0.

  • My 1st and above discussed IronWolf has:

    ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE

    1 Raw_Read_Error_Rate POSR-- 071    066     044  - 11634084


    My 2nd IronWolf has:

    ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE

    1 Raw_Read_Error_Rate POSR-- 083   064     044 - 220184064

    From the plain numbers it would say the my 2nd drive is even worse. Both drives have less than 60 hours of use, I will not dive deeper, i.e. handle these values as usual numbers.

    Again, thanks a lot for your support.


  • _Michael_

    Added the Label resolved

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!