search for: bootf

...t; 0000000 000000 000000 000000 000000 000000 > 0000012 > # > > Doesn''t look like an EFI label. > No that doesn''t appear like an EFI label. So it appears that ZFS is seeing something there that it''s interpreting as an EFI label. Then the command to set the bootfs property is failing due to that. To restate the problem the BE can''t be activated because we can''t set the bootfs property of the root pool and even the ZFS command to set it fails with "property ''bootfs'' not supported on EFI labeled devices" for exa...

I am getting the following error, however as you can see below this is a SMI label... cannot set property for ''rpool'': property ''bootfs'' not supported on EFI labeled devices # zpool get bootfs rpool NAME PROPERTY VALUE SOURCE rpool bootfs - default # zpool set bootfs=rpool/ROOT/s10s_u8wos_08a rpool cannot set property for ''rpool'': property ''bootfs'' not supported on EFI labeled devices...

...exentaCP and its zfs boot facility. I tried to figure out how what commands to run and I ran zpool history like this # zpool history 2007-06-20.10:19:46 zfs snapshot syspool/rootfs at mysnapshot 2007-06-20.10:20:03 zfs clone syspool/rootfs at mysnapshot syspool/myrootfs 2007-06-20.10:23:21 zfs set bootfs=syspool/myrootfs syspool As you can see it says I did a "zfs set bootfs=..." even though the correct command should have been "zpool set bootfs=...". Of course this is purely cosmetical. I currently don''t have access to a recent nevada build so I just wonder if this i...

I have NexentaCP2 (Opensolaris b104+). Parameters for the kernel: ''zfs-bootfs=syspool/rootfs-nmu-000,bootpath=/xpvd/xdf@0:a'' Pygrub returns: ''zfs-bootfs=syspool/30,bootpath=/xpvd/xdf@0:a'' Result: Boot with pygrub don''t work. What is "30" in syspool/30 ? _______________________________________________ Xen-users mailing list...

I''m still trying to find a fix/workaround for the problem described in Unable to mount root pool dataset http://opensolaris.org/jive/thread.jspa?messageID=492460 Since the Blade 1500''s rpool is mirrored, I''ve decided to detach the second half of the mirror, relabel the disk, create an alternative rpool (rpool2) there, copy the current BE (snv_134) using beadm

...with a simple zfs pool (not mirrored) and it just reboots right away. If I try to setup grub manually, it has no problem in both cases finding the root_archive, etc...: grub> root (hd0,0,a) Filesystem type is zfs, partition type 0xbf grub> /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS loading ''platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS cpu: ''AuthenticAMD'' family 15 model 47 step 0 [BIOS accepted mixed-mode target setting!] [Multiboot-kluge, loadaddr=0xbffe38, text-and-data=0x161958, bss=0x0, entry=0xc00000] ''/platform/i86pc/kernel...

...menu. The package contains a necessary module for CIFS. After pkg install SUNWsmbfskr, I rebooted the box. There was no grub menu anymore but only the grub prompt. I managed to boot it manually using another BE. I was unable to use the original BE getting this error message during the manual boot: bootfs rpool/ROOT/rp01 OK kernel$ /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS OK module$ /platform/i86pc/$ISADIR/boot_archive after this command I got the error: Error 16: Inconsistent filesystem structure. I had to use a different BE to boot up the system. I''ve tried to repair boot_arch...

Hi Lin, In addition to bug 6541114... Bug ID 6541114 Synopsis GRUB/ZFS fails to load files from a default compressed (lzjb) root ... I found yet another way to get the "Error 16: Inconsistent filesystem structure" from GRUB. This time when trying to boot a Xen Dom0 from a zfs bootfs Synopsis: grub/zfs-root: cannot boot xen from a zfs root ======================================================================== I''ve tried to install snv66 + xen into an lzjb compressed zfs root filesystem. menu.lst entry for xen is: # ----------------------------------------------...

https://bugzilla.redhat.com/show_bug.cgi?id=466681 just to be sure that some one in xvm-team notices that before any bits from xvm-gate are putback ;) Florian

Hi, yesterday evening I tried to upgrade my Ultra 60 to 2009.06 from SXCE snv_98. I can''t use AI Installer because OpenPROM is version 3.27. So I built IPS from source, then created a zpool on a spare drive and installed OS 2006.06 on it To make the disk bootable I used: installboot -F zfs /usr/platform/`uname -i`/lib/fs/zfs/bootblk /dev/rdsk/c0t1d0s0 using the executable from my new

...that work without a problem. What I am trying to do is recreate the rpool and underlying zfs filesystems (rpool/ROOT, rpool/s10_uXXXXXX, rpool/dump, rpool/swap, rpool/export, and rpool/export/home). I then mount the pool at a alternate root and restore the tar archive. Lastly, I set the zpool bootf option to the correct zfs filesystem and run the installgrub command. I have not had any luck so far. -- This message posted from opensolaris.org

