• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Help Me ! Intel X25M 80GB SSD Failure

C

Conrado

Junior Member
Hello.

I just had 2 Intel X25 M SSD in Raid 0 working good for 1 week then sundelly i got a BSOD then my system was not able to start anymore.

After some check i noticed my Raid array was faulty whit only one SSD as the raid member and the other as Non-Raid Member and with a label of 0 (Zero) mb hard drive space.

My system was in perfect state and all over nobreak and line filters.

After some googling i just cant find any help from intel.

I did to undo the raid volume and tryied the hdderase 3.3 but it just localiza a bootloader sector and can not touch it.

Nothing can acess the drive main volume, it does not appear in the Windows instalattion.

In the bios does not appear the SMART CAPABLE OK on this volume.

I did checked all the cables, and it is not the problem.

My PSU is a Ultra X3 1600 W.

I am so sad about it, can anybody help me ?

 
Did you back up? Otherwise your data is gone. Then RMA the drive to the vendor since it seems it was faulty.
 
Maybe your RAID controller is dead, dead, dead...
Try formatting the drives in another system, or as non-RAID on your current MB.

Your data is probably toast.
So it's a good thing that you backed up, because you knew how flakey RAID 0 arrays can be.
 
if the controller was the issue both drives would be gone... your drive sounds as dead as a drive can get.. rma it for replacement
 
I am in Brasil and bought drivers in USA.
Will try to DiskPath it before send it for a 60 days travel.

The problem is the driver.
Partition just disapeared.
Boot Sectors Erros are present.

I dont care about data, i am not stupid enough to put valuable data on that not time tested SSDS.

I think the BSOD just messed with boot sectors.

The othe SSD is Acessible but is reporting a 149 gb space and 80 gb free ( from the raid).

I need to reformat it too.

I sad i did not buy 4 WD Velociraptors.

One tip, take care wit overclock tests wit SSDs, looks like they can not support BSODs.

 
Good knowing this mates eh? I guess I will stick with the ancient spindle drives, lol

Thanks, JASTECH
 
Hello !

I know where the problem is.
The boot Sector is out.

Only visible part of disk is the MBR.

I tried some softwares but none is really capable to fix that SSD.

I tried and payed for DiskPath, PTDD, Stellar Phoenix but none of them are capable to fix my SSD.

Do somebody know a tool really capable to fix a SSD ?

Looks like a simple problem and i just need the right tool.

Other possibility is th total failure of internal controller.

Will try to RMA it but i know it will be a 60 + days waiting for my new unit.

INTEL promissed me a ultimate piece of hardware and give me a ultimate big HEADACHE.

I try to have the best to not have headache an do not loose time, i am wipping out the good SSD out of my system and will sell them when the RMA is done.

No more SSDs until this thecnology becomes really ready.

Already ordered 3 more WD Velociraptors to a 4 x Raid 0 ( I am loocking for peformance).

Please tell me about the SSD compatible tool.

Rgds.

Conrado
 
Conrado DOA's are a reality for any all hardware. You could have bought yourself two velociraptors and experienced the exact same fate.

It is unfortunate that in-field fails occur, but if you really required the manufacturer to implement a quality assurance protocol that has a zero tolerance policy for in-field fails then those $400 drives you bought would need to be priced around $800 or $1200 to pay for the massive increase in the manufacturers cost structure and overhead.

The tradeoff between cheap drives with tons of in-field fails versus uber expensive drives with near-zero fails is called a Warranty.

Your SSD drives have a warranty for a reason, unfortunately you are finding out why. For the rest of the us who got to buy the drive and won't ever use the warranty we are glad we didn't have to pay a higher price.

This is part of the reason why OEM CPU's (30 day warranty) are cheaper than Retail CPU's (3yr warranty)...I take the lower priced OEM's because I am willing to gamble that the quality is actually good enough that I won't have an in-field fail regardless the warranty duration. However having a 3yr warranty on a retail CPU does not in any way guarantee or assure me that my retail chips will have a lower fail-rate than my OEM chips.

At any rate my point is simply that I think you are over-doing it when it comes to attributing your SSD failure as indication of the entire country of Denmark being rotten. Something is rotten in Denmark, i.e. your dead SSD, but that is not to say the rest of the country stinks.
 
If you have 2x 80GB X25-M and it reports your total size as 149GB, then the "dead" drive isn't totally dead. Yea, you are right you need some tool that fits it.

Anyway, this is why the Xeons cost more than "similar" variants of the consumer CPUs and take longer to come to market.
 
I have similar problem with brand new x-25e ssd.
After installation it worked 24h only then crashed (BSOD) with badblocks (non-raid single drive configuration), after formatting it is showed me a lot of badblocks, but i did format again, next time the amount of badblocks was less then first time. So I did format again... and again until all badblocks are gone. S.M.A.R.T. parameter was changed - "Reallocated Sector Count" from 51 (brand new) to 73 (last time when SMART was available), but RAW value is same - 00000000000 (that's strange way how intel firmware relocates bad cells of SLC). After 2 weeks of use SSD crashed the same way as it was before. This time reformatting helped again, but after restarting I got the same problem as Conrado - the size of SSD is 0MB, serial number have changed to BAD_CTX string, S.M.A.R.T. is totally corrupted (every time after request it sends some random data to program) and I can't find the way to restore capacity. Any program that can change HPA option on the drive tells me that it is not possible (ssd sends error back).
I have no answer from Intel support yet... but looks like I need RMA if It is hardware problem, not just firmware failure
 
hmmm, looks like i found the way to restore capacity - it is hdderase v3.3. I have problem with my motherboard to run hdderase correctly, but now I disabled all other onboard controllers and it works! After securely erasing SSD my capacity is back, testing now!

After some write testing "reallocated sector count" in S.M.A.R.T. is 85 . Thats really strange, if ssd controller remaps bad cells with reserved capacity, then parameter must to go down, not to go up....wtf intel?

added 28.04.2009

Reallocated sector count - 128
Endurance Remaining (attribute 232) - 88

I can't explain growing of Reallocated sector count, where RAW still unchanged. It's stupid 🙂

More info here
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top