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

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

mrpasc

Well-Known Member
Jan 8, 2022
579
320
63
Munich, Germany
It depends. On your use-case, on your existing system, on your ability to get firmware updates (or at least to check if firmware is one which prevents from 30k/35k/45k hours bug).
If you are after performance: not worth, go used NVME U.2 drives, almost same price for much more power.
If you are after a good performance-powerusage ratio: not worth, go for used enterprise Sata SSDs.
If you have SAS infrastructure in place ( like HBA, backplane and so on) might be worth the money, but I have seen similar Samsungs 1633a for around 150€ even here in Europe.
the ones you have linked come with IBM firmware, imho the worst one to acquire any information or updates. Personally I would avoid them.
 
  • Like
Reactions: piranha32

peggleg1983

New Member
Mar 12, 2019
9
0
1
It depends. On your use-case, on your existing system, on your ability to get firmware updates (or at least to check if firmware is one which prevents from 30k/35k/45k hours bug).
If you are after performance: not worth, go used NVME U.2 drives, almost same price for much more power.
If you are after a good performance-powerusage ratio: not worth, go for used enterprise Sata SSDs.
If you have SAS infrastructure in place ( like HBA, backplane and so on) might be worth the money, but I have seen similar Samsungs 1633a for around 150€ even here in Europe.
the ones you have linked come with IBM firmware, imho the worst one to acquire any information or updates. Personally I would avoid them.
Thanks, I've seen NetApp ones (and have access to NetApp FW, but wouldnt know how to update ;)), but they are sold out atm. Will keep eye out and see if they can be had for under £150 each
I have SAS infrastructure already (Supermicro 24-bay SAS3)
 

mrpasc

Well-Known Member
Jan 8, 2022
579
320
63
Munich, Germany
(and have access to NetApp FW, but wouldnt know how to update ;))
If you have access to the *.lod file, updating them with sg_write is as easy as with any other SAS device. No need to have access to an ONTAP system… just make sure to have them reformatted to 512 before firmware update.
 

peggleg1983

New Member
Mar 12, 2019
9
0
1
If you have access to the *.lod file, updating them with sg_write is as easy as with any other SAS device. No need to have access to an ONTAP system… just make sure to have them reformatted to 512 before firmware update.
Thank you. Got NA54 and NA55 if anyone requires it
 

peggleg1983

New Member
Mar 12, 2019
9
0
1
If you have access to the *.lod file, updating them with sg_write is as easy as with any other SAS device. No need to have access to an ONTAP system… just make sure to have them reformatted to 512 before firmware update.
could you please let me know the command to apply the .lod file to a drive? managed to pick one up for £120 (waiting for delivery), but want to test and make sure i can upgrade FW as currently running NA51
 

mrpasc

Well-Known Member
Jan 8, 2022
579
320
63
Munich, Germany
Basically it’s like sudo sg_write_buffer -b 4k -m dmc_offs_save -I file.rel -v /dev/sg1
But of course you must adopt the path to your firmware binary as well the path to your device.
 

peggleg1983

New Member
Mar 12, 2019
9
0
1
Basically it’s like sudo sg_write_buffer -b 4k -m dmc_offs_save -I file.rel -v /dev/sg1
But of course you must adopt the path to your firmware binary as well the path to your device.
Thanks @mrpasc
Drive was at home when I got back after work. Updated successfully from NA51 to NA54

Screenshot 2023-09-04 at 20.34.42.png
 

yukas

Member
Jun 3, 2022
34
2
8
Basically it’s like sudo sg_write_buffer -b 4k -m dmc_offs_save -I file.rel -v /dev/sg1
But of course you must adopt the path to your firmware binary as well the path to your device.
i have 3 SSD'd with same problem - please see attach and below. (32k hours lock)
We use SAS HBA with IT mode and Samsung SSD Manager and other SG_utuls.
We've already used all the options, and can ship anywhere for disk data recovery. Please help us!

all drives with this errors:



