Sponsored Content
Full Discussion: Boot from Mirrored disk
Operating Systems Solaris Boot from Mirrored disk Post 302608237 by drew_1980 on Friday 16th of March 2012 02:24:13 PM
Old 03-16-2012
I ran a script that copied the first disk to the second disk. Can I just comment out c1t0d0 in the vfstab, add in c1t1d0 and reboot?
 

10 More Discussions You Might Find Interesting

1. HP-UX

Number of Disk Mirrored in HP-UX

In HP-UX 11.00 How can i check if there are disks mirrored (2 Replies)
Discussion started by: cgege
2 Replies

2. AIX

Mirrored disk.....

How do I know, which all disks are mirrored? any command? Bala (7 Replies)
Discussion started by: balaji_prk
7 Replies

3. UNIX for Dummies Questions & Answers

Creating create mirrored disk files systems using mkfs command

What is the correct mkfs syntax to create mirrored disk files systems? I need to make the file system 20gb. For example: machine# mkfs -F ufs /dev/md/dsk/d40 size not specified ufs usage: mkfs special size(sectors) \ -m : dump fs cmd line used to make this partition -V : print this... (4 Replies)
Discussion started by: GLJ@USC
4 Replies

4. UNIX for Dummies Questions & Answers

Solaris 10 not booting with mirrored disk

Hi all, I have a V490 running with Solaris 10. The OS disk was mirrored. I wanted to break the mirror, boot with the secondary mirror, and re-mirror the OS with a new disk. This is what I did, detached the metadevices of the secondary mirror disk (disk 1) metaclear-ed the metadevices,... (1 Reply)
Discussion started by: nitinp82
1 Replies

5. Solaris

Remove os mirrored disk Solaris 10

Hello once again seeking your help, I have a mirrored disk and need to unmirror it to mount it as a new file system (/export) but could not find the correct steps to do it with out affecting the original disk. can anybody point me out on how to get this done. Thanks!! (3 Replies)
Discussion started by: AQG
3 Replies

6. UNIX for Advanced & Expert Users

how to create multiple-boot system with disks mirrored(RAID1+0) and disk alone

I have a HP proliant ML 570 G3 with two 146GB disk drives mirrored(RAID1+0) windows server 2003 was installed on that disk. I will add a disk.(scsi 300GB) I will install Linux on that additional disk. I want to create multiple-boot system. Is it possible? I wanna know how to create... (0 Replies)
Discussion started by: lifegeek
0 Replies

7. Solaris

Need help replacing a mirrored boot disk

I have a v480 with a mirrored boot disk c1t0 and c1t1. The drives themselves don't show a failure but the mirror's need maintenance. This is my plan for replacing the drive. I would love feedback to point out what I"m missing or where my steps are incorrect. Two things I believe I'm... (3 Replies)
Discussion started by: pcoffey
3 Replies

8. Red Hat

Booting 2nd mirrored boot disk

Hi guys, thanks for helping out. If you have two boot disk mirrored and your primary boot disk fails, how will you boot the system from the second disk? Thank you very much for your assistance on this matter. Arrey (5 Replies)
Discussion started by: cjashu
5 Replies

9. Solaris

How to specify local boot up disk in CD boot Grub?

Hi Solaris 10 Experts, I am wondering what is the correct syntax to edit in Grub when trying to specify the local ZFS boot disk while booting up from a Solaris 10 x86 64bits DVD installation disk. In other word, I try to boot up from local disk without removing the Solaris installation disk... (0 Replies)
Discussion started by: gjackson123
0 Replies

10. Solaris

Use 'dd' to copy boot disk to larger target disk

Hi, I'm looking to copy a boot disk on an old Solaris 8 system using dd. I'll bring the system down to single user mode and begin from there. I'm copying my source disk to a larger target disk. Do I need to do anything other than the 'dd' command below because the target disk is bigger? ... (2 Replies)
Discussion started by: sparcman
2 Replies
stmsboot(1M)															      stmsboot(1M)

