SanDisk CloudSpeed Eco 1.92TB 2.5" SATA $120

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
Fritz

Fritz

Well-Known Member
Apr 6, 2015
3,392
1,394
113
70
My second one just arrived and it too is 100% health. POH are a little over 2k. Drive doesn't report reads or writes, at least not to HD Sentinel.
 
T_Minus

T_Minus

Build. Break. Fix. Repeat
Feb 15, 2015
7,652
2,066
113
Fritz said:
My second one just arrived and it too is 100% health. POH are a little over 2k. Drive doesn't report reads or writes, at least not to HD Sentinel.
Click to expand...
Nice! Which sellerthis time?
 
is39

is39

Member
Oct 5, 2022
42
23
8
SF Bay Area
My experience with a pair of those 1.92TB Sandisk Cloudspeeds SDLF1CRR-019T-1HA1 from semsotai2017, specifically
www.ebay.com

SANDISK CLOUDSPEED ECO SA620 1.92TB SATA III SSD SDLF1CRR-019T-1HA1 | eBay

Find many great new & used options and get the best deals for SANDISK CLOUDSPEED ECO SA620 1.92TB SATA III SSD SDLF1CRR-019T-1HA1 at the best online prices at eBay! Free shipping for many products!
www.ebay.com

- drive health in 80-90% range, ~58K hours
- sustained sequential read speed < 80MB/sec (1MB blocks) on wide variety of hardware; starts a bit faster (100-120MB/sec), then slows down
- sequential write speed as expected (300-400MB/sec range on 1MB blocks)

I could try upgrading firmware, but other drives with same firmware revs do not experience this anomaly; plus there was no obvious bugs in release notes which would cause this behavior; so i chose to return, which was processed promptly.
 
  • Like
Reactions: JJ27
T_Minus

T_Minus

Build. Break. Fix. Repeat
Feb 15, 2015
7,652
2,066
113
is39 said:
My experience with a pair of those 1.92TB Sandisk Cloudspeeds SDLF1CRR-019T-1HA1 from semsotai2017, specifically
www.ebay.com

SANDISK CLOUDSPEED ECO SA620 1.92TB SATA III SSD SDLF1CRR-019T-1HA1 | eBay

Find many great new & used options and get the best deals for SANDISK CLOUDSPEED ECO SA620 1.92TB SATA III SSD SDLF1CRR-019T-1HA1 at the best online prices at eBay! Free shipping for many products!
www.ebay.com

- drive health in 80-90% range, ~58K hours
- sustained sequential read speed < 80MB/sec (1MB blocks) on wide variety of hardware; starts a bit faster (100-120MB/sec), then slows down
- sequential write speed as expected (300-400MB/sec range on 1MB blocks)

I could try upgrading firmware, but other drives with same firmware revs do not experience this anomaly; plus there was no obvious bugs in release notes which would cause this behavior; so i chose to return, which was processed promptly.
Click to expand...
thank you for sharing!
 
F

Flintstone

Member
Jun 11, 2016
127
20
18
47
I bought two last week @ $47 ea from part-met-servers (now sold out) - will test them when they arrive. I later kind of regret not buying some Toshiba HK4R instead seeing that some have problems with xfer speeds.
 
fohdeesha

fohdeesha

Kaini Industries
Nov 20, 2016
2,748
3,109
113
33
fohdeesha.com
Flintstone said:
I bought two last week @ $47 ea from part-met-servers (now sold out) - will test them when they arrive. I later kind of regret not buying some Toshiba HK4R instead seeing that some have problems with xfer speeds.
Click to expand...
I did the same last week, arrived fine, updated the firmware, tests well, had like 19k power on hours if i remember right. 90% health (as reported by sandisks own tool)
 
is39

is39

Member
Oct 5, 2022
42
23
8
SF Bay Area
What about sequential IO, i.e.
dd if=/dev/hdX of=/dev/null bs=1M count=5000
dd if=/dev/zero of=/dev/hdX bs=1M count=5000

It's a cheezy test, but if the drive cannot perform within 50% deviation of expected speed, further tests usually are a waste of time.
Apparently you should not always trust SMART :-( plus some drives can develop slowdown *on read* way before than health runs out.
 
BackupProphet

BackupProphet

Well-Known Member
Jul 2, 2014
1,097
661
113
Stavanger, Norway
olavgg.com
I just tested mine from Semtosai, 55k power on hours. 90% life left. Read around 300-400MB/s and writes around 300-400MB/s for sequential read/write with 1MB block size. I have 30 units, and they all behaved similar.

I created a 100GB file with random data placed on a NVMe drive, so any compression tricks would not work.
 
  • Like
Reactions: T_Minus
is39

is39

Member
Oct 5, 2022
42
23
8
SF Bay Area
Yep, that's the numbers i would expect. I guess i got a pair of lemons :-(
I may try again, the price is too good ;-)

