From owner-freebsd-questions@FreeBSD.ORG Fri Oct 16 00:08:14 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 55FA2106568F for ; Fri, 16 Oct 2009 00:08:14 +0000 (UTC) (envelope-from af.gourmet@videotron.ca) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.freebsd.org (Postfix) with ESMTP id 2DC718FC15 for ; Fri, 16 Oct 2009 00:08:14 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=UTF-8 Received: from [192.168.0.51] ([96.21.103.185]) by VL-MR-MR001.ip.videotron.ca (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTP id <0KRK00C2ZYY6HC30@VL-MR-MR001.ip.videotron.ca> for freebsd-questions@freebsd.org; Thu, 15 Oct 2009 20:06:07 -0400 (EDT) Message-id: <4AD7B8F0.20903@videotron.ca> Date: Thu, 15 Oct 2009 20:06:08 -0400 From: PJ User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) To: Polytropon References: <4AD79FE4.6010109@videotron.ca> <20091016012610.99efbf26.freebsd@edvax.de> In-reply-to: <20091016012610.99efbf26.freebsd@edvax.de> Cc: freebsd-questions@freebsd.org Subject: Re: usb key problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Oct 2009 00:08:14 -0000 Polytropon wrote: > On Thu, 15 Oct 2009 18:19:16 -0400, PJ wrote: > >> I am running 7.2 but cannot properly attach/detach cruze 8gb and 4gb USB >> keys. >> When inserted, generate errors: >> da0 seems to be read correctly >> but then comes arow of >> (probe0:umass-sim0:0:0:1): snip CAM Status: SCSI Status Error >> snip NOT READY asc:3a,0 >> Medium not present >> Unretryable error >> then >> cd0 at umass-sim0 dada,dada,dada >> attempt to query device size failed; UNIT ATTENTION, Not ready to ready >> change, medium may have changed >> >> # camcontrol devlist >> at scbus1 target 0 lun 0 (da0,pass0) >> same as above ----- --------------------------- lun 1 (pass1,cd0) >> > > It would be good if you provide the full dmesg lines that > are corresponding with this problem. > > By the way, I had problems with "defective by design" SanDisk > USB sticks, too. This is how it looked: > > % dmesg | tail > umass0: on uhub2 > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Removable Direct Access SCSI-0 device > da0: 40.000MB/s transfers > da0: Attempt to query device size failed: UNIT ATTENTION, Medium not present > umass0: at uhub2 port 2 (addr 2) disconnected > (da0:umass-sim0:0:0:0): lost device > (da0:umass-sim0:0:0:0): removing device entry > umass0: detached > > I could not access the stick, /dev/da0 was the only device > that appeared, and I could only dump the partition table > (in terms of "DOS primary partitions", i. e. slices) with > the "fdisk da0" command. But I could not access it. > > Finally, I printed out dmesg on a line printer (looks very > impressing), marked the lines shown above and returned it to > the shop. I'm now happy with a Sony USB stick which works > excellently. > > > > >> Something is not functioning & I don't understand. It did function a >> while (some weeks) ago but now, no go... >> > > It did function, and now no more? I would say that if you didn't > change anything on your system, the SanDisk stick is broken. > > Could you try the stick in another system for reference? > > > > >> I did look on the web, but... >> ???? >> > > Did you see a spider that made the web? :-) > Yeah, and it scared the shit out of me... ;-) Anyway, I found the solution on the web... couldn't belive it was that simple: just ignore the crap spewed out on the screen and just mount iit as you would any other disk. # mount -t msdosfs /dev/da0s1 /mnt and that's it I don't know if it makes any difference, but I did delete everything on the key and formatted with Fat32. That got rid of everything and only took up 4k instead of 32 when not formatted and I could put my own label on the disk. Yea! Now to see how I can use it to restore stuff. :-D