On my class16 32GB SDHC card from ED's shop, I have an ext3 partition, on which I keep most of my pandora files (not pnds).
I also have a FAT32 partition which I use to transfer files. This is because I use a different UID on my Linux box (endless chmod -R 777 'ing was getting tedious) , and windows doesn't play well with non fat filesystems.
I do not have any important data on the fat partition.
Every time my pandora boots, or I access it using 'SD mass storage' it ends up read-only. I'm guessing something spotted a problem, and is trying to prevent (further) data loss.
What would be the best way to fix this? Are there nice tools for un-messing-up filesystems available? How should I stop this happening again (apart from the obvious umount before eject).
I could probably find out on teh interwebs, But I reckon there's a higher density of people doing strange things with SD cards here.
I also have a FAT32 partition which I use to transfer files. This is because I use a different UID on my Linux box (endless chmod -R 777 'ing was getting tedious) , and windows doesn't play well with non fat filesystems.
I do not have any important data on the fat partition.
Every time my pandora boots, or I access it using 'SD mass storage' it ends up read-only. I'm guessing something spotted a problem, and is trying to prevent (further) data loss.
What would be the best way to fix this? Are there nice tools for un-messing-up filesystems available? How should I stop this happening again (apart from the obvious umount before eject).
I could probably find out on teh interwebs, But I reckon there's a higher density of people doing strange things with SD cards here.