Posted 18 December 2016 - 10:06 AM
Shadow_647 is right in a way. You need, I think, to use the 'dd' command (also known as 'disk destroyer', if not used carefully!) in a Linux terminal in order to completely get rid of the 'write-protection'. There are also several other low-level Linux utilities (mostly command-line, therefore operated via the Linux 'terminal'), which can help with this; it's not as uncommon as you might imagine.
What most often occurs is that the drive, over time, accumulates a large number of bad sectors.....and the drive controller chip drops into *programming/diagnostic* mode in an attempt to protect itself, and exert some sort of 'damage control' over the situation.
The most relevant article I've been able to find on this whole business can be found here:-
Hope that helps. Let us know how you get on, please.
Distros:- Multiple 'Puppies'..... and Anti-X 16.1
My Puppy BLOG ~~~ My Puppy PACKAGES
Compaq Presario SR1916UK; Athlon64 X2 3800+, 3 GB RAM, WD 500GB Caviar 'Blue', 32GB Kingspec PATA SSD, Seagate 'Expansion' 3 TB USB 3.0 external HDD, ATI Radeon Xpress 200 graphics, Dell 15.1" pNp monitor (1024 x 768), TP-Link PCI-e USB 3.0 card, Belkin PCI USB 2.0 4-port card, self-powered 7-port USB 2.0 hub
Dell Inspiron 1100; 2.6 GHz P4, 1.5 GB DDR1, 64GB KingSpec IDE SSD, Intel 'Extreme' graphics, 1 TB Seagate 'Expansion' external storage, HP HD2300 webcam.