From owner-freebsd-questions@freebsd.org Thu Mar 1 14:58:29 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D9292F31F9C for ; Thu, 1 Mar 2018 14:58:28 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from inet08.hamilton.harte-lyne.ca (inet08.hamilton.harte-lyne.ca [216.185.71.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "inet08.hamilton.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2F31B69FE3 for ; Thu, 1 Mar 2018 14:58:27 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from localhost (localhost [127.0.0.1]) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTP id 4D16662559; Thu, 1 Mar 2018 09:58:27 -0500 (EST) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from inet08.hamilton.harte-lyne.ca ([127.0.0.1]) by localhost (inet08.hamilton.harte-lyne.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yRhj7oJZoox8; Thu, 1 Mar 2018 09:58:25 -0500 (EST) Received: from webmail.harte-lyne.ca (inet04.hamilton.harte-lyne.ca [216.185.71.24]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTPSA id C65F06254D; Thu, 1 Mar 2018 09:58:24 -0500 (EST) Received: from 216.185.71.44 (SquirrelMail authenticated user byrnejb_hll) by webmail.harte-lyne.ca with HTTP; Thu, 1 Mar 2018 09:58:25 -0500 Message-ID: <4a1d519581de35e96e95747ea9336177.squirrel@webmail.harte-lyne.ca> In-Reply-To: References: Date: Thu, 1 Mar 2018 09:58:25 -0500 Subject: Re: usb memory sticj recovery From: "James B. Byrne" To: "tech-lists" Cc: freebsd-questions@freebsd.org Reply-To: byrnejb@harte-lyne.ca User-Agent: SquirrelMail/1.4.22-5.el6 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Mar 2018 14:58:29 -0000 On Wed, February 28, 2018 13:54, tech-lists wrote: > On 28/02/2018 16:19, James B. Byrne via freebsd-questions wrote: >> I have a usb memory stick whose filesystem FreeBSD will not mount >> because it is 'dirty'. It is dirty because it was removed from the >> FreeBSD host it was connected to. I would would like to recovery >> this >> device if possible but my attempts to do so using fsck and fsck_ffs >> never start because it cannot find a SUPERBLOCK. >> >> newfs -N gives a list of alternate sb location but fsck_ffs will not >> acept them. >> >> Is there any way to manually turn ff the dirt bit and mount the >> device? >> >> > > man 8 mount: > > [...] > > -f > > Forces the revocation of write access when trying to downgrade a > file system mount status from read-write to read-only. Also > forces the R/W mount of an unclean file system (dangerous; use with > caution). This did not succeed. I do not have the exact message any more so I cannot provide the reason stated. > > [...] > > alternatively dd the device to an image and mount the image at /mnt > using mdconfig Also did not work. Messages were: mount -t msdosfs /dev/`mdconfig -f /root/usb_pki_master.img` /mnt mount_msdosfs: /dev/md2: Invalid argument mount -t ext3 /dev/`mdconfig -f /root/usb_pki_master.img` /mnt mount: /dev/md3: Operation not supported by device mount -t ufs /dev/`mdconfig -f /root/usb_pki_master.img` /mnt mount: /dev/md4: Invalid argument -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3