EXPIRED Ebay 3.84TB Netapp SAS SSD - $100
- Thread starter ca3y6
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
Just to be clear I am not related in any way with the seller and do not vouch for them.
My experience with netapp drives is that they just need to be reformatted to 512 blocks, there is a whole thread about how to do this.
The photo says those drives are from 2017, I think chances are they already clock way longer than 32k hours, so would be dead already if the version of the firmware was affected by the bug.
Popped in one of them, 44k hours. Why does it not matter if it's above 32k hours? Does that mean its already dead or that firmware is already updated and it's fine?
Code:
=== START OF INFORMATION SECTION ===
Vendor: NETAPP
Product: X356_S163A3T8ATE
Revision: NA01
Compliance: SPC-4
User Capacity: 3,900,767,794,560 bytes [3.90 TB]
Logical block size: 520 bytes
Physical block size: 4160 bytes
LU is resource provisioned, LBPRZ=1
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Logical Unit id: 0x5002538a0724bb60
Serial number: S394NA0J210344
Device type: disk
Transport protocol: SAS (SPL-4)
Local Time is: Tue Jan 7 15:50:54 2025 EST
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: 22 C
Drive Trip Temperature: 60 C
Accumulated power on time, hours:minutes 44078:41
Manufactured in week 05 of year 2017
Accumulated start-stop cycles: 12
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 86853.144 0
write: 0 0 0 0 0 57877.988 0
verify: 0 0 0 0 0 163359.447 0
Non-medium error count: 63
No Self-tests have been loggedyes, the bug is that the drive dies after 32k power on hours (or 40k hours, have seen both mentioned, don't remember which is which for which model).
If the drive survived to 44k it means the firmware has been updated to a version that fixes that bug so we are in the clear.
100% health. Nice. Waiting for mines. Looks like it was a great deal. 520 byte logical block, you will need to convert it to 512 or 4096 to use it, see this thread. (you can do that on windows too)
If the drive survived to 44k it means the firmware has been updated to a version that fixes that bug so we are in the clear.
100% health. Nice. Waiting for mines. Looks like it was a great deal. 520 byte logical block, you will need to convert it to 512 or 4096 to use it, see this thread. (you can do that on windows too)
Great deal, too bad I haven't been checking so I missed it.
AFAIK, the NA01 firmware has the bug. It was fixed in NA04.
I wouldn't put anything on those drives or even use them until its updated to NA04. You're treading on thin ice.
AFAIK, the NA01 firmware has the bug. It was fixed in NA04.
I wouldn't put anything on those drives or even use them until its updated to NA04. You're treading on thin ice.
How did the drive survive to 44k hours then?
[edit] In fact I am looking at my inventory of drives i have two more netapp drives, exactly the same model, same firmware, both clock 51k hours and going. Surely if they were affect by the bug they would be dead by now.
[edit] In fact I am looking at my inventory of drives i have two more netapp drives, exactly the same model, same firmware, both clock 51k hours and going. Surely if they were affect by the bug they would be dead by now.
Last edited:
Yeah I unfortunately don't have access to download it as a lonely homelabber... if someone can give me the firmware I'm happy to try it.
Searching the web, from what I can tell, the drive dies at 32k hours. So I think it you pass the threshold somehow you are in the clear. In any case I may be wrong but I am not overly worried about it myself. Of course, always backup your data! (in fact for me those drives are meant to be used as a backup of the backup!)
Sure, if that works for you. I do know that once the drive dies from the bug, there is no coming back. I'd rather not risk it if the fix is a simple firmware update.
I bought a couple of the PM1643a netapp drives a while back - they only had about 21K hours on them. Someone posted the NA04 firmware alongwith instructions to update. Update the firmware and use the drives without any worry. If the update fails, you can still return it for refund.