![]() As for using a manufacturers utility, that's good advice for noobs, but I don't buy that "clone to our SSD" utility first because drive manufacturers usually just bundle a light version from a vendor that sells fully licensed products and usually, the fully licensed products have more features and abilities than the lite versions, so my preference is to use the real thing, not the stripped down versions provided through hardware manufacturers. This drive didn't come with any additional tools, don't know why, it just didn't and it is not eligible for any either. and the same list repeated again at Stage 2: Examining file name linkage. I get 32 entries at Stage 1:Examining basic file system structure. ![]() The machine works just peachy and the Windows logs show nothing out of the ordinary. However, the issue I'm seeing moving forward is that the log also showed under the stage 1 phase a swag of entries about a USA Check value being incorrect with no indication that they were rectified, and the same list is persistently there every time I manually run a chkdsk /r On reboot, the Windows log file clearly showed that no bad blocks existed on the partition post scan. On researching ddrescue, I found it has a habit of copying everything, warts and all, including bad block records to the new drive and last time I did this, I only had to run chkdsk C: /b to have the bad blocks record cleared and the disk space used by C: fully scanned to recheck the surface for bad blocks. Windows booted fine on the new hard disk and so far, nothing stands out as missing or having suffered from any losses. I had a hard disk start failing on a Windows 10 (1903) machine so I cloned it before it died completely by using ddrescue from a Live Linux rescue ISO to a brand new hard disk and I got a 99.95% recovery after 17 hours of operation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |