Dang I sent an Offer for 6 without realizing that
.Hopefully I lowballed low enough (80 USD / Piece).
Enterprise SSD "small deals"
- 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.
.Hopefully I lowballed low enough (80 USD / Piece).
Doesn't mean sellers who don't accept returns have something to hide. As a private seller myself, I provide full transparency in term of smarts, along with big red warning that this is a U.2/SAS drive not compatible with SATA (and I put the warning as a photo for mobile users). I consider that it is sufficient information and if the buyer changed their mind or made a mistake, it is their responsibility to eat it. There are many businesses operating on ebay, but it was originally a consumer to consumer platform.
yes they are QLC. Not sure why. Are you concerned about their health or performance? I bought a couple of 5210 ION on ebay (not from this seller). They were in excellent state. Yes you can't use them for anything write intensive but they are perfectly fine for some other usage. I use one as an external drive when I travel. Their major downside in my opinion is their slow writes (so not suitable to be added in RAID with TLC drives).
Last edited:
I got 2 of these today. Both were 2020 manufacture dates with 4 years of power on time. One had 2TB written and the other says 2GB...
I finally got my 2 PM1633 drives.
Unfortunately, it seems like one of them might be in danger of the 32k bug. Not sure...
I've been trying to find firmware for these without luck and was wondering if someone had copies of versions not affected by the bug.
Any help would be greatly appreciated.
Drive1 with GQP2 firmware. I'm worried about this one; I can't find much information about it. Just a combability report from Adaptec:
This is the second Drive with EQP4 firmware. Looks like EQPC is the latest version:
Unfortunately, it seems like one of them might be in danger of the 32k bug. Not sure...
I've been trying to find firmware for these without luck and was wondering if someone had copies of versions not affected by the bug.
Any help would be greatly appreciated.
Drive1 with GQP2 firmware. I'm worried about this one; I can't find much information about it. Just a combability report from Adaptec:
Code:
=== 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: 4096 bytes
LU is resource provisioned, LBPRZ=1
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Logical Unit id: 0x5002538a066064f0
Serial number: S23TNAAH600102
Device type: disk
Transport protocol: SAS (SPL-4)
Local Time is: Sat Aug 23 13:52:39 2025 CDT
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: 36 C
Drive Trip Temperature: 60 C
Accumulated power on time, hours:minutes 11704:44
Manufactured in week 20 of year 2016
Accumulated start-stop cycles: 348
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 37711.836 0
write: 0 0 0 0 0 30592.779 0
verify: 0 0 0 0 0 0.001 0
Non-medium error count: 111
No Self-tests have been logged
Code:
=== START OF INFORMATION SECTION ===
Vendor: SAMSUNG
Product: P1633N38CLAR3840
Revision: EQP4
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: 0x5002538a06575620
Serial number: 2BNAAH500700
Device type: disk
Transport protocol: SAS (SPL-4)
Local Time is: Sat Aug 23 13:57:39 2025 CDT
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: 2%
Current Drive Temperature: 37 C
Drive Trip Temperature: 60 C
Accumulated power on time, hours:minutes 53672:56
Manufactured in week 21 of year 2016
Accumulated start-stop cycles: 85
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 400726.191 0
write: 0 0 0 0 0 339093.252 0
verify: 0 0 0 0 0 0.001 0
Non-medium error count: 107
So virtually no usage, not surprising he cherry picked a newer drive for his listing. I still don't have a tracking number for my 12 so we will see what shows up.
I got 2 of these as well. Not sure if I'm reading these smart values right, but mine say 7999473148 total LBAs written (~4TBW I think), with the other for some reason not having that value listed at all...
It lists "Media Wearout Indicator" 625980062587 which would be ~290TBW. Not sure if the firmware is different. The first one is GA36 and the second is HE58. I wish I had thought of that before putting it in a zfs array because its so much easier for me to just plug it into a windows vm and click the update button
7999473148 LBA's written equates to roughly 3.8TB/512k and 29TB/4096k, These drives are rated for 8400TB so I highly doubt anyone is gonna wear one out anytime soon.
Looks like you got one drive that was used minimally and one that was likely a HS drive and was never needed so almost nothing was written to it. In all likelihood these drives will die of old age long before many even get close to that TBW
Not really because I sold 8 MX500 4TB's that I paid $100 each for 8 months ago that covered almost the entire cost of the new drives. So in reality I have about $70 per drive invested in them.Ouch
Yeah I hit paydirt with that purchase because the eBay seller was clueless/lazy/just a nice guy because when they arrived 7 of them tested just fine but 1 of them was not detected by the server. I let the seller know that 1 was DOA but I was gonna try to open a RMA with Crucial to get it replaced under warranty but an hour after I sent that message to him he promptly refunded me for 1 drive.Those Crucial MX500 are a great Price. I paid 300 EUR / Piece for them a few Years ago
So then I attempted to RMA the failed drive and Crucial said "sorry we don't have anymore MX500 4TB but would substitute it with a BX500(QLC) 4TB" but while discussing why I wouldn't want an inferior drive the engineer told me if these drives had been sitting unpowered for a decent length of time to try grabbing a USB-SATA adapter and plug the drive in and just leave it for 60mins and then unplug and reconnect and after that the drive was working just fine and passed every test I could throw at it and ran in a ZFS pool for 6 months without issue.
Apparently the MX500 has a capacitor that will slowly drain when not powered up and it just needed to be hooked to power while it recharged. So in reality I only had $87.50 per drive in them and sold all 8 for $190 each.
And I guess we could do our own Overprovisioning, although to be honest since I never did it myself via
hdparm, I don't know if there is a difference between:- Doing via
hdparmand directly modify the Capacity that the SSD reports to the OS - Doing via Partitioning (e.g.
partedorgdisk) and create a Partition smaller than the entire Drive
Typically I always do Partitioning and always leave a small Fraction of the Drive (e.g. 512MB for a 0.5TB - 4TB Drive) unpartitioned at the End of the Drive, to account for slighly different Number of Sectors between Drives. I cannot say I ever saw the Need for it though, they seem to perfectly match in Terms of Sectors and if there are Differences, it's typically 3.84TB vs 3.6TB or 1.92TB vs 1.6TB or something like that, something that a meager 512MB cannot compensate at all.
I'd wonder for Overprovisioning if, using a Partition "Type" of Overprovisioning (e.g. leave 20% of the Drive unpartitioned), that would achieve the same Result as doing it via
hdparm.Since I don't really look at smartctl all that much (apart from TBW and Temperatures), but rather rely on ZFS Checksum Reports, probably the end Result, at least for me it's the same. Basically when the OS / ZFS thinks the Drive is full, there are actually still quite a few Sectors available, which could in Theory be used for Wear Levelling. BUT I guess that since the Drive itself does NOT know that we want that Part of the Drive to be used for Wear Levelling, it most likely would still generate SMART Errors.
Any Thought
?
I dunno but that quirk coupled with the fact if I ever actually had to RMA them I was getting QLC drives as replacements sealed the deal for me to let them go while I could still get the best capital for them.
Alright. I'm not tempted to touch a SSD which already has at least some Sectors that are Bad
.I just had a HDD fail on my Server Today without ANY Warning at all (which is weird in my Experience)
: just disappeared from the OS, no Click, no ATA Errors in dmesg, nothing. Just some ZFS ZIO Errors which is normal since the Drive couldn't be written to (and zfs failed it from the affected VDEV).others occasionally post deals here, but I only post enterprise drives myself. And given the inferior endurance and great number of counterfeits on ebay, I don't know that I would want to buy retail SSDs on ebay, particularly when enterprise can be so affordable.