Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 10 Dec 1998 22:38:06 +0100 (CET)
From:      Wilko Bulte <wilko@yedi.iaf.nl>
To:        ufkartfm@pacific.net (curtis)
Cc:        freebsd-alpha@FreeBSD.ORG
Subject:   Re: installing boot?
Message-ID:  <199812102138.WAA02376@yedi.iaf.nl>
In-Reply-To: <366EDEC0.81429EB2@pacific.net> from curtis at "Dec 9, 98 08:34:08 pm"

next in thread | previous in thread | raw e-mail | index | archive | help
As curtis wrote...
> Did you have the disk problem before you began to 'build world'?

Nope.

> How does your 2nd scsi 'show' during the SRM "power-up script"?

They look OK, but also see my earlier mail about the spinup issue.

> rootcd0 at ncr0 bus 0 target 4 lun 0  <---------8
> cd0: <DEC RRD45   (C) DEC 1645> Removable CD-ROM SCSI2 device 
> cd0: 4.237MB/s transfers (4.237MHz, offset 8)
> cd0: Attempt to query device size failed: NOT READY, 
> fs is 2880 (da1:ncr0:0:1:0): . CDB: 25 0 0 0 0 0 0 0 0 0  <---------8
> (da1:ncr0:0:1:0): NOT READY asc:4,2
> 
> On the ones I marked <---------8, was this because of cut and paste?


> Because it removes the device entry, it does not see da1 ; however, as
> Kenneth D. Merry mentioned "it looks like da0 is working fine..".

The spinup thingie it seems.

> The first thing I would check (if the drive is not recognized under SRM)
> is the scsi cable and make sure it is plugged in all the way.

Cables were OK, as was SRM.

> What do you have on da0 and do you mount it as /dev/sd0a or /dev/da0a?

...eh.... Digital Unix ;-)

> > About the NetBSD remark: I first installed Freebsd/axp when there was
> > not yet a working Freebsd boot floppy out there. So, the harddisk still
> > has the NetBSD boot bits on it.
> 
> (smile) This is how I started too and the reason I mentioned it. Here is
> a snip from one of my old posts.
> 
> > NetBSD boot floppies and setting up FreeBSD. -  I feel there should be
> > a note in the .org/alpha section that explains this method is no longer
> > used.  I have seen posts to the list where folks (including me) had set
> > up their systems this way & had problems with later FreeBSD installs.

Hear hear ;-)

> I experienced similar problems (as yours) when I moved everything to
> 3.0.
> Previous to this I was under 2.2.6, moved to 2.2.7, and had used the
> NetBSD install method.
> 
> Under 3.0, and when I got a working kern.flp & mfsroot.gz that took me
> to a working /stand/sysintall Main Menu, I ran into similar problems.
> Here is what Mike Smith told me:
> 
> > You are trying to run a mismatched sh/kernel pair; one is a FreeBSD 
> > binary, one is a NetBSD binary.  Boot from the NetBSD install floppy 
> > again and make sure that you have both from the same source.
> 
> Which was a big clue. The ONLY way (for me) to get around this was to
> re-format my drive.  I figured this out after I did a second NetBSD
> install and it put me back to the same place.   A re-format (for me) was
> the only way it would accept a 'clean' FreeBSD install and disk problems
> have gone away.

Sysinstall is currently doing it's thing so lets see what happens.

Wilko
_     ______________________________________________________________________
 |   / o / /  _  Bulte 				  email: wilko@yedi.iaf.nl 
 |/|/ / / /( (_) Arnhem, The Netherlands          WWW  : http://www.tcja.nl
______________________________________________ Powered by FreeBSD __________

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812102138.WAA02376>