Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 09 Dec 1998 20:34:08 +0000
From:      curtis <ufkartfm@pacific.net>
To:        Wilko Bulte <wilko@yedi.iaf.nl>
Cc:        "freebsd-alpha@FreeBSD.ORG" <freebsd-alpha@FreeBSD.ORG>
Subject:   Re: installing boot?
Message-ID:  <366EDEC0.81429EB2@pacific.net>
References:  <199812092244.XAA01378@yedi.iaf.nl>

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

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

I set up my system to do an install and noticed the follwing
differences:

I show:

Waiting 15 seconds for SCSI devices to settle
de0: enabling 10baseT port
rootfs is 2880 da0 at ncr0 bus 0 target 0 lun 0           
da0: <TOSHIBA MK2526FB 908B> Fixed Direct Access SCSI-2 device 

You show:

Waiting 15 seconds for SCSI devices to settle
de0: autosense failed: cable problem?
da0 at ncr0 bus 0 target 0 lun 0  <---------8
da0: <DEC RZ28     (C) DEC T436> Fixed Direct Access SCSI2 device 
da0: 10.0MB/s transfers (10.0MHz, offset 8), Tagged Queueing Enabled
da0: 2007MB (4110480 512 byte sectors: 255H 63S/T 255C)
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?

If not, please try kern.flp and mfsroot.gz from a newer SNAP and see if
it produces the same printout.

I see from an older post you can get into your system (axp33#).

Please list your current /etc/fstab.

> So: kernel probes see the disk allright

In a previous post you show:

> dering UFS root f/s.
> da1: invalid primary partition table: no magic
> da1: raw partition size != slice size
> da1: start 0, end 4110479, size 4110480
> da1c: start 0, end 4092479, size 4092480

It does see the 'raw partition'.(see NetBSD install below)

In this post you show:

> (da1:ncr0:0:1:0): . CDB: 25 0 0 0 0 0 0 0 0 0 
> (da1:ncr0:0:1:0): NOT READY asc:4,2
> (da1:ncr0:0:1:0):  field replaceable unit: 1
> (da1:ncr0:0:1:0): fatal error, failed to attach to device
> (da1:ncr0:0:1:0): lost device
> (da1:ncr0:0:1:0): removing device entry

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 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.

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

> 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.

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.

(smile) I did notice a 2.5% fragmentation increase.

'Hang in there', Wilko and good luck,
-- 
curtis - ufkartfm@pacific.net - site administrator for Nobody
      I want Nobody to control my life!  How about you?
               http://www.netvideo.com/nobody

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?366EDEC0.81429EB2>