In message <20030503215708.GA1479@zero>, you write: 

-> i'm trying to move everything to another drive, but i can't seem to make it
-> bootable. i've run sgivol -w boot /usr/mdec/boot sd1, but arc doesn't want
-> to boot it.
-> 
-> when i try to boot, it seems to exec the loader, but i get this:
-> 
-> Boot: scsi(1)disk(5)partition(0)netbsd
-> devopen: scsi(1)disk(5)partition(0) type scsi file netbsd
-> open scsi(1)disk(5)partition(0)netbsd: No such file or directory
-> Boot failed! Halting...

Is sd1 indeed id 5 on SCSI bus 1 -- whichever SCSI bus that happens to
be?  Even if that isn't a problem here, it may cause issues with the
kernel detecting the boot device later...

[..]
-> sd1 disklabel:
-> 4 partitions:
-> #        size    offset     fstype  [fsize bsize cpg/sgs]
->  a:   1541967      3605     4.2BSD   1024  8192   144   # (Cyl.    7 -
-> 3001*)
->  b:    524288   1545572       swap                      # (Cyl. 3001*-
-> 4019*)
->  c:   2069860         0     unused      0     0         # (Cyl.    0 -
-> 4019*)
->  d:      3605         0       boot                      # (Cyl.    0 - 6)
-> 
-> 
-> sgivol sd0:
-> Volume header files:
-> boot     offset    2 blocks, length    50464 bytes (99 blocks)
-> 
-> SGI partitions:
->  0:a blocks  7947440 first     3280 type  4 (BSD4.2)
->  1:b blocks   524800 first  7950720 type  3 (Raw)
->  3:d blocks     3280 first        0 type  4 (BSD4.2)
->  8:i blocks     3296 first        0 type  0 (Volume Header)
-> 10:k blocks  8482080 first        0 type  6 (Volume)
-> 
-> sgivol sd1:
-> Volume header files:
-> boot     offset    2 blocks, length    50464 bytes (99 blocks)
-> 
-> SGI partitions:
->  0:a blocks  2066725 first     3135 type  4 (BSD4.2)
->  8:i blocks     3135 first        0 type  0 (Volume Header)
-> 10:k blocks  2069860 first        0 type  6 (Volume)
-> 
-> i think the problem may be the missing 1 3 partitions. there's no docs for
-> sgivol, and i don't know how to force it to add those.

You don't make partitions with sgivol, use disklabel instead.  sgivol is
really only designed to do maintenance of the volhdr "file system".  But
in your case, it appears that the disklabel is correct; the problem is
most certainly *not* because of the missing '1' (aka 'b', aka swap) par-
tition on the second disk, and I doubt it's because of the missing '3'
partition (which actually seems wrong in the case of sd0 as it just
overlaps most of the volhdr).

I wonder whether your ARCS variables simply aren't set right (not that
I'm anywhere near a master of ARCS :-), but here's what my Challenge S
says:
	OSLoadPartition=scsi(0)disk(1)rdisk(0)partition(0)
		[Note the rdisk(0), though I'm not sure if it matters...]
	OSLoadFilename=/netbsd
		[Note leading /]

And my bootloader says:
	Boot: scsi(0)disk(1)rdisk(0)partition(0)/netbsd
	devopen: scsi(0)disk(1)rdisk(0)partition(0) type scsi file /netbsd

My guess if your missing '/' is killing things...

--rafal

----
Rafal Boni                                                     rafal@attbi.com
  We are all worms.  But I do believe I am a glowworm.  -- Winston Churchill