Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!vixen.cso.uiuc.edu!roundup.crhc.uiuc.edu!uivlsisd.csl.uiuc.edu!terry From: terry@uivlsisd.csl.uiuc.edu (Terry Lee) Newsgroups: comp.os.386bsd.questions Subject: Re: Anyone successful with UltraStor 12F use??? Date: 13 Nov 1993 22:18:33 GMT Organization: Coordinated Science Lab., Univ. of Illinois at Urbana-Champaign Lines: 42 Message-ID: <2c3mfpINNh8v@roundup.crhc.uiuc.edu> References: <1993Nov10.171540.18089@mksol.dseg.ti.com> <CGCEvM.6Bs@news.cis.umn.edu> <2bvam4$fln@vixen.cso.uiuc.edu> NNTP-Posting-Host: uivlsisd.csl.uiuc.edu rodeen@maroon.tc.umn.edu (Rick Odeen) writes: >In article <1993Nov10.171540.18089@mksol.dseg.ti.com>, >Bob Myers <bmyers@asd470.dseg.ti.com> wrote: >>I've been trying to install FreeBSD (Gamma, Epsilon, Release, even with >>the kcopy-altwd disk) and have yet to be able to sucessfully get a >>/dev/rwd0e to be created successfully. I'm using the Ultrastor 12f with >>a 345 mb esdi drive that has 18 bad spots. seems that the root partition >>can be created successfully, but there is a major problem with creating >>the usr file structure on my system. During the boot off the hard disk, >>i enter an endless loop that complains about an inconsistancy on this >>partition, that fsck must be run manually, and that an automatic reboot >>will occur (and yet never does). >> ... >I'm probably one of those "other two" people and my symptoms are identical. >I've tried all possible combinations of setting with the controller and >placement of FreeBSD on the drive including starting at cyl 0 and 1. > >Has anyone used NetBSD with this controller? Is this just a problem with >FreeBSD? I'd swear I used this controller back in the bad ol' days of >386BSD 0.1, but it may have been an Adaptec ESDI controller. I am running a system with an UltraStor 12F and used to have the same symptom. The problem, I think, is that bad144 -s fails to pick up the bad sectors marked by the controller. I don't know if this is only on the 12F or on all ST506-type controllers. How I got around this is to edit the "install" file on filesystem-floppy and comment out the line that says "bad144 $drive 0". You can do this either by mounting filesystem-floppy and using vi (if you have a working system) or by binary editing the filesystem-floppy image (using a Sun workstation, for example). This prevents install from wiping out any existing bad144 list. Next, create the bad144 list manually. First, let install create the proper disk label for you. Then run bad144 -s wd0 manually, and write down the bad block numbers reported by the kernel. Add the bad blocks to the bad144 list manually (bad144 -a wd0 blk1 blk2 ...). Run install again, and this time it should install OK. Good luck! -- Terry Lee (terry@uivlsi.csl.uiuc.edu) Coordinated Science Lab University of Illinois