similar to: [indiana-discuss] image-update doesn''t work anymore (bootfs not supported on EFI)

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

Hi, I was playing around with NexentaCP 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

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

Using build 70, I followed the zfsboot instructions at http:// www.opensolaris.org/os/community/zfs/boot/zfsboot-manual/ to the letter. I tried first with a mirror zfsroot, when I try to boot to zfsboot the screen is flooded with "init(1M) exited on fatal signal 9" Than I tried with a simple zfs pool (not mirrored) and it just reboots right away. If I try to setup grub

I''ve hit this bug on my home machine couple of times and finally decided to log it since I''ve spend 2 days configuring my "OpenSolaris 2008.11 snv_101b_rc2 X86" and after installing the SUNWsmbfskr package I ended up in the grub> menu. The package contains a necessary module for CIFS. After pkg install SUNWsmbfskr, I rebooted the box. There was no grub menu anymore

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

Let me thank everyone in advance. I''ve read a number of posts here and it helped tremendously in getting the install done. I have a couple of remaining issues which I can''t seem to overcome. Here are the basics: dom0 - CentOS 5.2 32-bit Xen 3.2.1 compiles from source domU - os200805.iso The install config: [root@internetpowagroup oshman]# cat opensolaris.install name =

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

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

Hi. Using ZFS-FUSE. $SUBJECT happened 3 out of 5 times while testing, just wanna know if someone has seen such scenario before. Steps: ------------------------------------------------------------ root at localhost:/# uname -a Linux localhost 2.6.24-24-generic #1 SMP Wed Apr 15 15:54:25 UTC 2009 i686 GNU/Linux root at localhost:/# zpool upgrade -v This system is currently running ZFS pool

> 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

Hi, I''m trying to create OpenSolaris (2008.11) domU on RedHat Linux dom0. I''m using a file backed VBD. I used the iso image to first launch and install OpenSolaris into the file VBD. Once that process is complete, I''m trying to run it using the config file below: name = ''opensolaris'' vcpus = 1 memory = "512" vif =

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

# HG changeset patch # User Zhigang Wang <zhigang.x.wang@oracle.com> # Date 1342720736 14400 # Node ID ec9655b30a5fa5b5abb3e05505f681f9be559613 # Parent 43e21ce7f22151524b800a6cf0ac4ba1233b34a7 pygrub: add syslog support to pygrub Currently, when pygrub failed, we don''t know the reason because xend/xl will not capture the stderr message. This patch will log the error message to

I had a drive fail and replaced it with a new drive,During the resilvering process,that show "Too many errors",and process fail. now,the pool can online,but cannot accept any zfs''s commands that change pool''s state,I can list File directory,but don''t mv?cp and rm -f. what can I do,I need that data files. root at opensolaris2:~# cat /etc/release

The guestfish prepared disks (-N option) all defaulted to 100M. This has always been too small for btrfs (so for example ‘-N fs:btrfs’ has failed for a long time), and can be too small for LVs with new LVM2 / kernel >= 4.16. This changes the default from 100M to 1G. The beginning of the 1.39 branch seems like a good time to make this change. --- fish/guestfish.pod | 14 +++++++-------

Hello all, I''d like to report a tricky situation and a workaround I''ve found useful - hope this helps someone in similar situations. To cut the long story short, I could not properly mount some datasets from a readonly pool, which had a non-"legacy" mountpoint attribute value set, but the mountpoint was not available (directory absent or not empty). In this case

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

Hi, I've got a problem with booting zfs-on-root FreeBSD 9.2-PRERELEASE. I'm getting: ZFS: i/o error - all block copies unavailable ZFS: can't read MOS of pool klawisz gptzfsboot: failed to mount default pool klawisz Machine is VM running under KVM on Proxmox 2.3-13. VM has 8 GB of RAM, 400 GB of local storage with SCSI Controller type: Default (lsi). I'm not sure what I did to