Unable to partition drive

[narayanjr]

That is the error msg I get while the software loads. It then proceeds to boot after that. However it does not recognize my SSD. I have both my SSD and WD in the case right now, it recognized the WD but had no trace of the SSD. I am currently looking for softare that is capable of erasing my SSD.

 

[dsperber]

That is the error msg I get while the software loads.

Interesting.

It's a Linux boot CD, but it does seem like its drivers can't handle this SSD. Either that, or because of something wrong with the current formatting on the SSD that Partition Wizard can't make sense of what it is.

It then proceeds to boot after that. However it does not recognize my SSD.

I suspect that once you get this all cleared up and get Win7 installed again on the SSD, and then install Partition Wizard on Win7, that there will be no problem accessing the drive under Win7.

I suppose you could email the author of Partition Wizard (contact link on the web site), just to inquire as to whether the problem is basic (i.e. the standalone boot CD cannot access your SSD) or whether it really should be able to. That would suggest the problem is really some kind of formatting corruption on the SSD itself.

You could also contact Crucial tech support.

I have both my SSD and WD in the case right now, it recognized the WD but had no trace of the SSD.

Yeah...

I am currently looking for software that is capable of erasing my SSD.

Phone Crucial tech support and ask them about this whole situation.

 

[narayanjr]

Ok so I took out my SSD and put in into an external and plugged it into my laptop. It doesnt show up in My Computer. However I found it when I go to Disk Management. It shows it as Unallocated for the full size. When I try and initialize it it just gives me an error it cant because of a device I/O error. I used Diskpart to attempt the same thing. When I try and create a partition or clean the drive I get the same error that there was a device I/O error. So I am assuming the drive is dead.

I attached the Event log from the time I connected the drive. The site doesnt support event log extensions so I compressed it into a .rar file.

So is the drive pretty much dead? and needs to be RMA'd?

Thanks for all the help.
Adam

 

[dsperber]

I attached the Event log from the time I connected the drive.

So is the drive pretty much dead? and needs to be RMA'd?

I'm no expert at all on SSD drives. But these entries in the event log sure look a hardware failure to me.

Did you call Crucial and ask their tech support for assistance? They built the drive... they should know about it, and how to diagnose it for failure (which would justify RMA, to the vendor presumably from whom you bought it... assuming it's within 30 days of purchase you shouldn't have any problem at all returning it for a new one).

 

[narayanjr]

I will call crucial on monday when they are back from the weekend. But on another forum someone suggested flashing the firmware of my drive with the 006 firmware. I already have that firmware but is it possible to safely reflash it again with the 006 firmware? and would I just use the 002 to 006 firmware update?

 

[dsperber]

I will call crucial on monday when they are back from the weekend. But on another forum someone suggested flashing the firmware of my drive with the 006 firmware. I already have that firmware but is it possible to safely reflash it again with the 006 firmware? and would I just use the 002 to 006 firmware update?

Couldn't tell you.

Normally, hardware firmware flashes are run by a vendor-provided utility which checks first to ensure that all physical prerequisites are met so that you don't do any damage.

But I would not think that re-flashing a current firmware BIN file to the hardware would do any harm. However the "002 to 006 firmware update" designation kind of makes me wonder... did it expect to discover 002 installed first, and would abort otherwise?

Don't know. And I wouldn't want to steer you wrong.

Why not just wait until Monday and find out what Crucial suggests.

 

[narayanjr]

I tried reflashing my firmware after reading up on it a bit more but it did not help. I contacted Crucial and they instructed me to perform an RMA, so I will be calling tomorrow do that.


Thanks for all the help,
Adam

 

[dsperber]

I tried reflashing my firmware after reading up on it a bit more but it did not help. I contacted Crucial and they instructed me to perform an RMA, so I will be calling tomorrow do that.

Any status update on this? New SSD on the way?

I'm just curious if the replacement SSD drive can be partitioned successfully (still recommend Partition Wizard), now that we've discussed all the ins and outs.

 

[narayanjr]

I contacted Crucial and after telling them everything the tech guy agreed it just needed to be RMA'd but he had no explanation as to what was wrong with it. They sent me a new one which I was able to install W7 onto no problem. Except for that same error I got the first time installing which had to do with RAM. Now I am scared that the RAM is what killed the SSD in the first place. I dont know how but that is my only conclusion. As of right now I am running on only 1 4gig stick instead of both as I am afraid to put the other one back in. I have run the windows Memory diagnostics It passed with just 1 stick in. It failed, i believe, with both sticks in. I unplugged the SSD when running these tests so Im assuming it shutting down mid test is a Fail as it couldn't boot to show me test results. I then changed what slot the second stick was in and then it passed. I then put that second stick back where it was when it failed and tested again and it passed. So I am not really sure what the issue is but I am still a little uneasy about putting in all 8 gigs and running it. Is it even possible that RAM can kill an SSD like that? Or should I just put in all 8gigs and not worry about it?

Thanks for the help.
Adam