From owner-freebsd-questions@FreeBSD.ORG Tue Jun 12 20:55:07 2012 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 77141106578F for ; Tue, 12 Jun 2012 20:55:07 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id D01718FC15 for ; Tue, 12 Jun 2012 20:55:06 +0000 (UTC) Received: from mart.js.berklix.net (p5DCBF61D.dip.t-dialin.net [93.203.246.29]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id q5CKt535057898; Tue, 12 Jun 2012 20:55:05 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id q5CKsrWA050199; Tue, 12 Jun 2012 22:54:53 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id q5CKsfMf090296; Tue, 12 Jun 2012 22:54:47 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201206122054.q5CKsfMf090296@fire.js.berklix.net> To: "O. Hartmann" From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Tue, 12 Jun 2012 21:31:46 +0200." <4FD79922.50106@zedat.fu-berlin.de> Date: Tue, 12 Jun 2012 22:54:41 +0200 Sender: jhs@berklix.com Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD 10/9: Lexar 64GB JumpDrive USB 2.0 isn't recognized anymore! 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: Tue, 12 Jun 2012 20:55:07 -0000 > I have a Lexar 64GB USB 2.0 JumpDrive which worked in its "pristine" or > "virgine" state very well. I used it yesterday, brand new, to fill it up > with data. Some 30GB data got stored, I shut down the system (FreeBSD > 10.0-CURRENT/amd64) and this morning, I put the USB drive out of the USB > port (computer off) and took it to the office. > > At the office, neither a FreeBSD10.0-CURRENT box nor a FreeBSD > 9.0-STABLE box (both moth recent buildworld) where able to recognize the > drive! While the USB drive was recognized as /dev/da1s1 before, this > time I see in the console something like this: > > ugen7.6: at usbus7 > umass1: on usb= > us7 > > And nothing further anymore. > > On a Linux box (Suse) the USB drive can be read as well as on a Windows > 7 box (I only read the content, I didn't write onto the USB drive on > both systems). > > What is up? Since Windows and Linux can read/recognize the drive and > FreeBSD not, I guess FreeBSD does have a problem with that kind of 64GB > drive. > > I do not care of the data on the USB drive, so I'd like to GPART it. But > without having a device node created, this is very unlikely to achieve. > > Any suggestions? > > Please CC my email, I'm not subscribing this specific list. Think hardware power cabling bad socket, Power available from socket. Power doubler (twin plug) cables. external powered hub I have some towers here cant power some discs. I have one powered hub here, has an extremely weak power supply, Its not always the OS that bites you, but hardware too. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below not above, cumulative like a play script, & indent with "> ". Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. Mail from @yahoo dumped @berklix. http://berklix.org/yahoo/