Sponsored Content
Operating Systems Solaris Trouble creating a disk partition slice (EFI) Post 302939516 by hicksd8 on Thursday 26th of March 2015 07:00:56 AM
Old 03-26-2015
Slice 8 is a reserved area at the end of the disk.

I don't see too much wrong with what you are doing except my first questions are:

1. What hardware is this?
2. What version of Solaris
3. The disk is being recognised as a 500MB disk. Emphasis on the "MB"! Is that right????
4. What type of disk is it? SCSI, SATA, IDE or what? Showing as a NetApp LUN?

If it is right, it's been a long time since I've seen one of those.

---------- Post updated at 11:00 AM ---------- Previous update was at 10:49 AM ----------

Oh, and one more question:

5. Have you actually written an EFI label to this disk?

(EFI labels occupy 34 sectors (0-33) so the first partition usually starts at sector 34.)
If you haven't written the EFI label you might need to use:
Code:
# format -e

expert mode to do that.
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

slice & partition???

:confused: Hello, What is the difference between slice and partition on Solaris world? Regards (4 Replies)
Discussion started by: XNOR
4 Replies

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

3. Solaris

Installing using ZFS - need to remove EFI disk labels

What is the preferred way of doing this from a bare metal install? (3 Replies)
Discussion started by: LittleLebowski
3 Replies

4. Solaris

ZFS - whole disk Vs slice

we have a ZFS file system that was created as a pool of just one disk (raid on a SAN) when this was created it was done as a whole disk, and so EFI label. now we want to mount this file system into an LDOM. my understanding of how ldom's and disk works this is that we can only do this as a... (1 Reply)
Discussion started by: robsonde
1 Replies

5. Solaris

Partition overlaps another partition while creating new parition in solaris

hi all while formatting hard disk i am getting following error. Partition 1 ends at 266338338 It must be between 34 and 143374704. label error: EFI Labels do not support overlapping partitions Partition 8 overlaps partition 1. Warning: error writing EFI. Label failed. I have formatted the... (2 Replies)
Discussion started by: nikhil kasar
2 Replies

6. BSD

Find Partition/Slice UUID

I thought I had figured this out at one point, but I can't remember. Is there a way/command to get the UUIDs of a disk's partitions/slices in FreeBSD? Linux has the blkid command, which doesn't seem to be available. (2 Replies)
Discussion started by: AntumDeluge
2 Replies

7. 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
UEFI(8) 						    BSD System Manager's Manual 						   UEFI(8)

NAME
UEFI -- Unified Extensible Firmware Interface bootstrapping procedures DESCRIPTION
The UEFI Unified Extensible Firmware Interface provides boot- and run-time services to operating systems. UEFI is a replacement for the legacy BIOS on the i386 and amd64 CPU architectures, and is also used on arm64 and ia64. The UEFI boot process loads system bootstrap code located in an EFI System Partition (ESP). The ESP is a GPT or MBR partition with a spe- cific identifier that contains an msdosfs(5) FAT file system with a specified file hierarchy. Partition Scheme ESP Identifier GPT C12A7328-F81F-11D2-BA4B-00A0C93EC93B MBR 0xEF The UEFI boot process proceeds as follows: 1. UEFI firmware runs at power up and searches for an OS loader in the EFI system partition. The path to the loader may be set by an EFI environment variable. If not set, the default is /EFI/BOOT/BOOTX64.EFI. The default UEFI boot configuration for FreeBSD installs boot1.efi as /EFI/BOOT/BOOTX64.EFI. 2. boot1.efi locates the first partition with the type freebsd-ufs, and from it loads loader.efi. 3. loader.efi loads and boots the kernel, as described in loader(8). The vt(4) system console is automatically selected when booting via UEFI. FILES
/boot/boot1.efi First stage UEFI bootstrap /boot/boot1.efifat msdosfs(5) FAT file system image containing boot1.efi for use by bsdinstall(8) and the bootcode argument to gpart(8). /boot/loader.efi Final stage bootstrap /boot/kernel/kernel default kernel /boot/kernel.old/kernel typical non-default kernel (optional) SEE ALSO
vt(4), msdosfs(5), boot(8), gpart(8) HISTORY
UEFI boot support first appeared in FreeBSD 10.1. AUTHORS
UEFI boot support was developed by Benno Rice <benno@FreeBSD.org>, Ed Maste <emaste@FreeBSD.org>, and Nathan Whitehorn <nwhitehorn@FreeBSD.org>. The FreeBSD Foundation sponsored portions of the work. CAVEATS
EFI environment variables are not supported by loader(8) or the kernel. boot1.efi loads loader.efi from the first FreeBSD-UFS file system it locates, even if it is on a different disk. boot1.efi cannot load loader.efi from a ZFS(8) file system. As a result, UEFI does not support a typical root file system on ZFS configura- tion. BSD
October 17, 2014 BSD
All times are GMT -4. The time now is 01:36 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy