03-10-2011
Hi DukeNuke2,
As you had mentioned in couple of posts earlier the error was due to EFI label .. the installation process was trying to set the property for bootfs .. i imported the zfs rpool and then try to set it but somehow the system was taking the disk as EFI labelled and you know very well that ZFS root only works on SMI label disk.
Thanks
This User Gave Thanks to fugitive For This Post:
10 More Discussions You Might Find Interesting
1. Solaris
Is it possible to create zfs pools and filesystems using the profile file in jumpstart?
edit to add: using Solaris 10 Release 11/06 (1 Reply)
Discussion started by: dangral
1 Replies
2. Solaris
I have created a flash archive from a Ldom on T5220 with zfs root solaris 10_u8. But after creation of flar the info shows the
content_architectures=sun4c,sun4d,sun4m,sun4u,sun4us,sun4s
but not sun4v due to which i 'm unable to install this flash archive on another Ldom on the same host. Is... (0 Replies)
Discussion started by: fugitive
0 Replies
3. Solaris
I have created a solaris10 update9 zfs root flash archive for sun4v environment which i 'm tryin to use for upgrading solaris10 update8 zfs root based server using live upgrade.
following is my current system status
lustatus
Boot Environment Is Active Active Can Copy
Name Complete Now... (0 Replies)
Discussion started by: fugitive
0 Replies
4. Solaris
Keep getting this message after system identification portion.
Search complete.
Discovering additional network configuration...
Completing system identification...
Starting remote procedure call (RPC) services:Assertion failed: *count <= max, file ns_dns_misc.c, line 189
Abort - core dumped... (0 Replies)
Discussion started by: soupbone38
0 Replies
5. Solaris
Has anyone tried Jumpstart with installing a ZFS root pool? I have read the docs (Custom Jumpstart and Advanced Install Guide(doc:821-1911);Network-Based Installations(doc:821-1909)).
My issue is that I get prompted for information each time I boot the client system. My goal is to get the... (8 Replies)
Discussion started by: bluescreen
8 Replies
6. Solaris
I jumpstarted a solaris sun4u box from WANboot and it completed but while coming up it gives following error and panics
Use is subject to license terms.
NOTICE: zfs_parse_bootfs: error 48
Cannot mount root on rpool/47 fstype zfs
panic/thread=180e000: vfs_mountroot: cannot mount root
... (0 Replies)
Discussion started by: fugitive
0 Replies
7. Solaris
I am building a new server on sol10_X86.
I am new to ZFS, this will be one of the first systems to use it.
I would like to have /opt /usr and a /u01 as separate file systems from the main ZFS pool. I know that this goes against the basic idea of ZFS, but this is so I can restrict the size/usage... (1 Reply)
Discussion started by: robsonde
1 Replies
8. Solaris
Hi All
After downloading ZFS documentation from oracle site, I am able to successfully migrate UFS root FS without zones to ZFS root FS. But in case of UFS root file system with zones , I am successfully able to migrate global zone to zfs root file system but zone are still in UFS root file... (2 Replies)
Discussion started by: sb200
2 Replies
9. Solaris
I've followed a few guides and have what appears to be a working jumpstart server. I can PXE boot a bare system, it gets an IP and launches the installer. However, it takes me to the screen:
SunOS Release 5.10 Version generic-147148-26 64 bit
Copyright (c) 1983, 2013, Oracle and/or its... (1 Reply)
Discussion started by: jnojr
1 Replies
10. Solaris
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
efi(4) Kernel Interfaces Manual efi(4)
NAME
efi - Extensible Firmware Interface description
DESCRIPTION
The EFI (Extensible Firmware Interface) is an interface between HP-UX and the Itanium-based platform firmware. The file system supported
by the Extensible Firmware Interface is based on the FAT file system. EFI encompasses the use of FAT-32 for a system partition, and FAT-12
or FAT-16 for removable media. The system partition is required on a bootable disk for the Itanium-based platform.
For a hard disk, the system partition is a contiguous grouping of sectors on the disk, where the starting sector and size are defined by
the EFI partition table, which resides on the second logical block of the hard disk, and/or by the Master Boot Record (MBR), which resides
on the first sector of the hard disk. For a floppy disk, a partition is defined to be the entire disk.
The System Partition can contain directories, data files, and EFI Images. The EFI system firmware may search the directory of the EFI sys-
tem partition, EFI volume, to find possible EFI Images that can be loaded. The HP-UX bootloader is one example of an EFI Image.
HP-UX contains a set of EFI utilities:
efi_fsinit(1M) Initialize an EFI volume; that is, create a header and an empty directory.
efi_cp(1M) Copy files to and from an EFI volume.
efi_mkdir(1M) Create directories in an EFI volume.
efi_ls(1M) List the contents of an EFI volume.
efi_rm(1M) Remove files from an EFI volume.
efi_rmdir(1M) Remove directories from an EFI volume.
The EFI utilities are the only utilities in HP-UX where the internal structure of an EFI volume is known. To the rest of HP-UX, an EFI
system partition is simply a partition containing unspecified data. The EFI volume cannot be mounted to HP-UX currently.
An EFI volume can be created on any HP-UX file (either regular disk file or device special file) that supports random access via lseek(2).
Within an EFI volume, individual files and directories are identified by 1- to 255-character file names. File names can consist of any
alphanumeric characters (A through Z, a through z, and 0 through 9) and the certain set of special characters (. $ % ' - _ @ ~ ` ! ( ) + ,
: ; = # & ? ^ [ ] { } space). The first character of an EFI file name can be any valid EFI characters, except the space. When comparing
two EFI names, differences in the case of alphabetic characters are not significant. For example, the following file names are considered
the same:
If one exists, the user will not be able to create the other.
The directory may be made up of multiple components, separated by slashes(/). The last directory component must be followed by a slash to
separate it from the file name. There are two special directory components, (.) and (..). They represent the current directory and the
parent directory as in other file systems.
SEE ALSO
efi_cp(1M), efi_fsinit(1M), efi_ls(1M), efi_mkdir(1M), efi_rm(1M), efi_rmdir(1M).
Itanium(R)-Based Processor Family Only efi(4)