cannot label 'c0t5000CCA0251EF65Cd0': EFI labeled devices are not supported on root pools


 
Thread Tools Search this Thread
Operating Systems Solaris cannot label 'c0t5000CCA0251EF65Cd0': EFI labeled devices are not supported on root pools
# 8  
Old 06-06-2012
You are indeed correct, I was missing s0 on both devices, worked w/o issue this time! Thanks guys.

Code:
prtvtoc /dev/rdsk/${disk}s2 | fmthard -s - /dev/rdsk/${mirrordisk}s2
fmthard:  New volume table of contents now in place.

zpool attach -f rpool ${disk}s0 ${mirrordisk}s0

Login or Register to Ask a Question

Previous Thread | Next Thread

4 More Discussions You Might Find Interesting

1. Solaris

Flash Archive Jumpstart with multiple ZFS Pools

Hi, I'm trying to get a Flash Archive Jumpstart Running with ZFS Filesystem. For Testing I set up a VirtualBox VM with 2 Disks attached. On the first disk I have the ZFS root pool, on the second Disk I have some more ZFS Pools which I use for 2 additional Zones I've set up. Restoring works fine if... (1 Reply)
Discussion started by: NoelzeN
1 Replies

2. Solaris

Installing Sun Cluster on ZFS root pools

Hi All! I have been tasked with creating a clustered file system for two systems running Sol 10 u8. These systems have 3 zones each and the global zone has ZFS on the boot disk. We currently have one system sharing an NFS mount to both of these systems. The root zfs pool status (on the... (2 Replies)
Discussion started by: bluescreen
2 Replies

3. Solaris

Help:"Bad checksum in disk label" and "Can't open disk label package"?

Hello, I'm brand new to Sun/Solaris. I have a Sun Blade 150, with SunOS 5.8. I wanted to make a backup to prevent future data loss, so I put the disk in a normal PC with Windows XP to try to make a backup with Norton Ghost, the disk was detected, but not the file volume, so I place the disk... (6 Replies)
Discussion started by: Resadija
6 Replies

4. UNIX for Dummies Questions & Answers

passthrough devices vs. named devices

I am having trouble understanding the difference between a passthrough device and a named device and when you would use one or the other to access equipment. As an example, we have a tape library and giving the command "camcontrol devlist" gives the following output: akx# camcontrol... (1 Reply)
Discussion started by: thumper
1 Replies
Login or Register to Ask a Question
CRM_DIFF(8)							  [FIXME: manual]						       CRM_DIFF(8)

NAME
crm_diff - identify changes to the cluster configuration and apply patches to the configuration files SYNOPSIS
crm_diff [-?|-V] [-o filename] [-O string] [-p filename] [-n filename] [-N string] DESCRIPTION
The crm_diff command assists in creating and applying XML patches. This can be useful for visualizing the changes between two versions of the cluster configuration or saving changes so they can be applied at a later time using cibadmin. OPTIONS
--help, -? Print a help message. --original filename, -o filename Specify the original file against which to diff or apply patches. --new filename, -n filename Specify the name of the new file. --original-string string, -O string Specify the original string against which to diff or apply patches. --new-string string, -N string Specify the new string. --patch filename, -p filename Apply a patch to the original XML. Always use with -o. --cib, -c Compare or patch the inputs as a CIB. Always specify the base version with -o and provide either the patch file or the second version with -p or -n, respectively. --stdin, -s Read the inputs from stdin. EXAMPLES
Use crm_diff to determine the differences between various CIB configuration files and to create patches. By means of patches, easily reuse configuration parts without having to use the cibadmin command on every single one of them. 1. Obtain the two different configuration files by running cibadmin on the two cluster setups to compare: cibadmin -Q > cib1.xml cibadmin -Q > cib2.xml 2. Determine whether to diff the entire files against each other or compare just a subset of the configurations. 3. To print the difference between the files to stdout, use the following command: crm_diff -o cib1.xml -n cib2.xml 4. To print the difference between the files to a file and create a patch, use the following command: crm_diff -o cib1.xml -n cib2.xml > patch.xml 5. Apply the patch to the original file: crm_diff -o cib1.xml -p patch.xml FILES
/var/lib/heartbeat/crm/cib.xml--the CIB (minus status section) on disk. Editing this file directly is strongly discouraged. SEE ALSO
??? AUTHOR
crm_diff was written by Andrew Beekhof. [FIXME: source] 07/05/2010 CRM_DIFF(8)