> Yeah, pretty much. Once you burn through the write endurance, the SSD is toast.
> That's why I keep my swap files, scratch space for compiling MAME, etc. on a hard
> disk and just keep OS and applications on SSD. That way I'm not using up the write
> endurance too quickly.
But with larger SSD coming, people just put everything on the SSD, and that's how they fry so quickly. Whenever anyone I know gets an SSD, I always tell them to 1. never defrag it (I still hear of people doing it) and 2. don't put working files in it. When I explain why they all go like, oh then SSD is crap. It's not crap, it's something that has a different usage than the mechanical HDs. I've moved/hardlinked all the temporal/working folders off the SSD, and basically I only have apps and sys in it, and after 3 years it's still healthy, while I got an external HD bought at the same time converted into a brick (haven't got any luck with it yet).
I think the worst they did is make SSDs work exactly like mechanical HDs from the system pov, that makes people think they are the same and misuse them.
Also I don't understand why once the SSD is fried, it doesn't default to read-only. It should be the case for *all* SSDs imho. Not like making it possible would double the price on them.
Wound up, can't sleep, can't do anything right, little honey / Oh, since I set my eyes on you. / I tell you the truth.
I can't get it right / Get it right / Since I met you...
|
Index 
Flat 
Re: Hard drive crashes worse now on SSD?
Reply
