EXPIRED Ebay - Cisco HGST SN200 7.68TB U.2 SSD - $299

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

ca3y6

Well-Known Member
Apr 3, 2021
835
819
93
So one thing I noticed with HGST SN200 is that they don’t like plx PCIe switches, so make sure it is connected to the MB directly
 

zxc_ee

Member
Apr 10, 2024
47
37
18
49
.be / .nl / .ee
Happen to have the steps used for this? :)
installed win2016, win soft (WDC-NVMe-30190240413-W2016-W2019.exe, WDC-NVMe-33210241615-S2016.exe)

ran cmd as admin, executed commands below,

dm-cli.exe scan
dm-cli.exe capture-diagnostics -u 1C58SDM00008907AUCSC-NVMEHW-H76800239 -f outputfile --clear-diag-data

hdm scan
hdm manage-firmware -u 1**************-*****-****** --load -f .\KNCCD122_padded.bin --slot 5 --activate --reset

hdm manage-firmware --activate --reset --slot 1 -u *************************

poweroff
device is visible windows, formatted , rebooted to linux and did full format, loaded KNCCD122_padded.bin to slot 5


Code:
smartctl -x /dev/nvme1
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-6.8.0-59-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       UCSC-NVMEHW-H7680
Serial Number:                      SDM000088807
Firmware Version:                   KNCCD111
PCI Vendor ID:                      0x1c58
PCI Vendor Subsystem ID:            0x1137
IEEE OUI Identifier:                0x000cca
Total NVM Capacity:                 7.687.991.459.840 [7,68 TB]
Unallocated NVM Capacity:           0
Controller ID:                      569
NVMe Version:                       1.2.1
Number of Namespaces:               1
Namespace 1 Size/Capacity:          7.681.501.126.656 [7,68 TB]
Namespace 1 Formatted LBA Size:     4096
Namespace 1 IEEE EUI-64:            000cca 0c0350d180
Local Time is:                      Wed May 14 16:23:31 2025 CEST
Firmware Updates (0x0b):            5 Slots, Slot 1 R/O
Optional Admin Commands (0x000e):   Format Frmw_DL NS_Mngmt
Optional NVM Commands (0x003f):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Resv
Log Page Attributes (0x03):         S/H_per_NS Cmd_Eff_Lg
Warning  Comp. Temp. Threshold:     66 Celsius
Critical Comp. Temp. Threshold:     71 Celsius
Namespace 1 Features (0x04):        Dea/Unw_Error

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
0 +    25.00W       -        -    0  0  0  0    15000   15000
1 +    24.00W       -        -    1  1  1  1    15000   15000
2 +    23.00W       -        -    2  2  2  2    15000   15000
3 +    22.00W       -        -    3  3  3  3    15000   15000
4 +    21.00W       -        -    4  4  4  4    15000   15000
5 +    20.00W       -        -    5  5  5  5    15000   15000
6 +    19.00W       -        -    6  6  6  6    15000   15000
7 +    18.00W       -        -    7  7  7  7    15000   15000
8 +    17.00W       -        -    8  8  8  8    15000   15000
9 +    16.00W       -        -    9  9  9  9    15000   15000
10 +    15.00W       -        -   10 10 10 10    15000   15000
11 +    14.00W       -        -   11 11 11 11    15000   15000
12 +    13.00W       -        -   12 12 12 12    15000   15000
13 +    12.00W       -        -   13 13 13 13    15000   15000
14 +    11.00W       -        -   14 14 14 14    15000   15000
15 -    10.00W       -        -   15 15 15 15    15000   15000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
0 -     512       0         0
1 -     512       8         2
2 +    4096       0         0
3 -    4096       8         1

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        43 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    60.273 [30,8 GB]
Data Units Written:                 11.994 [6,14 GB]
Host Read Commands:                 3.217.018
Host Write Commands:                566.385
Controller Busy Time:               10
Power Cycles:                       1
Power On Hours:                     0
Unsafe Shutdowns:                   0
Media and Data Integrity Errors:    0
Error Information Log Entries:      1
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               43 Celsius
Temperature Sensor 2:               34 Celsius
Temperature Sensor 3:               41 Celsius

Error Information (NVMe Log 0x01, 16 of 256 entries)
Num   ErrCount  SQId   CmdId  Status  PELoc          LBA  NSID    VS
  0          1     0  0x000c  0xc004  0x028            0     0     -

