Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!ux1.cso.uiuc.edu!uwm.edu!caen!batcomputer!ghost.dsi.unimi.it!ipgaix!peppe From: peppe@ipgaix.unipg.it (G. Vitillaro) Subject: 386BSD installation (disklabel problem?) Message-ID: <1993May25.091223.133795@ipgaix.unipg.it> Keywords: 386BSD, installation, disklabel Organization: Universita' di Perugia Date: Tue, 25 May 1993 09:12:23 GMT Lines: 40 I'm trying to install 386bsd (the distribution kit) on my home machine, a 486DX 33Mhz clone, ISA bus and a LomgShine LCS-6631(F) SCSI controller emulating a WD 1003/1006. My installation disk is a Fujitsu M26225-512 320Mb, that my controller see as a 731 cyl, 16 tracks, 55 sectors (I checked with pfdisk). On this disk there is already a DOS partition going from Cyl 0 to Cyl 311 (for 134Mb). There is something of geometry remapping going on in the controller, but I think (from other OS experience) that is completely masked to the SW. The dist.fs boot weel and the install program finish fine, installing 386BSD on a 180Mb partition going from Cyl 312 to Cyl 730 (the 386BSD part is the 4th in the MBR if I remember correctly). When I try to boot from HD, 386BSD come up, but saying that it is unable to mount the root and obviously it panics. OK. I checked the partition using the fixit diskette and disklabel. Using disklabel I discovered that the label have wrong block labels and the geometry is wrong (1024 Cyl, instead of 731). I relabeled the disk using disklabel and the correct geometry and I was able to mount /dev/wd0a from the fixit diskette. At this point I thaught I found the problem, but at the next boot again paning. Rebooting the fixit and the label was again wrong. What may be a correct strategy to install 386BSD on my system? Thank in advance, Peppe -- Giuseppe Vitillaro - IBM SEMEA | E-Mail : peppe@ipgaix.unipg.it University of Perugia Italy | 06100 Perugia Phone:+39.75.585-2200 --------------------------------------------------------------------------- All comments/opinions are mine and don't represent those of IBM