Pi Eating cards

[FatalXception]

I am using an Rpi2B- it is a few weeks old, and I have been running various Linux distros on it. I ran this command:flashed RetroPie to a brand-new Kingston class 10 32gb card and started the Pi. No display, but network LED's came on. I ssh'ed into it, ran raspi-config and resized the partition to max out the SD card. I rebooted, got the RetroPie logo this time and nothing else. I let it sit for 20 minutes, then checked DHCP to find the Pi on the network- its lease was gone (Windows DHCP server). I could not SSH into it and the monitor had gone to sleep and would not wake up, so I rebooted the Pi.Still nothing. I tried to read the card in several card readers on two different systems, Linux and Windows, and windows does not acknowedlge the physical card- no partitions appear in disk Management- just empty drives (The card reader shows empty drives for all slots if no cards are inserted). Linux at least gives me a drive designation in /dev, but if I try to mount it, it says the special device is unreadable and then turns off the card reader. Any idea how to recover my cards?

[FatalXception]

I think the Pi is corrupting the partition table after the initial boot past the resize. I tried dd if=/dev/zero of=/dev/sdc and it says the device cannot be found. Is there a way to directly hexedit the partition table of the card to fix it? dmesg gives me error 62 and says it is unable to ready the capacity of both cards. Appreciate any help.

[LittleNooby]

Did you try to access/repair your SD card with some more powerful tool as photorec/testdisk? Photorec is a tool of testdisk, if you're unsure, use photorec as it will never make things worst (it only try to access/address data, never to modify nor repair). When using testdisk, be careful and do only things you understand).

[FatalXception]

Testdisk seemed to scan and maybe find it, but it could not write to it. Are there any other recovery utilities that would work? I don't care about the data- I just want to use my micro SD cards in my RPi2b.

[tanix2]

Use bootice, you will be able to repartition it,
follow this: http://www.trishtech.com/2011/06/restor ... -capacity/

[fruit-uk]

Some flash memory devices were/are designed to present as write-proteced/read-only after certain internal errors.
It's supposed to protect your data - but often results in having to buy another card

You may be lucky and be able to re-use it - but maybe not

[FatalXception]

Are there any Linux-based utilities that might do this? The problem I am having is that the card is crashing the user-mode driver- that;s straight from the event log. I need to either directly access the device in Windows or in Linux. Bootice cannot fix it because it cannot see the disk because of the driver failures. Testdisk may be a little more promising. I'll take any further suggestions I an get.
Thanks everyone!
Dan

[FatalXception]

One more thing it does that is weird- I have two different USB readers I can use- One of them powers off about 10 seconds after it tries to do anything with the card- if I fsck -v /dev/sdc then the power light on the read shuts off and the four drives it adds disappear. What I would like to know is how/why the cards got this damaged just by a RPi2B trying to resize the partition. I can't get it to recover in Linux because the device won't allow me to manipulate it, but dmesg registers the card inserts, removals and failures- I get "timeout while waiting for setup address command" then "device not accepting address 17, error -62" followed by "READ CAPACITY FAILED" followed by "USB disconnect, device number 17"
and finally "xHCI xhci_drop_endpoint calle with disabled ep e5084bc0". I get this whether the reader is plugged in to the laptop, or if I have it plugged in to a powered hub. Did I choose bad cards? They are Kingston 32GB Class 10 SDHC's.