inquiry cdb: 12 00 00 00 24 00
spt_indirect, adapter: \\.\PhysicalDrive2 Length=56 ScsiStatus=0 PathId=0 TargetId=0 Lun=0
CdbLength=6 SenseInfoLength=64 DataIn=1 DataTransferLength=36
TimeOutValue=60 DataBufferOffset=124 SenseInfoOffset=60
SAMSUNG P043S7T6 EMC7680 ESV8 peripheral_type: disk [0x0]
PROTECT=0
inquiry cdb: 12 01 00 00 24 00
spt_indirect, adapter: \\.\PhysicalDrive2 Length=56 ScsiStatus=0 PathId=0 TargetId=0 Lun=0
CdbLength=6 SenseInfoLength=64 DataIn=1 DataTransferLength=36
TimeOutValue=60 DataBufferOffset=124 SenseInfoOffset=60
inquiry: pass-through requested 36 bytes (data-in) but got 19 bytes
inquiry cdb: 12 01 80 01 00 00
spt_indirect, adapter: \\.\PhysicalDrive2 Length=56 ScsiStatus=0 PathId=0 TargetId=0 Lun=0
CdbLength=6 SenseInfoLength=64 DataIn=1 DataTransferLength=256
TimeOutValue=60 DataBufferOffset=124 SenseInfoOffset=60
inquiry: pass-through requested 256 bytes (data-in) but got 16 bytes
Unit serial number: 5BNY0KA04703
inquiry cdb: 12 01 83 01 00 00
spt_indirect, adapter: \\.\PhysicalDrive2 Length=56 ScsiStatus=0 PathId=0 TargetId=0 Lun=0
CdbLength=6 SenseInfoLength=64 DataIn=1 DataTransferLength=256
TimeOutValue=60 DataBufferOffset=124 SenseInfoOffset=60
inquiry: pass-through requested 256 bytes (data-in) but got 76 bytes
LU name: 5002538b08a449d0
mode sense(10) cdb: 5a 00 01 00 00 00 00 00 fc 00
spt_indirect, adapter: \\.\PhysicalDrive2 Length=56 ScsiStatus=0 PathId=0 TargetId=0 Lun=0
CdbLength=10 SenseInfoLength=64 DataIn=1 DataTransferLength=252
TimeOutValue=60 DataBufferOffset=124 SenseInfoOffset=60
mode sense(10):
Fixed format, current; Sense key: Hardware Error
Additional sense: Logical unit failure
Raw sense data (in hex), sb_len=64, embedded_len=18
70 00 04 00 00 00 00 0a 00 00 00 00 3e 01 00 00
00 00
MODE SENSE (10) command: Medium or hardware error, type: sense key (plus blank check for tape)


1693893477508.png
 

Attachments

Last edited:

peggleg1983

New Member
Mar 12, 2019
9
0
1
Might be outside of scope for this thread but... I picked up a 3.84tb netapp branded PM1643a. It's sadly on firmware version NA51. Does anyone have good ideas for where to look for X357_S164A3T8ATE.NA54.LOD? (doesn't appear in the all.zip referenced on page 8)
I have NA54 if you are still looking for it
 

sephallen

New Member
Jan 22, 2021
15
0
1
Was anyone able to update a Samsung branded drive to EQPC?

I recently purchased a P1633N38 from eBay running EQP6 with over 45k hours and I am a little concerned - the drive does not seem to like to be trimmed!

Code:
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.19.17-Unraid] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               SAMSUNG
Product:              P1633N38 EMC3840
Revision:             EQP6
Compliance:           SPC-4
User Capacity:        3,840,774,504,448 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:      0x5002538a06bbb820
Serial number:        2BNA0HB02058
Device type:          disk
Transport protocol:   SAS (SPL-4)
Local Time is:        Sat Sep 16 07:48:35 2023 BST
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: 4%
Current Drive Temperature:     45 C
Drive Trip Temperature:        60 C

Accumulated power on time, hours:minutes 45841:20
Manufactured in week 46 of year 2016
Accumulated start-stop cycles:  58
Specified load-unload count over device lifetime:  0
Accumulated load-unload cycles:  0
Elements in grown defect list: 0

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:          0        0         0         0          0     460552.206           0
write:         0        0         0         0          0     287128.371           0

Non-medium error count:       10

No Self-tests have been logged
 

Whaaat

Active Member
Jan 31, 2020
358
187
43
I am a little concerned - the drive does not seem to like to be trimmed!
None of Samsung enterprise drives likes trimming. They will hang for about a minute throttling performance to several kilobytes per sec while handling TRIM command. Don't bother, they don't need trimming to demonstrate claimed performance numbers
 
  • Like
Reactions: sephallen

sephallen

New Member
Jan 22, 2021
15
0
1
None of Samsung enterprise drives likes trimming. They will hang for about a minute throttling performance to several kilobytes per sec while handling TRIM command. Don't bother, they don't need trimming to demonstrate claimed performance numbers
Ah that is exactly what I have been seeing too - good to know, cheers!

As for firmware, it seems some users have been flashing similar drives with NetApp firmware, but I have not been able to find any posts in this thread regarding doing that with a P1633N38. Is it even possible with this drive?
 

