From owner-freebsd-fs@FreeBSD.ORG Sun Jan 18 00:36:40 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C830CAFC; Sun, 18 Jan 2015 00:36:40 +0000 (UTC) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 89E67F2C; Sun, 18 Jan 2015 00:36:40 +0000 (UTC) Received: from gjp by mail.in-addr.com with local (Exim 4.85 (FreeBSD)) (envelope-from ) id 1YCdr3-000Fd2-RU; Sun, 18 Jan 2015 00:36:37 +0000 Date: Sun, 18 Jan 2015 00:36:37 +0000 From: Gary Palmer To: Lev Serebryakov Subject: Re: Could mount_msdosfs be less cryptic and more compatible with fsck_msdosfs? Message-ID: <20150118003637.GB94793@in-addr.com> References: <54BAE6DE.3050206@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <54BAE6DE.3050206@FreeBSD.org> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Jan 2015 00:36:40 -0000 On Sun, Jan 18, 2015 at 01:49:02AM +0300, Lev Serebryakov wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > > I could not mount FAT32 image, but "fsck_msdosfs" says, that it is > valid, good FAT32 image. > > % sudo fsck_msdosfs /dev/md0 > ** /dev/md0 > ** Phase 1 - Read and Compare FATs > ** Phase 2 - Check Cluster Chains > ** Phase 3 - Checking Directories > ** Phase 4 - Checking for Lost Files > 7 files, 96256 free (188 clusters) > % sudo mount -t msdosfs /dev/md0 /mnt > mount_msdosfs: /dev/md0: Invalid argument > % > > I don't know what should I do to mount this image. > > I'm using 10-STABLE. Did you check dmesg? Sometimes filesystems give more detail in kernel logs than is possible through error codes. Gary