Sorry to hear that didn't work. As I noted back in post #12, your MP3 player uses a different geometry (32 heads/cylinder, 52 sectors/track) than the linux standard of 255 heads/cylinder, 63 sectors/track, and even though that in itself should not be a problem, I think about the only thing I can suggest would be to use gparted to reformat the MP3 player drive and set up a FAT16 partition with standard linux rules; that might help. I would only do that if you don't plan on using that MP3 player for listening to music again, because it might be that setting up a different partition geometry will make it so the MP3 Player won't see the partition correctly. But even if that were to happen, I think you will always be able to use the MP3 player for storing files at least, like a standard thumb drive.
Originally Posted by babypeng
And another thing,
why did you write "bs=440" in the dd command ?
Isn't it supposed to be "512", which is the size of the mbr ?
I'm glad you decided to use "440" and not "512", because if you had used 512, you would have erased the partition table on that drive. It turns out that the MBR contains not only the boot code to boot the drive, but bytes 447-512 in the MBR contain the drive's partition table. Also, there is a 4 byte "disk signature" that comes before the partition table, so to preserve the disk signature and the partition table, the MBR boot code generally goes from bytes 1-440. Theoretically the boot code in the MBR could also use the bytes used by the disk signature, but that can wreak havoc with an OS like Windows Vista since it uses that disk signature. Fortunately, most boot loaders in the MBR never use more than the first 440 bytes so it's not an issue.