Sponsored Content
Operating Systems Solaris Installing using ZFS - need to remove EFI disk labels Post 302552377 by fpmurphy on Friday 2nd of September 2011 03:49:23 PM
Old 09-02-2011
As far as I know disks used in ZFS pools require EFI labels.
 

6 More Discussions You Might Find Interesting

1. Solaris

EFI Disk labels on 3510 raid array

Hi Peeps, Can anyone help me an EFI lablel on a 3510 raid array that I cannot get rid of, format -e and label just asks you if you want to label it. Want an SMI label writing to it. Anyone got any ideas on how to remove the EFI label? Thanks in advance Martin (2 Replies)
Discussion started by: callmebob
2 Replies

2. Solaris

Installing ZFS on an existing Solaris 10 install (UFS)

Hello, I am new to Solaris so i apologize upfront if my questions seem trivial. I am trying to install a ZFS file system on a Solaris 10 machine with UFS already installed on it. I want to run: # zpool create pool_zfs c0t0d0 then: # zfs create pool_zfs/fs My question is more to... (3 Replies)
Discussion started by: mcdef
3 Replies

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

4. Solaris

Need to remove a disk from zfs pool

I accidently added a disk in different zpool instead of pool, where I want. root@prtdrd21:/# zpool status cvfdb2_app_pool pool: cvfdb2_app_pool state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM cvfdb2_app_pool ONLINE 0 0 0... (1 Reply)
Discussion started by: solaris_1977
1 Replies

5. Solaris

Trouble creating a disk partition slice (EFI)

Hi all, I am using SPARC Solaris 11.1 with EFI labelled disks. I am new to ZFS file systems and slightly stuck when trying to create a partition (slice) on one of my LUNs. EFI labels use sectors and blocks and I am not sure how exactly it works. From here I can try and create a... (2 Replies)
Discussion started by: selectstar
2 Replies

6. Solaris

EFI disk labeling / understand the parition table / sectors not continue

Hi all, I have a EFI disk and it is use in zfs pool. partition> p Volume: rpool Current partition table (original): Total disk sectors available: 1172107117 + 16384 (reserved sectors) Part Tag Flag First Sector Size Last Sector 0 usr wm ... (8 Replies)
Discussion started by: javanoob
8 Replies
efi_alloc_and_init(3EXT)				    Extended Library Functions					  efi_alloc_and_init(3EXT)

NAME
efi_alloc_and_init, efi_alloc_and_read, efi_free, efi_write, efi_use_whole_disk - manipulate a disk's EFI Partition Table SYNOPSIS
cc [ flag ... ] file... -lefi [ library ... ] #include <sys/vtoc.h> #include <sys/efi_partition.h> int efi_alloc_and_init(int fd, uint32_t nparts, dk_gpt_t **vtoc); int efi_alloc_and_read(int fd, dk_gpt_t **vtoc); void efi_free(dk_gpt_t *vtoc); int efi_write(int fd, dk_gpt_t *vtoc); int efi_use_whole_disk(int fd); DESCRIPTION
The efi_alloc_and_init() function initializes the dk_gpt_t structure specified by vtoc in preparation for a call to efi_write(). It calcu- lates and initializes the efi_version, efi_lbasize, efi_nparts, efi_first_u_lba, efi_last_lba, and efi_last_u_lba members of this sturcture. The caller can then set the efi_nparts member. The efi_alloc_and_read() function allocates memory and returns the partition table. The efi_free() function frees the memory allocated by efi_alloc_and_init() and efi_alloc_and_read(). The efi_write() function writes the EFI partition table. The efi_use_whole_disk() function takes any space that is not contained in the disk label and adds it to the last physically non-zero area before the reserved slice (from slice 0 to slice 6 or unallocated space). The fd argument refers to any slice on a raw disk, opened with O_NDELAY. See open(2). The nparts argument specifies the number of desired partitions. The vtoc argument is a dk_gpt_t structure that describes an EFI partition table and contains at least the following members: uint_t efi_version; /* set to EFI_VERSION_CURRENT */ uint_t efi_nparts; /* number of partitions in efi_parts */ uint_t efi_lbasize; /* size of block in bytes */ diskaddr_t efi_last_lba; /* last block on the disk */ diskaddr_t efi_first_u_lba; /* first block after labels */ diskaddr_t efi_last_u_lba; /* last block before backup labels */ struct dk_part efi_parts[]; /* array of partitions */ RETURN VALUES
Upon successful completion, efi_alloc_and_init() returns 0. Otherwise it returns VT_EIO if an I/O operation to the disk fails. Upon successful completion, efi_alloc_and_read() returns a positive integer indicating the slice index associated with the open file descriptor. Otherwise, it returns a negative integer to indicate one of the following: VT_EIO An I/O error occurred. VT_ERROR An unknown error occurred. VT_EINVAL An EFI label was not found. Upon successful completion, efi_write() returns 0. Otherwise, it returns a negative integer to indicate one of the following: VT_EIO An I/O error occurred. VT_ERROR An unknown error occurred. VT_EINVAL The label contains incorrect data. Upon successfully completion, efi_use_whole_disk() returns 0. Otherwise, it returns a negative integer to indicate one of the following: VT_EIO An I/O error occurred. VT_ERROR An unknown error occurred. VT_EINVAL The label contains incorrect data. VT_ENOSPC Space out of label was not found. USAGE
The EFI label is used on disks with more than 1^32-1 blocks. For compatibility reasons, the read_vtoc(3EXT) and write_vtoc() functions should be used on smaller disks. The application should attempt the read_vtoc() or write_vtoc() call, check for an error of VT_ENOTSUP, then call the analogous EFI function. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Committed | +-----------------------------+-----------------------------+ |MT-Level |Unsafe | +-----------------------------+-----------------------------+ SEE ALSO
fmthard(1M), format(1M), prtvtoc(1M), ioctl(2), open(2), libefi(3LIB), read_vtoc(3EXT), attributes(5), dkio(7I) SunOS 5.11 8 May 2008 efi_alloc_and_init(3EXT)
All times are GMT -4. The time now is 07:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy