Just to confirm that the same happened to me too, with the latest Spotify app on Android 2.3.5, plugged into the charger while initiating a sync through the Mac OS X application.
Indeed, ancient old posts on Get Satisfaction report the same: https://getsatisfaction.com/spotify/topics/spotify_for_android_corrupting_sd_card_on_htc_desire
I don't know how full the card was (SanDisk 16GB microSD HC), but:
- Windows XP
chkdsk reports:
chkdsk e:
The type of the file system is FAT32.
Volume Serial Number is 76F4-1EE0
Insufficient disk space to correct disk error.
Please free some disk space and run CHKDSK again.
- HTC Wildfire S (in which the card was damaged) does not recognize it all, and does not even enable the option to format it. An older 2GB card and a brand new 32GB card work fine in that same device.
- An older Sony Xperia X10 mini goes through a verification cycle and then wants to format it for me.
- OS X Disk Utility reports "unknown filesystem" and cannot verify let alone repair that.
- Image Rescue 4 on OS X fails to scan it, but on Windows XP it reports the correct size, but then claims "No files found".
- Maybe
chkdsk on Windows XP reported a full disk as I had the card (reader) set to read-only, or maybe chkdsk needs the /r parameter. Anyway, with that parameter, two days later Windows 7 in Parallels on a Mac did manage to restore 1,464 files, being 1.26 GB, hence far less than the 16 GB capacity:
chkdsk e: /r
The type of the file system is FAT32.
Volume Serial Number is 76F4-1EE0
Correcting error in directory \
Windows is verifying files and folders...
File and folder verification is complete.
Convert lost chains to files (Y/N)? y
1234432 KB in 1464 recovered files.
Windows is verifying free space...
Free space verification is complete.
Windows has made corrections to the file system.
15,554,240 KB total disk space.
64 KB in 1 folders.
1,234,432 KB in 1,464 files.
32 KB in bad sectors.
14,319,680 KB are available.
32,768 bytes in each allocation unit.
486,070 total allocation units on disk.
447,490 allocation units available on disk.
Some file allocation tables (FAT) are unwriteable.
- Finder on OS X still shows an empty disk (named NO NAME), but indicates that not all space is free. But in Terminal it is easily accessible:
cd "/Volumes/NO NAME/"
ls
FOUND.000
cd FOUND.000
ls
FILE0000.CHK FILE0293.CHK FILE0586.CHK FILE0879.CHK FILE1172.CHK
FILE0001.CHK FILE0294.CHK FILE0587.CHK FILE0880.CHK FILE1173.CHK
FILE0002.CHK FILE0295.CHK FILE0588.CHK FILE0881.CHK FILE1174.CHK
FILE0003.CHK FILE0296.CHK FILE0589.CHK FILE0882.CHK FILE1175.CHK
...
...
Alternatively, in Finder one could hit Command-Shift-G to go to /Volumes/NO NAME/FOUND.000 directly too.
- So, this gave me a
FOUND.000 folder with files like FILE0001.CHK. The first five were not readable at all, but at least I could give the media files some file extension based on their magic number:
file -Ib * | sort | uniq -c
11 CDF V2 Document, corrupt: Can't read SAT; charset=binary
2 application/msword; charset=binary
693 application/octet-stream; charset=binary
3 application/ogg; charset=binary
15 application/pdf; charset=binary
6 application/x-empty; charset=binary
44 application/xml; charset=binary
10 application/xml; charset=us-ascii
9 application/zip; charset=binary
4 audio/x-wav; charset=binary
2 image/gif; charset=binary
508 image/jpeg; charset=binary
141 image/png; charset=binary
1 text/html; charset=binary
2 text/plain; charset=binary
7 text/plain; charset=us-ascii
6 video/3gpp; charset=binary
...and with that list of file types, I decided to recover just the media files:
mkdir renamed
for f in *
do
file -I $f | \
perl -n -e'/^([^.]*).*(3gpp|jpeg|ogg|wav)/ && print "$1.CHK renamed/$1.$2\n"' | \
xargs cp
done
So, I guess I recovered the most important stuff. Still, I now really don't dare to sync Spotify with my Nexus S, which has built-in USB storage that I cannot replace like a microSD. So, Spotify, if you happen to find a cause, then please don't silenty fix it but let us know that things are safe again!
