![]() Using terminal and going to that directory also shows only two two other folders: 'recovery' and 'system volume information'. So that looked good but in the gui file system thing only the first two partitions can be seen. So I ran ntfsfix -d with no luck on sdc but success on sdc1 which I suppose is what I should have done in the first place. The question now is how to 'cure' the disks of whatever ails them. ![]() I was able to mount the data partition: sdc4 read only and have rescued some 30,000 files I wanted. Which indicates to me the problem is software, not hardware. First thing: the clone (sdc) is reported as being exactly the same as the original (sdb). I contribute to a lot of open source projects on GitHub and have several of my own on GitLab, and I go by the pseudonym hamishmb in most places on the internet. I did a Superclone clone and worked on the clone a bit. I’m Hamish McIntyre-Bhatty, a self-employed software developer from the UK. ![]() But if you use HDDSuperClone and need help, you could provide the progress log file and I could analyze it, giving an indication of the issue of the drive, and further ideas, and if the paid pro features would be helpful or not. Also, if you choose to use ddrescue, I will not be able to provide assistance with that. But that would most likely require some paid software, although very affordable (should only be $25 total). Considering that the data you wish to recover does not seem very large (a few GB maybe?), it could be possible to target that data. When you get a drive to clone it to, and the cloning process is very slow and reports it will take many weeks or months or longer to complete, then you will need to rethink things. If the drive is suffering from the slow issue, it will take forever to clone. * I have stated that if it is only suffering from the slow responding issue, then there are ways to help with the read speed without being able to fix the slow issue, and to target the needed data. * The OP has indicated that the data is not worth professional data recovery. * If it is suffering from the common “slow responding issue”, then the issue could likely only be fixed by professional tools and an unlocked board (professional recovery). This Quick Start Guide discusses things you need to know to use SystemRescue. * This drive may be suffering from a common WD firmware issue, or possibly a bad or weak head. * This drive is a newer WD Blue drive, which likely has encrypted SA and a locked board. First, I would like to add some info from the thread in the other forum.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |