I bought a Kingston 16GB Class 6, which worked initially, but then started having problems. It turns out it was a fake (only ~4GB), so can you check to see if it's a fake or not? (some advice on this site.) Even if it's 16GB, if it's not a Kingston then of course you can't go by the listing on the wiki.

A bad SD card shouldn't cause a reboot, it will at worst cause a kernel panic (unless Debian is set to immediately reboot after a kernel panic?)

You can test this by pulling out the SD card while the Pi is booting, and see what sort of error you get. A reboot sounds like it could be a power supply problem. The Pi starts using more power as it boots up, so it may get to a point where your power supply and cable can't deliver enough power, and it browns out and resets itself.

Malvineous wrote:I bought a Kingston 16GB Class 6, which worked initially, but then started having problems. It turns out it was a fake (only ~4GB), so can you check to see if it's a fake or not? (some advice on this site.) Even if it's 16GB, if it's not a Kingston then of course you can't go by the listing on the wiki.

How did you find out it was 4GB - the DD recommended copy method ends up resizing the donar card.

@Geffers: the SD card isn't resized, it's just the partitions only occupy the first few GB. This leaves the rest of the space as unallocated. You can run fdisk to create more partitions in the unused space. I intended to use up the rest of the space by creating a 14GB partition to mount as /home, so I could store large files in my home directory. When I formatted this new partition, it refused to mount saying it was corrupted, and that's what led to my investigation.