SUMMARY: Boot from c0t0d0s0 instead of c0t3d0s0

From: Joe R. Jah (
Date: Fri Nov 26 1999 - 00:32:53 CST

Hi Folks,

Thank you very much; as usual you came through lightning fast;) I am
sorry for the late summary; applying your solutions has not been painless,
or fast;(

First of all I want express my special thanks to:
Charles Nguyen <>
Mike Ghicas <>
Jason Youngquist <>
Cesare Tensi <>
Richard Skelton <>
"Haydee Y. Ching" <>
Matthew Stier <>
Dieter Gobbers <>
David Robillard <David.Robillard@Matrox.COM>
Adrian Stovall <>
"Eric J. Reynolds" <>
"Ernie Bisson, MIT Bates Linear Accelerator" <BISSON@BATES.MIT.EDU>
Thomas Carter <>
Tom Erickson <>
Chris Marble <>
Casper Dik <>


I made extensive use of the summary Jason Youngquist had already sent in
June 1998. He kindly forwarded it to me:
Try's not painless though..

Date: Tue, 30 Jun 1998 09:25:44 -0500 (CDT)
From: Jason Youngquist <>
Subject: SUMMARY: Changing the root filesystem

I wanted to change the root filesystem from one hardrive to another. It
proved more difficult than I thought it would be.

Steps to do this are:

1. Make sure the target drive is partitioned and a new filesystem is
    created on the drive.
2. Mount the target drive on /mnt
3. Copy the contents of the current root drive to the target drive using
    ufsdump and ufsrestore.
        (ufsdump 0f - /dev/rdsk/c0t0d0s0 | (cd /mnt; ufsrestore xf -)

     Copying using the cp command doesn't work.

4. Run the program "installboot" (man installboot(1M)) on the target
5. Edit the /mnt/etc/vfstab to reflect the changes you want to make to
    the disk.
6. Write down the long name of the disk you want to boot up. Should look
    something like this:
7. Shutdown the system
8. Now you need to change the boot device and store it in the PROM.
9. To do this type "setenv boot-device (disk name) /kernel/unix"
    On a sun Ultra1 with the boot device being c1t2d0s0 the command would
    look like this:
        setenv boot-device /sbus@1f,0/SUNW,fas@0,8800000/sd@2,0:a
10. Type "reset" at the "OK" prompt to save the boot-device setting to
11. This will reboot the machine and if everything goes okay your machine
     should be able to boot up.

Jason is so right; it hasn't been painless. Painless is a relative word;)
what I meant was to have the double boot partitions available remotely,
i.e. login remotely, become super user, change configuration, shutdown and
restart from the alternative OS. I guess I was too ambitious;)

Any way, I have done the above steps up to and including step 7. I have
booted the system from the new boot partition without changing the default
boot device. I have been running the system on the new boot partition
without a problem for two weeks, but I know if the system restarts remotely
it would boot from the old, default, boot partition.

I plan to upgrade the non-active boot partition to Solaris 2.7 and change
system's active partition at the same time:
>From Thu Nov 25 22:01:04 1999
Date: Mon, 15 Nov 1999 10:47:50 +0100
From: Casper Dik <>
To: "Joe R. Jah" <>
Subject: Re: Boot from c0t0d0s0 instead of c0t3d0s0

Yes. You can do a custom install and preserve the other disks.

You can even first copy your current install to the new partition
(fixing /etc/vfstab for it so it can boot of it) and then have the
installer upgrade it.

If you install on a non-default partition, the installer will ask
if you want to change the default boot device.

The system I'm typing this on has two bootable partitions; one was
originally cloned from the other.


The original message:

> Date: Mon, 8 Nov 1999 18:04:36 -0800 (PST)
> From: "Joe R. Jah" <>
> To:
> Subject: Boot from c0t0d0s0 instead of c0t3d0s0
> Hi Folks,
> I run Solaris 2.5 on a Spark 5 box; it has two internal HD's, an HD and CD
> in an external shoe box, and an external tape drive.
> I like to upgrade to 2.7, but I do not want to destroy 2.5 yet. I'd like
> to install the new root and usr partitions on a second disk and boot from
> it without having to overwrite the present root and usr partitions.
> Is there a painless way of installing it on a non-active partition, and
> having the box boot from /dev/dsk/c0t0d0s0 instead of /dev/dsk/c0t3d0s0 ?
> I appreciate any pointers.
> Regards,
> Joe
> --
> _/ _/_/_/ _/ ____________ __o
> _/ _/ _/ _/ ______________ _-\<,_
> _/ _/ _/_/_/ _/ _/ ......(_)/ (_)
> _/_/ oe _/ _/. _/_/ ah

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:33 CDT