From owner-freebsd-usb@FreeBSD.ORG Fri Mar 23 05:14:16 2012 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 413551065673 for ; Fri, 23 Mar 2012 05:14:16 +0000 (UTC) (envelope-from day1234@hotmail.com) Received: from col0-omc1-s1.col0.hotmail.com (col0-omc1-s1.col0.hotmail.com [65.55.34.11]) by mx1.freebsd.org (Postfix) with ESMTP id 1FA1A8FC14 for ; Fri, 23 Mar 2012 05:14:15 +0000 (UTC) Received: from COL112-W35 ([65.55.34.9]) by col0-omc1-s1.col0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 22 Mar 2012 22:14:09 -0700 Message-ID: X-Originating-IP: [70.56.215.44] From: "J.J. Day" To: Date: Fri, 23 Mar 2012 05:14:08 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 23 Mar 2012 05:14:09.0041 (UTC) FILETIME=[C6C26810:01CD08B3] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: USB Flash drive problem with 9.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2012 05:14:16 -0000 I am upgrading a FreeBSD server and have encountered a problem with=20 mounting a USB flash drive. The system was on 6.3 and I upgraded to 9.0=20 using CVS repositories. The flash drive worked properly at all steps=20 throughout the upgrade. However=2C after the OS upgrade was complete=2C I=20 made a mistake and destroyed some of the server application. So=2C I set the=20 upgraded drive aside=2C copied the original source drive to a different spa= re=2C and=20 repeated the upgrade process taking care to verify the functioning of=20 the applications during the process. When I finished the second time=2C eve= rything worked properly except for mounting the flash drive. it appears that something changed with the OS code that reads the drive fir= mware between the first time I ran cvsup on (about) the 9th and the second = time I ran it about the 18th. This is the output from the first upgrade (3/11/2012) when the drive is ins= erted: =09 ugen4.2: at usbus4 umass0: on usbus4 umass0: SCSI over Bulk-Only=3B quirks =3D 0x0100 umass0:2:0:-1: Attached to scbus2 da0 at umass-sim0 bus 0 scbus2 target 0 lun 0 da0: Removable Direct Access SCSI-4 device=20 da0: 40.000MB/s transfers da0: 30960MB (63406080 512 byte sectors: 255H 63S/T 3946C) And diskinfo output: =09 da0 512 # sectorsize 32463912960 # mediasize in bytes (30G) 63406080 # mediasize in sectors 0 # stripesize 0 # stripeoffset 3946 # Cylinders according to firmware. 255 # Heads according to firmware. 63 # Sectors according to firmware. AA22064F00000035 # Disk ident. This is the output from the second upgrade (3/18/2012) when the drive is in= serted: =09 ugen4.2: at usbus4 umass0: on usbus4 umass0: SCSI over Bulk-Only=3B quirks =3D 0x0100 umass0:2:0:-1: Attached to scbus2 da0 at umass-sim0 bus 0 scbus2 target 0 lun 0 da0: Removable Direct Access SCSI-4 device=20 da0: 40.000MB/s transfers da0: 17454747090944MB (71776119061217281 512 byte sectors: 64H 32S/T 0C) And diskinfo shows: =09 da0 512 # sectorsize -144115188075855360 # mediasize in bytes () -281474976710655 # mediasize in sectors 0 # stripesize 0 # stripeoffset -137438953471 # Cylinders according to firmware. 64 # Heads according to firmware. 32 # Sectors according to firmware. AA22064F00000035 # Disk ident. Since the size information is incorrect=2C the /dev/da0s1 device is not cre= ated and the drive cannot be mounted. The problem only happens with a large= drive. When I use a 4GB or 8GB drive=2C everything works correctly. If there is any information that I can submit that can assist in solving th= e problem please let me know. Thanks=2C JJ =