From owner-freebsd-current@FreeBSD.ORG Mon Apr 26 02:21:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 225EF16A4CE for ; Mon, 26 Apr 2004 02:21:56 -0700 (PDT) Received: from smtp.covadmail.net (mx07.covadmail.net [63.65.120.67]) by mx1.FreeBSD.org (Postfix) with SMTP id 757D443D5C for ; Mon, 26 Apr 2004 02:21:55 -0700 (PDT) (envelope-from strick@covad.net) Received: (covad.net 10826 invoked from network); 26 Apr 2004 09:21:50 -0000 Received: from unknown (HELO mist.nodomain) (strick@covad.net@67.101.100.236) by sun-qmail13 with SMTP; 26 Apr 2004 09:21:49 -0000 Received: from mist.nodomain (localhost [127.0.0.1]) by mist.nodomain (8.12.9p2/8.12.9) with ESMTP id i3Q9Lqwk001329; Mon, 26 Apr 2004 02:21:53 -0700 (PDT) (envelope-from dan@mist.nodomain) Received: (from dan@localhost) by mist.nodomain (8.12.9p2/8.12.9/Submit) id i3Q9Lq4x001328; Mon, 26 Apr 2004 02:21:52 -0700 (PDT) (envelope-from dan) Date: Mon, 26 Apr 2004 02:21:52 -0700 (PDT) From: Dan Strick Message-Id: <200404260921.i3Q9Lq4x001328@mist.nodomain> To: solskogen@carebears.mine.nu cc: current@freebsd.org Subject: Re: mounting msdosfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Mon, 26 Apr 2004 09:21:56 -0000 On Sat, 17 Apr 2004 10:56:55 +0200, Christer Solskogen wrote: >> > I got two msdosfs(fat32) partitions on my machine. > I can mount them without any problems, but fsck wont work. > > # fsck_msdosfs /dev/ad0s5 > ** /dev/ad0s5 > backup doesn't compare to primary bootblock > > I did a clean FreeBSD 5.2.1 install(not upgraded or anything) > > ... >> I have the same problem. It turns out that fsck_msdosfs works with fat32 file systems created by Win98 but not those created by WinXP. I run FreeBSD 4.9. I assumed that the problem was that the fsck_msdosfs in 4.9 was not being kept up to date and that the problem was possibly already fixed in release 5.x. (I guess not.) Dan Strick strick@covad.net