Sponsored Content
Full Discussion: Moving to RAID1
Operating Systems Solaris Moving to RAID1 Post 302960744 by hicksd8 on Thursday 19th of November 2015 11:33:00 AM
Old 11-19-2015
Looking up the Sunfire V125 it appears that you have to resort to software mirroring (meta) because there is no built-in hardware RAID controller.

Therefore the first questions are:

Q: Are all the cylinders of the current disk allocated? Is there any unallocated space?

The SVM requires a very small slice to keep it's metadata on (typically circa 10MB) which also means...

Q: Are all slices allocated? For example is slice 7 not in use?

If you have a free slice but no cylinders it's possible that you can shrink one slice by a few cylinders in order that you can create your metadata slice.

Here's some reading material (one link is a thread on this great forum plus two others to complement) to give you the idea. Yes, you can do this without reinstallation.

root disk mirroring in solaris volume manager for solaris 10

Solaris Volume Manager (SVM)

[How To] Mirror Root Disk with Solaris Volume Manager (SVM) | UNIX Note

---------- Post updated at 04:33 PM ---------- Previous update was at 11:42 AM ----------

What filesystem is used? UFS or ZFS?

Last edited by hicksd8; 11-19-2015 at 08:18 AM..
These 2 Users Gave Thanks to hicksd8 For This Post:
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How can i set up Software disk mirroring(Raid1) in SCO 5.0.5 with two SCSI harddisk ?

thank u very much, (1 Reply)
Discussion started by: coralsea
1 Replies

2. Filesystems, Disks and Memory

Pulling a drive on RAID1 hangs system

I'm setting up a server with software RAID1, and everything is working perfectly, except that when I pull either of the drives, the system completely hangs and has to be rebooted. The computer is a Tyan Transport GX28, which is alleged to have hot-swappable SATA. I can fail a drive and the system... (1 Reply)
Discussion started by: vertigo23
1 Replies

3. Solaris

RAID1 and LDoms

I have a Netra T5220 Solaris 10 server with LDoms installed and enabled. RAID1 is enabled in the control domain with the following slices: d50 -m d51 d52 1 d51 1 1 c1t0d0s5 d52 1 1 c1t1d0s5 d10 -m d11 d12 1 d11 1 1 c1t0d0s0 d12 1 1 c1t1d0s0 d20 -m d21 d22 1 d21 1 1 c1t0d0s1 d22 1 1... (14 Replies)
Discussion started by: StarSol
14 Replies

4. AIX

rootvg and hardware raid1

Good Morning, We have a JS22 blade that we will be loading AIX5.3 onto it. We just discovered that the JS22 will only support one drive, so we are planning on booting this blade from the Fiber Channel SAN. Orginally we used 2 physical drives and set up RAID 1 and presented the logical drive... (0 Replies)
Discussion started by: brachinus
0 Replies

5. 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

6. Filesystems, Disks and Memory

Solaris 10 Raid1

does anyone k ow the answer to this? OS solaris 10 using the command raidctl -c c1t0d0 c1t1d0, this took about 4 mins to return to the prompt with "Volume c1t0d0 is created successfully!" then using format I saw AVAILABLE DISK SELECTIONS: 0. c1t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>... (1 Reply)
Discussion started by: powerrack
1 Replies

7. Linux

SPARC, Linux, RAID1, SILO

Hi, I've been searching for answers for two days and didn't find any definite answers on building RAID1 on SPARC. The main problem was with SILO (Sparc Improved boot LOader): can it boot from RAID partition or not. So I just tried it and it works. I've done this on Debian, but it should be... (0 Replies)
Discussion started by: Luka
0 Replies

8. Linux

raid1 (dmraid) - bad sectors - mount - smartd - complicated!

Hello, i'm running a server with two disks in raid1.. it seems that some bad sectors have recently appeared on one of the disks. Aug 9 08:26:19 linux smartd: Device: /dev/sda, FAILED SMART self-check. BACK UP DATA NOW! Aug 9 08:26:19 linux smartd: Device: /dev/sda, 2 Currently... (0 Replies)
Discussion started by: TehOne
0 Replies

9. Ubuntu

Ubuntu desktop RAID1 boot problem.

Hello, I installed ubuntu desktop just recently in aim to create a RAID1 configuration using software RAID MDADM. I have the following configuration as fdisk -l reports: Disk /dev/sda: 223,6 GiB, 240057409536 bytes, 468862128 sectors Units: sectors of 1 * 512 = 512 bytes Sector size... (5 Replies)
Discussion started by: Reol
5 Replies

