i didn't try any of the following coz i have just reinstalled:
RAMNISH SINGH write:
You can do that in two ways.
1. Create a file /reconfigure using the touch command and then do init 6.
i.e.
#touch /reconfigure
#init 6
Once the machine tries to reboot just power it off and connect the disk to
the
other box. Solaris with automatically reconfigure itself.
2. Try to boot the OS using the b -r command at the boot prompt.
SULLIVAN, JOHN wrote:
To do any serious modifications of a Solaris system (i.e.,
to replace a boot drive or controller, motherboard, CPU,
etc., or to move a boot drive to another system), insert
your install floppy and boot from your CD, then follow the
Sun Infodoc #13133 (below); that's always worked for me.
Good luck!
INFODOC ID: 13133
SYNOPSIS: How to move a Solaris 2.x x86 hard disk to another system
DETAIL DESCRIPTION:
It is possible to move a bootable installation of Solaris 2.x x86 to
another machine or hard drive controller. However, the procedure is not
straight forward. The procedure listed below might not work in all
situations. Always backup important data before attempting to try this.
Remember, this has not been WIDELY tested, but has worked in several cases.
Note: This procedure is not necessary to move a data drive which is not
used
for booting. This is for a drive which contains Solaris 2.x x86's
/, /usr, /opt, etc and is the boot drive.
Overall summary:
1) Install the drive in the new system, or a new hard drive controller.
2) Boot off the CD-ROM.
3) Mount the hard disk's /root and /usr.
4) Rebuild /devices and /dev.
5) Modify /etc/vfstab and /etc/bootrc if necessary.
6) Unmount the hard disk.
7) Attempt to reboot off hard disk.
1) Install the drive in new system, or anew hard drive controller.
Install any driver updates that are needed by the new hardware
BEFORE moving hard disk. Check the latest HCL to determine if
any driver updates are required by the destination hardware.
Be sure to check all the hardware basics such as target numbers,
termination, power, HBA irqs, HBAs IOs, and others. Consult the
X86 Device Configuration Guide for proper settings of any Hard
Drive Controllers (HBA)
2) Boot of the CD-ROM.
Use floppy boot disk in conjunction with the CD-ROM to boot off the
CD-ROM. Enter 'b -s' when asked for installation type. This will
boot into single user mode. A shell will follow shortly after this.
3) Mount the hard disk's /root and /usr.
# TERM=at386
# export TERM
# mount /dev/dsk/c?t?d?s0 /a (mounts root filesystem to '/a')
'?' varies on systems. Look in /dev/dsk to help determine which
device to use. Once the hard disk's root filesystem is mounted,
determine the slice number of the '/usr' filesystem.
Example:
# more /a/etc/vfstab | grep /usr
#/dev/dsk/c1d0s2 /dev/rdsk/c1d0s2 /usr ufs 1 yes -
/dev/dsk/c0t3d0s6 /dev/rdsk/c0t3d0s6 /usr ufs 1
no
-
^ ^
| |
This is the number needed
Now mount the hard disk's /usr filesystem under /a/usr.
# mount /dev/dsk/c?t?d?s* /a/usr (where * is the number found above )
(where ? are the numbers used for root)
4) Rebuild /devices and /dev.
# cd /a
# _INIT_RECONFIG=1
# export _INIT_RECONFIG
# /usr/sbin/chroot /a /etc/rcS.d/S50drvconfig
Configuring the /devices directory
# /usr/sbin/chroot /a /etc/rcS.d/S60devlinks
Configuring the /dev directory
Configuring the /dev directory (compatibility devices)
5) Modify /etc/vfstab and /etc/bootrc if necessary.
a) Determine the new boot path:
# ls -l /dev/dsk/c?t?d?s0 (This is the hard drive's root slice as
before
)
lrwxrwxrwx 1 root root 38 Mar 14 08:12 /dev/dsk/c1t1d0s0 -> ../..
/devices/eisa/ncrs@1,0/cmdk@1,0:a
^^^^^^^^^^^^^^^^^^^^^^^^
||||||||||||||||||||||||
This is the new boot path
# vi /a/etc/bootrc ( Replace old boot path with new boot path
)
b) Update vfstab:
Look in /a/dev/dsk/*. It is very likely that the controller numbers have
changed. It is even possible that the entries in here are different than
the entries in /dev/dsk/*. Be sure to update the /a/etc/vfstab according
to these new devices.
# vi /a/etc/vfstab ( Make any changes and save )
6) Unmount the hard disk.
# cd /
# umount /a/usr
# umount /a
7) Attempt to reboot off the hard disk.
# halt
Power-cycle the system. Boot off the floppy if the new hard disk is not
the first (boot) disk.
JOHN T. DOUGLASS wrote:
Your real problem here is probably the differences in the motherboards
and ide controllers (since you don't mention a particular SCSI
controller). This has been hashed out a few times on the x86 mailing
list (hosted at http://www.egroups.com) and if my memory serves the
easiest thing to do is reinstall.
You might check out http://fishbutt.fiver.net which is a good Solaris
x86 resource. It has a search engine for the x86 mailing list
archive. If nothing else if you are going to continue to use x86 the
resource might come in handy.
SIMON-BERNARD DROLET wrote:
I've just got my new Pentium Celeron 400MHz with an Asus P2B-F
motherboard.
I was using an old Pentium 100MHz, PCI ATI Xpression 2Mb, SoundBlaster
ISA, Adaptec ISA 1520b, SCSI CD, IDE cd and two internal scsi disks.
I've transfert the two disks, the cd and put them in the new Celeron
with ATI Xpert 98 8mb AGP, PCI SoundBlaster, Adaptec 1520B ISA and
Adaptec 2920 PCI and the only thing I had to do was when the system
started (b -r), I was force to reconfigure Xwindows (kdmconfig).
Everything is now working fine !
RON E. NELSON wrote:
I've done a certain amount of changes with Solaris X86 and still had a
system boot.
In fact, I think I went from an AMD 486 to a K6 and the system still
was able to boot. The key was I kept the same video card, and the
drive ID did not change (Still using Primary IDE interface, Master
drive.)
When I made a video card change, I was prompted with the kdmconfig
command in single user mode to change video card and monitor settings.
Note that when I moved the drive to a different controller on the
system I was no longer able to boot Solaris.
Again, thank you very much for all your replies.
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:26 CDT