nvme smart-log /dev/nvme1
Smart Log for NVME device:nvme1 namespace-id:ffffffff
critical_warning                        : 0
temperature                             : 43 C (316 Kelvin)
available_spare                         : 100%
available_spare_threshold               : 10%
percentage_used                         : 0%
endurance group critical warning summary: 0
data_units_read                         : 60.273
data_units_written                      : 11.994
host_read_commands                      : 3.217.018
host_write_commands                     : 566.385
controller_busy_time                    : 10
power_cycles                            : 1
power_on_hours                          : 1
unsafe_shutdowns                        : 0
media_errors                            : 0
num_err_log_entries                     : 1
Warning Temperature Time                : 0
Critical Composite Temperature Time     : 0
Temperature Sensor 1           : 43 C (316 Kelvin)
Temperature Sensor 2           : 34 C (307 Kelvin)
Temperature Sensor 3           : 40 C (313 Kelvin)
Thermal Management T1 Trans Count       : 0
Thermal Management T2 Trans Count       : 0
Thermal Management T1 Total Time        : 0
Thermal Management T2 Total Time        : 0


hdm manage-firmware --load --file KNCCD122_padded.bin --slot 5 -u 1C58SDM000088807UCSC-NVMEHW-H76800239
Results for manage-firmware: Operation succeeded.
hdm manage-firmware --activate --reset --slot 5 -u 1C58SDM000088807UCSC-NVMEHW-H76800239
Results for manage-firmware: Operation succeeded.
reboot -f

nvme list
Node                  SN                   Model                                    Namespace Usage                      Format           FW Rev
--------------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------
/dev/nvme0n1          BTNH944230BH512A     INTEL SSDPEKNW512G8H                     1         512,11  GB / 512,11  GB    512   B +  0 B   HPS0
/dev/nvme1n1          SDM000088807         UCSC-NVMEHW-H7680                        1           7,68  TB /   7,68  TB      4 KiB +  0 B   KNCCD122
hdm manage-firmware --list -u 1C58SDM000088807UCSC-NVMEHW-H76800239
[1C58SDM000088807UCSC-NVMEHW-H76800239]
  Product Name             = Ultrastar SN200
  Device Type              = NVMe Controller
  Device Path              = /dev/nvme1
  UID                      = 1C58SDM000088807UCSC-NVMEHW-H76800239
  Alias                    = @nvme1
  Running Firmware Version = KNCCD122 (Loaded from Slot 5)
  Slot 1 (Read-only)       = KNCCD111
  Slot 2                   = KNCCD111
  Slot 3                   = KNCCD111
  Slot 4                   = KNCCD111
  Slot 5                   = KNCCD122 (Next Running Firmware Slot)

summary:

- getting devices out from diag mode did not work on linux - no idea why.
- same operations were successeful on win srv 2016 (i could get them work early, but completely ignored windows option)
- firmware update can be done on linux or windows
- do full power off between operations
- load and acti vate default firmware before doing anything else.

good luck to all, and thanks a lot to members who shared the knownledge!!
 
Last edited:

ca3y6

Well-Known Member
Apr 3, 2021
835
819
93
can you provide more info about this ?
mine are perfectly fine with AOC-SLG3-4E2P
In my case it is with Ceacent 16x 8 ports PLX cards.They work fine with any other brand of SSD I tried: samsung, intel, micron. But the HGST SN100 and SN200 either refused to start when connected to the switch, or are dropping randomly during usage. But work fine with the same power cables when connected directly to a PCIe lane. Observed on two computers, multiple SN100 and SN200 drives.
 

camelshoko

Member
Jun 5, 2025
38
8
8
So one thing I noticed with HGST SN200 is that they don’t like plx PCIe switches, so make sure it is connected to the MB directly
Hi, this is really true? I have buy a SN200 and i want use it on PLX8748 PCIe switches card.
Could you give me more information for it?
 

ca3y6

Well-Known Member
Apr 3, 2021
835
819
93
I was using a Ceacent x16 to 8 x4 switch, with the drives connected either directly to the switch, or via a Backplane (Intel 8-Bay PCIe SAS/SATA Backplane Board P/N: H88386-251 Tested Working | eBay). Never had a problem with that set up with drives from other brands (Samsung, Intel, Micron) but for HGST drives (SN100 and SN200), they would either not switch on on boot (the light on the disk would stay off) or they would switch on but then would show some I/O errors and randomly drop in Windows when in use. Those very same drives were working fine when connected directly to a PCIe lane of the motherboard. So I am not sure why, but there seems to be some sort of incompatibility. Noticed that with two different Ceacent cards (same model).
 

camelshoko

Member
Jun 5, 2025
38
8
8
I was using a Ceacent x16 to 8 x4 switch, with the drives connected either directly to the switch, or via a Backplane (Intel 8-Bay PCIe SAS/SATA Backplane Board P/N: H88386-251 Tested Working | eBay). Never had a problem with that set up with drives from other brands (Samsung, Intel, Micron) but for HGST drives (SN100 and SN200), they would either not switch on on boot (the light on the disk would stay off) or they would switch on but then would show some I/O errors and randomly drop in Windows when in use. Those very same drives were working fine when connected directly to a PCIe lane of the motherboard. So I am not sure why, but there seems to be some sort of incompatibility. Noticed that with two different Ceacent cards (same model).
Oh, That's a bad news, my card is also BCM PEX8748 i will test it when i ready my NAS, thanks again. :)