Gary escribió:intenta formatear con los comandos diskpart desde la consola. Con eso he recuperado pendrives que aparentemente no se podian formetear. Buscare un video luego para guiarte mejor.
Lo intente con el CMD de la instalacion de windows y igual, no formatea.
sixor escribió:nah se jodio esa troja, por cierto, habiendo crucial, samsung, intel, pa que se ponen a comprar esa verga?
si con linux no furula olvidalo, con gparted
Ahora hago un linux booteable y pruebo. La ssd vino con una ibuypower de hace como 4 años. Era de las primeras ssd, hasta es SATA II.
PD: También intentare con otro cable sata...
EDIT: esto describe perfectamente el problema.
I'm having problems that are partly similar to the ones described in this thread.
I've been running a desktop computer with Windows 7 64-bit from my 128GB Kingston SSDnow, with just one system partition. It ran fine for some months, but then something went seriously wrong and some corrupt files emerged. Also, after every reboot (which seemed normal) windows informed me that it did not shut down properly and I discovered that no changes since the last reboot had taken effect -- even deleted files reappeared. Chkdsk produces "An unspecified error (696e647863686b2e dee)" and fails to fix anything. sfc /scannow also terminates unsuccessfully at 6%.
It's worth noting that I first thought this to be a RAM issue, but memtest gives a clean bill to my RAM.
After some frustration I decided to just format the thing and reintall Windows 7 from the original dvd. Not so easy: I've done a format, a 'clean' and 'clean all' in diskpart, deleted the system partition and created a new one, formatted again and again, deleted everything from the ssd manually with rd /s (expect for the corrupt files, which failed to delete). Same result every time: after a reboot all the old windows system files are there, as if nothing had happened. It's as if the ssd is in read only mode or something (but it's not, which I also checked from diskpart). I've also tried changing the SATA port which I use.
So, I'm completely baffled by this, and I wonder if the drive is just somehow physically damaged. The one thing that I haven't done is plugging it into a different computer, as I don't have an external case for it (and only a laptop in addition).
Any ideas?