Rockbox.org home
Downloads
Release release
Dev builds dev builds
Extras extras
themes themes
Documentation
Manual manual
Wiki wiki
Device Status device status
Support
Forums forums
Mailing lists mailing lists
IRC IRC
Development
Bugs bugs
Patches patches
Dev Guide dev guide
Search



Donate

Rockbox Technical Forums


Login with username, password and session length
Home Help Search Staff List Login Register
News:

Welcome to the Rockbox Technical Forums!

+  Rockbox Technical Forums
|-+  Support and General Use
| |-+  Hardware
| | |-+  Sansa Fuze memory
« previous next »
  • Print
Pages: [1]

Author Topic: Sansa Fuze memory  (Read 2327 times)

Offline schachwhiz

  • Member
  • *
  • Posts: 5
Sansa Fuze memory
« on: July 23, 2011, 02:12:26 PM »
I have a 4GB Sansa Fuze. I recently put Rockbox on it, and I love it. But I seem to be missing some memory for some reason. I have 41 albums on it, which on my Linux computer, is supposed to be 1.6GB. However, when I look at the free space using Linux, it says I have 2.4GB used, and 1.4GB free, with a total capacity of 3.8GB. When I use "Disk Usage Analyzer", it say I have 1.8GB used, which is probably accurate, considering that Rockbox probably needs some space to work. On the Sansa Fuze itself, Rockbox says I have "Int: 1.39GB/3.79GB". Any ideas where this memory went?
Logged

Offline AlexP

  • Global Moderator
  • Member
  • *
  • Posts: 3688
  • ex-BigBambi
Re: Sansa Fuze memory
« Reply #1 on: July 23, 2011, 03:14:10 PM »
Nowhere.  Hard drive manufacturers uses powers of 10 so they define a gigabyte as 1,000,000,000 bytes whereas operating systems generally use binary prefixes, so it defines a gigabyte as 1,073,741,824 bytes.  As a result your hard disk is quoted as 4 GB by the manufacturer which is 4,000,000,000 bytes, which the OS reports as 4,000,000,000/1,073,741,824 = 3.73 GB

As a note, to try to avoid confusion the binary version has been defined as gibibytes, GiB so you have 4 GB, but 3.73 GiB :)

See e.g. http://en.wikipedia.org/wiki/Gigabyte#Consumer_confusion
« Last Edit: July 23, 2011, 03:19:20 PM by AlexP »
Logged
H140, F60, S120, e260, c240, Clip, Fuze v2, Connect, MP170, Meizu M3, Nano 1G, Android

Offline schachwhiz

  • Member
  • *
  • Posts: 5
Re: Sansa Fuze memory
« Reply #2 on: July 23, 2011, 03:44:22 PM »
Thank you for replying, but I'm not concern about the "missing" memory of 4 - 3.73 = 0.27GB. I'm wondering how, if I put 1.6GB of music onto the player, I have 2.4GB used. What is taking up 0.8GB of space? Is that all Rockbox?
Logged

Offline AlexP

  • Global Moderator
  • Member
  • *
  • Posts: 3688
  • ex-BigBambi
Re: Sansa Fuze memory
« Reply #3 on: July 23, 2011, 04:52:06 PM »
No, Rockbox takes about 20 MB with fonts and all.

There are a few options.  One is that you have songs still on there that you copied over in MTP mode in the Sansa firmware, that Rockbox doesn't see.  Two is that you have loads of space taken up in a recycle bin.  Three is that the free space reporting is wrong (unlikely, but can happen in Rockbox as Windows doesn't update the FAT properly).

Try removing all folders created by the OF.
« Last Edit: July 23, 2011, 04:54:16 PM by AlexP »
Logged
H140, F60, S120, e260, c240, Clip, Fuze v2, Connect, MP170, Meizu M3, Nano 1G, Android

Offline schachwhiz

  • Member
  • *
  • Posts: 5
Re: Sansa Fuze memory
« Reply #4 on: July 24, 2011, 12:30:53 AM »
I don't believe that there are any files on it from MTP mode. Also, I deleted the ".trash..." folder. If I were to delete the folders from the OF, which ones would I delete? The ##MUSIC## folder?
Logged

Offline AlexP

  • Global Moderator
  • Member
  • *
  • Posts: 3688
  • ex-BigBambi
