Оценок - 2, средний балл: 4.5
(
)
)
|
Фрагмент инструкции
Since the boot device always has a mounted file system when booted, an alternate boot medium must be employed, and the volume created in that environment. One alternate medium is a network installation image in single-user mode. (Refer to the Solaris 10 Installation Guide for information about configuring and using network-based installations.) 1. Determine which disk is the default boot device. From the OpenBoot ok prompt, type the printenv command, and if necessary the devalias command, to identify the default boot device. For example: ok printenv boot -device boot-device = disk ok devalias disk disk /pci@0/pci@0/pci@2/scsi@0/disk@0,0 2. Type the boot net -s command. ok boot net -s 3. Once the system has booted, use the raidctl(1M) utility to create a hardware mirrored volume, using the default boot device as the primary disk. See “Create a Hardware Mirrored Volume” on page 15. For example: # raidctl -c -r 1 cltOdO cltldO Creating RAID volume cltOdO will destroy all data on member disks, proceed (yes/no)? yes Volume cltOdO is created successfully! # Managing Disks 19 4. Install the volume with the Solaris OS using any supported method. The hardware RAID volume cltOdO appears as a disk to the Solaris installation program. Note — The logical device names might appear differently on your system, depending on the number and type of add-on disk controllers installed. Related Information ■ “Disk Slot Numbers” on page 35 ■ “Create a Hardware Mirrored Volume” on page 15 ■ “Configure a Hardware RAID Volume for the Solaris OS” on page 22 ▼ Create a Hardware Striped Volume 1. Verify which hard drive corresponds with which logical device name and physical device name. See “Disk Slot Numbers” on page 35. To verify the current RAID configuration, type: # raidctl Controller: 1 Disk: 0 0. 0 Disk: 0 1. 0 Disk: 0 2 0 Disk: 0 3. 0 Disk: 0 4 0 Disk: 0 5 0 Disk: 0 6. 0 Disk: 0 7 0 The preceding example indicates that no RAID volume exists. 20 SPARC Enterprise T5140 and T5240 Servers Administration Guide • July 2009 2. Type the following command: # raidctl -c -r 0 diskl disk2 ... The creation of the RAID volume is interactive, by default. For example: # raidctl -c -r 0 cltldO c1t2d0 c1t3d0 Creating RAID volume will destroy all data on spare space of member disks, proceed (yes/no)? yes May 16 16: 33 :30 wgs57-06 scsi: /pci@0/pci@0/pci@2/scsi@0 (mpt0 May 16 16: 33 :30 wgs57-06 Physical disk 0 created. May 16 16: 33 :30 wgs57-06 scsi: /pci@0/pci@0/pci@2/scsi@0 (mpt0 May 16 16: 33 :30 wgs57-06 Physical disk 1 created. May 16 16: 33 :31 wgs57-06 scsi: /pci@0/pci@0/pci@2/scsi@0 (mpt0 May 16 16: 33 :31 wgs57-06 Physical disk 2 created. May 16 16: 33 :31 wgs57-06 scsi: /pci@0/pci@0/pci@2/scsi@0 (mpt0 May 16 16: 33 :31 wgs57-06 Volume 3 is jenabledjjoptimalj May 16 16: 33 :31 wgs57-06 scsi: /pci@0/pci@0/pci@2/scsi@0 (mpt0 May 16 16: 33 :31 wgs57-06 Volume 3 is jenabledjjoptimalj May 16 16: 33 :31 wgs57-06 scsi: /pci@0/pci@0/pci@2/scsi@0 (mpt0 May 16 16: 33 :31 wgs57-06 Volume 3 created. Volume c1t3d0 is created successfully! # When you create a RAID striped volume, the other member drives (in this case, c1t2d0 and c1t3d0) disappear from the Solaris device tree. As an alternative, you can use the -f option to force the creation if you are sure of the member disks and sure that the data on all other member disks can be lost. For example: # raidctl -f -c -r 0 cltldO c1t2d0 c1t3d0 Volume c1t3d0 is created successfully! # 3. To verify the existence of a RAID volume, type the following command: # raidctl -l Controller: 1 Volume:c1t3d0 Disk 0.0.0 Disk 0.1.0 Disk 0.2.0 Disk 0.3.0 Disk 0.4.0 Managing Disks 21 Disk: 0.5.0 Disk: 0.6.0 Disk: 0.7.0 4. To check the status of a RAID striped volume, type the following command: # raidctl -l c1t3d0 Volume Sub Disk Size Stripe Size Status Cache RAID Level c1t3d0 N/A 64K OPTIMAL OFF RAID0 0.3.0 N/A GOOD 0.4.0 N/A GOOD 0.5.0 N/A GOOD The example shows that the RAID striped volume is online and functioning. Under RAID 0 (disk striping), there is no replication of data across drives. The data is written to the RAID volume across all member disks in a round-robin fashion. If any one disk is lost, all data on the volume is lost. For this reason, RAID 0 cannot be used to ensure data integrity or availability, but can be used to increase write performance in some scenarios. For more information about the raidctl utility, see the raidctl (1M) man page. Note — The logical device names might appear differently on your system, depending on the number and type of add-on disk controllers installed. Related Information ■ “Disk Slot Numbers” on page 35 ■ “Delete a Hardware RAID Volume” on page 25 ▼ Configure a Hardware RAID Volume for the Solaris OS After a creating a RAID volume using raidctl, use format(lM) to configure and label the volume before attempting to use it in the Solaris Operating S...
Эта инструкция также подходит к моделям:Компьютеры - T5140 (269.52 kb)