Comments on: Rebuilding the Solaris Device Tree http://spiralbound.net/2005/12/21/rebuilding-the-solaris-device-tree my digital notebook Sat, 20 Mar 2010 20:44:56 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Stefan http://spiralbound.net/2005/12/21/rebuilding-the-solaris-device-tree#comment-185123 Stefan Wed, 28 Jan 2009 15:41:09 +0000 http://spiralbound.net/?p=135#comment-185123 To rebuild the path_to_inst file you can move the old /etc/path_to_inst to /etc/path_to_inst_old and in the bootpromt ok> type boot -ar then you will be asked to rebuild the path_to_inst Best regards Stefan To rebuild the path_to_inst file you can move the old /etc/path_to_inst to /etc/path_to_inst_old and in the bootpromt ok> type boot -ar then you will be asked to rebuild the path_to_inst
Best regards
Stefan

]]> By: How to copy a Solaris boot drive to a disk with a different partition layout « Not another blog http://spiralbound.net/2005/12/21/rebuilding-the-solaris-device-tree#comment-173211 How to copy a Solaris boot drive to a disk with a different partition layout « Not another blog Tue, 28 Oct 2008 03:41:51 +0000 http://spiralbound.net/?p=135#comment-173211 [...] we swap the disks and boot from the new one. To resolve this, it is strongly suggested that you rebuild the solaris device tree and change the vfstab file to reflect the new disk [...] [...] we swap the disks and boot from the new one. To resolve this, it is strongly suggested that you rebuild the solaris device tree and change the vfstab file to reflect the new disk [...]

]]> By: Guillermo Salas http://spiralbound.net/2005/12/21/rebuilding-the-solaris-device-tree#comment-150555 Guillermo Salas Wed, 07 May 2008 20:34:12 +0000 http://spiralbound.net/?p=135#comment-150555 A. Braunsdorf: I was having the same problem you are having. (because I installed it on one machine and then moved the disk to a completely different machine). I got the system running by starting up in safe mode and copying the file "path_to_inst" from the failsafe instance to the normal "etc" directory. I then modified the boot archive in the normal instance so that the file /boot/solaris/bootenv.rc had the parameter "boot device" pointing to the correct device. To find out what the new device was, I just made a ls -l to the /dev/dsk directory. Lastly I had to make some modifications to the vfstab file in the "normal" /etc/ directory. Hope this helps. A. Braunsdorf:

I was having the same problem you are having. (because I installed it on one machine and then moved the disk to a completely different machine). I got the system running by starting up in safe mode and copying the file “path_to_inst” from the failsafe instance to the normal “etc” directory. I then modified the boot archive in the normal instance so that the file /boot/solaris/bootenv.rc had the parameter “boot device” pointing to the correct device. To find out what the new device was, I just made a ls -l to the /dev/dsk directory. Lastly I had to make some modifications to the vfstab file in the “normal” /etc/ directory. Hope this helps.

]]> By: How to copy a Solaris boot drive to a disk with a different partition layout | IDGLabs.COM - tips, tools and resource http://spiralbound.net/2005/12/21/rebuilding-the-solaris-device-tree#comment-148573 How to copy a Solaris boot drive to a disk with a different partition layout | IDGLabs.COM - tips, tools and resource Tue, 15 Apr 2008 12:34:17 +0000 http://spiralbound.net/?p=135#comment-148573 [...] we swap the disks and boot from the new one. To resolve this, it is strongly suggested that you rebuild the solaris device tree and change the vfstab file to reflect the new disk [...] [...] we swap the disks and boot from the new one. To resolve this, it is strongly suggested that you rebuild the solaris device tree and change the vfstab file to reflect the new disk [...]

]]> By: Robert Sturrock http://spiralbound.net/2005/12/21/rebuilding-the-solaris-device-tree#comment-31046 Robert Sturrock Thu, 21 Dec 2006 05:00:35 +0000 http://spiralbound.net/?p=135#comment-31046 Very useful article - thanks. Like another poster, I was able to use this to help clone an already installed system from a V440 to a V240 with a different device layout. Robert. Very useful article – thanks. Like another poster, I was able to use this to help clone an already installed system from a V440 to a V240 with a different device layout.

