Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 28 Feb 2018 18:54:19 +0000
From:      tech-lists <tech-lists@zyxst.net>
To:        freebsd-questions@freebsd.org
Subject:   Re: usb memory sticj recovery
Message-ID:  <d21d56a6-64a4-1798-4fdc-4e1954d3057b@zyxst.net>
In-Reply-To: <470b77caf7d85febfa79244b761af019.squirrel@webmail.harte-lyne.ca>
References:  <470b77caf7d85febfa79244b761af019.squirrel@webmail.harte-lyne.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
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.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d21d56a6-64a4-1798-4fdc-4e1954d3057b>