Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Trouble creating a disk partition slice (EFI)
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

LEARN ABOUT SUNOS

bootctl

BOOTCTL(1)							      bootctl								BOOTCTL(1)

NAME

       bootctl - Control the firmware and boot manager settings

SYNOPSIS

       bootctl [OPTIONS...] status

       bootctl [OPTIONS...] list

       bootctl [OPTIONS...] update

       bootctl [OPTIONS...] install

       bootctl [OPTIONS...] remove

DESCRIPTION

       bootctl checks, updates, installs or removes the boot loader from the current system.

       bootctl status checks and prints the currently installed versions of the boot loader binaries and all current EFI boot variables.

       bootctl list displays all configured boot loader entries.

       bootctl update updates all installed versions of systemd-boot, if the current version is newer than the version installed in the EFI system
       partition. This also includes the EFI default/fallback loader at /EFI/BOOT/BOOT*.EFI. A systemd-boot entry in the EFI boot variables is
       created if there is no current entry. The created entry will be added to the end of the boot order list.

       bootctl install installs systemd-boot into the EFI system partition. A copy of systemd-boot will be stored as the EFI default/fallback
       loader at /EFI/BOOT/BOOT*.EFI. A systemd-boot entry in the EFI boot variables is created and added to the top of the boot order list.

       bootctl remove removes all installed versions of systemd-boot from the EFI system partition, and removes systemd-boot from the EFI boot
       variables.

       If no command is passed, status is implied.

OPTIONS

       The following options are understood:

       -h, --help
	   Print a short help text and exit.

       --version
	   Print a short version string and exit.

       --path=
	   Path to the EFI System Partition (ESP). If not specified, /efi, /boot, and /boot/efi are checked in turn. It is recommended to mount
	   the ESP to /boot, if possible.

       -p, --print-path
	   This option modifies the behaviour of status. Just print the path to the EFI System Partition (ESP) to standard output and exit.

       --no-variables
	   Do not touch the EFI boot variables.

EXIT STATUS

       On success, 0 is returned, a non-zero failure code otherwise.

SEE ALSO

       Boot loader specification[1] systemd boot loader interface[2]

NOTES

	1. Boot loader specification
	   https://www.freedesktop.org/wiki/Specifications/BootLoaderSpec

	2. systemd boot loader interface
	   https://www.freedesktop.org/wiki/Software/systemd/BootLoaderInterface

systemd 237																BOOTCTL(1)
All times are GMT -4. The time now is 11:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy