Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 29 Jul 2017 11:03:31 +0200
From:      Polytropon <freebsd@edvax.de>
To:        byrnejb@harte-lyne.ca
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Unable to mount USB Flash memory created on CentOS
Message-ID:  <20170729110331.de4d61a5.freebsd@edvax.de>
In-Reply-To: <1686132f906448c4e88d02f865da9a14.squirrel@webmail.harte-lyne.ca>
References:  <aa1eadff2a815bacb69dc015b4aa1f4f.squirrel@webmail.harte-lyne.ca> <20170728205144.c1fc18df.freebsd@edvax.de> <4a5c3fd942ff8566eefaaf9c990abba0.squirrel@webmail.harte-lyne.ca> <20170728212432.7be758bc.freebsd@edvax.de> <32ee693f24a1725290b47822cfd8bc9e.squirrel@webmail.harte-lyne.ca> <20170728220016.21aa7c83.freebsd@edvax.de> <1686132f906448c4e88d02f865da9a14.squirrel@webmail.harte-lyne.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 28 Jul 2017 17:09:01 -0400, James B. Byrne wrote:
> # mount -t ext2fs -o ro /dev/da0s1 /mnt/usb01
> # mount -t ext2fs -o ro /dev/da1s1 /mnt/usb02
> 
> These both work on the second and third usb stick, the ones whose
> insertion seemed to trigger the problem.

Okay, good!



> This is the backup stick which was already inserted and mounted when
> the problem started:
> 
> # gpart list da0
> Geom name: da0
> modified: false
> state: OK
> fwheads: 255
> fwsectors: 63
> last: 122915327
> first: 63
> entries: 4
> scheme: MBR
> Providers:
> 1. Name: da0s1
>    Mediasize: 62928519168 (59G)
>    Sectorsize: 512
>    Stripesize: 0
>    Stripeoffset: 4128768
>    Mode: r0w0e0
>    attrib: active
>    rawtype: 12
>    length: 62928519168
>    offset: 4128768
>    type: !12
>    index: 1
>    end: 122915327
>    start: 8064
> Consumers:
> 1. Name: da0
>    Mediasize: 62932647936 (59G)
>    Sectorsize: 512
>    Mode: r0w0e0
> 
> 
> So what is type !12?  How would I mount it?

As I said in a previous message: That entry looks damaged, and
you probably cannot mount it anymore. Maybe recovery is possible
using native Linux programs, I suggest you give it a try.

In worst case, re-initialize the file system (at the price of
data loss, of course).


-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170729110331.de4d61a5.freebsd>