Hi:
(Note: The following is done inside VMWare 6.1 on XP)
I had Solaris SXCRnv82 running off of c1t1d0s0, but instead wanted it
to run off of c1t0d0s0. (The only reason it ended up on c1t1d0 was
because of a live upgrade to it).
The following is what I did to accomplish this switch, but it's causing a
panic at the very beginning stages of boot, as shown in the attachment.
(1) I swapped the names of these two disk files...
> Solaris10SXCR_c1t0d0-flat.vmdk
> Solaris10SXCR_c1t1d0-flat.vmdk
(2) With VIM, I edited their associated text files, to reflect the rename
above...
> Solaris10SXCR_c1t0d0.vmdk
> Solaris10SXCR_c1t1d0.vmdk
(3) Next, I booted the VM to single user mode off the SXCRnv82 DVD and
make the following adjustments:
root# mount -F ufs -o rw /dev/dsk/c1t0d0s0 /a
root# vi /a/etc/vfstab (made appropriate path adjustments)
root# devfsadm -Cvr /a (for good measure, before I run the next command)
root# bootadm update-archive -v -R /a (updated the archive)
> cannot find: /a/etc/cluster/nodeid: No such file or directory
> cannot find: /a/etc/devices/mdi_ib_cache: No such file or directory
> cannot find: /a/etc/devices/retire_store: No such file or directory
> cannot find: /a/platform/i86pc/ucode/AuthenticAMD: No such ...
(Note: I even renamed "boot_archive" to ensure a fresh creation)
root# cd /a/boot/grub
root# installgrub -m ./stage1 ./stage2 /dev/rdsk/c1t0d0s0
(Output omitted, but updated master boot record went fine).
root# vi /a/boot/grub/menu.lst (It has the following contents now)...
============================================
default 0
timeout 10
splashimage /boot/grub/splash.xpm.gz
title Solaris10_SXCRnv82
root (hd0,0,a)
kernel$ /platform/i86pc/kernel/$ISADIR/unix
module$ /platform/i86pc/$ISADIR/boot_archive
============================================
root# cd /; umount /a; reboot (Making sure to disconnect the DVD).
After doing this, as you can see from the attachment, I must have
missed something, because basic special filesystems right at the start
of boot cannot be mounted due to "version mismatches".
Note that the nv82 O/S booted fine many times before the steps above.
Thus I must be missing something. Any thoughts and ideas.
Thanks In Advance.
Noel Milton
This message posted from opensolaris.org
_______________________________________________
opensolaris-help mailing list
[email protected]