Disk Issues

mhammett

Renowned Member
Mar 11, 2009
165
2
83
DeKalb, Illinois, United States
We have added some new disks to our Proxmox servers, and we were just looking for some verification that we've reached the right conclusion.

We currently have 2x Dell 2.4TB drives in a mirror with a hot spare. We added two more. Of the four that we added (two each to two hosts), two aren't working properly.

Code:
root@Dekalb1:~# lsblk -o tran,name,type,size,vendor,model,label,rota,log-sec,phy-sec
TRAN NAME      TYPE  SIZE VENDOR   MODEL        LABEL ROTA LOG-SEC PHY-SEC
[trimmed]
sas  sdd       disk  2.2T SEAGATE  DL2400MM0159          1     512    4096
sas  sde       disk    0B SEAGATE  DL2400MM0159          1     512     512
[trimmed]
root@Dekalb1:~# smartctl -a /dev/sdd
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.8.4-2-pve] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               SEAGATE
Product:              DL2400MM0159
Revision:             ST5C
Compliance:           SPC-4
User Capacity:        2,400,476,553,216 bytes [2.40 TB]
Logical block size:   512 bytes
Physical block size:  4096 bytes
LU is fully provisioned
Rotation Rate:        10000 rpm
Form Factor:          2.5 inches
Logical Unit id:      0x5000c500c24f7227
Serial number:        WBM1Q02G
Device type:          disk
Transport protocol:   SAS (SPL-4)
Local Time is:        Mon Feb 24 11:45:34 2025 CST
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

Grown defects during certification = 0
Total blocks reassigned during format = 0
Total new blocks reassigned = 0
Power on minutes since format = 13414
Current Drive Temperature:     32 C
Drive Trip Temperature:        60 C

Accumulated power on time, hours:minutes 396:35
Manufactured in week 31 of year 2019
Specified cycle count over device lifetime:  10000
Accumulated start-stop cycles:  57
Specified load-unload count over device lifetime:  300000
Accumulated load-unload cycles:  1597
Elements in grown defect list: 0

Vendor (Seagate Cache) information
  Blocks sent to initiator = 29296
  Blocks received from initiator = 184
  Blocks read from cache and sent to initiator = 3641
  Number of read and write commands whose size <= segment size = 53
  Number of read and write commands whose size > segment size = 0

Vendor (Seagate/Hitachi) factory information
  number of hours powered up = 396.58
  number of minutes until next internal SMART test = 59

Error counter log:
           Errors Corrected by           Total   Correction     Gigabytes    Total
               ECC          rereads/    errors   algorithm      processed    uncorrected
           fast | delayed   rewrites  corrected  invocations   [10^9 bytes]  errors
read:      67564        0         0     67564          0          0.015           0
write:         0        0         0         0          0          0.903           0

Non-medium error count:        0

No Self-tests have been logged

root@Dekalb1:~# smartctl -a /dev/sde
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.8.4-2-pve] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               SEAGATE
Product:              DL2400MM0159
Revision:             ST5C
Compliance:           SPC-4
LU is fully provisioned
Rotation Rate:        10000 rpm
Form Factor:          2.5 inches
Logical Unit id:      0x5000c500c1e3543b
Serial number:        WBM1EXCV
Device type:          disk
Transport protocol:   SAS (SPL-4)
Local Time is:        Mon Feb 24 11:45:47 2025 CST
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

Grown defects during certification = 0
Total blocks reassigned during format = 0
Total new blocks reassigned = 0
Power on minutes since format = 1311
Current Drive Temperature:     32 C
Drive Trip Temperature:        60 C

scsiPrintBackgroundResults Failed [medium or hardware error (serious)]
Manufactured in week 22 of year 2019
Specified cycle count over device lifetime:  10000
Accumulated start-stop cycles:  64
Specified load-unload count over device lifetime:  300000
Accumulated load-unload cycles:  1435
Vendor (Seagate Cache) information
  Blocks sent to initiator = 189952
  Blocks received from initiator = 325544
  Blocks read from cache and sent to initiator = 32037
  Number of read and write commands whose size <= segment size = 215
  Number of read and write commands whose size > segment size = 4

Vendor (Seagate/Hitachi) factory information
  number of hours powered up = 27.98
  number of minutes until next internal SMART test = 59

Error counter log:
           Errors Corrected by           Total   Correction     Gigabytes    Total
               ECC          rereads/    errors   algorithm      processed    uncorrected
           fast | delayed   rewrites  corrected  invocations   [10^9 bytes]  errors
read:      87206        0         0     87206          0          0.096           0
write:         0        0         0         0          0          0.406           0
verify:      299        0         0       299          0          0.001           0

Non-medium error count:        0

No Self-tests have been logged

Those are the results from one host. We did kick off a long SMART test on the problematic drive.

Seagate says they don't have any firmware available for those drives but to check with the PC vendor. We checked with Dell and they have installers for Windows and Red Hat. We use Proxmox, which is obviously Debian.

Can these be pushed via the iDRAC or any methods other than a Windows or Red Hat install?
 
This might work...
Don't think so - to be able to update the firmware of a drive, raw physical device passthrough is not going to do it. You will need to pass through the actual controller of the drive - which could be possible, depending on the OP's HW.

So more likely something of this.