From owner-freebsd-questions@freebsd.org Tue Aug 1 06:58:10 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3AF70DB7FCF for ; Tue, 1 Aug 2017 06:58:10 +0000 (UTC) (envelope-from datasmurf@mail.ru) Received: from fallback.mail.ru (fallback6.mail.ru [94.100.181.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 83E4567513 for ; Tue, 1 Aug 2017 06:58:08 +0000 (UTC) (envelope-from datasmurf@mail.ru) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru; s=mail2; h=Content-Transfer-Encoding:Content-Type:Mime-Version:References:In-Reply-To:Message-Id:Subject:To:From:Date; bh=MiH7eEpSY9qnCQ3gV5K496muU8pzchzkTvMTmRhjYMg=; b=fOmuPR8xlxPqFzeI13N/unkQL5hoZ7gF10jHdlfYyRuP2sVhWtAvLsojO1euBk56LTAfxSX+zcvyDPeEN5XSHDGtUkfwICK4FsNXFPhiONdCQ0pPKM8T0QvOvmPH4xKo7PjDKjFFF8Br0uhPAiMtmZqrhdpTkd748uc4K6zI6VA=; Received: from [10.161.25.37] (port=55926 helo=smtp60.i.mail.ru) by fallback6.mail.ru with esmtp (envelope-from ) id 1dcR80-0003LA-DW for freebsd-questions@freebsd.org; Tue, 01 Aug 2017 09:58:04 +0300 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru; s=mail2; h=Content-Transfer-Encoding:Content-Type:Mime-Version:References:In-Reply-To:Message-Id:Subject:To:From:Date; bh=MiH7eEpSY9qnCQ3gV5K496muU8pzchzkTvMTmRhjYMg=; b=fOmuPR8xlxPqFzeI13N/unkQL5hoZ7gF10jHdlfYyRuP2sVhWtAvLsojO1euBk56LTAfxSX+zcvyDPeEN5XSHDGtUkfwICK4FsNXFPhiONdCQ0pPKM8T0QvOvmPH4xKo7PjDKjFFF8Br0uhPAiMtmZqrhdpTkd748uc4K6zI6VA=; Received: by smtp60.i.mail.ru with esmtpa (envelope-from ) id 1dcR7r-0006aY-WC for freebsd-questions@freebsd.org; Tue, 01 Aug 2017 09:57:56 +0300 Date: Tue, 1 Aug 2017 08:56:23 +0200 From: Datasmurf To: freebsd-questions@freebsd.org Subject: Re: Unable to mount USB Flash memory created on CentOS Message-Id: <20170801085623.611a65933badaaaa31bcf1da@mail.ru> In-Reply-To: <72688c988dae728f8fe92593aa464dc7.squirrel@webmail.harte-lyne.ca> References: <20170728223744.a94ce254.freebsd@edvax.de> <20170729110144.1cce7c70.freebsd@edvax.de> <72688c988dae728f8fe92593aa464dc7.squirrel@webmail.harte-lyne.ca> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; amd64-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-7FA49CB5: 0D63561A33F958A552C10446081F943A0FB198A8D90C0D81EB732653D2204D93725E5C173C3A84C3D27EA2B1546FA1FC1D0E62BE7A39628EB344165809136645C4224003CC836476C0CAF46E325F83A50BF2EBBBDD9D6B0F20A889B128FC2D163B503F486389A921A5CC5B56E945C8DA X-Mailru-Sender: 94EAD701BF8768C03D039424890234D1C78D85EAE2BB13E2B343D00D05882DFB575867FEF4FB1C0A05F5843394B6D2FA07A8E8AA53D06C71B46DB209221C5EA56A10A1D2956C07803CD5A379DB4F65C1A110CCB9F05026F93453F38A29522196 X-Mras: OK X-Mras: OK X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Aug 2017 06:58:10 -0000 On Mon, 31 Jul 2017 11:49:52 -0400 "James B. Byrne via freebsd-questions" wrote: > Lest it be lost in the minutiae of solving this difficulty I thank you > for all your help. > > > On Sat, July 29, 2017 05:01, Polytropon wrote: > > > > I'd suggest you use the Linux native fsck (e2fsck). If I > > remember correctly, there is also an "ext2 fsck" in the > > port e2fsprogs with the same name. > > > > Or maybe it came with FUSE? > > > > Basically, you'd so something like > > > > # fsck -t ext2 /dev/da1 > > > > or, as I mentioned, > > > > # e2fsck /dev/da1 > > > > An automatic file system type detection relies on an entry > > in /etc/fstab, which you don't have, so you need to specify > > the FS type manually. > > > > > > When I try to verify the flash drives I see this: > > # e2fsck /dev/da1 > e2fsck 1.43.4 (31-Jan-2017) > ext2fs_open2: Bad magic number in super-block > e2fsck: Superblock invalid, trying backup blocks... > e2fsck: Bad magic number in super-block while trying to open /dev/da1 > . . . > > So I redid the command using the partition values instead: > > # e2fsck /dev/da0s1 > e2fsck 1.43.4 (31-Jan-2017) > CA_HLL_2016_BKUP has gone 267 days without being checked, check > forced. Pass 1: Checking inodes, blocks, and sizes > Pass 2: Checking directory structure > Pass 3: Checking directory connectivity > Pass 4: Checking reference counts > Pass 5: Checking group summary information > Error writing file system info: Invalid argument > > CA_HLL_2016_BKUP: ***** FILE SYSTEM WAS MODIFIED ***** > > However, the device remains unmountable in Mate. You have to be careful and choose the correct superblock. run e2fsck with -b option as root. I had similar problems with external HDD's in the past. But using the correct superblock with the fsck command fixed it. e2fsck -b 32768 /dev/da0s1 Reading man e2fsck won't hurt too. -- #irc - real netizens last resort