Date: Sat, 23 Apr 2005 19:26:01 -0400 From: Mike Jeays <Mike.Jeays@rogers.com> To: Fridtjof Busse <fbusse@gmx.de> Cc: freebsd-questions@freebsd.org Subject: Re: Mounting USB-stick Message-ID: <1114298761.7355.19.camel@chaucer> In-Reply-To: <20050423214149.7e0afbd7.fbusse@gmx.de> References: <20050423214149.7e0afbd7.fbusse@gmx.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 2005-04-23 at 15:41, Fridtjof Busse wrote: > Hi > I've got a problem with mounting a USB-stick on FreeBSD 5.4-RC3 (and > according to google I'm not the only one, but noone seems to have had > the problem I have): > If I plug the stick in, I get lots of > > Apr 23 21:26:08 fbsd kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI > Status Error > Apr 23 21:26:08 fbsd kernel: (da0:umass-sim0:0:0:0): SCSI Status: > Check Condition > Apr 23 21:26:08 fbsd kernel: (da0:umass-sim0:0:0:0): UNIT ATTENTION > asc:3a,0 > Apr 23 21:26:08 fbsd kernel: (da0:umass-sim0:0:0:0): Medium not > present > Apr 23 21:26:08 fbsd kernel: (da0:umass-sim0:0:0:0): Retrying > Command (per Sen se Data) > Apr 23 21:26:08 fbsd kernel: (da0:umass-sim0:0:0:0): READ CAPACITY. > CDB: 25 0 0 0 0 0 0 0 0 0 > [...] > > It ends with > > Apr 23 21:26:08 fbsd kernel: (da0:umass-sim0:0:0:0): Retries Exhausted > Apr 23 21:26:08 fbsd kernel: Opened disk da0 -> 6 > > Now I have /dev/da0, but no /dev/da0s1. > No matter what I try with camcontrol, I don't get da0s1. > By accident I found out that after I mount /dev/da0 (which of course > doesn't give me any files on the stick) and umount it, I get /dev/da0s1. > What's going on/wrong and how can I fix it? I don't need amd, so I'd be > happy about a simple solution, if there's any. > Thanks! :) Run fdisk on the drive, and see where the partitions are. I have found cases where the fourth partition holds the data, and you can mount it with 'mount -t msdos /dev/da0s4 /mnt'. Running fdisk with no parameters won't do any damage - but see below. In other cases of trouble, try 'camcontrol devlist' to get a list of which device numbers have been assigned. It isn't always da0. (As a digression, I experimented with recreating partition tables using fdisk and a configuration file, until the day I forgot to enter the 'da0' as the final parameter, and it wiped the disk partition on my dual-boot system disk. Easily the worst case of finger trouble I have had to date).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1114298761.7355.19.camel>