Sansa Fuze randomly unmounts on OSX

[mhLeft]

When I have my rockbox'd sansa fuze v1 plugged into my mac to transfer music, it will randomly unmount every couple minutes. Sometimes the screen will go black and I'll have trouble turning it on again, but this past time, it continued to keep the usb icon on the screen the whole time. The battery is charged the whole way and I never had trouble with it before on OF. Any ideas what's wrong with it? I tried turning off HID for the USB and setting the power saver time to off just incase either of those was an issue, but it doesn't seem to be.

[Chronon]

Does the OF still behave as expected?  Confirming that the OF is behaving as expected currently will help eliminate external factors.  If this is a problem that only occurs while running Rockbox, is it a new problem?  Finally, which build of Rockbox are you using?

[mhLeft]

I haven't tried OF since installing rockbox. I also just killed the original folder structure (##MUSIC#) and I have a feeling booting OF will bring that back and cruddy up what I've done with the place. As of when I stopped using the OF, I never had issues with it connecting to the computer. It used to freeze if I tried to remove songs directly on the sansa, but no problems with the computer.

Rockbox version r29534-110306

[Chronon]

Freezing while deleting files could lead to file system errors.  It might be worth checking the file system.

[mhLeft]

File system errors are quite likely. Would that affect it unmounting/freezing while connected? I tried running fsck on it and got this:


$ fsck /dev/disk1
** /dev/rdisk1
BAD SUPER BLOCK: MAGIC NUMBER WRONG

LOOK FOR ALTERNATE SUPERBLOCKS? [yn] y

SEARCH FOR ALTERNATE SUPER-BLOCK FAILED. YOU MUST USE THE
-b OPTION TO FSCK TO SPECIFY THE LOCATION OF AN ALTERNATE
SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; SEE fsck(.


What else can I use to clear that up?

[Chronon]

I'm not familiar with that option with fsck, so I can't offer advice about that.  I'm not sure it's necessary but formatting the device (using Sandisk's firmware) should be sufficient.

[sideral]

$ fsck /dev/disk1
** /dev/rdisk1
BAD SUPER BLOCK: MAGIC NUMBER WRONG

You're running the wrong fsck program.  The one for FAT32 is typically called fsck.vfat on Linux.

[Chronon]

$ fsck /dev/disk1
** /dev/rdisk1
BAD SUPER BLOCK: MAGIC NUMBER WRONG

You're running the wrong fsck program.  The one for FAT32 is typically called fsck.vfat on Linux.

Consulting the man page, fsck is just a front-end for the other programs so it should also work in principle.  I guess you need to specify the file system type when running this way, though.

[mhLeft]

fsck_msdos (I'm on mac, not linux), but it doesn't seem to do much, I get this:


** /dev/disk1
** Phase 1 - Preparing FAT
** Phase 2 - Checking Directories
** Phase 3 - Checking for Orphan Clusters
1119 files, 1908000 KiB free (59625 clusters)

The man page had very little in it so I don't know if I need to run some more options to get it to make repairs. How likely is it that this is actually causing it to hang?
Post Merge: March 24, 2011, 03:01:50 PMAn update. I ran fsck.vfat on my linux machine. It was more helpful than fsck_msdos, but the sansa still freezes up and dismounts on fedora just like OSX.

[Machete234]

Same happens to me in Windows 7 (64bit)
Since I boot in the OF before doing file transfers I dont have this issue anymore.

But booting into OF is suboptimal because the player allways wants to rebuild the database when I unplug it.

[mhLeft]

I reformatted from OF and things are better, but it's still having issues.

[themapleboy]

I have the same issue occasionally when transferring large file groups (like 4gb of mp3's). Not a real deal breaker just a nuisance, the funny thing is individual large files have no problem transferring (like a 4gb video).  If any one can tell me how to collect logs I'd post some if needed.

Edit:
Data abort
at 30053884
(domain0, fault8)
address 0xA00000BF

is what the player says upon unmounting.

[Chronon]

I didn't see a relevant bug report in the tracker.  Care to post one for this? 

[themapleboy]

Just did, never made a formal bug report before; wasn't sure all too sure what to include.
http://www.rockbox.org/tracker/task/12059

[vsl2005]

This may be overly simplistic, but I was experiencing similar random unmounts w my e260. After reformatting the device and reinstalling Rockbox several times I assumed the unit was dying.  I had purchased a cable accessory kit aftermarket for very cheap and was using one of the included cables. As a last resort I tried another cable and that fixed it. No problems since.

Using Win7 64bit.

Cheers!