Sansa clip+ cannot be mounted in MSC mode

Details:

Firmware: v01.01.05A

Settings --> USB mode --> MSC

Just bought the clip+ today.  I picked it up over the ipod mainly so that I could treat it as any old fat formatted hard drive and not bother worrying about all the proprietary apple stuff. 

Well… I cant mount the partition.  I can’t even sucessfully read the partition table.  I have not tried this on windows but have tested several other operating systems/PCs so it is not machine or OS specific. Are there issues with the clip+ not going to MSC mode when selected?  The minimum sys requirements say USB 2.0… is there a technical reason for this? Has this been tested with USB 1?  I’m going to test this on some higher spec machines tomorrow and also in Windows.  If this magically works in Windows -that is it doesnt turn out to be the old machines I 'm using (USB1) … I’m probably going to return it.

Don’t have a Clip+ to play with yet, but I have had no problems with V1 and V2 Clips. I can connect to those in MSC mode on a Windows 98 machine with USB1 ports and a universal USB driver loaded. It also worked on the E200s, C200s, Fuze and View. The file transfers are very slow. The View was a bit inconsistent (works much better in MTP mode on a XP machine), but all the other series worked fine.

So… this doesn’t work on any non windows machine I’ve tested.  I’m assuming that is because its not switching to MSC mode though short of using mtpfs or something I’m not sure how to confirm this.  I’m not terribly familiar with MTP in general.  Works fine in Windows XP.  I see the sdhc device (empty) and then in the onboard partition I see ‘Audible’, ‘Audiobooks’, ‘Music’, ‘Podcasts’, sys files etc.  I must mount half a dozen different removable devices on a weekly basis on various linux and unix boxes without issue.  I’m a little disapointed atm and will probably try to backup the partition table and redo it to see if that fixes the issue.

Message Edited by thrush on 10-25-2009 04:43 PM

Some people have it working with Linux. See: http://forums.sandisk.com/sansa/board/message?board.id=clipplus&thread.id=17

Or search clip+ linux.

If the above won’t work, you might want to try giving SanDisk Customer Service a call.  I’m kinda wondering, if all fails, if the unit might be defective.  By any chance, do you have a Windows PC handy to try the Clip in MSC mode out on?

You can try manually selecting MSC.


With the new Clip+ , this procedure is slightly different from the previous version, as we have no mechanical Hold switch.

  • Start with the Clip+ ON or OFF.
  • Press and HOLD the center botton, then:
  • Plug in the Clip+.   You can release the button once it begins communicating. It will be in MSC mode.
  • After the communication session, after powering down, the device will revert to the previously selected mode.

Bob  :smileyvery-happy:

Message Edited by neutron_bob on 01-04-2010 07:43 PM

I have the same problem with my new sansa clip+ 8gb.

The firmware is the latest, 01.02.16.

I put the clip in the msc mode but if I connect it to my pc, with archlinux as os, the message of the kernel is:

Jan 19 23:55:15 darkstar kernel: scsi10 : usb-storage 1-4.4:1.0
Jan 19 23:55:15 darkstar mtp-probe: checking bus 1, device 39: “/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-4/1-4.4”
Jan 19 23:55:15 darkstar mtp-probe: bus: 1, device: 39 was not an MTP device
Jan 19 23:55:16 darkstar kernel: scsi 10:0:0:0: Direct-Access SanDisk Sansa Clip+ 8GB v01. PQ: 0 ANSI: 0
Jan 19 23:55:16 darkstar kernel: sd 10:0:0:0: Attached scsi generic sg0 type 0
Jan 19 23:55:16 darkstar kernel: scsi 10:0:0:1: Direct-Access SanDisk Sansa Clip+ 8GB v01. PQ: 0 ANSI: 0
Jan 19 23:55:16 darkstar kernel: sd 10:0:0:1: Attached scsi generic sg1 type 0
Jan 19 23:55:16 darkstar kernel: sd 10:0:0:0: [sdb] 15462400 512-byte logical blocks: (7.91 GB/7.37 GiB)
Jan 19 23:55:16 darkstar kernel: sd 10:0:0:0: [sdb] Write Protect is off
Jan 19 23:55:16 darkstar kernel: sdb:
Jan 19 23:55:16 darkstar kernel: sd 10:0:0:1: [sdc] Attached SCSI removable disk
Jan 19 23:55:16 darkstar kernel: sd 10:0:0:0: [sdb] Attached SCSI removable disk


if I check the partition table I see:


Disk /dev/sdb: 7916 MB, 7916748800 bytes

244 heads, 62 sectors/track, 1022 cylinders, total 15462400 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System

???   # seems that the partition lost!!!


lsusb command confirm that the clip is connected as msc:


darkstar mnt # lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 028: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 029: ID 045e:0750 Microsoft Corp. Wired Keyboard 600
Bus 001 Device 030: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse (M-BT58)
Bus 001 Device 039: ID 0781:74d1 SanDisk Corp. Sansa Clip+ (msc)


When I plug a microsd card fdisk show me:


Disk /dev/sdb: 7916 MB, 7916748800 bytes
244 heads, 62 sectors/track, 1022 cylinders, total 15462400 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System

Disk /dev/sdc: 15.9 GB, 15931539456 bytes
255 heads, 63 sectors/track, 1936 cylinders, total 31116288 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sdc1 8192 31116287 15554048 c W95 FAT32 (LBA)


I have connect the clip with my windows pc and I haven’t problem neither in the mtp mode neither in msc mode.

What is the problem?

Thanks at all

I have installed gparted for testing the drive and the result is:

http://imageshack.us/photo/my-images/809/gpartedscreenshot01.jpg/

http://imageshack.us/photo/my-images/43/gpartedscreenshot02.jpg/

http://imageshack.us/photo/my-images/856/gpartedscreenshot03.jpg/

The partition sda1 seems have some problems; dosfstools and mtools are installed.

In Windows7 I haven’t the same error, in fact the partition (sda=7Gb) is reading without errors and named SANSA CLIPP

If I format the partition with gparted from linux in fat32, I can reinstall the OF without problems? What is the procedure?

Thanks

Sounsa like you’re trying awful hard to break it. If it’s new, why not just return it and get another one? They are warrantied after all.

Sounds like you’re trying awful hard to break it beyond repair. If it’s new, why not just return it and get another one? They are warrantied after all.

If it mounts in Windows but not in linux, its probably a bug in your distro or USB driver.

With Ubuntu live cd the drive is recognized.

In fact the drive manager show me this:

internal memory named as /dev/sdc: http://imageshack.us/photo/my-images/813/schermatasandisksansacl.png/

external memory named as /dev/sdd1: http://imageshack.us/photo/my-images/828/schermatasandisksansacl.png/

The difference is that /dev/sdc is not partitioned, but ubuntu mount ti on /media/0123-4567 without problem.

The sd card is well partitioned, the type of the partition is W95 FAT32 (LBA) (0x0C), so the kernel mount it on /media/3437-6235.

If I use fdisk to format the internal memory, after is possible to install the original firmware or rockbox firmware?

Thanks