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
cmhaltcl(1m)															      cmhaltcl(1m)

NAME
cmhaltcl - halt a high availability cluster SYNOPSIS
cmhaltcl [-f] [-v] DESCRIPTION
cmhaltcl causes all nodes in a configured cluster to stop their cluster daemons, optionally halting all packages or applications in the process. To stop a cluster, a user must either be superuser(UID=0), or have an access policy of FULL_ADMIN allowed in the cluster configuration file. See access policy in cmquerycl(1). This command will halt all the daemons on all currently running systems. If the user only wants to shutdown a subset of daemons, the cmhaltnode command should be used instead. Options cmhaltcl supports the following options: -f Force the cluster to shutdown even if packages or group members are currently running. This will cause the packages and group members to be halted. If a package halt fails, the cluster halt will also fail. -v Verbose output will be displayed. RETURN VALUE
cmhaltcl returns the following value: 0 Successful completion. 1 Command failed. EXAMPLES
Halt the cluster daemons: cmhaltcl AUTHOR
cmhaltcl was developed by HP. SEE ALSO
cmquerycl(1m), cmhaltnode(1m), cmruncl(1m), cmrunnode(1m), cmviewcl(1m). Requires Optional Serviceguard Software cmhaltcl(1m)