I had a similar problem (not exactly the same!) a few weeks ago, and I got the following hints on the solaris-x86 list, from Adrian Saul (thanks to him! :)) - it is about changing the whole hw, so that you put the old disk into a new machine - but that is what you did, right? :)) Below that you'll find a few remarks from me.
And there is a similar procedure on riddleware.com too, but the site seems to be down at the moment. hope this helps! =======================================> Date: Tue, 03 Apr 2007 22:00:13 +1000 Subject: Re: [solarisx86] Migrating Solaris - mobo/cpu change... Chances? I have done it a number of times, it isnt something I recommend on a production box, but it works. The great thing is the failsafe boot makes it so much easier now, dont even need a CD :) Procedure: 1. Take a backup. Rince and repeat. Take another backup as well. 2. change hardware 3. Boot failsafe single user on new hardware - normally your root disk gets mounted as /a doing this. 4. Replace /a/etc/path_ to_inst with the failsafe /etc/path_to_ inst (should be a single stub line) 5. Remove the physical devices from /a/devices i.e the [EMAIL PROTECTED] paths (rm -rf). Dont touch any pseudo or others you are unsure of. 6. do an rm /dev/dsk/*, /dev/rdsk/* to get rid of the old entries 7. run devfsadm to fix up the device config from scratch: # devfsadm -r /a 8. Check that the entries in /a/devices and /a/etc/path_ to_inst are now populated. If not, use tar to copy the failsafe device tree in place and run step 7 again i.e # cd /devices; tar cvf -|(cd /a/devices; tar xf -) 9. Check /a/dev/dsk - make sure you have disks. 10. edit /a/boot/solaris/ bootenv.rc - fix your boot-device path 11. Check no disk names have changed - if they have, fix /etc/vfstab 12. Run "bootadm update-archive -R /a" to repack your boot archive. You should now be able to boot off the disk as if it always lived on your system. this is really just a modification of an old procedure for SPARC systems to re-order controller numbers. There is probably an Infodoc on it somewhere. Cheers, Adrian A few remarks from me: There is a missing dot in this line: # cd /devices; tar cvf -|(cd /a/devices; tar xf -) (homework: find where :)))) With nv_b60 devfsadm -r /a told me that it cannot open /a/devices// a/devices/ etc (...or similar, sorry I forgot to write it down) - whilst with S10 U3 everything was ok. I thinks it'a s bug, but I didn't check it on bugs.opensolaris. org though... It populated the device tree, so I didn't care too much. But somehow it did not populate /etc/path_to_ inst, so I have googled an other solution: there is a fully populated path_to_inst in /tmp/root/etc , so I copied it over to /a/etc, and everything was OK. <==================================== This message posted from opensolaris.org _______________________________________________ networking-discuss mailing list [email protected]
