Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!crcnis1.unl.edu!wupost!cs.utexas.edu!koriel!lll-winken.llnl.gov!iggy.GW.Vitalink.COM!wetware!spunky.RedBrick.COM!psinntp!psinntp!newstand.syr.edu!rodan.acs.syr.EDU!smcarey From: smcarey@rodan.acs.syr.EDU (Shawn M Carey) Subject: Re: Those NetBSD hard-drive hangs... Message-ID: <1993Jul9.180852.1280@newstand.syr.edu> Organization: Syracuse University, Syracuse, NY References: <9319017.15979@mulga.cs.mu.OZ.AU> <1993Jul9.090546.23934@cs.utwente.nl> Date: Fri, 9 Jul 93 18:08:51 EDT Lines: 22 I am using 386bsd (patch-kit 0.2.4), and I recently had problems with the system hanging like you describe. What happened to me may not apply to NetBSD, but I thought you might like to know. I decided to set up my drive with "real" partitions, and I stumbled accross the "diskpart" command which I ended up using to make the partitions. One thing I noticed with the new partition scheme was that there were more sectors being used (ie. the c partition was larger) than with the old layout. I didn't think much of it until the system started hanging occasionally (this usually happened when the disk was trying to write something). Then I remembered the section in the diskpart manpage that mentioned certain disktab entries needing free space at the end of the disk for bad sector forwarding. Now, I don't use bad144, nor do I have the "sf" flag in my disktab entry, but forcing diskpart to only use the size of the original c partition seems to have solved the problem for me. It may be worth lookinng into your disktab entry to see if something like this is happening. From what I've heard about NetBSD, you make your own partitions when you install it. Hope this helps... -Shawn Carey