Subject: Re: Is this a new disk problem?
To: Henry B. Hotz <hotz@jpl.nasa.gov>
From: Colin Wood <cwood@ichips.intel.com>
List: port-mac68k
Date: 07/09/1998 15:25:41
Henry B. Hotz wrote:
> At 12:52 PM -0700 7/9/98, Dr. Bill Studenmund wrote:
> >What does disklabel say for sd3?
>
> 6 partitions:
> # size offset fstype [fsize bsize cpg]
> a: 1226685 795 unknown # (Cyl. 1 - 1543)
> b: 81885 1227480 unknown # (Cyl. 1544 - 1646)
> c: 1309735 0 unused 0 0 # (Cyl. 0 - 1647*)
> d: 370 1309365 unknown # (Cyl. 1647 - 1647*)
> e: 328 96 unknown # (Cyl. 0*- 0*)
> f: 371 424 unknown # (Cyl. 0*- 0*)
> disklabel: boot block size 0
> disklabel: super block size 0
You did say that this contains NetBSD partitions, right? I'd say
something was definitely wrong with the formatting here....did you zap
these with Mkfs?
> Also for reference sd0 gives:
> 2 partitions:
> # size offset fstype [fsize bsize cpg]
> a: 437642 96 4.2BSD 0 0 0 # (Cyl. 0*- 1683*)
> b: 41612 437738 HFS # (Cyl. 1683*- 1843*)
> disklabel: boot block size 0
> disklabel: super block size 0
> disklabel: warning, unused partition c: size 479350 offset 0
This looks more normal
> sd1 gives:
> 2 partitions:
> # size offset fstype [fsize bsize cpg]
> b: 164075 64 swap # (Cyl. 0*- 932*)
> disklabel: boot block size 0
> disklabel: super block size 0
> disklabel: warning, unused partition c: size 164139 offset 0
as does this
> And sd2 gives:
> 4 partitions:
> # size offset fstype [fsize bsize cpg]
> a: 451 96 unknown # (Cyl. 0*- 1*)
> b: 75524 950396 HFS # (Cyl. 1740*- 1878*)
> c: 1025920 0 unused 0 0 # (Cyl. 0 - 1878*)
> d: 949849 547 unknown # (Cyl. 1*- 1740*)
> disklabel: boot block size 0
> disklabel: super block size 0
But this would probably also be a problem (assuming that 'a' and 'd' are
actually NetBSD partitions). What did you use to set these up?
--
Colin Wood cwood@ichips.intel.com
Component Design Engineer - PMD Intel Corporation
-----------------------------------------------------------------
I speak only on my own behalf, not for my employer.