A big thank-you to Christian Weisgerber -- your ASCII-art diagrams
explain the problem very clearly. (Otto Moerbeek's tweaks also help.)
I think having these in the FAQ would be a great idea!
In parallel (i.e., at about the same time, but without yet having seen
those messages), I decided to ret
Here's a patch to FAQ 14 and to FAQ 4. It encorporates
both Otto's recommended clarity improvement and Jason's recommended
reference in 4.6.3.
Index: www/faq/faq14.html
===
RCS file: /cvs/www/faq/faq14.html,v
retrieving revision 1.24
On 11/05/2014 06:42 AM, Josh Grosse wrote:
> On 2014-11-05 09:25, Christian Weisgerber wrote:
>
>> Here's a sketch:
>>
>>biosboot
>> :
>> MBR : disklabel
>> :: :
>> 0 : 1 64 : 65 : 66
>> |=|===
On Wed, Nov 05, 2014 at 09:42:42AM -0500, Josh Grosse wrote:
> On 2014-11-05 09:25, Christian Weisgerber wrote:
>
> >Here's a sketch:
> >
> > biosboot
> > :
> >MBR : disklabel
> > :: :
> > 0 : 1 64 : 65
On 2014-11-05 09:25, Christian Weisgerber wrote:
Here's a sketch:
biosboot
:
MBR : disklabel
:: :
0 : 1 64 : 65 : 66
|=|==|=|=|=|==|==>
|
On 2014-11-04, Jonathan Thornburg wrote:
> It's as if the 'a' partition I created (which started at offset 64) was
> actually overlapping the disklabel metadata!
Well, it does.
On architectures that use the MBR partition scheme, the disklabel
is located in the second sector of the OpenBSD area.
i just noticed an obvious stupid mistake of mine, the 'dd' should go before
the 'fdisk' as well (for the same reason as 'disklabel').
On Tue, 04 Nov 2014 07:04:23 -0500 thev...@openmailbox.org wrote:
> yes, you are zeroing the whole disklabel, which is located in the openbsd area
> starting at 32k
> If it's a new disk, you don't need to zero anything. That's to clean up
> previous RAID array data.
>
> That doesn't really answer the question of what is going wrong but at
> least it gets you up and running.
>
> Tim.
>
Well, I take it back. The FAQ does say to zero a crypto partition. I
nev
On Tue, Nov 4, 2014 at 12:53 AM, Brian McCafferty
wrote:
> On 11/03/14 22:33, Jonathan Thornburg wrote:
> > I'm trying to set up 5.6/amd64 on a new-from-the-factory 750GB disk
> > which I've just had installed in a Thinkpad T60. (This Thinkpad had
> > previously been running 5.5/amd64 using an o
On Tue, 04 Nov 2014 00:53:38 -0500 Brian McCafferty wrote:
> On 11/03/14 22:33, Jonathan Thornburg wrote:
> > I'm trying to set up 5.6/amd64 on a new-from-the-factory 750GB disk
> > which I've just had installed in a Thinkpad T60. (This Thinkpad had
> > previously been running 5.5/amd64 using an
yes, you are zeroing the whole disklabel, which is located in the openbsd area
starting at 32k (or 64 sectors). make sure you do the 'disklabel' AFTER 'dd'.
if you do a 'dd if=/dev/sd0c bs=512 skip=64 count=2 | strings' and you should
see the disk's model number (after the disklabel has been confi
On 11/03/14 22:33, Jonathan Thornburg wrote:
> I'm trying to set up 5.6/amd64 on a new-from-the-factory 750GB disk
> which I've just had installed in a Thinkpad T60. (This Thinkpad had
> previously been running 5.5/amd64 using an older/smaller disk, with
> no problems).
>
> I want to try having t
I'm trying to set up 5.6/amd64 on a new-from-the-factory 750GB disk
which I've just had installed in a Thinkpad T60. (This Thinkpad had
previously been running 5.5/amd64 using an older/smaller disk, with
no problems).
I want to try having the entire new disk secured with softraid crypto.
So, I bo
13 matches
Mail list logo
