Samsung SSD PM1643 3.8TB SAS 12Gb/s MZ-ILT3T8A 2.5" @ $289.98

[LodeRunner]

So I have X319_S16437T6ATE (the 7.68 TB drive) running NA53. Anyone know if this will suffer from the 32k or 40k power-on hours death? The drive is listed as eligible for NA54, but I'm having trouble finding that LOD.

 

[bandit8623]

So I have X319_S16437T6ATE (the 7.68 TB drive) running NA53. Anyone know if this will suffer from the 32k or 40k power-on hours death? The drive is listed as eligible for NA54, but I'm having trouble finding that LOD.

X319_S16437T6ATE.NA54.rar

drive.google.com

here ya go

 

[LodeRunner]

here ya go

Thank you very much.

 

[redeamon]

Index of /linux/netapp/test/disk_fw

 

[redeamon]

Important! Use this link: http://ftp.otenet.gr/linux/netapp/all.zip

This file contains firmware's from 2020 i.e., X670_S164315TATE.NA54.LOD 9/9/2020 over the directory listing file of X670_S164315TATE.NA53.LOD from 2019-06-20.

 

[tozmo]

Important! Use this link: http://ftp.otenet.gr/linux/netapp/all.zip

This file contains firmware's from 2020 i.e., X670_S164315TATE.NA54.LOD 9/9/2020 over the directory listing file of X670_S164315TATE.NA53.LOD from 2019-06-20.

Thank you! I have to use this on a pm1633a drive running NA51. Hopefully I don't screw it up, as those drives are in an Unraid setup

 

[tozmo]

For my PM1633a's:

smartctl lists them as NETAPP x357's with NA51.

I have the NA54.lod (3.98MB) from the all.zip here. Also have the MZ7LM240HCGR-00003_3F3Q.bin (1MB) from the huge firmware list from this forum TFW.zip (MEGA).

Any ideas which to use? Is flashing to NA54 the easiest fix, keeping it within the Netapp line, or flip it to Samsung from the perhaps-unverified-source TFW.zip?

 

[redeamon]

For my PM1633a's:

smartctl lists them as NETAPP x357's with NA51.

I have the NA54.lod (3.98MB) from the all.zip here. Also have the MZ7LM240HCGR-00003_3F3Q.bin (1MB) from the huge firmware list from this forum TFW.zip (MEGA).

Any ideas which to use? Is flashing to NA54 the easiest fix, keeping it within the Netapp line, or flip it to Samsung from the perhaps-unverified-source TFW.zip?

If NA51 is working for you, I'd just go with NA54 and call it a day. Cross flashing should work, but there's a small chance it might brick the drive or cause data loss due to the change over.

 

[tozmo]

Are these (1633 and 1643) at risk for sudden death from hours on?

 

[redeamon]

Yes. See: https://forums.servethehome.com/index.php?threads/15-3-tb-sas-12g-ssd-for-750-usd.37144/

 

[silent_303]

Hello,
i would like to crossflash my Samsung PM1633 3.84 to NetApp. I think this one suffers from the bug and i can't find firmware from Samsung.

=== START OF INFORMATION SECTION ===
Vendor: SAMSUNG
Product: MZILS3T8HCJM/003
Revision: GQP2
Compliance: SPC-4
User Capacity: 3,840,755,982,336 bytes [3.84 TB]
Logical block size: 512 bytes
Physical block size: 4096 bytes
LU is resource provisioned, LBPRZ=1
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Logical Unit id: 0x5002538a07397df0
Serial number: S23TNA0J301431
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Sat Jan 28 08:11:41 2023 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning: Enabled

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Percentage used endurance indicator: 0%
Current Drive Temperature: 43 C
Drive Trip Temperature: 60 C

Accumulated power on time, hours:minutes 36382:15
Manufactured in week 10 of year 2017
Accumulated start-stop cycles: 69
Specified load-unload count over device lifetime: 0
Accumulated load-unload cycles: 0
Elements in grown defect list: 0



Can anyone tell me which is the correct NetApp Firmware version and crossflash with sg_buffer does work?

Thank you very much
Tobias

 

[silent_303]

From my research the Samsung PM1633 = X356_S16333T8ATE

Tried:
root@tera-ve:/tmp# sg_write_buffer -b 4k -m dmc_offs_save -I /tmp/X356_S16333T8ATE.NA04.LOD /dev/sg2
Write buffer failed: Illegal request
sg_write_buffer failed: Illegal request

And:
root@tera-ve:/tmp# sg_write_buffer --m 5 -vvvvvv --in=/tmp/X356_S16333T8ATE.NA04.LOD /dev/sg2
found sg_bsg_major=243
open /dev/sg2 with flags=0x802
tried to read 8388608 bytes from /tmp/X356_S16333T8ATE.NA04.LOD, got 4177920 bytes
will write 4177920 bytes
sending single write buffer, mode=0x5, mpsec=0, id=0, offset=0, len=4177920
Write buffer cdb: [3b 05 00 00 00 00 3f c0 00 00]
Write buffer parameter list (first 256 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
check_file_type: file descriptor is sg device
set_pt_file_handle: sg driver version 3.05.36 so choose v3
duration=1052 ms
Write buffer:
Fixed format, current; Sense key: Illegal Request
Additional sense: Invalid field in parameter list
Field replaceable unit code: 37
Sense Key Specific: Error in Data parameters: byte 0
Raw sense data (in hex), sb_len=24, embedded_len=24
70 00 05 00 00 00 00 10 00 00 00 00 26 00 25 80
00 00 09 65 26 00 00 00
Write buffer failed: Illegal request, type: sense key, apart from Invalid opcode


No success, looks like there are checks :-(
I am to noob to get fixed this myself. Since i have 4 of these and they all have 36.000h runtime i get nervous
Anyone can support original Firmware from Samsung or does have a clue how to crossflash them to NetApp ?

Thank you very much