|
|
Sponsored Content
Operating Systems
Solaris
EFI Disk labels on 3510 raid array
Post 302291730 by callmebob on Thursday 26th of February 2009 08:55:42 AM
02-26-2009
sorted thanks lowbyte. Apparently because it was over a TB, it automatically gives it an EFI label. Annoying thing was it kept putting /usr tags on the slices as I was trying to carve it up 
|
|
7 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I have 2 3510FC arrays, one a JBOD with (7) 146GB drives, and the other with dual RAID controllers, also (7) 146GB drives. The idea was to get 1TB mirrored. Anyway, after installing the Enterprise Storage Manager on a connected V880, I was able to use the "sccli" command and see/configure all the... (7 Replies)
Discussion started by: ridgeback00
7 Replies
2. Solaris
I would like to extend a logical drive on our 3510. I have four unallocated disks which I would like to use for this purpose.
The 3510 supports a Sun Cluster but for now all I wish to see is a "new" disk when I run format.
I am a little familiar with the telnet/ssh session on the 3510 but am... (2 Replies)
Discussion started by: malcqv
2 Replies
3. UNIX for Advanced & Expert Users
I have a 3510 disk array attached to a T2000 server.
The dmesg command shows disk error as follows and is generated a couple of times during the day
Aug 18 03:35:51 myserver SUNWscsdMonitor: <rctrl6042> Standard General Event, CHL:2 ID:22 Drive NOTICE: Drive Recovered Error - 5F8E1F... (1 Reply)
Discussion started by: Tirmazi
1 Replies
4. Solaris
What is the preferred way of doing this from a bare metal install? (3 Replies)
Discussion started by: LittleLebowski
3 Replies
5. Solaris
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. Filesystems, Disks and Memory
Hello,
On 4/20/2018, we performed a disk replacement on our IBM 8202 P7 server. After the disk was rebuilt, the SAS Disk Array sissas0 showed a status of degraded. However, the pdisks in the array all show a status of active.
We did see a message in errpt. DISK ARRAY PROTECTION SUSPENDED.
... (1 Reply)
Discussion started by: terrya
1 Replies
7. Solaris
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 POSIX
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)