From owner-freebsd-questions@FreeBSD.ORG Mon Jul 21 16:31:47 2008 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A60B9106566B for ; Mon, 21 Jul 2008 16:31:47 +0000 (UTC) (envelope-from crtb@cape.com) Received: from mrelay1.cape.com (mrelay3.cape.com [216.237.97.20]) by mx1.freebsd.org (Postfix) with ESMTP id 6FB138FC1B for ; Mon, 21 Jul 2008 16:31:47 +0000 (UTC) (envelope-from crtb@cape.com) Received: from tomato (209-213-65-25.meganet.net [209.213.65.25]) by mrelay1.cape.com (Postfix) with ESMTP id 262D728139; Mon, 21 Jul 2008 12:11:28 -0400 (EDT) Date: Mon, 21 Jul 2008 12:15:35 -0400 (EDT) From: Charles Bacon X-X-Sender: crtb@tomato.local To: questions@freebsd.org Message-ID: <20080721115525.N38345@tomato.local> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Chuck Bacon Subject: Have I poisoned something in USB filesystems? 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: Mon, 21 Jul 2008 16:31:47 -0000 I have 2 mem sticks and several CF cards from a Nikon Coolpix camera. In the past I've freely used these both ways, through USB. My OS is, via uname -a: FreeBSD daisy.local 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 10:35:36 UTC 2008 root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 I had a problem with a new 4GB CF card which wouldn't mount in an audio recorder (M-Audio Microtrack), and tried formatting it using the recorder's own formatter. OK so far. But it wouldn't mount on my FreeBSD. So I perhaps unwisely tried working from scratch, rebuilding the MBR (copied from /boot/mbr) and using fdisk from there. Now I can mount it and all the other (photo) CF cards, but xv(1) for the first time complains of *.jpg saying: : "Corrupt JPEG data: premature end of data segment" and quits. At one time I guessed perhaps badly that I should use fdisk with powers of two and rebuild a CF card with 64 heads and 32 sectors; let the #cyls fall out. Looks good, but now fdisk on all my USB CF cards says those are the numbers unless I use fdisk -i -t. Yet I can reboot. When I do, CF cards still mount and are still not viewable with xv. something strange has happened and I wonder if some persistent data regarding msdosfs structures has been written. I had hoped that #cyl, #head, #sec values would be ignored in favor of LBA, but I guess I'm wrong. Any ideas? Chuck Bacon -- crtb@cape.com ABHOR SECRECY -- DEFEND PRIVACY