p.s. i know for sure it's not my test environment, i was so surprised i've tested on 3 different platforms; no other SSD i've shown such behavior recently, though in the past i've Samsung's getting slow way before their age; reportedly that was firmware bug, and they did not fix it across the board; but it's not the firmware either.

Here is "smartctl -a" output from one of those drives; nothing really jumped at me (ABRT can be ok after SANITIZE).

Code: 
smartctl 6.5 (build date Mar  2 2021) [x86_64-linux-4.4.59+] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Sandisk SATA Cloudspeed Max and GEN2 ESS SSDs
Device Model:     SDLF1CRR-019T-1HA1
Serial Number:    202B5902
LU WWN Device Id: 5 001173 1008691fc
Firmware Version: ZR06RPA1
User Capacity:    1,920,383,410,176 bytes [1.92 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    Solid State Device
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4c
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Wed Jul 19 19:13:34 2023 PDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                (20160) seconds.
Offline data collection
capabilities:                    (0x5d) SMART execute Offline immediate.
                                        No Auto Offline data collection support.
                                        Abort Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   1) minutes.
Extended self-test routine
recommended polling time:        (   1) minutes.
SCT capabilities:              (0x003d) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.
                                        
                                        SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME                                                   FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct                                            0x0033   100   100   010    Pre-fail  Always       -       0
  9 Power_On_Hours                                                   0x0032   033   033   000    Old_age   Always       -       58856 (0 252 0)
 13 Lifetime_UECC_Ct                                                 0x0012   100   100   001    Old_age   Always       -       0
 32 Lifetime_Write_AmpFctr                                           0x0002   100   100   000    Old_age   Always       -       0
 33 Write_AmpFctr                                                    0x0002   100   100   000    Old_age   Always       -       100