NAME
stmsboot - administration program for the Solaris I/O multipathing feature SYNOPSIS
/usr/sbin/stmsboot [-d | -e | -u | -L | -l controller_number] The Solaris I/O multipathing feature is a multipathing solution for storage devices that is part of the Solaris operating environment. This feature was formerly known as Sun StorEdge Traffic Manager (STMS) or MPxIO. The stmsboot program is an administrative command to manage enumeration of fibre channel devices under Solaris I/O multipathing. Solaris I/O multipathing-enabled devices are enumerated under scsi_vhci(7D), providing multipathing capabilities. Solaris I/O multipathing-disabled devices are enumerated under the physical controller. In the /dev and /devices trees, Solaris I/O multipathing-enabled devices receive new names that indicate that they are under Solaris I/O multipathing control. This means a device will have a different name from its original name (following installation) when it is under Solaris I/O multipathing control. The stmsboot command automatically updates /etc/vfstab and dump configuration to reflect the device names changes when enabling or disabling Solaris I/O multipathing. A reboot is required for changes to take effect. The following options are supported: -e Enables Solaris I/O multipathing on all fibre channel (fp(7D)) controller ports. Following this enabling, you are prompted to reboot. During the reboot, vfstab and the dump configuration will be updated to reflect the device name changes. -d Disables Solaris I/O multipathing on all fibre channel (fp(7D)) controller ports. Following this disabling, you are prompted to reboot. During the reboot, vfstab and the dump configuration will be updated to reflect the device name changes. -u Updates vfstab and the dump configuration after you have manually modified the configuration to have Solaris I/O multipathing enabled or disabled on specific fp(7D) controller ports. This option prompts you to reboot. During the reboot, vfstab and the dump configura- tion will be updated to reflect the device name changes. -L Display the device name changes from non-Solaris I/O multipathing device names to Solaris I/O multipathing device names. -l controller_number Display the device name changes from non-Solaris I/O multipathing device names to Solaris I/O multipathing device names for the speci- fied controller. Along with its primary function of enabling or disabling Solaris I/O multipathing, the stmsboot command is used to update vfstab and the dump configuration to reflect device name changes. For a system to function properly, you must configure the applications that consume the devices by old names to use the new names. The -L and -l options display the mapping between the old and new device names. These options work after the changes made to the Solaris I/O multipathing configuration have taken effect. For example, you can use these options following the reboot after invoking stmsboot -e. The old device names must exist in order to display the mappings. Example 1: Enabling Solaris I/O Multipathing Following OS Upgrade To enable Solaris I/O multipathing on all fibre channel (fp(7D)) controller ports run: # stmsboot -e Example 2: Disabling Solaris I/O Multipathing To disable Solaris I/O multipathing on all fibre channel (fp(7D)) controller ports, run: # stmsboot -d Example 3: Enabling Solaris I/O Multipathing on Selected Ports You want to enable Solaris I/O multipathing on some fibre channel controller ports and disable the feature on the rest. You edit the fp.conf file (see fp(7D)) to enable or disable Solaris I/O multipathing on specific controller ports. You then run the following command to have vfstab and the dump configuration updated to reflect the new device names: # stmsboot -u See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |SPARC | +-----------------------------+-----------------------------+ |Availability |SUNWcsu, SUNWcslr | +-----------------------------+-----------------------------+ |Interface Stability |Obsolete | +-----------------------------+-----------------------------+ SEE ALSO
dumpadm(1M), ufsdump(1M), dumpdates(4), vfstab(4), fcp(7D), fctl(7D), fp(7D), qlc(7D), scsi_vhci(7D) Consult the Sun StorEdge Disk Tray [or Subsystem] Administrator's Guide for the T3, 3910, 3960, 6120, and 6320 storage subsystems. Sun StorEdge Traffic Manager Installation and Configuration Guide Solaris I/O multipathing is not supported on all devices. After enabling Solaris I/O multipathing, only those devices that Solaris I/O mul- tipathing supports are placed under Solaris I/O multipathing control. Non-supported devices remain as before. For Solaris releases prior to the current release, the -e and -d options remove the mpxio-disable property entries from fp.conf file (see fp(7D)) and add a global mpxio-disable entry to fp.conf. The current release of the Solaris operating system does not support the mpxio-disable property. Solaris I/O multipathing is always enabled. If you want to disable multipathing, you must use the mechanisms provided by the HBA drivers. See fp(7D). Enabling Solaris I/O Multipathing on a Sun StorEdge Disk Array The following applies to Sun StoreEdge T3, 3910, 3960, 6120, and 6320 storage subsystems. To place your Sun StorEdge disk subsystem under Solaris I/O multipathing control, in addition to enabling Solaris I/O multipathing, the mp_support of the subsystem must be set to mpxio mode. The preferred sequence is to change the subsystem's mp_support to mpxio mode, then run stmsboot -e. If Solaris I/O multipathing is already enabled but the subsystem's mp_support is not in mpxio mode, then change the mp_support to mpxio mode and run stmsboot -u. Refer to the Sun StorEdge Administrator's Guide for your subsystem for more details. ufsdump Users The ufsdump command keeps records of the filesystem dumps in /etc/dumpdates (see dumpdates(4)). Among other items, the records contain device names. An effect of the "active" stmsboot options (-e, -d, and -u) is to change the device name of a storage device. The stmsboot command does not modify the dumpdates file. Because of this, the dumpdates records will refer to the old device names, that is, the device names that were in effect before you ran stmsboot. The effect of this device name-dumpdates disagreement is that, following use of stms- boot, ufsdump will be processed as if no previous dump had ever been made, thus dumping the entire filesystem (effectively, a level 0 dump). Procedure to Use stmsboot in Sun Cluster Environment If possible, use stmsboot -e before you start installing Sun Cluster software. After you run stmsboot, you install Sun Cluster software as you normally would. If you install Sun Cluster software before running stmsboot, you must use the following procedure. On each machine in the cluster on which you want to enable the Solaris multipathing feature, enter: # stmsboot -e ...and allow the system to reboot. When the system comes up, enter the following two commands: 1. # /usr/cluster/bin/scdidadm -C 2. # /usr/cluster/bin/scdidadm -r The preceding commands update did mappings with new device names while preserving did instance numbers for disks that are connected to multiple cluster nodes. did instance numbers of the local disks might not be preserved. For this reason, the did disk names for local disks might change. 3. Update /etc/vfstab to reflect any new did disk names for your local disks. 4. Reboot the system. To disable the Solaris multipathing feature, use stmsboot -d (instead of stmsboot -e), then follow the procedure above. To view mappings between the old and new device names, run stmsboot -L. To view did device name mappings, run /usr/cluster/bin/scdidadm -L. 3 Mar 2005 stmsboot(1M)
All times are GMT -4. The time now is 07:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy