MSFN Forum: ssd is corrupted by windows install (or me?) - MSFN Forum

Jump to content


Hard Drive and Removable Media issues Rules

If you have questions about Seagate 7200.11, do read the READ_ME_FIRST, then read the FGA. If your questions remain unanswered after reading those two stickies, then post. For all other Hard Drive and Removable Media issues, you may post right away.
Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

ssd is corrupted by windows install (or me?) Rate Topic: -----

#1 User is offline   bwana 

  • Group: Members
  • Posts: 6
  • Joined: 21-March 06

Posted 03 October 2012 - 07:59 PM

I started installing windows 7 to a micron c300 ssd. I chose the whole ssd as the install target, The install cycle started and then i realized i forgot to save some raw space for a linux install. so i just shut off the computer.

reboot into win 7 installer now shows the ssd has zero bytes available.
bring up a cmd terminal with shift +f10 and start disk part.
list the disks -> the ssd is disk 0
select disk 0
'clean'
it says 'cleaned'

reboot-> still only zero bytes on the ssd.

plug the ssd into another windows 7 box-> ssd doesnt show up in explorer.
however, I do see it in device manager.
bring up administrative tools->computer management->disk management , NO SSD!
uninstall the ssd in device manager. reinstall the diver by selecting 'scan fr hardware changes'
no improvement-ssd still invisible in disk management

boot into ubuntu linux-> gparted doesnt see the ssd.

So....., I did download the firmware update,C400 mSATA Rev. 01MG Bootable Media Firmware Update, from here
http://www.micron.co...rage/client-ssd
This did recognize the disk and successfully flashed the firmware! However the disk is still seen by the windows startup disk as having zero bytes. diskpart still gives the same errors.

so i rebooted with the firmware update disk. this is a linux based iso. by holding f8, it traces the boot process.
the following erros are reported:
InitiDiskBIOS reported 0 sectors/track, assuming 63!
Error reading partition table drive sector 0 BIOS reported 0 sectors/track, assuming 63!

The disk continues to boot properly and this time recognizes that the firmware does not need updating, it is already at version 01MG, the most recent.

Curious that the disk is seen by the bios and some parts of windows but not resettable. i attached the ssd to a windows xp system and ran crystaldiskinfo.
This utility says my ssd is 2199 gb! not bad for something that is supposed to be ~128gb. so how can i fix thix this ssd? minitools and easus wont fix it.


#2 User is offline   GrofLuigi 

  • GroupPolicy Tattoo Artist
  • PipPipPipPipPipPip
  • Group: Members
  • Posts: 1,275
  • Joined: 21-April 05
  • OS:none specified
  • Country: Country Flag

Posted 03 October 2012 - 09:22 PM

Try this. Crucial and Micron are the same company (or, at least, their SSDs are the same).

*Edit: It might not apply fully to your situation, but you have nothing to lose...

GL

This post has been edited by GrofLuigi: 03 October 2012 - 09:25 PM


#3 User is offline   jaclaz 

  • The Finder
  • Group: Developers
  • Posts: 11,433
  • Joined: 23-July 04
  • OS:none specified
  • Country: Country Flag

Posted 04 October 2012 - 08:43 AM

Also, an ATA Secure Erase may reset the device :unsure:
http://www.iishacks....tate-drive-ssd/
(on linux hdparm can do the same)

The "power cycle procedure" is reported verbatim (and "generically") at newegg:
http://www.newegg.ca...x?articleId=292
At first sight it does not make much sense, but there are several reports that it worked.


jaclaz

#4 User is offline   bwana 

  • Group: Members
  • Posts: 6
  • Joined: 21-March 06

Posted 04 October 2012 - 10:45 AM

tnx again for your thoughts.

secure erase doesnt see the ssd
power cycling did nothing

i have an email into crucial/micron-we'll see what they say

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

2 User(s) are reading this topic
0 members, 2 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2013 msfn.org
Privacy Policy