Self Fubaring Sd Card


AireTamStorm

Unix Addict
Joined
Nov 13, 2005
Messages
971
Age
38
Website
Visit site
I received my GP2X today.... this isn't really a GP2X problem but rather a general SD problem.

I was all excited, got music and stuff playing, already had all the Chaos Emeralds in Sonic 3... was playing video.... (at work)

So I come home and start writing a movie to the SD card. Well, the card suddenly couldn't be accessed, all the files on it disappeared, and so did the device file for it. (Linux)

My PC had been acting up for a while, so I immediately blamed it, and no matter how much I tried, the device file wouldn't reappear. Frustrated, I reboot the machine.

The BIOS froze. Before I panicked, I hit the power. Turned it back on. Still froze. So I unplug the SD card reader, ready to try the power again, but the second I pulled the reader the BIOS went through the memory check. Plug the SD card back in, the memory check froze. Unplug==resume, plug in==pause. On my DESKTOP.

The GP2X showed similar behavior, but if it was plugged in at all during power-on it just wouldn't continue.

The SD card (Kingston 1 GB) FUBARed (or is it FedUBAR?) itself when writing. I'm guessing it burned a hole in its memory, and therefore is permanently unusable.

Any ideas, miracles, or similar experiences would be greatly appreciated.
 
your card reader might be broken. The gp2x doesn't boot when the SD card inserted isn't formatted in Fat32 or has malicious data on it. -I guess you can say goodbye to all the data that was on your SD, however the SD Card itself is most likely still working, it just needs to be reformatted in Fat32.
 
Mr. Anderson posted on Dec 19 2005 at 04:52 PM said:
your card reader might be broken. The gp2x doesn't boot when the SD card inserted isn't formatted in Fat32 or has malicious data on it.

I'll try another card (and card reader) and get back to you.
 
Last edited by a moderator:
Actually I was using my brother's SD card which is formatted FAT and it works fine on the GP2X.

AireTamStorm : I've fudged up my SD card before by formatting it and having my PC freeze on me while it was still formatting. Luckily there's warranty and I got a replacement.
 
Well I got impatient trying to borrow SD cards and readers from random people, just went out and bought another one. Same card reader(Sandisk), different card brand(Sandisk instead of Kingston) all seems well at the time.

Kayday posted on Dec 19 2005 at 06:03 PM said:
I've fudged up my SD card before by formatting it and having my PC freeze on me while it was still formatting. Luckily there's warranty and I got a replacement.

A) I'd think you could just retry the format if it fails, but hey. And I wasn't writing to the partition tables, I was just copying a freaking movie to the card. It doesn't even IDENTIFY itself correctly anymore when plugged in (random 16-bit character gibberish). I just think they might have tested the card one too many times ;- )

"Thats the 16,000th write. Passed!"

As for the warranty, I got it from NewEgg not to long ago, I'm sure they'll replace it once I bother to find all the packaging.
 
Last edited by a moderator:
Mr. Anderson posted on Dec 19 2005 at 03:52 PM said:
your card reader might be broken. The gp2x doesn't boot when the SD card inserted isn't formatted in Fat32 or has malicious data on it. -I guess you can say goodbye to all the data that was on your SD, however the SD Card itself is most likely still working, it just needs to be reformatted in Fat32.

Call me stupid and all but shouldn't FAT16 work just fine? Heck fat32 is meant for things OVER 1gb and as of now the gp2x does not support it.

I used my card and it was FAT16, sure I ended up bricking it, but it did work fine. I also highly dought that the bricking was because of my FAT16 card.
 
Last edited by a moderator:
reallynotnick posted on Dec 19 2005 at 06:15 PM said:
Call me stupid and all but shouldn't FAT16 work just fine? Heck fat32 is meant for things OVER 1gb and as of now the gp2x does not support it.

I used my card and it was FAT16, sure I ended up bricking it, but it did work fine. I also highly dought that the bricking was because of my FAT16 card.

They're just using the vfat driver from Linux I think, so almost any FAT-based filesystem should work for everything other than firmware upgrades.
At least that has been my experience. Correct me if I'm wrong.
 
Last edited by a moderator:
Back
Top