Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.Hawaii.Edu!news.uoregon.edu!arclight.uoregon.edu!feed1.news.erols.com!howland.erols.net!news.bbnplanet.com!cam-news-hub1.bbnplanet.com!uunet!in1.uu.net!206.63.63.70!nwnews.wa.com!news1.halcyon.com!usenet From: "Duane H. Hesser" <dhh@androcles.com> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Disk crash problem...any ideas of what is going wrong? Date: Fri, 13 Dec 1996 22:03:36 -0800 Organization: Northwest Nexus Inc. Lines: 67 Message-ID: <32B24338.446B9B3D@androcles.com> References: <32AF6751.41C6@ucdavis.edu> <58qe96$jbi@anorak.coverform.lan> <32B0D1A0.41C6@ucdavis.edu> NNTP-Posting-Host: androcles.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.0Gold (X11; U; FreeBSD 2.1.6-RELEASE i386) Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:32576 Michael White wrote: > > Brian Somers wrote: > > > > In article <32AF6751.41C6@ucdavis.edu>, > > Michael White <mdwhite@ucdavis.edu> writes: > > [.....] > > : My filesystems (which are okay) are: > > : > > : Filesystem 512-blocks used avail cap. > > : /dev/wd1a 38974 31806 4052 89% / > > : /dev/wd1s1e 793790 265758 464530 36% /usr > > : procfs 8 8 0 100% /proc > > [.....] > > > > What about "disklabel wd1s1" - what does that say. This sounds a > > bit like overlapping partitions. > > > > -- > > Brian <brian@awfulhak.demon.co.uk>, <brian@freebsd.org> > > <http://www.awfulhak.demon.co.uk/> > > Don't _EVER_ lose your sense of humour.... > > . > That looks suspicious: here it is: > ======================================================================= > #disklabel wd1s1 > > type: EDSI > disk: wd1s1 > label: > flags: > bytes/sector: 512 > sectors/track: 63 > tracks/cylinder: 16 > sectors/cylinder: 1008 > cylinders: 2099 > sectors/uint: 2116737 > 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: 40960 0 4.2BSD 0 0 0 #(cyl. 0-40*) > b: 131072 40960 4.2BSD #(cyl. 40*-170*) > c:2116737 0 unused 0 0 #(cyl. 0-2099*) > e: 819200 172032 4.2BSD 0 0 0 #(cyl. 170*-983*) > f:1125505 991232 4.2BSD 0 0 0 #(cyl. 983*-2099*) > ====================================================================== > > Now, I only set up 4 partitions (/, swap, /usr, /u) which look to > correspond to a,b,e & f above. Where on earth c came from is beyond > me. Any ideas of what is happening (& why & how to fix)? Thanks > for the time. > -- > - Mike > mdwhite@ucdavis.edu 'c' is, by convention, the whole disk. not a problem. -- Duane H. Hesser dhh@androcles.com