smartctl messages ‘Error: UNC at LBA’ invalid value for Windows

[zlsd]

The value displayed as LBA is interpreted in Windows erroneously unlike Linux

For example, the error 248

Linux Error: WP at LBA = 0x008c3c2e = 9190446
Windows Error: WP at LBA = 0x3c008c2e = 1006668846

See attached files

[zlsd]

Windows output

[zlsd]

Linux output

[Christian Franke]

Windows.txt:

...
SMART Extended Comprehensive Error Log Version: 1 (5 sectors)
...
Error 248 [7] occurred at disk power-on lifetime: 18290 hours (762 days + 2 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 3c 00 8c 2e 00 00  Error: WP at LBA = 0x3c008c2e = 1006668846
...

Linux:

...
SMART Error Log Version: 1
...
Error 248 occurred at disk power-on lifetime: 18290 hours (762 days + 2 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 2e 3c 8c 00  Error: WP at LBA = 0x008c3c2e = 9190446
...

These are different error logs because you only used -a instead of -x on Linux. Only the SMART Extended Comprehensive Error Log supports 48-bit LBA. The legacy SMART Error Log might return truncated or bogus values for LBAs > 28-bit.

Try smartctl -x -a ... on both systems and compare the results.

Also try with -F xerrorlba as the above output suggests that the firmware has a common byte ordering bug in the extended log.