Damaged Internal SD Card?

---

When I boot up the phone, I get a message in my notification bar saying:

Damaged Internal SD Card.

Not an external memory card. My internal SD card. The one built into the phone. Anyone know if there's a way to fix this? Is there a way to reformat the built in SD card? My computer can't recognize it anymore. Am I pretty much screwed?

I posted this in androidforums as well.

EDIT: I found the "Format Card" option in settings. It's working fine, although the fact that this came up in the first place is very troublesome. Some further information: I did the GPS thing where you dial *#*# and some number, then rebooted my phone. My internal card was fine until I rebooted. That was the first time I got that message of a damaged internal sd card.

dude same thing happened to me today - any way to fix this ?

Format it, and hope you never see those dreadful words again.

Originally Posted by norcal einstein

Format it, and hope you never see those dreadful words again.

This is a known fact that has been reported on some Galaxy S phones, it is coming from doing multiple Lag fixes of the phone internal SD from RFS to EXT. buyer be ware when flashing lag fixes over and over.

Originally Posted by dpmurphy81

This is a known fact that has been reported on some Galaxy S phones, it is coming from doing multiple Lag fixes of the phone internal SD from RFS to EXT. buyer be ware when flashing lag fixes over and over.

what about when you flash a ROM that comes with LAg fix by default ? and you Disable it all the time can that happen to you? cuz ive flashed but most roms r being gay now with Lag fix ... i disable always might i get that msg? :/

Originally Posted by dpmurphy81

This is a known fact that has been reported on some Galaxy S phones

This affects the bell vibrants only, the captivates never had this issue.

Originally Posted by peachpuff

This affects the bell vibrants only, the captivates never had this issue.

One can assume that the captivate can have this problem also the hardware is no different really from the vibrant. And I feel in my opinion that it is related to the quality of the flash memory chip itself weather you have this problem. compound this with the relentless conversion of the RFS file system it is just a matter of time I believe. The trade off of speed is stability. But that is only my opinion...

Originally Posted by dpmurphy81

One can assume that the captivate can have this problem also the hardware is no different really from the vibrant. And I feel in my opinion that it is related to the quality of the flash memory chip itself weather you have this problem. compound this with the relentless conversion of the RFS file system it is just a matter of time I believe. The trade off of speed is stability. But that is only my opinion...

That actually is a pretty big assumption. Just because two phones appear "similar" based on the published specs doesn't mean their insides are at all related. We already know that from a strictly hardware standpoint, even the two GSM cousins in America (the Vibrant and the Captivate) have different physical hardware inside, and many other versions of the i9000 abroad vary quite a bit too. Samsung produces these phones in very large batches, and who knows exactly what the differences are in the individual components put onto each board.

And as far as I'm aware, there's not been a single case of repeated "lag fix" operations causing damage to the hardware. Which makes sense when you think about it too. If I load a single 720p movie onto my internal SD (OneNAND), that probably requires a lot more NAND cells to be touched than an entire system/data/dbdata/cache lag fix being applied. Since all those operations really do is backup the partition, delete the partition, format a new partition, and then restore the data back over. Not really the most intensive thing you can do with your internal SD...

The OP's problem probably lies somewhere in PEBKAC. Not unmounting storage cleanly from the PC, or accidentally unplugging during a file transfer, battery came out unexpectedly at some point, etc. I end up re-flashing my ROM so regularly that I never really have time for little problems to build into big problems, but that might have happened here. Just so many corrupt sectors before the OS finally gives up trying to deal with it. Either way, since formatting seems to have fixed the problem, and this storage is solid-state, not mechanical, the problem is probably not in the hardware.

I had this issue on my captivate, as did two others that I know of, with a certain release of voodoo lag fix. Haven't heard of complaints since, and although it was tricky to fix haven't had problems since

Its not just with Bell phones. But I agree I think its software not hardware (at least for us Cappy folks!)

Sent from my GT-I9000 using XDA App

Originally Posted by fatttire

I had this issue on my captivate, as did two others that I know of, with a certain release of voodoo lag fix. Haven't heard of complaints since, and although it was tricky to fix haven't had problems since

Its not just with Bell phones. But I agree I think its software not hardware (at least for us Cappy folks!)

Sent from my GT-I9000 using XDA App

What was the fix you applied exactly? I'm interested to it. Thanks