6.4TB INTEL P4608 SSD DC $250

[Damo]

Intel P4608 6.4TB Solid State Drive (SSDPECKE064T701) for sale online | eBay

Find many great new & used options and get the best deals for Intel P4608 6.4TB Solid State Drive (SSDPECKE064T701) at the best online prices at eBay! Free shipping for many products!

www.ebay.com

 

[Cruzader]

Now this was a bit of a temptation.
Seen them a few times at 240-280$ but this is first one with ebay global shipping active ive seen under 300$ while looking.
(Without global these quickly are 150-200$ UPS rates to Europe instead of 26$ like this one)

 

[Damo]

Now this was a bit of a temptation.
Seen them a few times at 240-280$ but this is first one with ebay global shipping active ive seen under 300$ while looking.

I should be getting mine tomorrow will update, just need to find a good test to run to put these through the works.

 

[Bjorn Smith]

Remember - these should according to specs not show up as a single drive, but as two individual nvme drives of 3.2TB each

 

[ano]

yes what Bjorn said, aren't this basicly 2x 3.2TB drives on a X8 card? gotto keep your focus when setting up ceph/vmware/whatever then

 

[VMman]

Thanks for sharing, these are really high endurance and at this price its almost wrong to use the 1.6tb P3605 units now.

 

[efschu3]

Will they work in PCIe x4 (x2 x1) slots too, or are those system specific cards with PCIe x8 requirement?

 

[ano]

guessing no and requires x8 or.. maybe only get 3.2 capacity

 

[BackupProphet]

They should work fine on pcie 4x 2x or 1x

 

[Sacrilego]

Dang you STH! Got 2...

 

[tjk]

And gone.

 

[BackupProphet]

This NVMe drive has some issues with a newer Linux kernel, for now you need to user an older Linux kernel or recompile your own with a flag set. Only one drive will show, because of a namespace unique id conflict. See 216049 – Unable to boot system, won't mount because of missing partitions because of "nvme nvme1: globally duplicate IDs for nsid 1"

 

[Harmony]

Who bought 20+?

 

[Propaganda]

IIRC these don't support trim with the oracle firmware. Not sure if that is an issue but I figure I would mention it.

 

[drobbins]

These cards are quirky.

With ESXi 8, you will only see half of the available storage (you won't see both drives.)

You may be OK with Linux/Proxmox.

For the right setup, this could be a great deal, and when used in an incompatible setup, you won't be happy. I know because I tried an ESXi 8 deployment using these cards and got half my expected storage.

 

[Sacrilego]

These cards are quirky.

With ESXi 8, you will only see half of the available storage (you won't see both drives.)

You may be OK with Linux/Proxmox.

For the right setup, this could be a great deal, and when used in an incompatible setup, you won't be happy. I know because I tried an ESXi 8 deployment using these cards and got half my expected storage.

Oh crap, really?
Seems like the issue might be related to what BackupProphet mentioned.
Newer Linux kernels will only see one of the drives by default.
I was planning on deploying 4 (ended up buying two more before they ran out.) using TrueNAS scale.
Might just use them with TrueNAS core instead if that's the case.

 

[tjk]

This NVMe drive has some issues with a newer Linux kernel, for now you need to user an older Linux kernel or recompile your own with a flag set. Only one drive will show, because of a namespace unique id conflict. See 216049 – Unable to boot system, won't mount because of missing partitions because of "nvme nvme1: globally duplicate IDs for nsid 1"

Confirmed "broken" with Proxmox 6.2.11-1 kernel.

Confirmed working with Proxmox 5.15.107-1 kernel.

Stats for one of the units:

root@pve:~# nvme smart-log /dev/nvme4n1
Smart Log for NVME device:nvme4n1 namespace-id:ffffffff
critical_warning            : 0
temperature                : 23 C
available_spare                : 99%
available_spare_threshold        : 10%
percentage_used                : 1%
endurance group critical warning summary: 0
data_units_read                : 543,442,323
data_units_written            : 490,622,025
host_read_commands            : 24,899,381,590
host_write_commands            : 29,823,764,501
controller_busy_time            : 8,505
power_cycles                : 35
power_on_hours                : 42,529
unsafe_shutdowns            : 25
media_errors                : 0
num_err_log_entries            : 0
Warning Temperature Time        : 0
Critical Composite Temperature Time    : 0
Thermal Management T1 Trans Count    : 0
Thermal Management T2 Trans Count    : 0
Thermal Management T1 Total Time    : 0
Thermal Management T2 Total Time    : 0


root@pve:~# nvme smart-log /dev/nvme5n1
Smart Log for NVME device:nvme5n1 namespace-id:ffffffff
critical_warning            : 0
temperature                : 24 C
available_spare                : 100%
available_spare_threshold        : 10%
percentage_used                : 1%
endurance group critical warning summary: 0
data_units_read                : 540,967,903
data_units_written            : 317,703,938
host_read_commands            : 24,438,416,976
host_write_commands            : 15,978,860,097
controller_busy_time            : 7,685
power_cycles                : 35
power_on_hours                : 42,529
unsafe_shutdowns            : 25
media_errors                : 0
num_err_log_entries            : 0
Warning Temperature Time        : 0
Critical Composite Temperature Time    : 0
Thermal Management T1 Trans Count    : 0
Thermal Management T2 Trans Count    : 0
Thermal Management T1 Total Time    : 0
Thermal Management T2 Total Time    : 0

 

[Sacrilego]

Can confirm the issue in ESXi 8.0u1. The compatibility matrix shows that it is compatible, but only a single drive shows up.
There also seems to be a newer firmware listed as version QDV1RF35.

Working fine so far out of the box in Windows, TrueNAS Core and Scale.

 

[tjk]

There also seems to be a newer firmware listed as version QDV1RF35.

Were you able to get and apply this fw?

 

[Sacrilego]

Were you able to get and apply this fw?

Unfortunately not.
Requires a contract to download it. The only other reference to that firmware I could find was in the ODA (oracle data appliance) update isos. But as you can guess, also needs a contract.