Custom Query (1365 matches)


Show under each result:

Results (61 - 63 of 1365)

Ticket Resolution Summary Owner Reporter
#1722 duplicate error_log on Seagate FireCuda 510 NVMe (Debian 11 and 12) kolAflash

I'm getting error_log entries for my Seagate FireCuda 510 SSD ZP2000GM30001. See the attachment. OS: Debian 11 and 12 (Linux 5.10 and 6.1)

I guess there's not really a hardware defect. Because the system is running totally fine. (yes, I do daily backups)

Maybe it's some bad NVMe commands like in #1663 !? If yes, how can I find out which commands and why they are being send? Is opening a ticket on a good idea to get those bad NVMe commands fixed?

P.S. With Debian-12 this became more prominent, because now there's a graphical notification (smart-notifier).

Hard Disk Health Warning
The hard disk health status has changed. This could mean that hard drive failure is imminent. It is always a good idea to have up to date backups.
This message was generated by the smartd daemon running on:

   host name:  myhost
   DNS domain: mydomain

The following warning/error was logged by the smartd daemon:

Device: /dev/nvme0, number of Error Log entries increased from 343 to 345

Device info:
Seagate FireCuda 510 SSD ZP2000GM30001, S/N:XXXXXXXX, FW:STES1024, 2.00 TB

For details see host's SYSLOG.

You can also use the smartctl utility for further investigation.
The original message about this issue was sent at Fri Dec 25 13:31:06 2020 CET
Another message will be sent in 24 hours if the problem persists.
#1721 fixed Please add SanDisk SDSA6DM-016G-1006 to the Database Christian Franke Cmdr_Zod

Please find attached the output of smartctl -x /dev/sdX

#1720 invalid Western Digital SN730 SDBQNTY-1T00-1001 displaying incorrect data opethfan91
Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.