Re: Sansa Fuze memory
« Reply #5 on: July 24, 2011, 05:51:14 AM »
Yes, all those folders.  Rockbox doesn't take the space, so you must have some additional files on there somewhere.
Logged
H140, F60, S120, e260, c240, Clip, Fuze v2, Connect, MP170, Meizu M3, Nano 1G, Android

Offline bluebrother

  • Developer
  • Member
  • *
  • Posts: 3421
  • creature
Re: Sansa Fuze memory
« Reply #6 on: July 24, 2011, 06:17:14 AM »
You could also have lost clusters in the FAT. Try running chkdsk /f on Windows or fsck.vfat on Linux.
Logged
Rockbox Utility development binaries (updated infrequently) · How to ask questions the smart way · We do not estimate timeframes.

Offline schachwhiz

  • Member
  • *
  • Posts: 5
Re: Sansa Fuze memory
« Reply #7 on: July 24, 2011, 10:59:04 AM »
I deleted ##MUSIC# and ##PORT#, which freed up 113MB. I don't think I ran fsck.vfat correctly. I ran it as root, and my user, and this is what I got:
~$ fsck.vfat -av /media/SANSA\ FUZE/
dosfsck 3.0.9 (31 Jan 2010)
dosfsck 3.0.9, 31 Jan 2010, FAT32, LFN
open: Is a directory

And for root, same thing:
~# fsck.vfat -av /media/SANSA\ FUZE/
dosfsck 3.0.9 (31 Jan 2010)
dosfsck 3.0.9, 31 Jan 2010, FAT32, LFN
open: Is a directory

Now I have a little more space, but I still don't know where the other 0.7GB is.   ???


Also, when booting into OF, it freezes on "Refreshing database". I don't know if this has any bearing on my problem, but I thought it might be important.
Logged

Offline AlexP

  • Global Moderator
  • Member
  • *
  • Posts: 3688
  • ex-BigBambi
Re: Sansa Fuze memory
« Reply #8 on: July 24, 2011, 02:03:41 PM »
You need to run it on the device, so unmount the sansa then run as root

fsck.vfat -a /dev/sdxN

replacing sdxN with the partition of interest, e.g. sdb1

The OF failing to refresh its db could also indicate a damaged file system.
Logged
H140, F60, S120, e260, c240, Clip, Fuze v2, Connect, MP170, Meizu M3, Nano 1G, Android

Offline schachwhiz

  • Member
  • *
  • Posts: 5
Re: Sansa Fuze memory
« Reply #9 on: July 24, 2011, 04:34:40 PM »
Here's the results:
# fsck.vfat -av /dev/sdb
dosfsck 3.0.9 (31 Jan 2010)
dosfsck 3.0.9, 31 Jan 2010, FAT32, LFN
Checking we can access the last sector of the filesystem
Boot sector contents:
System ID "MSDOS5.0"
Media byte 0xf8 (hard disk)
       512 bytes per logical sector
     32768 bytes per cluster
        38 reserved sectors
First FAT starts at byte 19456 (sector 38)
         2 FATs, 32 bit entries
    498176 bytes per FAT (= 973 sectors)
Root directory start at cluster 2 (arbitrary size)
Data area starts at byte 1015808 (sector 1984)
    124417 data clusters (4076896256 bytes)
63 sectors/track, 255 heads
         0 hidden sectors
   7964672 sectors total
FATs differ but appear to be intact. Using first FAT.
Reclaiming unconnected clusters.
Unable to create unique name


Also, the ##MUSIC# and ##PORT# folders have been recreated, for no apparent reason.
« Last Edit: July 24, 2011, 04:36:58 PM by schachwhiz »
Logged

Offline [Saint]

  • Rockbox Expert
  • Member
  • *
  • Posts: 1662
  • Hayden Pearce
    • Google+
Re: Sansa Fuze memory
« Reply #10 on: July 24, 2011, 09:04:44 PM »
Quote from: schachwhiz on July 24, 2011, 04:34:40 PM
Also, the ##MUSIC# and ##PORT# folders have been recreated, for no apparent reason.

And they will be recreated every single time the OF boots.


[St.]
Logged
Using PMs to annoy devs about bugs/patches is not a good way to have the issue looked at.

  • Print
Pages: [1]
« previous next »
+  Rockbox Technical Forums
|-+  Support and General Use
| |-+  Hardware
| | |-+  Sansa Fuze memory
 

  • SMF 2.0.17 | SMF © 2019, Simple Machines
  • Rockbox Privacy Policy
  • XHTML
  • RSS
  • WAP2

Page created in 0.087 seconds with 14 queries.