Path: utzoo!utgpu!attcan!uunet!lll-winken!ncis.llnl.gov!helios.ee.lbl.gov!pasteur!ucbvax!decwrl!labrea!rutgers!mit-eddie!uw-beaver!rice!sun-spots-request
From: SYSRUTH@utorphys.bitnet (Ruth Milner, Systems Manager x2746)
Newsgroups: comp.sys.sun
Subject: Re: fixing bad ND partitions
Message-ID: <8901171645.AA16782@gpu.utcs.toronto.edu>
Date: 23 Jan 89 22:27:52 GMT
Sender: usenet@rice.edu
Organization: Eikonix Corp., Bedford, MA
Lines: 41
Approved: Sun-Spots@rice.edu
Original-Date: Tue, 17 Jan 89 11:45 EST
X-Sun-Spots-Digest: Volume 7, Issue 116, message 4 of 13
X-Issue-Reference: v7n105

In v7n105, Tony Tran (versatc!tran@sun.com) asks:
>We have a server with 12 ND partitions, 4 of which are bad.  What is the
>easiest/safest way to fix these partitions ?

The easiest way is essentially to replicate what setup does. For each one:

1. First use mkfs on an ndl partition which is bad (be careful that your
   specified root filesystem size matches what nd.local says). Run fsck on it.
2. Shut down one of your good clients (of same type as bad one) and use the
   script /usr/etc/setup.files/copy_client to create the new root from the
   existing one. Run fsck on it again.
3. Mount it on /mnt or somewhere unused and cd to it. Fix it up by doing a
   MAKEDEV std pty0 pty1 pty2 win0 win1 win2 nd0 nd1 ndp0 (and ndp1 or other
   devices if you have them) in its dev directory, and change ownerships of
   private/usr/spool/at,log, and lpd directories to daemon.daemon if necessary.
4. Copy your hosts and networks files to its etc directory. Fix up rc* and
   fstab files, and any other local setups for mail, mount points, whatever.
5. Type "sync" a couple of times. cd out of /mnt and umount it. Run fsck on
   the ndl partition again.

At this point, if your tftp links and /etc/ethers entries are set up
properly, you should be able to boot a client off that partition. I used
exactly this procedure recently to add six new clients on a partition
previously used for data. The nd.local file was updated and fed to nd
first, of course. It took little more than an hour to do all six, and they
all booted like a charm.

It is not much more difficult to do this for brand new clients either; in
that case, instead of step 2, check the manual for the tape contents, tar
off the necessary stuff into /pub and one root, make sure links into /pub
are set up properly (for lib, stand, bin, and vmunix if the kernel is
shared), and continue with step 3. You should also make a non-GENERIC
kernel after booting the first client and before creating the others.

Hope this helps.

Ruth Milner
Systems Manager
University of Toronto Physics

sysruth@helios.physics.utoronto.ca   (Internet)