> http://blogs.sun.com/ptelles/entry/sun_xvm_hypervisor_ > part_i Hello, I can''t get this to work. My pc just reboots after "Syncing filesystem" when I try to boot into xVM Hypervisor. I have a clean install of OpenSolaris 2008.11. -- This message posted from opensolaris.org

...pha, beta), data = RPOvTS, start = list(alpha = 10, beta = 1), control = list(maxiter = 10000, minFactor=1/20048), trace = T) summary(NlMFunc1) logLik(NlMFunc1) #Generate non-parametric bootstrap estimates of alpha and beta #using bootstrapping ################################################ BootF=function (data,i){ # take a random sample of size 18 from a SqRtFemPhoto # sample with replacement d <- data[i,] NlmResampF<- function(x, a, b) {(a*x)/(b+x)} NlmResampF <- nls(y ~ NlmResampF (x, alpha, beta), data = d, start = list(alpha = 10, beta = 1), control = list(maxiter =...

...reconfigure var dev lost+found root But I can''t get it to mount at boot. Did I do something wrong during the install? Is there an incompatibility with Xen that I am unaware of. I tried using the option: extra = ''/platform/i86xpv/kernel/unix -B zfs-bootfs=rpool/27'' And it failed as well. Has anyone had this problem and is there a solution? Thanks. This message posted from opensolaris.org

I''ve got a CentOS 5.3 dom0 with Xen 3.4.1-rc5 (or so). I''ve tried the same stuff below with 3.4.0, no difference. I''m trying to install 2009.06 PV domU based on instructions from [1] and [2]. I can run the install fine, I can also get the kernel and boot archive (from [2]) after the install. But for the life of me I can''t get the installed domU to boot. If I

...Example /var/log/messages log: Jul 19 11:59:53 ovs030 [2012-07-19 11:59:53,504 7112] ERROR (pygrub:848) [Errno 95] Operation not supported Traceback (most recent call last): File "/share/repos/xen-unstable/tools/pygrub/src/pygrub", line 828, in ? fs = fsimage.open(file, offset, bootfsoptions) IOError: [Errno 95] Operation not supported Jul 19 11:59:53 ovs030 [2012-07-19 11:59:53,508 7112] ERROR (pygrub:892) Unable to find partition containing kernel ''7112'' is the pygrub PID, so we can distinguish each process. Also in this patch: 1). Fix indentation for s...

...-05.14:02:50 zfs create -b 131072 -V 1023m rpool/dump 2009-01-05.14:03:19 zfs set mountpoint=/a/export rpool/export 2009-01-05.14:03:19 zfs set mountpoint=/a/export/home rpool/export/home 2009-01-05.14:03:19 zfs set mountpoint=/a/export/home/mike rpool/export/home/mike 2009-01-05.14:17:32 zpool set bootfs=rpool/ROOT/opensolaris rpool 2009-01-05.14:18:54 zfs set org.opensolaris.caiman:install=ready rpool 2009-01-05.14:18:55 zfs set mountpoint=/export/home/mike rpool/export/home/mike 2009-01-05.14:18:55 zfs set mountpoint=/export/home rpool/export/home 2009-01-05.14:18:55 zfs set mountpoint=/export r...

...filesystem. This defaults to -creating a 100MB disk with the VG and LV called C</dev/VG/LV>, with an +creating a 1G disk with the VG and LV called C</dev/VG/LV>, with an ext2 filesystem."); ("bootroot", "create a boot and root filesystem", [ "bootfs", "ext2", "the type of filesystem to use for boot"; "rootfs", "ext2", "the type of filesystem to use for root"; - "size", "100M", "the size of the disk image"; - "bootsize", "32M"...

I was attempting one way to solve: https://bugzilla.redhat.com/show_bug.cgi?id=1400332 "RFE: virt-builder should support templates with encrypted filesystems" However this approach doesn't really work because templates containing encrypted partitions cannot be compressed, and therefore the guest template would be a multi-gigabyte download. I better approach will likely be to use

...eway = "10.226.33.1" disk = [ ''file:/Application/xen/images/opensolaris_2008_11.disk,0,w'' ] kernel = ''/boot/osol/kernel.opensolaris'' ramdisk = ''/boot/osol/ramdisk.opensolaris'' extra = ''/platform/i86xpv/kernel/unix -B zfs-bootfs=rpool/54,bootpath=/xpvd/xdf@0:a'' on_shutdown = ''destroy'' on_reboot = ''destroy'' on_crash = ''destroy'' When I do that, I get an error message like this. Unable to find number for device (0) Can someone please help me debug this problem...