L. V. Lammert wrote:
At 03:10 PM 8/23/2006 -0400, Nick Guenther wrote:
On 8/23/06, Andreas Maus <[EMAIL PROTECTED]> wrote:
Hello everybody.
# disklabel wd1
16 partitions:
# size offset fstype [fsize bsize cpg]
a: 234372222 63 4.2BSD 0 0 0 # Cyl
0*-232512*
c: 234375000 0 unused 0 0 # Cyl
0 -232514*
My first guess is that something is wiping out the disklabel on wd1.
That is, some boundary is configured wrong and, in the process of
writing to the ccd, sometimes it "spills over" and smashes the
disklabel. In that case you'd also be losing whatever data is getting
put there when you fix the disklabel.
PMFJI, but since when is a disk label bigger than 64 sectors?
Lee
It isn't, but the disklabel isn't at sector zero of the DISK (that's the
MBR), it is near the beginning of the PARTITION.
SO..if you put the ccd partition starting at offset 0 within the OpenBSD
partition, you can clobber the OpenBSD partition's disklabel.
In fact, that is what the OP says he did, by using ccd0c for data, he
put the ccd partition information on top of the OpenBSD disklabel...
which is not a good thing.
Unfortunately, there is a quirk in the ccd(4) driver which creates a
bogus disklabel that must be 'D'efaulted before it can be used, so it is
an easy error to make.
Nick.
