Relocating My Documents to another drive?

[the_randomizer]

https://www.samsung.com/semiconductor/minisite/ssd/product/consumer/850evo/

The drive warranty is "5 Years or 75 TBW"

I use Samsung Magician to show Terrabytes Written. My 120GB EVO 850 got to 35TB in 2.5 years. My 2TB EVO 870 Pro is at 2.7TB after 7 months (and that has a 600 TBW warranty).

I was pretty reckless with the 120GB, but also having to keep uninstalling/reinstalling pushed it up. A couple of windows and visual studio version updates will soon add up.

Sooo, uh, I mean, I don't exactly use it for more than Windows and those few document/files. I don't have any games on there, and have had it for well over a year *Shrug* I don't have money for a new drive right now, nor any way to clone it to a new drive. I think I should be fine right?

 

[smf]

Sooo, uh, I mean, I don't exactly use it for more than Windows and those few document/files. I don't have any games on there, and have had it for well over a year *Shrug* I don't have money for a new drive right now, nor any way to clone it to a new drive. I think I should be fine right?

What does samsung magician say?

One thing to look out for, if you still have a swap file and not much ram then it could be hammering the ssd.

 

[the_randomizer]

What does samsung magician say?

One thing to look out for, if you still have a swap file and not much ram then it could be hammering the ssd.

Currently have 16 GB DDR3 SDRAM. How do I know if I have a swapfile for the SSD? I was told not to edit the automatic file swap size and let Windows take care.

Edit: Currently set to 2 GB for all drives (combined), I mean, it wasn't an issue before, it's not an issue now. You're just giving me more things to worry about.
If it ain't broke, don't fix it, I never run out of the 16 GB of RAM I have, so... yeah. I'm not changing it.

 

[smf]

If it ain't broke, don't fix it, I never run out of the 16 GB of RAM I have, so... yeah. I'm not changing it.

Once it's broke then it's too late to fix it. What does Samsung Magician say about the total bytes written, that will tell you how quickly you're writing to the disk and whether it's going to be a problem.

As long as there is nothing stupid going on then you're fine, but without knowing what the total bytes written is then you can't tell if there is something stupid going on.

 

[the_randomizer]

Once it's broke then it's too late to fix it. What does Samsung Magician say about the total bytes written, that will tell you how quickly you're writing to the disk and whether it's going to be a problem.

As long as there is nothing stupid going on then you're fine, but without knowing what the total bytes written is then you can't tell if there is something stupid going on.

10.4 TB, Drive Condition good (blue font), had for about one year. No idea how often or how much it actually writes, no way to find out. TRIM status Enabled, AHCI mode Enabled, using old firmware
version apparently. So yeah, no idea.

Edit: SMART tests all have OK

Edit 2: Considering it's 10.4 TB after one year or so, sounds to me that it will last a while longer

 

[Originality]

To those saying SSDs last longer than HDDs, that’s not necessarily true. My drawer at work has 3 dead Origin and 1 dead ScanDisk SSDs (and 3 dead HDDs too but that’s normal) that I’m being asked to try recovering data at some point.

A graceful death for a SSD is to hit the write limit where it becomes “read only”. However all of the SSDs that died on me died from the controller failing, which makes the drive unable to mount in Windows. Cheap SSDs use cheap controller and will likely be the point of failure in 2-4 years (based on experience at work). Older Sandforce controllers (ala OCZ Vertex 2 and 3 and others) also suffered from a controller flaw, although firmware updates patches that up to make it last a while longer (provided you use SecurErase any time the controller chokes up on IO).

 

[PityOnU]

Also chiming in here with some insight:

I'm not sure how Windows redirects your storage to other drives, but it may (for compatibility reasons) just copy your data to the new location, and create a symbolic link to the new location in the same place as the original path.

That would create a situation where to you (the user) and legacy programs, could still access your documents folder using the original filepath, but it would exist in a different location/drive. You would also be able to access the data at the new location.

It would appear (from a high level) that you are maintaining two copies of the data, but it's actually just stored in a single location, but accessible by multiple names.

I had manually done this on a few computers before they implemented this functionality.