1gb Sd Card Ruined
- Thread starter Lectern
- Start date
WhiteFalcon
Certified Guru
I don't think taking the SD card out when the GP2X is running is bad, I have done it a few times. It is just bad to take it when it is being written to (and possibly read from, not sure about the updates).
Mr Doctor
Member
Just format it. If you pulled it out during a write it can corrupt the data, a format will fix all.
aapje89
Still here...
what do you mean?, you can see the card, but cannot format it?Lectern posted on Feb 2 2006 at 01:29 PM said:
Last edited by a moderator:
Mr Doctor
Member
try putting the card in the reader, then plug the USB cable in.
aapje89
Still here...
hmm... weirdLectern posted on Feb 2 2006 at 01:42 PM said:
Last edited by a moderator:
whiskthecat
whiskthecat
Maybe the batterry light could be used as a read/write light in the future.
Mr Doctor
Member
No, I mean take the USB cable out, stick the card in the reader then plug it back in. I had a cheapo card that strangely wouldnt work unless I did that (my other ones are fine)Lectern posted on Feb 2 2006 at 01:54 PM said:
Last edited by a moderator:
Taking the card out while it's still turned on (or before/during sync) can corrupt the SD card's partition table. Don't ask me why, blame gamepark.
Since windows expects there to be at least 1 partition on it, it doesn't see the card.
Your card is probably not broken. Just fix the partition table AND reformat. (some cameras can do this for you)
How to do this in windows is your problem - I don't have a clue.
In linux, just let fdisk rewrite the partition table (it's not entirely gone) and run mkdosfs -F 32.
Since windows expects there to be at least 1 partition on it, it doesn't see the card.
Your card is probably not broken. Just fix the partition table AND reformat. (some cameras can do this for you)
How to do this in windows is your problem - I don't have a clue.
In linux, just let fdisk rewrite the partition table (it's not entirely gone) and run mkdosfs -F 32.
I had this recently happen with my card reader.
It was working fine, I was copying a large file then I suddenly got an error and the card couldn't be read by every device I tried it in.
This kind of failure seems to be common early on with cheap cards, just send it back to where you bought it or the manufacturers
It was working fine, I was copying a large file then I suddenly got an error and the card couldn't be read by every device I tried it in.
This kind of failure seems to be common early on with cheap cards, just send it back to where you bought it or the manufacturers
shrubberyrobbery
Member
- Joined
- Dec 1, 2005
- Messages
- 174
whiskthecat posted on Feb 2 2006 at 02:05 PM said:
now that's a GREAT idea! how about it, GPH?
Last edited by a moderator:
aapje89
Still here...
someone had already implemented this in a program... cant remember wich one.shrubberyrobbery posted on Feb 2 2006 at 05:52 PM said:
Last edited by a moderator:
Squidge
Certified Guru
hmm, maybe you could use gfoot's usb serial driver on another card, get a bash prompt with that, and then swap cards (umount first to be on the safe side, since you don't want another damaged card) and run fdisk. That should be able to repair a bad partition table.
Other than that, maybe get another 1gb card, and then use the linux 'dd' command to read the new card and copy it directly to the old one, which should make the cards almost identical.
Other than that, maybe get another 1gb card, and then use the linux 'dd' command to read the new card and copy it directly to the old one, which should make the cards almost identical.
You can even try the drive manager within WinXP and see if you can setup a new partition table.
T
TelcoLou
Guest
aapje89 posted on Feb 2 2006 at 01:30 PM said:
VICE. It's quite neat to see in action too
Last edited by a moderator: