Custom Query (1405 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (238 - 240 of 1405)

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

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 https://bugzilla.kernel.org/ 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.
#1725 duplicate NVMe pass-through support for Argon ONE M.2 Expansion Board (NVME) RobertCezar
Description

I tried to get info of Argon ONE M.2 Expansion Board (NVME), but got this error (I had to specify -d scsi by trial and error otherwise got error)

sudo smartctl /dev/sdb
smartctl 7.2 2020-12-30 r5155 [aarch64-linux-6.1.21-v8+] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

/dev/sdb: Unknown SNT device type 'sntasmedia'
Please specify device type with the -d option.

Use smartctl -h to get a usage summary

 sudo smartctl -a -d scsi /dev/sdb
smartctl 7.2 2020-12-30 r5155 [aarch64-linux-6.1.21-v8+] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               Argon
Product:              Forty
Revision:             0
Compliance:           SPC-4
User Capacity:        2,000,398,934,016 bytes [2.00 TB]
Logical block size:   512 bytes
LU is fully provisioned
Rotation Rate:        Solid State Device
Logical Unit id:      0x5000000000000001
Serial number:        50F000000000
Device type:          disk
Local Time is:        Sat May 13 10:38:14 2023 EEST
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Disabled or Not Supported

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK
Current Drive Temperature:     0 C
Drive Trip Temperature:        0 C

Error Counter logging not supported

Device does not support Self Test logging

sudo smartctl -a -d sntrealtek /dev/sdb -r ioctl,2
smartctl 7.2 2020-12-30 r5155 [aarch64-linux-6.1.21-v8+] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

 [NVMe call: opcode=0x06, size=0x1000, nsid=0x00000000, cdw10=0x00000001]
>>>> do_scsi_cmnd_io: sg_io_ver=3
 [<vendor specific>: e4 00 10 06 01 00 00 00 00 00 00 00 00 00 00 00 ]
  scsi_status=0x0, sg_transport_status=0x0, sg_driver_status=0x0
  sg_info=0x0  sg_duration=0 milliseconds  resid=4096
  Incoming data trimmed to nothing by resid
 [NVMe call succeeded: result=0x00000000
 00     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00    ................
 10     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00    ................
 ...
 ]
=== START OF INFORMATION SECTION ===
Model Number:
Serial Number:
Firmware Version:
PCI Vendor ID:                      0x0000
PCI Vendor Subsystem ID:            0x0000
IEEE OUI Identifier:                0x000000
Total NVM Capacity:                 0
Unallocated NVM Capacity:           0
Controller ID:                      0
NVMe Version:                       <1.2
Number of Namespaces:               0
Local Time is:                      Sat May 13 10:41:39 2023 EEST
Firmware Updates (0x00):            0 Slots
Optional Admin Commands (0x0000):   -
Optional NVM Commands (0x0000):     -
Log Page Attributes (0x00):         -
Maximum Data Transfer Size:         -
Warning  Comp. Temp. Threshold:     -
Critical Comp. Temp. Threshold:     -
Namespace 4294967295 Features (0x00):      -

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     0.00W       -        -    0  0  0  0        0       0

=== START OF SMART DATA SECTION ===
 [NVMe call: opcode=0x02, size=0x0200, nsid=0xffffffff, cdw10=0x007f0002]
>>>> do_scsi_cmnd_io: sg_io_ver=3
 [<vendor specific>: e4 00 02 02 02 00 00 00 00 00 00 00 00 00 00 00 ]
  scsi_status=0x0, sg_transport_status=0x0, sg_driver_status=0x0
  sg_info=0x0  sg_duration=4 milliseconds  resid=512
  Incoming data trimmed to nothing by resid
 [NVMe call succeeded: result=0x00000000
 00     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00    ................
 10     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00    ................
 ...
 ]
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        -
Available Spare:                    0%
Available Spare Threshold:          0%
Percentage Used:                    0%
Data Units Read:                    0
Data Units Written:                 0
Host Read Commands:                 0
Host Write Commands:                0
Controller Busy Time:               0
Power Cycles:                       0
Power On Hours:                     0
Unsafe Shutdowns:                   0
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               -
Temperature Sensor 2:               -
Temperature Sensor 3:               -
Temperature Sensor 4:               -
Temperature Sensor 5:               -
Temperature Sensor 6:               -
Temperature Sensor 7:               -
Temperature Sensor 8:               -
Thermal Temp. 1 Transition Count:   0
Thermal Temp. 2 Transition Count:   0
Thermal Temp. 1 Total Time:         0
Thermal Temp. 2 Total Time:         0

 [NVMe call: opcode=0x02, size=0x0040, nsid=0xffffffff, cdw10=0x000f0001]
>>>> do_scsi_cmnd_io: sg_io_ver=3
 [<vendor specific>: e4 40 00 02 01 00 00 00 00 00 00 00 00 00 00 00 ]
  scsi_status=0x0, sg_transport_status=0x0, sg_driver_status=0x0
  sg_info=0x0  sg_duration=0 milliseconds  resid=0
  Incoming data, len=64:
 00     50 00 00 00 00 00 00 01  00 b0 00 3c 00 00 00 01
 10     00 00 08 00 00 00 00 00  00 00 00 00 00 00 00 00
 20     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 30     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 [NVMe call succeeded: result=0x00000000
 00     50 00 00 00 00 00 00 01  00 b0 00 3c 00 00 00 01    P..........<....
 10     00 00 08 00 00 00 00 00  00 00 00 00 00 00 00 00    ................
 20     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00    ................
 ...
 ]
Error Information (NVMe Log 0x01, 1 of 1 entries)
Num   ErrCount  SQId   CmdId  Status  PELoc          LBA  NSID    VS
  0 72057594037928016 45056  0x3c00  0x0000  0x100       524288     0     -

#1730 duplicate Unknown USB bridge [0x04e8:0x61fb (0x100)] skoehler
Description

This is a Samsung T7 Shield, 4TB.

It has a USB to NVMe bridge. I don't know which one.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.