Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mira.net.au!inquo!news.uoregon.edu!news1.mpcs.com!bbs.mpcs.com!hgoldste From: hgoldste@bbs.mpcs.com (Howard Goldstein) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: HEEELP! Installation of 2.1.0 :^( Date: 21 Jan 1996 12:13:56 GMT Organization: disorganization Lines: 48 Message-ID: <4dtam4$d1r@news1.mpcs.com> References: <SOUCHU.96Jan16101815@batman.news.u-psud.fr> Reply-To: hg@n2wx.ampr.org NNTP-Posting-Host: bbs.mpcs.com X-Newsreader: slrn (0.8.0) On 16 Jan 1996 09:18:15 GMT, Nicolas Souchu <souchu@batman.news.u-psud.fr> wrote: : My EIDE controller is a Promise 2300+, HD WD Caviar 420 (989/15/56). : A IDE CDROM is connected to the secondary controller (I don't use : it for installation, just floppies). : : Ok, I boot with boot.flp, -c and I choose my drivers. : : Then I install. No problem, but the first boot from HD fails ( : the boot prompt appears but boot fails). : : I've tried many things : : - DOS-compatible-partitioning : - DOS-incompatible-partitioning (whole disk for FreeBSD, using : 'A' option when partitioning and labeling) : : The emergency shell (ALT-F4) works fine. With the fixit disk, : I can mount my partitions without any problem. : : But during install, something seems to go wrong : my HD should receive : 840 sectors per cylinder and sysinstall calculates about 4096 sectors : per cylinder or something else, it warns me and makes a newfs -b 8192 : -u 4096 !! :^( Thats why, I think, the bootstrap program can't find : /kernel, no ? I don't have an answer but I'd like to report a similar problem on a non-EIDE drive, a 400mb maxtor 986/16/52. Many of the figures went by too quickly for my little hands to write but the stuff on vty2 reported on one label creating a filesystem with 4096 sectors on one cyl and 1 track and the other 65536 sectors on 16 cyl and 1 track. This is in a setup preserving a DOS partition and using FreeBSD's boot manager. Unlike Nicolas though I get good boots. The attempt to check the filesystem for bad blocks failed though (hung up), here too I forget the exact message but it was swap related [on a 5mb system] -- Howard Goldstein <hg@n2wx.ampr.org> http://www.tapr.org/~n2wx/