Go here for recent NetApp firmware as of June 2023:
Thank you for the help! Upgrade was a cinch with the right file in hand. I'm really happy to be off of NA51.Go here for recent NetApp firmware as of June 2023:
Go here for recent NetApp firmware as of June 2023:
Thank you for the help! Upgrade was a cinch with the right file in hand. I'm really happy to be off of NA51.Go here for recent NetApp firmware as of June 2023:
Well, I also have dozens of PM1633N38 EMC3840 disks w/ EQPC firmware rivision and it's working well over 53000 hours.so i'm rather confused.
i have about 15 MZ-ILS3T80 (PM 1633 1632 REV 0) ish drives.
Model: P1633N38 EMC3840
Revision: EQPC
unfortunately i can't read this one in my possession but i also bought some other drives that are showing up as:
(1633a)
Product: PA33N3T8 EMC3840
Revision: EQL8
@ 33834 hours currently
how does one actually know if the ssd's are affected?
thanks
Thanks, I've seen NetApp ones (and have access to NetApp FW, but wouldnt know how to updateIt 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.
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.(and have access to NetApp FW, but wouldnt know how to update)
Thank you. Got NA54 and NA55 if anyone requires itIf 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 NA51If 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.
sudo sg_write_buffer -b 4k -m dmc_offs_save -I file.rel -v /dev/sg1
Thanks @mrpascBasically it’s likesudo 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)Basically it’s likesudo 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 NA54 if you are still looking for itMight 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)
EQPC
?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!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
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 numbersI am a little concerned - the drive does not seem to like to be trimmed!
Ah that is exactly what I have been seeing too - good to know, cheers!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
P1633N38
. Is it even possible with this drive?