Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 3 Dec 2006 21:04:51 -0600
From:      ajm <ajm91qw@sbcglobal.net>
To:        freebsd-questions@freebsd.org
Subject:   Re: umass mount woes
Message-ID:  <20061204030451.GA741@powerfull.bsd>
In-Reply-To: <469123.56791.qm@web56508.mail.re3.yahoo.com>
References:  <469123.56791.qm@web56508.mail.re3.yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Dec 03, 2006 at 02:56:12PM -0800, Neil Short wrote:
> I got a new whiz-bang mp3 play from SanDisk. I went
> with SanDisk because they have always worked so well
> with non-windows for me.
> 
> Anyway, I'm having a bit of a problem mounting it.
> Other umass devices work fine on my system. Any help
> will be appreciated. The device is a Sansa c240. as a
> usb device, it doesn't default to umass behavior; but
> it can be set to behave that way. I have set the
> device USB mode to MSC mode.
> 
> Some sample system behavior:
> 
> [root@carmen ~]# uname -a
> FreeBSD carmen.opera 7.0-CURRENT FreeBSD 7.0-CURRENT
> #0: Wed Nov 29 22:46:47 MST 2006    
> root@carmen.opera:/usr/obj/usr/src/sys/CARMEN  i386
> 
> ... so I plug in a jump drive. Stdout shows:
> 
> umass0: <LEXAR MEDIA JUMPDRIVE, class 0/0, rev
> 2.00/30.00, addr 2> on uhub2
> (probe0:umass-sim0:0:0:0): Uninitialized Transport
> 5:e44a4b24?
> da0 at umass-sim0 bus 0 target 0 lun 0
> da0: <LEXAR JUMPDRIVE 1000> Removable Direct Access
> SCSI-0 device 
> da0: 40.000MB/s transfers
> da0: 991MB (2030592 512 byte sectors: 64H 32S/T 991C)
> 
> Now I can do the following:
> [root@carmen ~]# mount -t msdos /dev/da0s1 /mnt
> [root@carmen ~]# mount
> /dev/ad4s1a on / (ufs, local)
> devfs on /dev (devfs, local)
> /dev/ad4s1e on /tmp (ufs, local, soft-updates)
> /dev/ad4s1f on /usr (ufs, local, soft-updates)
> /dev/ad4s1d on /var (ufs, local, soft-updates)
> /dev/da0s1 on /mnt (msdosfs, local)
> [root@carmen ~]# umount /mnt
> 
> ... I then unplug that device and plug in the mp3
> player. Stdout:
> umass0: <SanDisk Sansa c240, class 0/0, rev 2.00/7.20,
> addr 2> on uhub2
> (probe0:umass-sim0:0:0:0): Uninitialized Transport
> 5:c412049c?
> da0 at umass-sim0 bus 0 target 0 lun 0
> da0: <SanDisk Sansa c240 Sans> Removable Direct Access
> SCSI-0 device 
> da0: 40.000MB/s transfers
> da0: 979MB (2006528 512 byte sectors: 64H 32S/T 979C)
> (probe0:umass-sim0:0:0:1): Uninitialized Transport
> 5:c045de9c?
> da1 at umass-sim0 bus 0 target 0 lun 1
> da1: <SanDisk Sansa c240 Sans> Removable Direct Access
> SCSI-0 device 
> da1: 40.000MB/s transfers
> da1: Attempt to query device size failed: NOT READY,
> Medium not present
> (da1:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0
> 0 0 0 0 0 0 
> (da1:umass-sim0:0:0:1): CAM Status: SCSI Status Error
> (da1:umass-sim0:0:0:1): SCSI Status: Check Condition
> (da1:umass-sim0:0:0:1): NOT READY asc:3a,0
> (da1:umass-sim0:0:0:1): Medium not present
> (da1:umass-sim0:0:0:1): Unretryable error
> Opened disk da1 -> 6
> (da1:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0
> 0 0 0 0 0 0 
> (da1:umass-sim0:0:0:1): CAM Status: SCSI Status Error
> (da1:umass-sim0:0:0:1): SCSI Status: Check Condition
> (da1:umass-sim0:0:0:1): NOT READY asc:3a,0
> (da1:umass-sim0:0:0:1): Medium not present
> (da1:umass-sim0:0:0:1): Unretryable error
> Opened disk da1 -> 6
> (da1:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0
> 0 0 0 0 0 0 
> 
> So I then attempt to mount it:
> 
> [root@carmen ~]# mount -t msdos /dev/da0s1 /mnt
> mount_msdosfs: /dev/da0s1: Invalid argument
> [root@carmen ~]# mount -t msdos /dev/da1 /mnt
> mount_msdosfs: /dev/da1: Device not configured
> [root@carmen ~]# mount -t msdos /dev/da0 /mnt
> mount_msdosfs: /dev/da0: Invalid argument
> [root@carmen ~]# ls /dev/da*
> /dev/da0        /dev/da0s1      /dev/da0s2     
> /dev/da1
> [root@carmen ~]# mount -t msdos /dev/da0s1 /mnt
> mount_msdosfs: /dev/da0s1: Invalid argument
> 
> ...
> 
> any ideas?
> Thanks for checking out my plight.
> 
> -N
> 

Some players have a way to format the memory.  Check your owners manual.
Since the MSC was not the default...it could be it needs formating.

-- 
Alexander
FreeBSD 6.0-RELEASE i386



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061204030451.GA741>