You might yet be the White Knight.Vize wrote:Apologies for cutting in your conversation, but your description brought some old memories back to life.
I take it that the disk with problems is the 2nd disk: dev/sdb WDC WD10EADS.
This makes the disk part of the (unfortunately infamous) Western Digital WD Green Series (manufactured ~2009)
Is this disk part of an external backup drive like WD MyBook Essential connected via USB ?
If so, your problem is in all likelihood a damaged USB connector board.
Small fragile board but absolute essential to read data from disk and -that's why infamous- for 'security' reasons was paired with the disk, making it almost impossible to replace or bypass.
Not all hope would be lost though...just yet
It is the second Disk.
It was a WD Green series from 2009.
It was also an external back-up drive. From memory it was created just before the whole "mybook" thing came out of WD, and as such isn't classed as a "MyBook", yet still looks the same when in its case.
I keep saying 'was' by the way because I pulled it out and SATA wired it direct to the motherboard, hoping to bypass the original issue. I do still have the external components though, including the USB board.
With what you say, that would explain the random software behaviour and why no programs can do anything with the disk, including windows, because I by-passed the USB board by SATA wiring it.
It would also explain why the Disk seemingly had software issues when the problem was seemingly caused by impacts to the hardware during flight (assumption based on time between working and not).
Ignoring the frankly terrible design choices by WD, you state not all hope is lost? why.
Do you have a potential solution? Can you help me?