Recovery from a Windows7 bootable SSD. - Page 1
Forum section: electronics / general

author: luiHS
author_rank: Frequent Contributor
timestamp: July 12, 2024, 09:13:04 pm
content: Hello.I'm having problems with my boot disk, a 256GB SSD running Windows7. The main problem is that the Windows backup has not been working for me for two years. I recently did a CHKDSK /F /R and it was fixed, I recovered 16GB lost and the backup worked again. But as soon as the computer is turned off and on again, the problem appears, 16GB of disk is lost and I can no longer make the backup.In addition to CHKDSK, I have done an sfc /scannow that has not fixed anything, although the process says it detects errors and corrects them.I have also done these cleanup procedures, which recovered my disk space but did not correct the problem:Deleting Temp filesDeleting %Temp% filesDeleting prefetch filesEvent viewer logs deletedDeleting files with Disk Cleanup.I don't consider reinstalling the system because I have many programs and I would have to reinstall them all again, for that I prefer to run a CHKDSK at night and make the backup the next day.Is there anything else I could do to repair the disk without having to reinstall the system again?Best Regards

author: Messtechniker
author_rank: Frequent Contributor
timestamp: July 12, 2024, 10:01:03 pm
content: First do a sector by sector clone. And if possible work with that.

author: thephil
author_rank: Regular Contributor
timestamp: July 13, 2024, 06:00:55 pm
content: I'm keeping my fingers crossed that you get your disk back up and running.BUT: even if you are able to apparently recover fully. Do not continue to work with that disk unless the data on it isn't important to you.At the very least, reinstall the system after backing up your data. Better still thoroughly check the disk or ditch it for a new one right away.I know – re-installation is a pain in the neck, but if you like your data it's what you want to do. Especially, as the problem seems to be recurring...I also endorse the previous recommendation to not try and fix the diskin situbut create an image that you then try to fix. Do not touch the original disk more than absolutely necessary. Automated repair programs (just like humans) can easily cause additional damage to the disk without it being obvious, at first. You may find out much later that crucial files have been corrupted.Good luck! Phil

author: bson
author_rank: Unknown
timestamp: July 13, 2024, 09:08:04 pm
content: Can't help with the drive, but I can highly recommend not using Windows Backup. Instead use the Macrium Reflect free version to take regular system snapshots. If the system fails to boot you can boot from the Reflect volume and restore.

author: Haenk
author_rank: Super Contributor
timestamp: July 14, 2024, 09:06:20 am
content: This sounds like a damaged drive (probably worn out), "fixing" it will likely - at best - move data to spare blocks, but if the stated 16GB are true, all hope is lost, that drive is toast (as there are not enough spare blocks to cover 16GB).Macrium is a good choice to backup your data.With the stated symptoms you *will* have to reinstall anyway, better go with something "supported", Win7 has not been supported for years and has more exploitable bugs than you care to count.Edit: You might want to use another computer with a program like Hard Disk Sentinel running and attach the drive as a secondary drive (don't boot from it). This program can read a lot of parameters, like SMART status, revovered blocks and so on. It can even do a block-wise read check on the drive - I don't recommend that with a drive in an unknown state though.

author: luiHS
author_rank: Frequent Contributor
timestamp: July 17, 2024, 10:55:49 am
content: I decided to do a test with the CHKDSK and the /B parameter that I had not used until now, and now it is worse, the disk no longer recovers the lost 16GB and the Windows backup no longer works even by doing the CHKDSK / F /R. Before, at least when I did CHKDSK /F /R the Windows backup worked again until the computer was turned off and on and it was damaged again, so at least I could make the backup from time to time.I also booted with the Windows installation USB for the disk repair utilities, but they didn't solve anything either. I have tried some other free tools but to no avail.I downloaded the Samsung Magician utility from Samsung for their SSD drives. According to this utility the disk is fine, so I assume that Windows has been corrupted and is no longer recoverable. In this utility there is the "Data Migration" option to duplicate disks, I will try it with another 1TB SSD that I bought a long time ago, to see if duplicating the disk will repair it.If I don't get anything, then I will install a Windows 10 on the new 1TB SSD disk, I will also take the opportunity to install an Ubuntu on the same disk with Dual boot.

author: amyk
author_rank: Super Contributor
timestamp: July 22, 2024, 01:48:18 pm
content: 840 EVO? I recommend replacing ASAP - this interesting article was linked from another thread here, it seems to have bad TLC NAND:https://forum.acelab.eu.com/viewtopic.php?t=8735Also, does that also show anST3000DM001? That's another model of drive I would beverycautious of.

author: luiHS
author_rank: Frequent Contributor
timestamp: July 23, 2024, 03:24:15 pm
content: Today I tried to install Windows 10 on another SSD drive, a 1TB Samsung 870 that I bought a long time ago. This is to start changing from W7 to W10, currently working with both, and also installing Ubuntu on the same W10 disk.My surprise is that installing W10 on another disk has modified the boot of the disk where I had W7 and damaged it so that it no longer started. I got a W10 W7 dual boot screen to choose from, but the boot for W7 doesn't work, it gives errors.So I had no choice but to resort to the last Windows 7 backup that I was able to make on July 13, fortunately it worked and I recovered the disk with W7, and the good thing is that now the backup works again even without doing the chckdsk /f /r. It seems that when recovering from a disk image, it is loaded onto useful sectors of the disk, avoiding damaged ones, and this allows the backup to work again.What has bothered me a lot is that the installation of Windows 10 on another disk has modified the boot of Windows 7, when both are on different disks, and the worst thing is that this dual boot does not work for W7.Now I will begin to gradually install, in Windows 10, all the programs that I am using in Windows 7 and when everything works, I will definitely start working in Windows 10. I also want to try installing Ubuntu for a dual boot W10 - Linux.

author: Messtechniker
author_rank: Frequent Contributor
timestamp: July 24, 2024, 05:53:14 am
content: Forget this dual boot stuff. Its much too wonky.

author: coromonadalix
author_rank: Super Contributor
timestamp: July 29, 2024, 05:04:07 pm
content: as for recovery or errors it's hard to tell without seeing them, mbr / fat related / corrupted boot files etc ... or the drive has began to create track or data loss(es) ? degradation ?i simply would use some power switch or hot swap caddys with on / off switchs to switch between 7 or 10 or else, i never use more than one bootable drive, even if you switch between different os... to be sure an os dont see the other(s)i had the same problems, yes you do have multiboot softwares but, you mess things up ... change MBR etc ... and recovering them is a messorthe best would be a main os aka 10 and you virtualize the others, AND you declare a folder or a drive as a shared one between them, to put anything you may need for them ...my 2 cents

author: Messtechniker
author_rank: Frequent Contributor
timestamp: July 30, 2024, 05:42:02 am
content: Quote from: coromonadalix on July 29, 2024, 05:04:07 pmExactly