On Mon, 8 May 2000, Michael Kukat wrote:

> On Sun, 7 May 2000, Chuck McManis wrote:
[newer snapshot at:]
> > ftp://ftp.neurotica.com/pub/os/NetBSD/vax/1.4x-24APR00/
> 
> But this doesn't have the KA660 support in it, i think. And the soures i used
> were the last tarballs, which i found to be compileable, except the bootblock,
> i didn't get it fixed for compiling.
> 
[Marc Schneiders wrote:]
> > > Netbooting and installing works alright. I do not seem to be able to
> > > get bootblocks written to the disk though. Well none that work.
> 
> I use my 4000/300 by getting the booter via MOP and telling it
> boot ra(0)netbsd
> to continue. The system is on disk, the booter comes from the network. Works
> very fine this way. Disk is a RF71 on a KFQSA.
> 

Thanks, a great idea :-) I tried it, but the booter doesn't like my
disklabel and gives an error message:

getdisklabel: no disk label.

The disklabel looks like this:

vax# disklabel -r ra1
# /dev/rra1c:
type: MSCP
disk: RA82
label: vaxbsd
flags:
bytes/sector: 512
sectors/track: 67
tracks/cylinder: 14
sectors/cylinder: 938
cylinders: 1359
total sectors: 1274742
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 1           # milliseconds
track-to-track seek: 0  # milliseconds
drivedata: 0 

8 partitions:
#        size   offset     fstype   [fsize bsize   cpg]
a:   204800        0     4.2BSD     1024  8192    16   
  # (Cyl.    0- 218*)
b:   196608   204801       swap                        
  # (Cyl.  218*- 427*)
c:  1274742        0     unused        0     0         
  # (Cyl.    0- 1358)
d:   873334   401408     4.2BSD     1024  8192    16   
  # (Cyl.  427*- 1358) 

For the record, disk works otherwise fine (can be mounted and used).
I've had another look at man disklabel and /etc/disktab and noticed
the number of sectors (etc) in disktab differs from what I had in my
disklabel as well as the names of the partitions (a, b, c, d
versus a, b, h, g). So I tried to follow man instructions very closely
(I had not done a *new* label on the above disk, but merely edited
it with disklabel -i) and labeled an empty disk (ra2) with:

disklabel -w -r ra2 ra82

Then I changed the partitions to suit my needs, gave it a name (both
with disklabel -i) and this is the result:

vax# disklabel -r ra2
# /dev/rra2c:
type: MSCP
disk: ra82
label: ra2
flags:
bytes/sector: 512
sectors/track: 57
tracks/cylinder: 15
sectors/cylinder: 855
cylinders: 1423
total sectors: 1216665
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0           # milliseconds
track-to-track seek: 0  # milliseconds
drivedata: 0 

8 partitions:
#        size   offset     fstype   [fsize bsize   cpg]
  a:   204800        0     4.2BSD     1024  8192    16   
# (Cyl.    0- 239*)
  b:    98304   204801       swap                        
# (Cyl.  239*- 354*)
  c:  1216665        0     unused     1024  8192         
# (Cyl.    0- 1422)
  d:    15884   375345     unused      512  4096         
# (Cyl.  439- 457*)
  e:   307200   391590     unused     1024  8192         
# (Cyl.  458- 817*)
  f:   517275   699390     unused     1024  8192         
# (Cyl.  818- 1422)
  g:    94361  1122304     4.2BSD     1024  8192    16   
# (Cyl. 1312*- 1422)
  h:   819200   303104     4.2BSD     1024  8192    16   
# (Cyl.  354*- 1312*)

After a newfs on a, g and h I expected things to work. But booting
from this drive (still empty I know) after loading the bootloader 
through MOP gives me the same error:

>boot ra(2)netbsd
getdisklabel: no disk label
nfs_open: must mount first
Boot failed: Device not configured

Disk *is* ok. I just ftp-ed tcsh and lynx packages to it and installed
them from there.
--
Marc Schneiders --- marc@venster.nl --- marc@vrijdom.com

FreeBSD propro.freebeastie.org 5.0-CURRENT