*BSD News Article 28343


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!convex!convex!cs.utexas.edu!howland.reston.ans.net!vixen.cso.uiuc.edu!newsrelay.iastate.edu!news.iastate.edu!musik
From: musik@iastate.edu (Soli Deo Gloria)
Newsgroups: comp.os.386bsd.questions
Subject: NetBSD: Having weird fdisk/disklabel problems...
Date: 10 Mar 1994 06:24:12 GMT
Organization: Iowa State University, Ames, IA
Lines: 69
Distribution: world
Message-ID: <2lmeec$afa@news.iastate.edu>
NNTP-Posting-Host: avatar.cc.iastate.edu

Here's what's happening...
_Each_ time (of four so far) that I've installed NetBSD, the following
situation occurs.  fdisk (including the DOS version and the Norton diskedit
version) etc., shows the partition table as following...
With totally bogus values...

******* Working on device /dev/rwd0d *******
parameters extracted from in-core disklabel are:
cylinders=683 heads=16 sectors/track=38 (608 blks/cyl)

parameters to be used for BIOS calculations are:
cylinders=683 heads=16 sectors/track=38 (608 blks/cyl)

Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 0 is:
<UNUSED>
The data for partition 1 is:
<UNUSED>
The data for partition 2 is:
<UNUSED>
The data for partition 3 is:
sysid 165,(386BSD)
    start 0, size 50000 (24 Meg), flag 80
	beg: cyl 0/ sector 1/ head 0;
	end: cyl 1023/ sector 63/ head 255

Now here's the output from disklabel.  This _is_ correct, as far as I know,
as it reflects the parameters I gave the installation program.


# /dev/rwd0d:
type: ST506
disk: MAX_LXT
label: 
flags:
bytes/sector: 512
sectors/track: 38
tracks/cylinder: 16
sectors/cylinder: 608
cylinders: 683
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0		# milliseconds
track-to-track seek: 0	# milliseconds
drivedata: 0 

4 partitions:
#        size   offset    fstype   [fsize bsize   cpg]
  a:   164160   210368    4.2BSD     1024  8192    16 	# (Cyl.  346 - 615)
  b:    40736   374528      swap                    	# (Cyl.  616 - 682)
  c:   204896   210368    unused        0     0       	# (Cyl.  346 - 682)
  d:   415264        0    unused        0     0       	# (Cyl.    0 - 682)


Now... if I go and change the partition table with fdisk or any other
util, it can't boot... change it back to the bogus values, no problem.
But, of course, I can't install DOS with those bogus values out there.
Help!  Any ideas? Hints? Suggestions?
Yes, I've read the FAQ section on partitioning...
It doesn't cover this particular issue...

Thanks a mil, folx!
Damien Guay
-- 
Soli Deo Gloria
musik@iastate.edu