170 Reserve_Erase_BlkCt                                              0x0032   100   100   000    Old_age   Always       -       18160
171 Program_Fail_Ct                                                  0x0032   100   100   000    Old_age   Always       -       0
172 Erase_Fail_Ct                                                    0x0032   100   100   000    Old_age   Always       -       0
175 Lifetime_Die_Failure_Ct                                          0x0032   100   100   000    Old_age   Always       -       0
178 SSD_LifeLeft(0.01%)                                              0x0012   100   100   000    Old_age   Always       -       8283
183 LT_Link_Rate_DwnGrd_Ct                                           0x0032   100   100   000    Old_age   Always       -       0
191 Clean_Shutdown_Ct                                                0x0032   100   100   000    Old_age   Always       -       46
192 Unclean_Shutdown_Ct                                              0x0032   100   100   000    Old_age   Always       -       0
194 Temperature_Celsius                                              0x0022   065   051   030    Old_age   Always       -       35 (Min/Max 13/49)
196 Lifetime_Retried_Blk_Ct                                          0x001b   100   100   010    Pre-fail  Always       -       0
211 Read_Disturb_ReallocEvt                                          0x0032   100   100   000    Old_age   Always       -       0
233 Lifetime_Nand_Writes                                             0x0032   100   100   000    Old_age   Always       -       2644032
235 Capacitor_Health                                                 0x0032   100   100   000    Old_age   Always       -       0
241 Total_LBAs_Written                                               0x0032   100   100   000    Old_age   Always       -       1269504
242 Total_LBAs_Read                                                  0x0032   100   100   000    Old_age   Always       -       1833600
244 Therm_Throt_Activation                                           0x0032   100   100   000    Old_age   Always       -       0
245 Drive_Life_Remaining%                                            0x0012   083   083   002    Old_age   Always       -       83
253 SPI_Test_Remaining                                               0x0012   100   100   001    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 4
        CR = Command Register [HEX]
        FR = Features Register [HEX]
        SC = Sector Count Register [HEX]
        SN = Sector Number Register [HEX]
        CL = Cylinder Low Register [HEX]
        CH = Cylinder High Register [HEX]
        DH = Device/Head Register [HEX]
        DC = Device Command Register [HEX]
        ER = Error register [HEX]
        ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 4 occurred at disk power-on lifetime: 58847 hours (2451 days + 23 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 51 00 00 4f c2 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  b0 d0 00 00 4f c2 00 00      00:00:00.003  SMART READ DATA
  b4 00 00 00 00 00 00 00      00:00:00.003  SANITIZE DEVICE
  b4 00 00 00 00 00 00 00      00:00:00.003  SANITIZE DEVICE
  b4 00 00 00 00 00 00 00      00:00:00.003  SANITIZE DEVICE
  b4 00 00 00 00 00 00 00      00:00:00.003  SANITIZE DEVICE

Error 3 occurred at disk power-on lifetime: 58847 hours (2451 days + 23 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 51 00 00 4f c2 00  Error: ABRT
 
   Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  b0 d0 00 00 4f c2 00 00      00:00:00.003  SMART READ DATA
  b4 00 00 00 00 00 00 00      00:00:00.003  SANITIZE DEVICE
  b4 00 00 00 00 00 00 00      00:00:00.003  SANITIZE DEVICE
  b4 00 00 00 00 00 00 00      00:00:00.003  SANITIZE DEVICE
  b4 00 00 00 00 00 00 00      00:00:00.003  SANITIZE DEVICE

Error 2 occurred at disk power-on lifetime: 58847 hours (2451 days + 23 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 51 00 00 4f c2 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  b0 d0 00 00 4f c2 00 00      00:00:00.003  SMART READ DATA
  b4 00 00 00 00 00 00 00      00:00:00.003  SANITIZE DEVICE
  b4 00 00 00 00 00 00 00      00:00:00.003  SANITIZE DEVICE
  b4 00 00 00 00 00 00 00      00:00:00.003  SANITIZE DEVICE
  b4 00 00 00 00 00 00 00      00:00:00.003  SANITIZE DEVICE

Error 1 occurred at disk power-on lifetime: 58494 hours (2437 days + 6 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 51 00 00 4f c2 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  b0 d0 00 00 4f c2 00 00      00:00:00.003  SMART READ DATA
  b4 00 00 00 00 00 00 00      00:00:00.003  SANITIZE DEVICE
  b4 00 00 00 00 00 00 00      00:00:00.003  SANITIZE DEVICE
  b4 00 00 00 00 00 00 00      00:00:00.003  SANITIZE DEVICE
  b4 00 00 00 00 00 00 00      00:00:00.003  SANITIZE DEVICE

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
 
BackupProphet

BackupProphet

Well-Known Member
Jul 2, 2014
1,097
661
113
Stavanger, Norway
olavgg.com
Remember to test these drives on a filesystem on not directly. It seems like reading/writing directly is very slow. Also remember to bypass kernel cache with directio
Example
Code: 
#Write
dd if=/f320pool/testfile of=/mnt/testdrive/testfile bs=1M status=progress oflag=direct
#Read
dd if=/mnt/testdrive/testfile of=/dev/null bs=1M status=progress iflag=direct
 
  • Like
Reactions: T_Minus
is39

is39

Member
Oct 5, 2022
42
23
8
SF Bay Area
I test on raw devices, right after drive attachment, so no caching could be involved; some of the platforms i've used do not have "direct" (older FreeBSD boxes).

With regard to filesystem versus raw device - you open a whole new can of worms with a filesystem (xfs? ext4? btrfs? ufs?they all behave differently).
If the drive cannot perform sequential reads as raw device, filesystem can mask that, but not improve.
It's possible that the drive needs concurrency to utilize full speed, but that would prevent me from, say, duplicating those drives quickly using dd, or using those as raw database volumes.
I've a whole zoo of enterprise SSDs (Intel, Samsung, Toshiba and HGST) and they all can achieve full expected speed on raw device.

Do you also see poor performance on raw device?
 
A

alaricljs

Active Member
Jun 16, 2023
199
74
28
  • Like
Reactions: T_Minus
is39

is39

Member
Oct 5, 2022
42
23
8
SF Bay Area
Actually Samsung PM863 wins on TBW (2800 vs 2100) and on IOPS (99K/18K r/w vs 76K/16K), at least per spec; warranty is 3 years vs 5; both have PLP/capacitors.
The main issue with those bargain bin SSDs is if drive is hosed; too many hours or too many blocks written; most sellers do not specify health or other details in the ad; you can always mail it back, but time is wasted.

I had very good luck with Intel DC series, even with considerable (20-30%) health used; but unfortunately those are rare at those ($25/TB) prices; i suspect those would continue to come down; comparable NVMe/U.2 SSDs in 1.92-3.84TB range are actually at least 25% cheaper than SATA now (on secondary market); i guess not many people have multi-slot U.2 chassis.
 
T

tasort

New Member
Dec 6, 2022
9
6
3
is39 said:
comparable NVMe/U.2 SSDs in 1.92-3.84TB range are actually at least 25% cheaper than SATA now
Click to expand...
Any model numbers or search terms you can share? I'm looking for a pair of drives and m.2/u.2 drives all seem quite a bit pricier than sata.
 
is39

is39

Member
Oct 5, 2022
42
23
8
SF Bay Area
eBay - "nvme 3.84tb" "nvme 7.68tb" (or try u.2 instead of nvme); buy it now, lowest price+shipping, skip ranged offers with varying drive sizes;
usual price range for 3.84tb is ~150, 7.68tb ~300; SATA are extra 25%; check health info if available or be ready to return;
still trying to come up with cheap-ish way to attach those u.2 drives; so far that price differential is not enough to cover extra spend.
 
  • Like
Reactions: Auggie and nexox
You must log in or register to reply here.
Top Bottom