3 ms·
Anyone that had to deal with the aftermath of a failed HDD Raid set certainly was glad SpinRite was around. After the rise of shingled writes and SSD, the soft
by Joel_Mckay 2y ago
Anyone that had to deal with the aftermath of a failed HDD Raid set certainly was glad SpinRite was around.
After the rise of shingled writes and SSD, the software was not as applicable to modern systems.
Notably, most good SSD manufacturers provide automated hidden maintenance tools built into the firmware. Thus, some may be surprised to learn leaving an SSD with no power for more than a year is a really bad practice.
Flushing the SSD cache after a system update is usually good practice once a week in off peak service hours. Most Linux distros will similarly defer the trim operations to a scheduled weekly cleaning cycle as well (lowers drive wear).
If you still run old spinning HDD in equipment, than SpinRite can still save you a $2k recovery bill.
Cheers =)
- Dylan16807 2y ago> If you still run old spinning HDD in equipment, than SpinRite can still save you a $2k recovery bill. If you're running a hard drive that old, you should go spend less than fifty dollars on a basic TLC SSD and an adapter to turn it from SATA to IDE.
- Joel_Mckay 2y agoI've done repairs that way sometimes, but older OS can wear SSD out a lot faster than normal. It is a less than ideal solution, but does speed up old platforms a lot (thus, usually we provided the recovered disk image file backup on another drive.) Most modern HDD include proprietary sector error-mapping in flash on the controller chip. Thus, unless you have the vendor software you are not going to access anything helpful, or get away with a donor drive controller pcb. Sometimes, people learn the hard way about backing up regularly, and testing the recovery set periodically. The rise in remote workstations has had its downsides for sure. Cheers =3