- Joined
- Dec 27, 2014
- Messages
- 6,110
- Reaction score
- 7,296
- Points
- 373
- Location
- Germany
- Printer Model
- L805, WF2010, ET8550, T3100X
SSD's/flash memory vary by the number of write cycles they can reliably do, and this depends directly on the chip/memory cell structure. Serious companies specify a number of Terabytes written as a kind of guaranteed minimum amongst other parameters like the number of IOPS for speed. The Samsung SSD Magician software gives you access to some of these data - mainly the Terabytes written as a wear indicator. I have not seen such software from many other SSD manufacturers. There are 3rd party utilities to read out the SMART data from a drive but some companies hide some of such usage data as proprietary data. I have not seen any dropouts yet with several Samsung SSD's I'm using since several years - quite heavily (EVO type units). I have experienced several damages of SD card flash memories which were not even heavily used.
Just a comment to RAID protection - I'm reading above that you were using a RAID configuration. RAID is pretty good for protection against hardware failures of an individual disk, but not in all cases. I had a case that a defect IDE drive was blocking the other RAID drive such that both were unusable after a failure, and the drive not actually defect got the file table completely screwed up by the other drive, and it took quite some recovery time to get the system starting again. And the other case was a malfunctioning software installation which did some damage to Win XP which could not be recovered. The software supplier admitted indirectly that they had a problem with an unrecognized virus on their installation disks - and that got installed on both RAID drives.
That's cases a RAID system cannot help . You may consider some other/additional backup method besides RAID to cover such situations as well. Memory prices are that low that additional chips/cards/drives should not be a limiting factor anymore.
Just a comment to RAID protection - I'm reading above that you were using a RAID configuration. RAID is pretty good for protection against hardware failures of an individual disk, but not in all cases. I had a case that a defect IDE drive was blocking the other RAID drive such that both were unusable after a failure, and the drive not actually defect got the file table completely screwed up by the other drive, and it took quite some recovery time to get the system starting again. And the other case was a malfunctioning software installation which did some damage to Win XP which could not be recovered. The software supplier admitted indirectly that they had a problem with an unrecognized virus on their installation disks - and that got installed on both RAID drives.
That's cases a RAID system cannot help . You may consider some other/additional backup method besides RAID to cover such situations as well. Memory prices are that low that additional chips/cards/drives should not be a limiting factor anymore.