So you know, what I (and probably Roger also) am looking for is something that looks abnormal with one of your database files. Something that would distort the player application and make the database image in memory so large that it could not possibly spin down the drives.

For reference, on my player (with lots and lots of FIDS), my files are:

q

Restored terminal settings

Remounting first music partition read-only

Remounting second music partition read-only

Player exited normally: 0

Switching to shell-player loop

Starting bash.

empeg:/empeg/bin#

empeg:/empeg/bin# ls -al /drive0/var

total 4255

drwxr-xr-x    2 root     root         1024 Feb 12 10:58 .

drwxr-xr-x    6 root     root         1024 Feb  4 10:45 ..

-rw-------    1 root     root         1594 Dec 21 14:16 config.ini

-rw-rw-r--    1 root     root      4201145 Feb 12 10:57 database

-rw-rw-r--    1 root     root       131836 Feb 12 10:58 playlists

-rw-rw-r--    1 root     root          376 Feb 12 10:57 tags

empeg:/empeg/bin#

Granted, yours will not be the exact same size, but if they look significantly bigger, or the directory structure looks different, you may want to try to manually rebuild the databases.