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
thank u very much, (1 Reply)
Discussion started by: coralsea
1 Replies
2. Filesystems, Disks and Memory
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
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
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
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
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
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
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
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
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
LEARN ABOUT FREEBSD
boot0cfg
BOOT0CFG(8) BSD System Manager's Manual BOOT0CFG(8)
NAME
boot0cfg -- boot manager installation/configuration utility
SYNOPSIS
boot0cfg [-Bv] [-b boot0] [-d drive] [-e bell character] [-f file] [-i volume-id] [-m mask] [-o options] [-s slice] [-t ticks] disk
DESCRIPTION
The FreeBSD 'boot0' boot manager permits the operator to select from which disk and slice an i386 machine (PC) is booted.
Note that what are referred to here as ``slices'' are typically called ``partitions'' in non-BSD documentation relating to the PC. Typi-
cally, only non-removable disks are sliced.
The boot0cfg utility optionally installs the 'boot0' boot manager on the specified disk; and allows various operational parameters to be con-
figured.
On PCs, a boot manager typically occupies sector 0 of a disk, which is known as the Master Boot Record (MBR). The MBR contains both code (to
which control is passed by the PC BIOS) and data (an embedded table of defined slices).
The options are:
-B Install the 'boot0' boot manager. This option causes MBR code to be replaced, without affecting the embedded slice table.
-b boot0
Specify which 'boot0' image to use. The default is /boot/boot0 which will use the video card as output, alternatively /boot/boot0sio
can be used for output to the COM1 port. (Be aware that nothing will be output to the COM1 port unless the modem signals DSR and CTS
are active.)
-d drive
Specify the drive number used by the PC BIOS in referencing the drive which contains the specified disk. Typically this will be 0x80
for the first hard drive, 0x81 for the second hard drive, and so on; however any integer between 0 and 0xff is acceptable here.
-e bell character
Set the character to be printed in case of input error.
-f file
Specify that a backup copy of the preexisting MBR should be written to file. This file is created if it does not exist, and replaced
if it does.
-i volume-id
Specifies a volume-id (in the form XXXX-XXXX) to be saved at location 0x1b8 in the MBR. This information is sometimes used by NT, XP
and Vista to identify the disk drive. The option is only compatible with version 2.00 of the 512-byte boot block.
-m mask
Specify slices to be enabled/disabled, where mask is an integer between 0 (no slices enabled) and 0xf (all four slices enabled).
Each mask bit enables corresponding slice if set to 1. The least significant bit of the mask corresponds to slice 1, the most sig-
nificant bit of the mask corresponds to slice 4.
-o options
A comma-separated string of any of the following options may be specified (with ``no'' prepended as necessary):
packet Use the disk packet (BIOS INT 0x13 extensions) interface, as opposed to the legacy (CHS) interface, when doing disk I/O.
This allows booting above cylinder 1023, but requires specific BIOS support. The default is 'packet'.
setdrv Forces the drive containing the disk to be referenced using drive number definable by means of the -d option. The default is
'nosetdrv'.
update Allow the MBR to be updated by the boot manager. (The MBR may be updated to flag slices as 'active', and to save slice
selection information.) This is the default; a 'noupdate' option causes the MBR to be treated as read-only.
-s slice
Set the default boot selection to slice. Values between 1 and 4 refer to slices; a value of 5 refers to the option of booting from a
second disk. The special string ``PXE'' or a value of 6 can be used to boot via PXE.
-t ticks
Set the timeout value to ticks. (There are approximately 18.2 ticks per second.)
-v Verbose: display information about the slices defined, etc.
FILES
/boot/boot0 The default 'boot0' image
/boot/boot0sio Image for serial consoles (COM1,9600,8,N,1,MODEM)
EXIT STATUS
The boot0cfg utility exits 0 on success, and >0 if an error occurs.
EXAMPLES
To boot slice 2 on the next boot:
boot0cfg -s 2 ada0
To enable just slices 1 and 3 in the menu:
boot0cfg -m 0x5 ada0
To go back to non-interactive booting, use fdisk(8) to install the default MBR:
fdisk -B ada0
SEE ALSO
geom(4), boot(8), fdisk(8), gpart(8)
AUTHORS
Robert Nordier <rnordier@FreeBSD.org>
BUGS
Use of the 'packet' option may cause 'boot0' to fail, depending on the nature of BIOS support.
Use of the 'setdrv' option with an incorrect -d operand may cause the boot0 code to write the MBR to the wrong disk, thus trashing its previ-
ous content. Be careful.
BSD
October 1, 2013 BSD