On 12/1/11 1:48 PM, Robert Huff wrote:
>
> Damien Fleuriot writes:
>
>> >> Try this:
>> >> gpart delete -i 1
>> >> gpart create -s 78g -i 1 -t freebsd-ufs /dev/ad1
>> >
>> > Done
>>
>> >>> gpart show ad1
>> > => 34 976773101 ad1 GPT (465G)
>> > 34 163577856
Damien Fleuriot writes:
> >> Try this:
> >> gpart delete -i 1
> >> gpart create -s 78g -i 1 -t freebsd-ufs /dev/ad1
> >
> >Done
>
> >>> gpart show ad1
> > => 34 976773101 ad1 GPT (465G)
> > 34 1635778561 freebsd-ufs (78G)
> > 163577890 813195245
On Thu, 01 Dec 2011 02:07:41 -0600, CyberLeo Kitsana wrote:
> On 11/30/2011 03:01 PM, Robert Huff wrote:
> >
> > One of my systems has a hot-swap eSATA device, which reports as
> > "ad1". I'm trying to use this to prepare a new disk using gpart and
> > something (possibly my understanding) is
On 11/30/2011 03:01 PM, Robert Huff wrote:
>
> One of my systems has a hot-swap eSATA device, which reports as
> "ad1". I'm trying to use this to prepare a new disk using gpart and
> something (possibly my understanding) is broken.
> After removing another disk and inserting the new o
On 12/1/11 4:51 AM, Robert Huff wrote:
>
> I'm not sure how, but I have achieved this:
>
>>> gpart show ad1
> => 34 976773101 ad1 GPT (465G)
> 34 9767731011 freebsd-ufs (465G)
>
> ... which is correct, except for the size.
> I have a new problem:
>
I'm not sure how, but I have achieved this:
>> gpart show ad1
=> 34 976773101 ad1 GPT (465G)
34 9767731011 freebsd-ufs (465G)
... which is correct, except for the size.
I have a new problem:
>> newfs /dev/ad1p1
newfs: wtfs: 512 bytes at sector 9
On 12/1/11 3:14 AM, Robert Huff wrote:
>
> Warren Block writes:
>
>> > One of my systems has a hot-swap eSATA device, which reports as
>> > "ad1". I'm trying to use this to prepare a new disk using gpart and
>> > something (possibly my understanding) is broken.
>> > After removing anot
Warren Block writes:
> >One of my systems has a hot-swap eSATA device, which reports as
> > "ad1". I'm trying to use this to prepare a new disk using gpart and
> > something (possibly my understanding) is broken.
> >After removing another disk and inserting the new one, I do:
> >
>
On Wed, 30 Nov 2011, Robert Huff wrote:
One of my systems has a hot-swap eSATA device, which reports as
"ad1". I'm trying to use this to prepare a new disk using gpart and
something (possibly my understanding) is broken.
After removing another disk and inserting the new one, I
On 11/30/11 11:28 PM, Robert Huff wrote:
>
> Damien Fleuriot writes:
>
>> >>> gpart destroy ad1
>> > gpart destroy ad1
>> > gpart: Input/output error
>> >
>> > Huh?
>>
>> Huh indeed.
>>
>> Please toggle GEOM debug and try again:
>>
>> sysctl kern.geom.debugflags=17
>
> gpart:
On 11/30/11 10:01 PM, Robert Huff wrote:
>
> One of my systems has a hot-swap eSATA device, which reports as
> "ad1". I'm trying to use this to prepare a new disk using gpart and
> something (possibly my understanding) is broken.
> After removing another disk and inserting the new o
11 matches
Mail list logo