Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

device_remap(1m) [opensolaris man page]

device_remap(1M)					  System Administration Commands					  device_remap(1M)

NAME
device_remap - administer the Solaris I/O remapping feature SYNOPSIS
/usr/platform/sun4v/sbin/device_remap [-v | -R dir] DESCRIPTION
Certain multi-node sun4v platforms, such as T5440 and T5240 servers, have an integrated PCI topology that cause the I/O device paths to change in a CPU node failover condition. The device remapping script, device_remap, remaps the device paths in /etc/path_to_inst file and the symlinks under /dev to match the hardware. OPTIONS
The following options are supported: -v Displays the /etc/path_to_inst and /dev symlink changes. -R dir Perform remapping on the /etc/path_to_inst and /etc/path_to_inst files in the root image at dir. USAGE
The primary function of device_remap is to remap the device paths in the /etc/path_to_inst file and the symlinks under /dev in a CPU node failover condition to match the hardware. After adding CPU node(s) or removing CPU node(s), boot the system to the OBP prompt and use the following procedure: 1. Boot either the failsafe miniroot using: boot -F failsafe , or an install miniroot using boot net -s or similar command. 2. Mount the root disk as /mnt. 3. Change directory to the mounted root disk: # cd /mnt 4. Run device_remap script: # /mnt/usr/platform/sun4v/sbin/device_remap 5. Boot the system from disk. All the error messages are self-explanatory, except for the error message "missing ioaliases node" which means the firmware on the system does not support device remapping. EXAMPLES
Example 1 Displaying Changes Following Failover The following command displays the path_to_inst and /dev changes following a CPU node failover. # device_remap -v Example 2 Changing Directory Prior to Any Changes The following command changes the directory on which the boot image is mounted prior to making any changes. # device_remap -R /newroot ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWkvm.v | +-----------------------------+-----------------------------+ |Interface Stability |Unstable | +-----------------------------+-----------------------------+ SEE ALSO
boot(1M), attributes(5) SunOS 5.11 24 Dec 2008 device_remap(1M)

Check Out this Related Man Page

installgrub(1M) 														   installgrub(1M)

NAME
installgrub - install GRUB in a disk partition or a floppy SYNOPSIS
/sbin/installgrub [-fm] stage1 stage2 raw-device The installgrub command is an -only program. GRUB stands for GRand Unified Bootloader. installgrub installs GRUB stage 1 and stage 2 files on the boot area of a disk partition. If you specify the -m option, installgrub installs the stage 1 file on the master boot sector of the disk. The installgrub command accepts the following options: -f Suppresses interaction when overwriting the master boot sector. -m Installs GRUB stage1 on the master boot sector interactively. The installgrub command accepts the following operands: stage1 The name of the GRUB stage 1 file. stage2 The name of the GRUB stage 2 file. raw-device The name of the device onto which GRUB code is to be installed. It must be a character device that is readable and writable. For disk devices, specify the slice where the GRUB menu file is located. (For Solaris it is the root slice.) For a floppy disk, it is /dev/rdiskette. Example 1: Installing GRUB on a Hard Disk Slice The following command installs GRUB on a system where the root slice is c0d0s0: example# /sbin/installgrub /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c0d0s0 Example 2: Installing GRUB on a Floppy The following command installs GRUB on a formatted floppy: example# mount -F pcfs /dev/diskette /mnt # mkdir -p /mnt/boot/grub # cp /boot/grub/* /mnt/boot/grub # umount /mnt # cd /boot/grub # /sbin/installgrub stage1 stage2 /dev/rdiskette /boot/grub Directory where GRUB files reside. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ boot(1M), fdisk(1M), fmthard(1M), kernel(1M), attributes(5) Installing GRUB on the master boot sector (-m option) overrides any boot manager currently installed on the machine. The system will always boot the GRUB in the Solaris partition regardless of which fdisk partition is active. 24 May 2005 installgrub(1M)
Man Page