Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 12 Sep 1995 23:20:53 -0700 (PDT)
From:      Julian Elischer <>
Subject:   Re: Disk corruption problems in 2.0.5R (CDROM)?
Message-ID:  <>
In-Reply-To: <> from "Scott Blachowicz" at Sep 12, 95 06:21:55 pm

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
> 	free inode /usr/20096 had -268370322 blocks

are you sure that the DOS filesystems know that they end at the end 
of their slice...
if you shrink a DOS partition, but don't re-format the 'drive', then dos will
happily allocate blocks in the next slice
(well what used to belong to it)
I believe 'fips' can fix that..

your fdisk and disklabels look good..

> sd0s2  - swap (shared between Linux & FreeBSD, or at least that's the goal)
hmmm,  a C partition, and it's right after the swap too..

>    What are "npx0" and "lp0"? Or more generally, where do I look to find
>    out what a particular device/controller designation refers to?
lp0 is a the lp port.. npx is the numeric coprocessor..
check /usr/src/sys/i386/conf/LINT
> 4) For my sd0, I've seen C/H/S numbers of 1009/43/63 reported by pfdisk
>    under DOS and 3053/43/63 from the FreeBSD fdisk. Huh? That makes no
>    sense. That's the first time I've noticed THAT discrepancy. It's a
>    1.4Gb (roughly) disc, so the first set of numbers makes more
>    sense. Hmmm...maybe I ran that fdisk command after the corruption
>    occurred, so maybe the "in-core disklabel" was corrupt?
ignore the # cylinders..
what does boot -v say about BIOS geometries?
(use dmesg to see it after booting)

> I ran a bunch of commands (e.g. dmesg, disklabel, fdisk) and their output
> follows.
excellant.. unfortunatly I can't see anythong wrong there, 
unless the swap is going to the wrong BSD slice..
(hmm might this be a bug? )
(It MIGHT be untested code?)

> Help... (imagine a pathetic, tired little voice there...if I can't get
> past this, I might have to fall back to Linux or weed wacking my yard :-()
you seem to have done a very proffessional job of partitionning your disk
I can't fault it, unless the BIOS sees things differntly..


Want to link to this message? Use this URL: <>