yukas

Member
Jun 3, 2022
34
2
8
Lovely. At least I can confirm the disks I have have the newest firmware on them. (EQPC)

I'm at a loss as to why they would give firmware out encrypted. To decrypt it, their updater software must have the private key in it. It makes no sense.

Are you able to find the updater application that process the gpg file?
i have decrypted files , but i cant flash to drive - error - pleasee my post https://forums.servethehome.com/ind...2gb-s-mz-ilt3t8a-2-5-289-98.32725/post-391701

ps. firmware for ESV8 SAMSUNG P043S7T6 EMC7680 on this link https://dropmefiles.com/fIMkJ
 

Jianshu

New Member
Jul 5, 2024
1
0
1
Smart says:

Revision: ESFA

Two of the drive labels say:

F/W VFT50Z2Q

So I'm not really sure, TBH.

Update to my earlier post... after formatting to 512, I created a new GPT table and a new partition and now I'm dd'ing the drives to wipe them. I also did a fsck for good measure... which didn't report any problems. Watching dmesg, I haven't seen the errors on the drives for about 3 hours now.
Hi buddy,

I recently got a few PM1643 SSDs with firmware version ESFA, I have reformatted them to 512 format. They're now installed in my DELL T630 server, and everything seems to be running smoothly so far.

Since these drives should be the same model as yours, I would like to ask you a few questions: how long have your drives been running? Do these ESFA drives still have the 32K HOURS BUG or 40K HOURS BUG issue? Any feedback would be greatly appreciated!
 
Last edited:

BusError

New Member
Jul 17, 2024
20
3
3
I got myself a pair of these drives(SAMSUNG P1633N38 EMC3840EQPCN), but they show as "Unsupported" on my Dell Perc (PERC H730 Adapter FW: 25.4.0.0015) -- the Perc firmware is moderately recent, and I had assumed they'd "just work"... what am I missing?
Even smartctl -d megaraid,X fails to read them. megacli has no trouble finding them, but they show as "Unconfigured(good)"
What option do I have? Is that QPCN firmware affected by the 32k problem?
 

LodeRunner

Active Member
Apr 27, 2019
553
235
43
I got myself a pair of these drives(SAMSUNG P1633N38 EMC3840EQPCN), but they show as "Unsupported" on my Dell Perc (PERC H730 Adapter FW: 25.4.0.0015) -- the Perc firmware is moderately recent, and I had assumed they'd "just work"... what am I missing?
Even smartctl -d megaraid,X fails to read them. megacli has no trouble finding them, but they show as "Unconfigured(good)"
What option do I have? Is that QPCN firmware affected by the 32k problem?
They may be formatted as 520 bytes/sector. If so, you’ll need a SAS HBA and sgutils to low level format them as 512.
 
  • Like
Reactions: nexox and BusError

BusError

New Member
Jul 17, 2024
20
3
3
So I finally managed to get the disk formatted to 512 with in an external enclosure, and they seem fine there (and 0% usage on them, so great), but they still fail to be recognized by my raid card! Could it be they are incompatible with 12Gbs cards?
The bizarre thing is that megacli still claim it is 520 sectors, while, it isn't it was formated (and verified) in the other enclosure... SO my guess is that, it's 'guessing'...

w Size: 0 KB [0x0 Sectors]
Non Coerced Size: 0 KB [0x0 Sectors]
Coerced Size: 0 KB [0x0 Sectors]
Sector Size: 520
Logical Sector Size: 520
Physical Sector Size: 4160
Firmware state: Unconfigured(bad)
Device Firmware Level: EQPC
Shield Counter: 0
Successful diagnostics completion on : N/A
SAS Address(0): 0x5002538a06a725e2
SAS Address(1): 0x0
Connected Port Number: 5(path0)
Inquiry Data: SAMSUNG P1633N38 EMC3840EQPCNZNA0HA02469
FDE Capable: Not Capable
FDE Enable: Disable
Secured: Unsecured
Locked: Unlocked
Needs EKM Attention: No
Foreign State: None
Device Speed: Unknown
Link Speed: Unknown
Media Type: Hard Disk Device
Drive: Not Supported
Drive Temperature :34C (93.20 F)
PI Eligibility: No
Drive is formatted for PI information: No
PI: No PI
Port-0 :
Port status: Active
Port's Linkspeed: Unknown
Port-1 :
Port status: Active
Port's Linkspeed: Unknown
Drive has flagged a S.M.A.R.T alert : No