Not really 'broke a drive' . But kind of.
I have a Western Digital 2T that was a Win10 system disk and suddenly couldn't be read, couldn't even be seen by Windows.
Put it in my LinuxMint box and found it could be seen but could not be mounted fully - only as read only.
But mounted read only was good enough for SuperClone to clone it onto a fresh new Hard Drive.
And that's where it gets interesting because now the new drive cannot be mounted except read only.
It looks like it wasn't a hardware fault, isn't a hardware fault, it is something to do with the software, the data that SuperClone wrote on the disk.
So maybe if I simply use SuperClone again and clone a working drive onto it - the LinuxMint drive for instance, that will fix it, both of them, the original WD 'broken' drive and the clone - a Seagate 2T? What would you think?
Or perhaps someone with a deeper knowledge than mine can see a quicker, easier way to fix that problem?
I have a Western Digital 2T that was a Win10 system disk and suddenly couldn't be read, couldn't even be seen by Windows.
Put it in my LinuxMint box and found it could be seen but could not be mounted fully - only as read only.
But mounted read only was good enough for SuperClone to clone it onto a fresh new Hard Drive.
And that's where it gets interesting because now the new drive cannot be mounted except read only.
It looks like it wasn't a hardware fault, isn't a hardware fault, it is something to do with the software, the data that SuperClone wrote on the disk.
So maybe if I simply use SuperClone again and clone a working drive onto it - the LinuxMint drive for instance, that will fix it, both of them, the original WD 'broken' drive and the clone - a Seagate 2T? What would you think?
Or perhaps someone with a deeper knowledge than mine can see a quicker, easier way to fix that problem?