Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 26 Oct 2002 00:43:58 -0400
From:      John De Boskey <jwd@freebsd.org>
To:        Current List <freebsd-current@freebsd.org>
Subject:   5.0 disklabel warnings against 4.7 disk
Message-ID:  <20021026044358.GA96714@BSDWins.Com>

next in thread | raw e-mail | index | archive | help
Hi,

   I've (re)scanned my -current folder for issues related
to the following but didn't see a good match. Pointing
out my blindness is allowed if this was discussed...

   I have a system onto which I installed a 4.7-RC a couple
of weeks ago. I then upgraded that newly installed system
to -current.

   After the upgrade, disklabel now complains about
every disk in the system, for example:

# disklabel -r ad6s1
# /dev/ad6s1c:
type: unknown
disk: amnesiac
label: 
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 193820
sectors/unit: 195371505
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0           # milliseconds
track-to-track seek: 0  # milliseconds
drivedata: 0 

8 partitions:
#        size   offset    fstype   [fsize bsize bps/cpg]
  a: 195371505       63    4.2BSD     2048 16384 28512  # (Cyl.    0*- 193820*)
  c: 195371505       63    unused        0     0        # (Cyl.    0*- 193820*)
partition a: partition extends past end of unit
partition c: partition extends past end of unit
Warning, partition c doesn't start at 0!
Warning, An incorrect partition c may cause problems for standard system utilities
#

This is an fdisk'd drive, with the entire disk allocated to the
1st slice.

An identical disk (ad4):

ad4: 95396MB <WDC WD1000JB-32CWE0> [193821/16/63] at ata2-master UDMA100
ad6: 95396MB <WDC WD1000JB-32CWE0> [193821/16/63] at ata3-master UDMA100

which I then fdisk and disklabel under -current shows up as:

8 partitions:
#        size   offset    fstype   [fsize bsize bps/cpg]
  c: 195371505        0    unused        0     0        # (Cyl.    0 - 193820*)

The only difference being the offset of 0 (and lack of warning msgs).

Both systems come up with the same disk size, but the offsets not matching
seems to be a problem. An older 4.7 pre-release  system from Sep 16 creates
the 'c' slice with an offset of 0.  I don't think this is something I did
wrong. Any thoughts, comments, or pointy hats are welcome.

Thanks,
John

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




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