home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.sgi
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!ames!sgi!fido!zola!zuni!anchor!olson
- From: olson@anchor.esd.sgi.com (Dave Olson)
- Subject: Re: comp.sys.sgi.admin comp.sys.sgi.hardware comp.sys.sgi.misc
- Message-ID: <tkt79mo@zuni.esd.sgi.com>
- Sender: news@zuni.esd.sgi.com (Net News)
- Organization: Silicon Graphics, Inc. Mountain View, CA
- References: <1992Dec12.191411.29641@cs.cornell.edu>
- Date: Tue, 15 Dec 92 18:26:27 GMT
- Lines: 39
-
- In <1992Dec12.191411.29641@cs.cornell.edu> rogerj@cs.cornell.edu (Roger Jagoda) writes:
- | We just got some new Indigos. I must say we are impressed!
- | Very fasy machines. BUT, the documentation is pretty
- | poor.
- |
- | We want to add a BOOTABLE 1G drive to one machine.
- | We have tried dvhtool AND a direct sash copy (from ROM) from the
- | OEM bootable disk (the small 236 ST1280 that comes with the
- | machine) but no luck. We tried:
- |
- | dvhtool -v create /stand/sash sash
- |
- | That wanted to know
- | starting end ending blocks
- | which of course we couldn't
- | tell it. How does one know
- | where to start and end.
-
- Sounds like you never partitioned the drive. dvhtool normally
- asks for nothing like that.
-
- Run fx on the drive (under unix), and initialize the volume header
- and partitions (fx does that automatically if it doesn't find
- the volume header), then exit and answer yes to the question about
- writing the changes to disk.
-
- Then dvhtool and mkfs will work. I'm assuming that you *did*
- specify the other disk number, otherwise you were copying sash
- into your current system disk, and there should have been no
- problems.
-
- mkfs /dev/rdsk/dks0d1s0
- mkfs /dev/rdsk/dks0d1s6
-
- Will make the 2 'standard' filesystems for an SGI system disk.
- --
- Let no one tell me that silence gives consent, | Dave Olson
- because whoever is silent dissents. | Silicon Graphics, Inc.
- Maria Isabel Barreno | olson@sgi.com
-