Support and General Use > Hardware

Sansa Clip+ Database not building

(1/1)

kevin1911:
Hi everyone. I'm a newbie here so please accept my apologies in advance if I ask some really silly questions...

I recently bought a Sansa Clip+ 4Gb and bought with it a Samsung 64Gb SDXC card. I couldn't get the original firmware to see the SD card, so installed the latest stable version of Rockbox on it last night. Now my PC sees the Clip+, and the memory card, and I can copy music to the card, but I can't seem to get the database to build - it seems to get stuck showing "building Database... 392 Found".

I've ran chkdsk on the card, and it seems to be fine. I've also tried to enable metadata logging, but can't find the log file in the .rockbox folder. Does anyone know what it should be called?

I've also checked the MP3 tags with ID3-TagIT. They all seem fine, although some are 2.3 and others are 2.2 - I assume that's not a problem?

Does anyone have any other ideas at all?

Thanks in advance!!

Kevin

[Saint]:
My guess, for now, is that the device is entirely ignorant of the presence of the sdcard and/or the content thereon.

That number seems to suggest that the device is completely incapable of finding any media on the device at all (the database init count lists ALL files it encounters while displaying progress, not just media).

This seems to reflect the symptoms of trying to initiate a database with zero media files present (or visible to the system), which admittedly is somewhat of a weird long-standing bug, one that jumps out and scares users from time to time.

What file system, may I ask, is the sdcard formatted with? SDXC comes formatted by default with the exFAT file system, as the sd specification dictates. We do not support this file system.

If you could verify that the sdcard file system is indeed FAT32 (the only file system Rockbox supports on non-hosted platforms), we can either put this to bed, or go a bit further in debugging this for you.


[Saint]

kevin1911:
Thanks Saint - I'll double check this evening, but I think I just left it as the default, which would certainly explain why it's not working.

Will come back later. Thanks again!

kevin1911:
Well, you were spot on! That was exactly the problem. Many thanks indeed!!

Navigation

[0] Message Index