Robert.

]]> By: Jay Herbig http://spiralbound.net/2005/12/21/rebuilding-the-solaris-device-tree#comment-7359 Jay Herbig Mon, 21 Aug 2006 13:59:16 +0000 http://spiralbound.net/?p=135#comment-7359 Doh, sorry, should have looked further down the page. Pardon my redundancy. Jay Doh, sorry, should have looked further down the page. Pardon my redundancy.

Jay

]]> By: Jay Herbig http://spiralbound.net/2005/12/21/rebuilding-the-solaris-device-tree#comment-7358 Jay Herbig Mon, 21 Aug 2006 13:58:14 +0000 http://spiralbound.net/?p=135#comment-7358 Your directions look pretty good but I'm not quite sure about the arguments. Why, when you have the root mounted under /mnt are you using -r /a? I know the /a convention is usually what you'll use if you're mounting a filesystem under a failed boot which exits to the degraded single user mode... but wouldn't the -r (root_dir) also be the mounted filesystem under /mnt? Thanks, other than that looks great. I'm using some of your notes to migrate a fibre based V480 disk to a scsi based V440. Jay Your directions look pretty good but I’m not quite sure about the arguments. Why, when you have the root mounted under /mnt are you using -r /a? I know the /a convention is usually what you’ll use if you’re mounting a filesystem under a failed boot which exits to the degraded single user mode… but wouldn’t the -r (root_dir) also be the mounted filesystem under /mnt?

Thanks, other than that looks great. I’m using some of your notes to migrate a fibre based V480 disk to a scsi based V440.

Jay

]]> By: A Braunsdorf http://spiralbound.net/2005/12/21/rebuilding-the-solaris-device-tree#comment-7220 A Braunsdorf Wed, 16 Aug 2006 20:30:24 +0000 http://spiralbound.net/?p=135#comment-7220 /etc/inst_to_path doesn't seem to be used (or created by this procedure) on i86pc. Moved a drive from an older V40 to a newer one and can't get it to work, so any clues would be appreciated. I've done basically what's above moving from SPARC to SPARC, but doesn't seem to work on the AMDs. :-( /etc/inst_to_path doesn’t seem to be used (or created by this procedure) on i86pc. Moved a drive from an older V40 to a newer one and can’t get it to work, so any clues would be appreciated. I’ve done basically what’s above moving from SPARC to SPARC, but doesn’t seem to work on the AMDs. :-(

]]> By: Jim Weller http://spiralbound.net/2005/12/21/rebuilding-the-solaris-device-tree#comment-6190 Jim Weller Sun, 23 Jul 2006 17:41:04 +0000 http://spiralbound.net/?p=135#comment-6190 Shouldn't <code> # devfsadm -r /a -p /mnt/etc/path_to_inst </code> be <code> # devfsadm -r /mnt -p /mnt/etc/path_to_inst </code> Shouldn’t


# devfsadm -r /a -p /mnt/etc/path_to_inst

be


# devfsadm -r /mnt -p /mnt/etc/path_to_inst

]]> By: spiralbound.net » How to copy a Solaris boot drive to a disk with a different partition layout http://spiralbound.net/2005/12/21/rebuilding-the-solaris-device-tree#comment-283 spiralbound.net » How to copy a Solaris boot drive to a disk with a different partition layout Wed, 21 Dec 2005 19:20:54 +0000 http://spiralbound.net/?p=135#comment-283 [...] Notice that the target number will remain 2, not move to 0 when we swap the disks and boot from the new one. To resolve this, it is strongly suggested that you rebuild the solaris device tree and change the vfstab file to reflect the new disk position. [...] [...] Notice that the target number will remain 2, not move to 0 when we swap the disks and boot from the new one. To resolve this, it is strongly suggested that you rebuild the solaris device tree and change the vfstab file to reflect the new disk position. [...]

]]>