10. Ubuntu

Samba share on software raid1

Hello! i am having a ubuntu server with two empty disks and connected software raid1 to it. I am having /mnt/raid folder which i created to mount it. SO should i now make a share folder inside that or what? I ama bit confused when a raid is present. (27 Replies)
Discussion started by: tomislav91
27 Replies
re-preinstall(1M)					  System Administration Commands					 re-preinstall(1M)

NAME
re-preinstall - installs the JumpStart software on a system SYNOPSIS
cdrom-mnt-pt/Solaris_XX/Tools/Boot/usr/sbin/install.d/re-preinstall [-m Solaris_boot_dir] [-k platform_name] target-slice DESCRIPTION
re-preinstall installs the JumpStart software (preinstall boot image) on a system, so you can power-on the system and have it automatically install the Solaris software (perform a JumpStart installation on the system). When you turn on a re-preinstalled system, the system looks for the JumpStart software on the system's default boot disk. All new SPARC systems have the JumpStart software already preinstalled. The XX in Solaris_XX is the version number of the Solaris release being used. You can use the re-preinstall command in several ways. The most common way is to run re-preinstall on a system to install the JumpStart software on its own default boot disk. This is useful if you want to restore a system to its original factory conditions. (See the first procedure described in EXAMPLES.) You can also run re-preinstall on a system to install JumpStart software on any attached disk (non-boot disk). After you install the Jump- Start software on a disk, you can move the disk to a different system and perform a JumpStart installation on the different system. (See the second procedure described in EXAMPLES.) re-preinstall creates a standard file system on the specified target-slice (usually slice 0), and re-preinstall makes sure there is enough space on the target-slice for the JumpStart software. If sufficient space is not available, re-preinstall fails with the following message: re-preinstall: target-slice too small xx Megabytes required You can use the format(1M) command to create sufficient space on the target-slice for the JumpStart software. OPTIONS
The following options are supported: -k platform_name Platform name of the system that will use the disk with the JumpStart software. The default is the platform name of the system running re-preinstall. (Use the uname(1) command (-i option) to determine a system's platform name.) -m Solaris_boot_dir Absolute path to the Solaris_XX/Tools/Boot subdirectory of a mounted Solaris CD or a Solaris CD copied to disk that re-preinstall uses to install the JumpStart software. The default is root (/), which is where the Solaris CD is mounted in single-user mode. OPERANDS
The following operands are supported: target-slice Device name of the disk slice where the JumpStart software will be installed (usually slice 0), for example, c0t3d0s0. EXAMPLES
Example 1: Installing the JumpStart Software on a System's Own Default Boot Disk The following procedure installs the JumpStart software on a system's own default boot disk: 1. From the ok prompt, boot the system from the Solaris media CD or DVD in single-user mode: ok boot cdrom -s 2. The following command installs the Jumpstart software on the System default boot disk, c0t0d0s0 on a Solaris 9 system: example# /usr/sbin/install.d/re-preinstall c0t0d0s1 3. Reboot the slice: example# reboot disk:b Example 2: Installing the JumpStart Software on a System's Attached (non-boot) Disk The following procedure installs the JumpStart software on a system's attached (non-boot) disk: 1. Mount the Solaris CD or DVD if vold(1M) is not running or CD or DVD is not mounted. 2. Use the format(1M) command to determine the target-slice where JumpStart will be installed. 3. Use the uname(1) command (-i option) to determine the platform name of the system that will use the re-preinstalled disk 4. Run re-preinstall with the -m Solaris_boot_dir option if the Solaris CD or DVD is not mounted on /cdrom. The following command installs the JumpStart software on the system's attached disk for a system with a Sun4u kernel architecture, and it uses the Solaris CD or DVD mounted with vold(1M) on a Solaris 9 system: example# /cdrom/cdrom/s1/usr/bin/install.d/re-preinstall -m /cdrom/cdrom/s1 -k sun4u c0t2d0s0 EXIT STATUS
The following exit values are returned: 0 Successful completion. 1 An error has occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcdrom (Solaris CD, | | |SPARC Platform Edition) | +-----------------------------+-----------------------------+ SEE ALSO
uname(1), eeprom(1M), format(1M), mount(1M), vold(1M), attributes(5) Solaris 10 Installation Guide: Basic Installations SunOS 5.10 9 Apr 2002 re-preinstall(1M)
All times are GMT -4. The time now is 08:36 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy