Opened 4 months ago

Closed 4 months ago

#1967 closed enhancement (invalid)

Firecuda 530r Not fully identified. Just identified as Seagate ZP1000GM30063

Reported by: remixedcat Owned by:
Priority: minor Milestone:
Component: drivedb Version:
Keywords: nvme Cc:

Description (last modified by remixedcat)

Drive is not listed as Seagate Firecuda 530r, just by this Seagate ZP1000GM30063 in all drive related tools and info, My Barracuda 510 nvme drive is identified as Barracuda 510.

I have the 1TB Firecuda 530r

Here's the info from the following command:

sudo smartctl -a /dev/nvme0n1
=== START OF INFORMATION SECTION ===
Model Number:                       Seagate ZP1000GM30063
Serial Number:                      redacted
Firmware Version:                   SU6SX030
PCI Vendor/Subsystem ID:            0x1bb1
IEEE OUI Identifier:                0x6479a7
Total NVM Capacity:                 1,000,204,886,016 [1.00 TB]
Unallocated NVM Capacity:           0
Controller ID:                      1
NVMe Version:                       1.4
Number of Namespaces:               1
Namespace 1 Size/Capacity:          1,000,204,886,016 [1.00 TB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            6479a7 903f005573
Local Time is:                      Thu Sep 11 23:20:00 2025 EDT
Firmware Updates (0x18):            4 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005d):     Comp DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Log Page Attributes (0x08):         Telmtry_Lg
Maximum Data Transfer Size:         128 Pages
Warning  Comp. Temp. Threshold:     86 Celsius
Critical Comp. Temp. Threshold:     87 Celsius

Attachments (1)

SEAGATEFIRECUDA-SMARTCTL-OUTPUT.txt (3.0 KB ) - added by remixedcat 4 months ago.

Download all attachments as: .zip

Change History (4)

comment:1 by remixedcat, 4 months ago

Component: alldrivedb
Type: defectenhancement

comment:2 by remixedcat, 4 months ago

Description: modified (diff)

by remixedcat, 4 months ago

comment:3 by Christian Franke, 4 months ago

Keywords: nvme added
Resolution: invalid
Status: newclosed

There are no drive database entries for NVMe devices. See the FAQ for further info.

Note: See TracTickets for help on using tickets.