EXPIRED Samsung/Netapp 7.68TB PM1643 SAS SSD - ebay - EUR 250

[luckylinux]

The main benefit of the API is that it returns a json object and you can apply lots of filters on that. So for instance you can get rid of items where multiple sizes are advertised, and where the search picks it up because of the price of the lowest size. You also get to search on multiple ebay platforms (right now I only do UK, US and DE). You can't really search by part number as the descriptions are awefully inconsistent and imprecise on ebay, and then you have all the OEM alternatives. But if you search for enterprise SSD sizes (3.2TB, 3.84TB), you filter out lots of garbage. The only problem is Intel 4TB drives, and my main source of garbage.

Then you need to be smart about the logic for parsing the description and filtering out unwanted stuff (cases, USB, ps5, external, etc). Also need some logic for spotting lots of multiple drives (so you can filter by price per TB rather than absolute price, a $400 lot of 4x 3.84TB drive is a great deal).

But do you use the "RAW" JSON API or the Python (or other Language one) ?

The eBay API makes the Atlassian JIRA API look like Child Play to be honest ...

 

[ca3y6]

I use the raw rest API using C#. I only needed to implement a couple types of calls so not a huge amount of work. The difficulty is parsing and filtering the description. The only third party library I used is to handle the authentication. You also have to be careful about your calls to stay under the daily rate limits.

 

[luckylinux]

I use the raw rest API using C#.

It's been a long Time since I tried to use C# . I'm mainly doing Python Stuff nowadays .

I only needed to implement a couple types of calls so not a huge amount of work.

I can imagine that. If it's only a Couple of EndPoints and a couple Methods (GET/POST) etc, IMHO most of the Work might be to implement Pagination to go through the Pagination Results (via "Cursor", if that's how they implement it).

The difficulty is parsing and filtering the description.

I guess I would have to try to see how hard it is indeed. Shouldn't be too hard IMHO. But ... already Locale-Dependent Settings play a huge Part in how good Results are: whether you look for 3.84TB / 3,84TB / 3840GB makes all the Difference and of course not consistent ever.

The only third party library I used is to handle the authentication.

Pretty sure I looked briefly into the RAW API and saw there were like 4 or so Types of API Keys, then said "Forget it".

You also have to be careful about your calls to stay under the daily rate limits.

Probably will need to split into a "Crawler" Part and a "Processor" Part, especially when testing in the Beginning.

Let the first Part Cache Results (either save JSON File or possibly much more advanced stuff like Valkey / Redis or anything in-between), then once that's done run the 2nd Part.

 

[heromode]

It's been a long Time since I tried to use C# . I'm mainly doing Python Stuff nowadays .


I can imagine that. If it's only a Couple of EndPoints and a couple Methods (GET/POST) etc, IMHO most of the Work might be to implement Pagination to go through the Pagination Results (via "Cursor", if that's how they implement it).


I guess I would have to try to see how hard it is indeed. Shouldn't be too hard IMHO. But ... already Locale-Dependent Settings play a huge Part in how good Results are: whether you look for 3.84TB / 3,84TB / 3840GB makes all the Difference and of course not consistent ever.



Pretty sure I looked briefly into the RAW API and saw there were like 4 or so Types of API Keys, then said "Forget it".



Probably will need to split into a "Crawler" Part and a "Processor" Part, especially when testing in the Beginning.

Let the first Part Cache Results (either save JSON File or possibly much more advanced stuff like Valkey / Redis or anything in-between), then once that's done run the 2nd Part.

I would recommend Geo-Ship.com for an easy solution, you can do a few searches for free when you register, and more if you pay

 

[ca3y6]

for those based in the US, looking for SAS drives:

Pardon Our Interruption...

Pardon Our Interruption...

Pardon Our Interruption...

Pardon Our Interruption...

Pardon Our Interruption...

 

[josh]

for those based in the US, looking for SAS drives:

Pardon Our Interruption...

Pardon Our Interruption...

Pardon Our Interruption...

Pardon Our Interruption...

Pardon Our Interruption...

All sold lol

 

[ericloewe]

Let's see if they bite at 200 bucks (pushing my luck, but you never know).

 

[ericloewe]

Seller did go for 240 instead of 250 (good enough to cover shipping). Ordered four, will share details once they arrive next week-ish.

 

[usbTypeD]

Also bought two. Have yet to find a usecase for it but i dont think people here will judge.

 

[fossxplorer]

So there are uncertainty about whether these NetApp 7.68TB SAS SSDs can be low-level formatted to 512B?

 

[ca3y6]

I am not related to the seller, but from the seller's screenshots, the drives are already formatted to 512b. That's the logical block size in the smartctl output. Now when you buy an OEM drive there is always a small risk, but netapp drives have been fairly solid for me, and if the drive is not formatted to 512b and cannot be formatted to 512b, I think you would have a claim that it was mis-advertised by the seller on ebay which would warrant a return.

 

[luckylinux]

I am not related to the seller, but from the seller's screenshots, the drives are already formatted to 512b. That's the logical block size in the smartctl output. Now when you buy an OEM drive there is always a small risk, but netapp drives have been fairly solid for me, and if the drive is not formatted to 512b and cannot be formatted to 512b, I think you would have a claim that it was mis-advertised by the seller on ebay which would warrant a return.

To be fair I think he said "Should be able to be formatted ...". Should != Shall/Must/Can.

EDIT 1: he said "most Probably":

They can either be used in Netapp or with a low level format most probably also in other servers supporting SAS SSD.

 

[vitamins]

Netapp E-Series drives (the E-X4133A sticker) do not come in 520b/s, only 512b/s. E-Series uses a different OS, santricity, rather than ontap. The version compatible with ontap would have a X319A label on it and show as an X319A with NAXX firmware in sellers smartctl output.