SUMMARY: Changing boot drive on 3500

From: Bill Voight <>
Date: Mon Feb 03 2003 - 06:58:00 EST
Original post below.

The answer, which is in Sun's INFODOC #15010 is the following:

Go to the ok> prompt
Insert bootable Solaris CD
boot cdrom -sw
mount your_new_boot_disk /a
cd /a/dev/dsk
rm c*
cd /a/dev/rdsk
rm c*
cd /
drvconfig -r /a devices -p /a/etc/path_to_inst
devlinks-r /a
disks-r /a
tapes -r /a
ports -r /a
cd /
umount /a

Sun warns about third party disk drivers (not applicable in my case).  There
is also a note about the cdrom /etc/name_to_major that the doc mentions.
INFODOC 22269 uses a tar version of this procedure and INFODOC 13133 has a
related procedure for x86 boxes.

Of course, I'm still in upgrade hell because the upgrade now fails, but at
least I've gotten this far.  I'm going to Sun support about; the upgrade
failure, I'll also summarize that.

Bill Voight
UNIX System Engineer
NOVA Technology
(202) 418-0021
For Internal Use Only

>>> Bill Voight 01/25/03 01:17PM >>>
Sports fans,

I'm in upgrade hell.  I'm trying to upgrade a 3500 from Solaris 7 to 8.  The
existing boot drive is too small to take the upgrade (/var and /opt are only
about 125MB each).  We found an 18GB drive to replace it, so I did the

1).  I put the new drive in an internal slot I cleared, partitioned and made
filesystems. I have upgraded 3500's successfully before, but never have I had
to remove a (non-system) drive from a slot and substitute another.  Each of
the other upgraded boxes had at least one spare slot.
2:.  I ufsdumped all the boot drive partitions to the new, larger ones.  I
compared sizes of the copied partitions and all are almost exactly the same
size.  I also manually reviewed critical segments of /usr and /var.
3).  I installed the bootblock on the new drive.
4).  I fsck'ed each partiton and all seem healthy.
5).  I brought the machine down, removed the old drive, and put the larger
in it's slot.  I also replaced the drive I removed to make room for the new
one (it has no system partitions on it).
6).  I rebooted the system and it recognized the drive, saw the OS, but can't
find the /usr partition.
7).  I have rechecked all the new partitions several times and all seem
healthy to fsck when I boot from the old drive and mount the new drives
partitons by hand.
8).  I compared eeprom settings (ver 3.2.29) and all appear as they were
before I started.  Boot-device is socald as expected.

Any ideas?  I will summarize.

The good news is that the machine comes right back up with the old boot drive
and (non-system) drive returned to their original places.  I suspect there's
something to do with luxadm, but the fact that the system sees the operating
system, but not the /usr partiton is throwing me for a loop.

Bill Voight
UNIX System Engineer
NOVA Technology
(202) 418-0021
For Internal Use Only
sunmanagers mailing list
sunmanagers mailing list
Received on Mon Feb 3 07:05:14 2003

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:02 EST