From owner-freebsd-questions@freebsd.org Wed Feb 28 18:54:22 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 82119F3CF4D for ; Wed, 28 Feb 2018 18:54:22 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 2860C87BC2 for ; Wed, 28 Feb 2018 18:54:21 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id A74B32086A for ; Wed, 28 Feb 2018 13:54:20 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Wed, 28 Feb 2018 13:54:20 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=89QwUJ9cA0UERHZ9BEUwBm7a5Tn58 VhcPIlmZIa+oGs=; b=iYG0g0a2lvIk2urA31Ui0tiePzqTBjyq8wf/ul1RN+Vci M6+QR5VxoTbZD24T4P2tCg24ao5VqAq2DGsVqRRxORESfw8r0xbA9SZ+04f1HPb/ spEK5f1lpIXf/CexAdzm8X3YquRcXXi7DIOcecyjwQ3DpNkXSEO9AKC7R111NkB1 SzLCwPcVOVodaP7U7DY6QD4VX1d/H2XdIvMI3JkFMNGO/1DsVTZXKsJ8nu+oj9Vo 1FJWGDCH6lp8WmCmun4mz6eClo1WX8yjpQoKzWbFIQiHx3ycmMTaoXi4fZHThejO 6Hie7hAzsmhNGHCtTz/xr9qZ0AwqAUzkwlx0YoxlQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=89QwUJ 9cA0UERHZ9BEUwBm7a5Tn58VhcPIlmZIa+oGs=; b=hSKGvY669n0+HpBfHWJL4s wuPVV6GgvYMafY33dY/ae/99dZLxwFNMeh4bf7bVP/Tczps5oEHn3TQWjFX9ftyQ Y7u/on2Y2b141xNnxDc62MLHCNl2VQEFqhIgRw+7VrTZM8eEj9Is2nz7o88YQk6m w8qGI4nz4057wg5YzayWjBtKUAyOeksq0c1Hjrt985Q/kHM+Lm0MDCugU4Pog+71 n6fBLYJg8pFahsONSEv7HVJ31T9hHG4keVyrihgfnIPtmJ29FbeKQTeaHsm4vQlL 4+ykuJR/etHZDaWdJGNvGwsqBI5e1PemZO0bEPkSsTeLbXGgELzzkkE0Za3JlDxQ == X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 401862482D for ; Wed, 28 Feb 2018 13:54:20 -0500 (EST) Subject: Re: usb memory sticj recovery To: freebsd-questions@freebsd.org References: <470b77caf7d85febfa79244b761af019.squirrel@webmail.harte-lyne.ca> From: tech-lists Message-ID: Date: Wed, 28 Feb 2018 18:54:19 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <470b77caf7d85febfa79244b761af019.squirrel@webmail.harte-lyne.ca> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit 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: Wed, 28 Feb 2018 18:54:22 -0000 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). [...] alternatively dd the device to an image and mount the image at /mnt using mdconfig -- J.