From owner-freebsd-current@FreeBSD.ORG Wed Apr 9 18:30:59 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B7761065674 for ; Wed, 9 Apr 2008 18:30:59 +0000 (UTC) (envelope-from ml@t-b-o-h.net) Received: from vjofn.tucs-beachin-obx-house.com (vjofn-pt.tunnel.tserv1.fmt.ipv6.he.net [IPv6:2001:470:1f00:ffff::5e5]) by mx1.freebsd.org (Postfix) with ESMTP id F18B08FC12 for ; Wed, 9 Apr 2008 18:30:58 +0000 (UTC) (envelope-from ml@t-b-o-h.net) Received: (from tbohml@localhost) by vjofn.tucs-beachin-obx-house.com (8.14.2/8.14.2) id m39IUwxH071627; Wed, 9 Apr 2008 14:30:58 -0400 (EDT) From: Tuc at T-B-O-H Message-Id: <200804091830.m39IUwxH071627@vjofn.tucs-beachin-obx-house.com> To: peterjeremy@optushome.com.au (Peter Jeremy) Date: Wed, 9 Apr 2008 14:30:58 -0400 (EDT) In-Reply-To: <20080403180137.GE49813@server.vk2pj.dyndns.org> from "Peter Jeremy" at Apr 04, 2008 05:01:37 AM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, "Tuc at T-B-O-H.NET" Subject: Re: [freebsd-current] re: fsck_4.2bsd: cannot alloc 4294967292 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Apr 2008 18:30:59 -0000 > On Thu, Apr 03, 2008 at 08:51:53AM -0400, Tuc at T-B-O-H.NET wrote: > >not the drive... As soon as I mount the drive and try to create > >filesystems on it I get a kernel panic > >(http://www.freebsd.org/cgi/query-pr.cgi?pr=3D122380) > > > > I even brought a 7.0 system up elsewhere, formatted it there, > >and mounted it on the Soekris system, and as soon as I start to use > >it it panics. > > This sounds very much like data corruption between the flash and the > filesystem layer. > > How does the flash connect to valhalla? USB or card slot or ...? > Can you provide a verbose dmesg of da0 and all its parents? > Did you get that previously? Its a USB, and the dmesg is: http://204.107.90.128/dmesg.txt > Try dd'ing off the first 1MB or so using valhalla and also using one > of your other systems and compare the results. My suspicion is that > there is either an off-by-1-sector or similar error or you will find > valhalla is reading chunks of 0xff bytes where it shouldn't. > They matched.. Any thoughts where to go? Thanks, Tuc