From owner-freebsd-sparc64@FreeBSD.ORG Tue Jun 30 09:38:12 2009 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 036E21065670 for ; Tue, 30 Jun 2009 09:38:12 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe10.swipnet.se [212.247.155.33]) by mx1.freebsd.org (Postfix) with ESMTP id 55DE48FC0C for ; Tue, 30 Jun 2009 09:38:11 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=3W9nIpSlnLoA:10 a=gg2W7PyvkLb8p4ie143lBA==:17 a=bd3dSubjuKLhHN1Of64A:9 a=KGmBr3qKyMzKW7BECO4A:7 a=ZID33FF8_twxhpauDgNQixx-x1oA:4 a=rMF7JWUDq7kA:10 a=3O3SN4BzDi2WpXVh:21 a=pEEoSdhRxZUyVQHI:21 Received: from [194.248.135.20] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe10.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 1099128278; Tue, 30 Jun 2009 10:38:08 +0200 From: Hans Petter Selasky To: freebsd-sparc64@freebsd.org Date: Tue, 30 Jun 2009 10:37:38 +0200 User-Agent: KMail/1.11.4 (FreeBSD/8.0-CURRENT; KDE/4.2.4; i386; ; ) References: <4A444374.3090008@apz.fi> <4A445143.1090503@acm.poly.edu> In-Reply-To: <4A445143.1090503@acm.poly.edu> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200906301037.40138.hselasky@c2i.net> Cc: Ari =?iso-8859-1?q?Sovij=E4rvi?= Subject: Re: "cg 0: bad magic number" with umass X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jun 2009 09:38:12 -0000 On Friday 26 June 2009 06:40:35 Boris Kochergin wrote: > Ari Sovij=E4rvi wrote: > > Hi folks! > > > > I added a 1 terabyte USB harddisk to my Fire V100 for backups. I have > > recently used the same device with Linux and with i386 FreeBSD. I > > zeroed the disk and labeled it with sunlabel. However, newfs always > > dies with the error "cg 0: bad magic number". I also tried to label it > > into several smaller chunks, no luck. > > > > I also tried to newfs the whole device without a disklabel, but that > > also ends with the same error. > > > > Here's an example of the outcome, with 1 gigabyte partition: > > # newfs /dev/da0b > > /dev/da0b: 1027.6MB (2104512 sectors) block size 16384, fragment size > > 2048 > > using 6 cylinder groups of 183.72MB, 11758 blks, 23552 inodes. > > super-block backups (for fsck -b #) at: > > 160, 376416, 752672, 1128928, 1505184, 1881440 > > cg 0: bad magic number > > > > Here's bits of the dmesg, showing the drive: > > umass0: > 2> on uhub0 > > da0 at umass-sim0 bus 0 target 0 lun 0 > > da0: Fixed Direct Access SCSI-2 device > > da0: 1.000MB/s transfers > > da0: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C) > > > > Any ideas of what's wrong? > > I had the same problem on an i386 machine with an onboard USB 1.1 > controller some time ago, using external Seagate disks. I Googled around > and found that the error message means that newfs tried to read back > something it wrote near the beginning of the filesystem when it created > it, but the contents were not what it expected. After making sure that > it worked with my laptop's ICH6 USB controller--which it did--I > dismissed the onboard controller as faulty, bought a PCI VT6202 > controller, and it's worked great ever since. Could you show the dmesg of the USB controller? At which bus is it connecte= d?=20 Nexus? There might be bugs in the actual USB device/host hardware. You could also try enabling USB debugging for umass: sysctl hw.usb.umass.debug=3D-1 And look for any errors. Are you using 8-current ? =2D-HPS