Sponsored Content
Operating Systems Solaris Adding new hard drives on Sun SPARC T5440 server with Solaris 10 Post 302511069 by jlliagre on Tuesday 5th of April 2011 05:20:41 PM
Old 04-05-2011
A late comment but anyway, a much simpler method would have been to use ZFS instead of UFS. For example something like:
Code:
zpool create mirror c0t2d0 c0t2d1

and that's it.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Info Needed in Seting up An apache Web Server on A Sun Sparc with Solaris 8

I need help in the form of the complete procedures necessary in setting up an Apache web server on a Sun Sparc running Solaris 8 David Johnston P.S New to the Unix arena (1 Reply)
Discussion started by: David Johnston
1 Replies

2. Solaris

Add new hard disk to sun sparc server?

A sparc server has a new SCSI hard disk added and labeled by the engineer, but they need to be formatted identically to an existing disk (c4t0d0). You decide to script the process and run from the command line without interaction. I know that the following command line must be achieve this. #... (3 Replies)
Discussion started by: kingsan
3 Replies

3. Solaris

Sun Solaris 9 E250 -- Suggestions For External Hard Drives

Hello, Running a Sun Solaris 9 E250 and need advice or suggestions on what type of external hard disks are compatible and or available. It's an old machine and is due for replacement soon but in the short term need an external hard drive for backup etc as the partner/backup machine has just... (2 Replies)
Discussion started by: KenLynch
2 Replies

4. Filesystems, Disks and Memory

Help adding new hard drives

Folks; I just added 2 physical new hard drives to my SUSE server. My server is already running SUSE 10.3 version. Is there a command i can use to add the new space or even see if the system can sees them? (3 Replies)
Discussion started by: Katkota
3 Replies

5. Solaris

Application running too slow on Sun SPARC T5440 but run normal on sun M3000

Hi all, I have application running on sun server T5440 4x8x1.4 GHz, 64 GB RAM, application running very slow though load average too low. when I install my application on another server SUN M3000 (One CPU 1x8x2.5GHz, 8GB RAM), application run smoothly. Here is my server T5440 info: ... (6 Replies)
Discussion started by: insatiable1610
6 Replies

6. Solaris

Unplug power from Sparc Server T5440 when in OpenBoot

show /HOST command shows that status = OpenBoot Running when in this state, can the power be unplugged from the server ? we are unable to bring the status to "powered off". Even if we issue "stop /SYS" it will momentarily be in the powered off status and then go back to power on... (1 Reply)
Discussion started by: paulk93
1 Replies

7. Solaris

SPARC Enterprise T5440 Server, can not power off

SPARC Enterprise T5440 Server, can not power off I connect to Service Processor via serial port and submit the following to boot the system, it boots fine but can not power off the system. Can someone help? The following takes me to unix login -> start /SYS -> start /SP/console... (6 Replies)
Discussion started by: paulk93
6 Replies

8. Solaris

Solaris 8 - Accessing Hard Drives

Hi, I have two SCSI Hard Drives in a Sun Solaris 8 server as shown below. I would like to access Disk1 and look at its contents, directory structure and files. How do I change my default directory from Disk 0 to Disk 1 and vice versa? Thank you. (5 Replies)
Discussion started by: ssabet
5 Replies
GPTZFSBOOT(8)						    BSD System Manager's Manual 					     GPTZFSBOOT(8)

NAME
gptzfsboot -- GPT bootcode for ZFS on BIOS-based computers DESCRIPTION
gptzfsboot is used on BIOS-based computers to boot from a filesystem in a ZFS pool. gptzfsboot is installed in a freebsd-boot partition of a GPT-partitioned disk with gpart(8). IMPLEMENTATION NOTES
The GPT standard allows a variable number of partitions, but gptzfsboot only boots from tables with 128 partitions or less. BOOTING
gptzfsboot tries to find all ZFS pools that are composed of BIOS-visible hard disks or partitions on them. gptzfsboot looks for ZFS device labels on all visible disks and in discovered supported partitions for all supported partition scheme types. The search starts with the disk from which gptzfsboot itself was loaded. Other disks are probed in BIOS defined order. After a disk is probed and gptzfsboot determines that the whole disk is not a ZFS pool member, the individual partitions are probed in their partition table order. Currently GPT and MBR partition schemes are supported. With the GPT scheme, only partitions of type freebsd-zfs are probed. The first pool seen during probing is used as a default boot pool. The filesystem specified by the bootfs property of the pool is used as a default boot filesystem. If the bootfs property is not set, then the root filesystem of the pool is used as the default. zfsloader(8) is loaded from the boot filesystem. If /boot.config or /boot/config is present in the boot filesystem, boot options are read from it in the same way as boot(8). The ZFS GUIDs of the first successfully probed device and the first detected pool are made available to zfsloader(8) in the vfs.zfs.boot.primary_vdev and vfs.zfs.boot.primary_pool variables. USAGE
Normally gptzfsboot will boot in fully automatic mode. However, like boot(8), it is possible to interrupt the automatic boot process and interact with gptzfsboot through a prompt. gptzfsboot accepts all the options that boot(8) supports. The filesystem specification and the path to zfsloader(8) are different from boot(8). The format is [zfs:pool/filesystem:][/path/to/loader] Both the filesystem and the path can be specified. If only a path is specified, then the default filesystem is used. If only a pool and filesystem are specified, then /boot/zfsloader is used as a path. Additionally, the status command can be used to query information about discovered pools. The output format is similar to that of zpool status (see zpool(8)). The configured or automatically determined ZFS boot filesystem is stored in the zfsloader(8) loaddev variable, and also set as the initial value of the currdev variable. FILES
/boot/gptzfsboot boot code binary /boot.config parameters for the boot block (optional) /boot/config alternative parameters for the boot block (optional) EXAMPLES
gptzfsboot is typically installed in combination with a ``protective MBR'' (see gpart(8)). To install gptzfsboot on the ada0 drive: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 gptzfsboot can also be installed without the PMBR: gpart bootcode -p /boot/gptzfsboot -i 1 ada0 SEE ALSO
boot.config(5), boot(8), gpart(8), loader(8), zfsloader(8), zpool(8) HISTORY
gptzfsboot appeared in FreeBSD 7.3. AUTHORS
This manual page was written by Andriy Gapon <avg@FreeBSD.org>. BUGS
gptzfsboot looks for ZFS meta-data only in MBR partitions (known on FreeBSD as slices). It does not look into BSD disklabel(8) partitions that are traditionally called partitions. If a disklabel partition happens to be placed so that ZFS meta-data can be found at the fixed off- sets relative to a slice, then gptzfsboot will recognize the partition as a part of a ZFS pool, but this is not guaranteed to happen. BSD
September 15, 2014 BSD
All times are GMT -4. The time now is 02:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy