<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Home Fileserver: ZFS boot pool recovery</title>
	<atom:link href="http://breden.org.uk/2009/08/30/home-fileserver-zfs-boot-pool-recovery/feed/" rel="self" type="application/rss+xml" />
	<link>http://breden.org.uk/2009/08/30/home-fileserver-zfs-boot-pool-recovery/</link>
	<description>Complexifying simplicity</description>
	<lastBuildDate>Thu, 29 Jul 2010 12:25:04 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Anonymous</title>
		<link>http://breden.org.uk/2009/08/30/home-fileserver-zfs-boot-pool-recovery/comment-page-1/#comment-16832</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Sat, 24 Oct 2009 10:32:42 +0000</pubDate>
		<guid isPermaLink="false">http://breden.org.uk/?p=139#comment-16832</guid>
		<description>Just wanted to point out that instead of reinstalling, then recovering over the top of the new rpool, you can prepare the root disk using the livecd and restore directly. I assume the whole disk being prepared will be allocated to the rpool.

* It may be necessary to remove traces of the existing rpool. I found that &#039;zpool import&#039; was discovering phantom rpools. To get around this, I created a new pool from the vdevs &#039;zpool import&#039; claimed were members of these phantom rpools, then destroyed the newly created pool.

* Partition the disk. Restore the partition table from backup, if you have it. Otherwise, use format/fdisk to create a whole-disk Solaris partition. Make sure the partition table is type SMI, not EFI, for the boot disk (format -e). Make sure this partition is active.

* Use format/partition to setup the slices. Make sure the first slice (0) is set to type &quot;root&quot; and starts at cylinder 1, to the maximum cylinder. Slice 2 (whole-disk) and 8 (boot) should already exist by default.

* Create a new rpool with zpool, as per your instructions.

* Restore zfs backup stream, as per your instructions.

* Set the pool root, as per your instructions.

* Reinstall grub, as per your instructions.

* Update the boot archive (may not be necessary):
zfs set mountpoint=/tmp/a rpool/ROOT/opensolaris
mkdir /tmp/a
zfs mount rpool/ROOT/opensolaris
bootadm image-update -R /tmp/a
umount /tmp/a
zfs set mountpoint=/ rpool/ROOT/opensolaris</description>
		<content:encoded><![CDATA[<p>Just wanted to point out that instead of reinstalling, then recovering over the top of the new rpool, you can prepare the root disk using the livecd and restore directly. I assume the whole disk being prepared will be allocated to the rpool.</p>
<p>* It may be necessary to remove traces of the existing rpool. I found that &#8216;zpool import&#8217; was discovering phantom rpools. To get around this, I created a new pool from the vdevs &#8216;zpool import&#8217; claimed were members of these phantom rpools, then destroyed the newly created pool.</p>
<p>* Partition the disk. Restore the partition table from backup, if you have it. Otherwise, use format/fdisk to create a whole-disk Solaris partition. Make sure the partition table is type SMI, not EFI, for the boot disk (format -e). Make sure this partition is active.</p>
<p>* Use format/partition to setup the slices. Make sure the first slice (0) is set to type &#8220;root&#8221; and starts at cylinder 1, to the maximum cylinder. Slice 2 (whole-disk) and 8 (boot) should already exist by default.</p>
<p>* Create a new rpool with zpool, as per your instructions.</p>
<p>* Restore zfs backup stream, as per your instructions.</p>
<p>* Set the pool root, as per your instructions.</p>
<p>* Reinstall grub, as per your instructions.</p>
<p>* Update the boot archive (may not be necessary):<br />
zfs set mountpoint=/tmp/a rpool/ROOT/opensolaris<br />
mkdir /tmp/a<br />
zfs mount rpool/ROOT/opensolaris<br />
bootadm image-update -R /tmp/a<br />
umount /tmp/a<br />
zfs set mountpoint=/ rpool/ROOT/opensolaris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon</title>
		<link>http://breden.org.uk/2009/08/30/home-fileserver-zfs-boot-pool-recovery/comment-page-1/#comment-15951</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Wed, 16 Sep 2009 10:50:57 +0000</pubDate>
		<guid isPermaLink="false">http://breden.org.uk/?p=139#comment-15951</guid>
		<description>Good question. Never tried it but it should be possible to &#039;zfs send&#039; your root pool to a file, as shown above, and then copy the resulting file to the Windows machine.</description>
		<content:encoded><![CDATA[<p>Good question. Never tried it but it should be possible to &#8216;zfs send&#8217; your root pool to a file, as shown above, and then copy the resulting file to the Windows machine.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chojin</title>
		<link>http://breden.org.uk/2009/08/30/home-fileserver-zfs-boot-pool-recovery/comment-page-1/#comment-15810</link>
		<dc:creator>chojin</dc:creator>
		<pubDate>Mon, 14 Sep 2009 13:46:30 +0000</pubDate>
		<guid isPermaLink="false">http://breden.org.uk/?p=139#comment-15810</guid>
		<description>can i use a windows machine for backing up my rootpool?</description>
		<content:encoded><![CDATA[<p>can i use a windows machine for backing up my rootpool?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
