![]() I ran it at defaults (Level 2 scan), and let it run over night. So I fired up Rufus Portable to make myself a bootable DOS USB key, plunked the tiny spinrite.exe right on there, and booted it up on my ThinkPad W520 with the suspect SSD. Turns out the Gibson Research license recovery process was quick and easy. I also didn't seem to have my license key recorded. Despite hearing his insistence it can help with SSDs, I was very skeptical. Yeah, I listen to Steve Gibson on Security Now, and used to use Spinrite on failing spinning drives pretty regularly. Given no backup program that I had tried would successfully complete a backup, I felt I didn't have much to lose by taking good old Spinrite out for a spin. Similar to known performance issues that I had thought I fixed last fall. Over time, I noticed my write speeds were also degrading. In addition to some evidence of corruption that chkdsk wouldn't fix, another concern began to develop. A full backup, even if some of that data backed up was bad. Windows Server 2012 R2 Essentials complaining about one of your drives? How to queue up multiple chkdsk operations for the next reboot.ĭuring these of on-again off-again troubleshooting sessions, I also figured out that sector-by-sector backup from AOMEI Backupper worked.Despite heroic effort, in the end, the finger of blame was pointing at a bad drive. I worked with Veeam's excellent free VEB support for weeks, running various chkdsk flags diagnostic software, to look for and possibly fix the reason nothing likes to back up my SSD. Note that mSATA form factor owners like me weren't able to use that firmware upgrade anyway. If it's just my particular drive that's failing, then much or all of the above story is a red herring.Įven though felow Samsung 840 EVO owners have experienced well documented dormant-file-read-speed issues with this drive, that firmware EXT0DB6Q fixes, that wasn't my primary concern. My extended family has had great success with several Samsung SSDs these past 3 years. Also important to note that it's quite possible my particular Samsung 840 EVO 1TB mSATA drive is simply defective. Over time, I realized the problem wasn't getting worse, and it would seem that >99% of my data is good. So fixing this wasn't actually my highest priority, hoping to merely buy some time until Windows 10 GA'd. Planned to do a fresh install of Windows 10 soon anyway, and my crucial data (Documents) were on a spinning D: drive. ![]() I was traveling a bit at the time, so Weeks went by before the realty sunk in that I had some real trouble here, and my last good backup was getting stale real fast. So did AOMIE Backupper in normal backup mode. So I went back to using Microsoft Windows Server 2012 R2 Essentials, it failed too. More importantly, I then noticed that my daily backups had begun to fail, including Veeam Endpoint Backup. Both the troublesome application, and the VM, were running during those BSODs. Then, my VMware Workstation's large Windows 7 VM that I use on a daily basis complained it couldn't start any Microsoft Office 2013 applications. First, I couldn't get an applications to work right, even though it was working just fine before. I will likely never really know the root cause of my months of troubles that started that day. But what happened in the following weeks is where things got interesting.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |