On 21/01/2024 03:23, gene heskett wrote:
On 1/20/24 10:24, Max Nikulin wrote:
On 19/01/2024 06:10, gene heskett wrote:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
WHEN_FAILED RAW_VALUE
190 Airflow_Temperature_Cel 0x0032 071 049 000 Old_age
Always - 29
Initial 100 decreased to 49 means that sometimes the drive is hot enough.
I've been under the impression that 100C was the absolute temp limit
Do not confuse normalized values (100 means shiny new, 0 means really
old or damaged) and RAW_VALUE. For some drives smartctl -x may report
history of temperature measurements, but I think summer values are
already unavailable.
and it not been over 36C that I know of according to gkrellm which s set
to monitor that stuff in real time. Right now nothing in the system is
north of 32C, might get to 36C
71 <-> 29 °C and 49 <-> 36 °C mapping might be possible, but I would
expect higher temperature for 49.
# 2 Extended offline Completed: read failure 50%
10917 1847474376
# 3 Extended offline Completed: read failure 50%
10586 1847474376
May it happen that disk firmware does not remap failed sectors to
allow the user to identify what file is damaged?
IDK Max. I know the microware os9 file system well enough to connect the
dots, but have little knowledge for how one might do this with ext4.
If you are motivated enough then docs either for badblocks or for some
data recovery software may give you a recipe. A search engine should
help to find it.
