zfs discuss - Apr 2007 - zfs boot image conversion kit is posted

The kit that I promised for patching an install image
to support the profile-based install of systems with
zfs root file systems has been posted.  It''s at:

http://www.opensolaris.org/os/community/install/files/zfsboot-kit-20060418.i386.tar.bz2

Unpack it and see the README file for instructions.

Good luck and let me know how it works for you.

(Thanks to Dave Miner for putting this out on the install
community download page for me.)

Lori

If the goal is to test ZFS as a root file system, could I suggest making a
virtual machine of b62-on-zfs available for download?  This would reduce
duplicated effort and encourage new people to try it out.
 
 
This message posted from opensolaris.org

I was hoping that someone more well-versed in virtual machines
would respond to this so I wouldn''t have to show my ignorance,
but no such luck, so here goes:

Is it even possible to build a virtual machine out of a
zfs storage pool?  Note that it isn''t just zfs as a root file system
we''re trying out.  It''s the whole concept of booting from
a dataset within a storage pool.   I don''t know enough about
how one sets up a virtual machine to know whether it''s
possible or even meaningful to talk about generating a
b62-on-zfs virtual machine.

Lori

MC wrote:
>If the goal is to test ZFS as a root file system, could I suggest making a
virtual machine of b62-on-zfs available for download?  This would reduce
duplicated effort and encourage new people to try it out.
> 
> 
>This message posted from opensolaris.org
>_______________________________________________
>zfs-discuss mailing list
>zfs-discuss at opensolaris.org
>http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>  
>

I''m not sure I understand the question.
Virtual machines are built by either running a virtualization technology
in a host operating systems, such as running VMware Workstation in
Linux, running Parallels in Mac OS X, Linux or Windows, etc.
These are sometimes referred to as Type II VMMs, where the
VMM (Virtual Machine Monitor - the chunk of software responsible
for running the guest operating system) is hosted by a traditional
operating system.

In Type I VMMs, the VMM runs on the hardware. VMware ESX
Server is an example of this (although some argue it is not, since
technically there''s an ESX kernel that runs on the hardware in
support of the VMM). So....

Building a virtual machine on a zpool would require that the host
operating system supports ZFS. An example here would be our
forthcoming (no, I do not know when), Solaris/Xen integration,
assuming there is support for putting Xen domU''s on a ZFS.

It may help to point out that when a virtual machine is created,
it includes defining a virtual hard drive, which is typically just a
file in the file system space of the hosting operating system.
Given that, a hosting operating system that supports ZFS can allow
for configuring virtual hard drives in the ZFS space.

So I guess the anwer to your question is theoretically yes, but I''m
not aware of an implementation that would allow for such a
configuration that exists today.

I think I just confused the issue...ah well...

/jim

PS - FWIW, I have a zpool configured in nv62 running in a Parallels
virtual machine on Mac OS X. The nv62 "system disk" is a virtual
hard disk that exists as a file in Mac OS X HFS+, thus this particular
zpool is a partition on that virtual hard drive.



Lori Alt wrote:
> I was hoping that someone more well-versed in virtual machines
> would respond to this so I wouldn''t have to show my ignorance,
> but no such luck, so here goes:
>
> Is it even possible to build a virtual machine out of a
> zfs storage pool?  Note that it isn''t just zfs as a root file
system
> we''re trying out.  It''s the whole concept of booting from
> a dataset within a storage pool.   I don''t know enough about
> how one sets up a virtual machine to know whether it''s
> possible or even meaningful to talk about generating a
> b62-on-zfs virtual machine.
>
> Lori
>
> MC wrote:
>
>> If the goal is to test ZFS as a root file system, could I suggest 
>> making a virtual machine of b62-on-zfs available for download?  This 
>> would reduce duplicated effort and encourage new people to try it out.
>>
>>
>> This message posted from opensolaris.org
>> _______________________________________________
>> zfs-discuss mailing list
>> zfs-discuss at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>>  
>>
>
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

On Thu, Apr 19, 2007 at 08:55:24PM -0400, Jim Mauro
wrote:
> 
> Server is an example of this (although some argue it is not, since
> technically there''s an ESX kernel that runs on the hardware in
> support of the VMM). So....
And that kernel is linux, so......  ;)
> Building a virtual machine on a zpool would require that the host
> operating system supports ZFS. An example here would be our
This is not true.  See below.
> It may help to point out that when a virtual machine is created,
> it includes defining a virtual hard drive, which is typically just a
> file in the file system space of the hosting operating system.
> Given that, a hosting operating system that supports ZFS can allow
> for configuring virtual hard drives in the ZFS space.
Again, this is not true, the "host" OS (the OS running VMWare or
whatnot) doesn''t need to know anything at all about what filesystem
the "guest" OS (the OS you are installing into the virtual machine)
uses.

The virtualization software takes that file you mention and makes it
appear to be a physical device to the guest OS, so the guest OS is
none the wiser.  The host OS just has a file (or sometimes that file
is split into smaller chunks) that contains the guest OS''s pretend
hard-drive.

There is no reason why zfsroot/boot shouldn''t work in a VM any more
than any other OS/FS combo wouldn''t.

I run Solaris in VMs all the time, a lot of times with ZFS pools, and
it works great.

I will setup a VM image that can be downloaded (I hope to get it done
tomorrow, but if not definitely by early next week) and played with
by anyone who is interested.

-brian
-- 
"Perl can be fast and elegant as much as J2EE can be fast and elegant.
In the hands of a skilled artisan, it can and does happen; it''s just
that most of the shit out there is built by people who''d be better
suited to making sure that my burger is cooked thoroughly."  -- Jonathan
Patschke

Hello Brian,

Friday, April 20, 2007, 3:20:03 AM, you wrote:

BH> On Thu, Apr 19, 2007 at 08:55:24PM -0400, Jim Mauro wrote:
>> Building a virtual machine on a zpool would require that the host
>> operating system supports ZFS. An example here would be our
BH> This is not true.  See below.
>> It may help to point out that when a virtual machine is created,
>> it includes defining a virtual hard drive, which is typically just a
>> file in the file system space of the hosting operating system.
>> Given that, a hosting operating system that supports ZFS can allow
>> for configuring virtual hard drives in the ZFS space.
BH> Again, this is not true, the "host" OS (the OS running VMWare
or
BH> whatnot) doesn''t need to know anything at all about what
filesystem
BH> the "guest" OS (the OS you are installing into the virtual
machine) uses.


I think you misunderstood Jim and you''re both right.

One case is running virtual machine on a zfs, and another one is using
zfs inside a virtual machine. Those are two different things.


Running virtual machines on a host os with ZFS has several
advantages when you consider all benefits coming from snapshots,
clones and possibly thin zvol provisioning. Not to mention
checksuming which is even more important with virtual machines as
potential data corruption in host os could affect many virtual
systems.

Now the original question by MC I belive was about providing
VMware and/or Xen image with guest OS being snv_62 with / as zfs.
This should allow people to just download such image and run snv_62
with zfs as rootfs without all the hassle there''s right now to set it
up.


-- 
Best regards,
 Robert Milkowski                      mailto:rmilkowski at task.gda.pl
                                       http://milek.blogspot.com

A virtual machine can be thought of as a physical machine with the hardware
removed.  ;-)

To set up a VMware virtual machine, for instance, you''d just (a) start
with a VM with a blank disk, (b) install OpenSolaris, (c) configure as desired.

I think this is all the original poster is suggesting.  This can be done for
free using VMware Server.  The big advantage is that each user doesn''t
need to do the configuration.  One person can do the install and lots of people
can download and try it out.
 
 
This message posted from opensolaris.org

> Now the original question by MC I belive was about providing
VMware and/or Xen image with guest OS being snv_62 with / as zfs.

This is true.

I''m not sure what Jim meant about the host system needing to support
zfs.  Maybe you''re on a different page, Jim :)
> I will setup a VM image that can be downloaded (I hope to get it done
tomorrow, but if not definitely by early next week) and played with
by anyone who is interested.

That would be golden, Brian.  Let me know if you can''t get suitable
hosting for it!
 
 
This message posted from opensolaris.org

On Fri, Apr 20, 2007 at 12:25:30PM -0700, MC wrote:
> 
> > I will setup a VM image that can be downloaded (I hope to get it done
> tomorrow, but if not definitely by early next week) and played with
> by anyone who is interested.
> 
> That would be golden, Brian.  Let me know if you can''t get
suitable hosting for it!
I have somewhere I can put it, thanks for the offer though.  :)

I''m not going to get it done today.  What I will do, however, is upload
the tarball of the patches b62 dvd image (once it''s done compressing)
for anyone who wants to snag it.  I''ll probably turn it back into an
ISO come monday as well.

Probably a little later today.  I''ll let you all know when
it''s up.

-brian
-- 
"Perl can be fast and elegant as much as J2EE can be fast and elegant.
In the hands of a skilled artisan, it can and does happen; it''s just
that most of the shit out there is built by people who''d be better
suited to making sure that my burger is cooked thoroughly."  -- Jonathan
Patschke

Good deal.  We''ll have a race to build a a vm image, then :)
 
 
This message posted from opensolaris.org

remember that solaris express can only be distributed by authorized parties.

On 20/04/07, MC <rac at eastlink.ca> wrote:
> > Now the original question by MC I belive was about providing
> VMware and/or Xen image with guest OS being snv_62 with / as zfs.
>
> This is true.
>
> I''m not sure what Jim meant about the host system needing to
support zfs.
> Maybe you''re on a different page, Jim :)
>
> > I will setup a VM image that can be downloaded (I hope to get it done
> tomorrow, but if not definitely by early next week) and played with
> by anyone who is interested.
>
> That would be golden, Brian.  Let me know if you can''t get
suitable hosting
> for it!
>
>
> This message posted from opensolaris.org
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>

-- 
"Less is only more where more is no good." --Frank Lloyd Wright

Shawn Walker, Software and Systems Analyst
binarycrusader at gmail.com - http://binarycrusader.blogspot.com/

Hi Lori,
  Thanks to you and your team for posting the zfs boot image kit.  I was able to
jumpstart a VMWare virtual machine using a Nevada b62 image patched with your
conversion kit and it went very smoothly.

Here is the profile that I used:
# Jumpstart profile for VMWare image w/ two emulated IDE drives
# ZFS boot settings based off Nevada b62 patched install image
install_type initial_install
cluster SUNWCreq
cluster SUNWCssh
package SUNWbash add
filesys c0d0s1 auto swap
pool bootpool free / mirror c0d0s0 c0d1s0
dataset bootpool/BE1 auto /
dataset bootpool/BE1/usr auto /usr
dataset bootpool/BE1/opt auto /opt
dataset bootpool/BE1/var auto /var
dataset bootpool/BE1/export auto /export

# uname -a
SunOS zfsboot 5.11 snv_62 i86pc i386 i86pc
# df -k
Filesystem            kbytes    used   avail capacity  Mounted on
bootpool/BE1         7676928  353874 7153830     5%    /
/devices                   0       0       0     0%    /devices
/dev                       0       0       0     0%    /dev
ctfs                       0       0       0     0%    /system/contract
proc                       0       0       0     0%    /proc
mnttab                     0       0       0     0%    /etc/mnttab
swap                  300032     364  299668     1%    /etc/svc/volatile
objfs                      0       0       0     0%    /system/object
sharefs                    0       0       0     0%    /etc/dfs/sharetab
bootpool/BE1/usr     7676928  158180 7153830     3%    /usr
/usr/lib/libc/libc_hwcap1.so.1
                     7312010  158180 7153830     3%    /lib/libc.so.1
fd                         0       0       0     0%    /dev/fd
bootpool/BE1/var     7676928    9672 7153830     1%    /var
swap                  299668       0  299668     0%    /tmp
swap                  299692      24  299668     1%    /var/run
bootpool/BE1/export  7676928      18 7153830     1%    /export
bootpool/BE1/opt     7676928      18 7153830     1%    /opt
#
# zpool list
NAME                    SIZE    USED   AVAIL    CAP  HEALTH     ALTROOT
bootpool               7.44G    511M   6.94G     6%  ONLINE     -
# zpool status
  pool: bootpool
 state: ONLINE
 scrub: none requested
config:

        NAME        STATE     READ WRITE CKSUM
        bootpool    ONLINE       0     0     0
          mirror    ONLINE       0     0     0
            c0d0s0  ONLINE       0     0     0
            c0d1s0  ONLINE       0     0     0

errors: No known data errors

--
William Hathaway
http://williamhathaway.com
 
 
This message posted from opensolaris.org

> The kit that I promised for patching an install image
> to support the profile-based install of systems with
> zfs root file systems has been posted.  It''s at:
> 
> http://www.opensolaris.org/os/community/install/files/
> zfsboot-kit-20060418.i386.tar.bz2
> 
> Unpack it and see the README file for instructions.
> 
> Good luck and let me know how it works for you.
> 
> (Thanks to Dave Miner for putting this out on the
> install
> community download page for me.)
> 
> Lori
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discu
> ss
> 
Lori,

I tried your kit, specifically the "Detailed Steps for the Install"
Unfortunately, it didn''t work. I copy / pasted the profile from the
README file, then did pfinstall /tmp/profile. The error was:

Error: Field 1 - Keyword "pool" is invalid.

Perhaps I messed up?

Ron
 
 
This message posted from opensolaris.org

> I tried your kit, specifically the "Detailed Steps for the
Install"
>
>Unfortunately, it didn''t work. I copy / pasted the profile from the
README file, then did pfinstall /tmp/profile. The error was:
>
>Error: Field 1 - Keyword "pool" is invalid.
>
>Perhaps I messed up?
>
This error is what I would expect if you were using the old
install software.  Are you sure that the conversion of the
install image succeeded?

Lori
>
>Ron
> 
> 
>This message posted from opensolaris.org
>_______________________________________________
>zfs-discuss mailing list
>zfs-discuss at opensolaris.org
>http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>  
>

> remember that solaris express can only be distributed by authorized
parties.
Mmmyeah, I think we''ll be fine.  Sun is a capable organization and
doesn''t need you or I to put a damper on the growth of OpenSolaris.  If
they have a problem with something, they''ll let us know.

Just waiting on you, Brian!
 
 
This message posted from opensolaris.org

As promised, here it is:

https://jeffshare.jefferson.edu/users/blh008/Public/Solaris/

b62_zfsboot.iso.bz2 is a bootable patched b62 DVD.

b62_zfsboot_cd1.iso.bz2 is a bootable patched b63 CD1.  I''m not
sure how useful this is unless you know how to tell pfinstall how
to look to an NFS server for install media and mount the dvd image
there.

zfsboot.tar.bz2 is a vmware image made on a VMWare Server 1.0.1
machine.

I did the install with no network setup, so you''ll have to manually do
the network setup yourself.

I originally set it up and was going to do a sys-unconfig before tarring
it up, but some broken logic in sys-unconfig sees a zfs root system as
being diskless and refuses to run.  That being the case I reinstalled
with no network setup and haven''t even done the first reboot at this
point so expect to sit through the initial SMF import. (didn''t take
long on the machine I was doing it on).

Oh, btw, in /zfsboot on the dvd/cd (shows up under /cdrom/zfsboot when
you are booted into the installer) there is an example profile that sets
up a non-mirrored zfsboot system.  This is the exact one I used for the
install of this VM, and I put it there so that if you need to change it
you could copy it to /tmp and tweak it.  I found that pasting into the
vmware console didn''t work for me and I got tired of hand-writing it.
;)

Enjoy!!

-brian

ps: the iso''s will be up shortly, they are zipping now.  You will be
able
to tell they are done because I won''t upload the cksum files until
after
the iso images upload completes.  When you see .sum files, you know they
are done.
-- 
"Perl can be fast and elegant as much as J2EE can be fast and elegant.
In the hands of a skilled artisan, it can and does happen; it''s just
that most of the shit out there is built by people who''d be better
suited to making sure that my burger is cooked thoroughly."  -- Jonathan
Patschke

That''s awesome!

So, to clarify... If I burn the b62_zfsboot.iso to a DVD and boot from it
with the intention of doing a fresh install....
What are the correct steps to do the setup with a zfs mirrored boot? Follow
the installer? Follow the netinstall or Tom''s instructions?

Thanks,
Malachi

On 4/25/07, Brian Hechinger <wonko at 4amlunch.net>
wrote:
>
> As promised, here it is:
>
> https://jeffshare.jefferson.edu/users/blh008/Public/Solaris/
>
> b62_zfsboot.iso.bz2 is a bootable patched b62 DVD.
>
> b62_zfsboot_cd1.iso.bz2 is a bootable patched b63 CD1.  I''m not
> sure how useful this is unless you know how to tell pfinstall how
> to look to an NFS server for install media and mount the dvd image
> there.
>
> zfsboot.tar.bz2 is a vmware image made on a VMWare Server 1.0.1
> machine.
>
> I did the install with no network setup, so you''ll have to
manually do
> the network setup yourself.
>
> I originally set it up and was going to do a sys-unconfig before tarring
> it up, but some broken logic in sys-unconfig sees a zfs root system as
> being diskless and refuses to run.  That being the case I reinstalled
> with no network setup and haven''t even done the first reboot at
this
> point so expect to sit through the initial SMF import. (didn''t
take
> long on the machine I was doing it on).
>
> Oh, btw, in /zfsboot on the dvd/cd (shows up under /cdrom/zfsboot when
> you are booted into the installer) there is an example profile that sets
> up a non-mirrored zfsboot system.  This is the exact one I used for the
> install of this VM, and I put it there so that if you need to change it
> you could copy it to /tmp and tweak it.  I found that pasting into the
> vmware console didn''t work for me and I got tired of hand-writing
it. ;)
>
> Enjoy!!
>
> -brian
>
> ps: the iso''s will be up shortly, they are zipping now.  You will
be able
> to tell they are done because I won''t upload the cksum files until
after
> the iso images upload completes.  When you see .sum files, you know they
> are done.
> --
> "Perl can be fast and elegant as much as J2EE can be fast and elegant.
> In the hands of a skilled artisan, it can and does happen; it''s
just
> that most of the shit out there is built by people who''d be better
> suited to making sure that my burger is cooked thoroughly."  --
Jonathan
> Patschke
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20070425/b948cde9/attachment.html>

On Wed, Apr 25, 2007 at 04:36:46PM -0700, Malachi de ??lfweald
wrote:
> That''s awesome!
> 
> So, to clarify... If I burn the b62_zfsboot.iso to a DVD and boot from it
> with the intention of doing a fresh install....
Yes.  Upgrade/Flash installs are not availble with zfs boot yet.
> What are the correct steps to do the setup with a zfs mirrored boot? Follow
> the installer? Follow the netinstall or Tom''s instructions?
all you need to do is change this line:

pool mypool free / c0d0s0

to this:

pool mypool free / mirror c0d0s0 c0d1s0

obviously you might need to change what the disks are.

-brian
-- 
"Perl can be fast and elegant as much as J2EE can be fast and elegant.
In the hands of a skilled artisan, it can and does happen; it''s just
that most of the shit out there is built by people who''d be better
suited to making sure that my burger is cooked thoroughly."  -- Jonathan
Patschke

You''ve delivered us to awesometown, Brain.
> zfsboot.tar.bz2 is a vmware image made on a VMWare Server 1.0.1
machine.

But oops, what is the root login password?! :)
 
 
This message posted from opensolaris.org

On Wed, Apr 25, 2007 at 07:50:16PM -0700, MC wrote:
> You''ve delivered us to awesometown, Brain.
> 
> > zfsboot.tar.bz2 is a vmware image made on a VMWare Server 1.0.1
> machine.
> 
> But oops, what is the root login password?! :)
D''Oh!

The root password is......

wait for it......

password

:)

-brian
-- 
"Perl can be fast and elegant as much as J2EE can be fast and elegant.
In the hands of a skilled artisan, it can and does happen; it''s just
that most of the shit out there is built by people who''d be better
suited to making sure that my burger is cooked thoroughly."  -- Jonathan
Patschke

Don''t mean to be a pest - but is there an eta on when the
b62_zfsboot.iso will be posted?

I''m really looking forward to ZFS root, but I''d rather
download a working dvd image then attempt to patch the image myself :-)

cheers and thanks,
-bp
 
 
This message posted from opensolaris.org

Benjamin Perrault wrote:
> Don''t mean to be a pest - but is there an eta on when the
b62_zfsboot.iso will be posted?
>
> I''m really looking forward to ZFS root, but I''d rather
download a working dvd image then attempt to patch the image myself :-)
Actually, we hadn''t planned to release zfsboot dvd images, but
I''ll
look into it. 

Lori

Lori Alt wrote:
> Benjamin Perrault wrote:
>
>> Don''t mean to be a pest - but is there an eta on when the
>> b62_zfsboot.iso will be posted?
>> I''m really looking forward to ZFS root, but I''d
rather download a
>> working dvd image then attempt to patch the image myself :-)
>
> Actually, we hadn''t planned to release zfsboot dvd images, but
I''ll
> look into it.
Or an alternative CD1, for those of us who do network installs after
booting from CD.

Ian

I think Benjamin was referring to the image Brian promised to upload, which, I
see now, is up on his web space.

My experience with the vmware image is as follows:

Doing a zpool scrub after booting up causes Solaris to restart about half way
through.  After the crash, a zpool status says there is one error found.

I tried to switch the install over to a different virtual disk, but mirroring by
add/attach didn''t work, and snapshots didn''t work ("disk
is busy"?), and replace didn''t work.

So while I''m stuck, you have your feedback :)
 
 
This message posted from opensolaris.org

Actually, I think that one might not be ready quite yet..... per:
> ps: the iso''s will be up shortly, they are zipping now.  You will
be able
> to tell they are done because I won''t upload the cksum files until
after
> the iso images upload completes.  When you see .sum files, you know they
> are done.
>
Malachi


On 4/26/07, MC <rac at eastlink.ca> wrote:
>
> I think Benjamin was referring to the image Brian promised to upload,
> which, I see now, is up on his web space.
>
> My experience with the vmware image is as follows:
>
> Doing a zpool scrub after booting up causes Solaris to restart about half
> way through.  After the crash, a zpool status says there is one error
found.
>
> I tried to switch the install over to a different virtual disk, but
> mirroring by add/attach didn''t work, and snapshots didn''t
work ("disk is
> busy"?), and replace didn''t work.
>
> So while I''m stuck, you have your feedback :)
>
>
> This message posted from opensolaris.org
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20070426/a4a597ac/attachment.html>

On Thu, Apr 26, 2007 at 02:51:24PM -0700, MC wrote:
> I think Benjamin was referring to the image Brian promised to upload,
which, I see now, is up on his web space.
Which is now complete, and the sum file is also uploaded.
> Doing a zpool scrub after booting up causes Solaris to restart about half
way through.  After the crash, a zpool status says there is one error found.
> 
> I tried to switch the install over to a different virtual disk, but
mirroring by add/attach didn''t work, and snapshots didn''t work
("disk is busy"?), and replace didn''t work.
> 
> So while I''m stuck, you have your feedback :)
Hmmm.  Did it boot all the way up normally on first boot?  I hadn''t
tried
a scrub when I did the VM install.  Double hmmm.

I''ll poke at my copy tomorrow at work and see if I can duplicate those
results.

-brian
-- 
"Perl can be fast and elegant as much as J2EE can be fast and elegant.
In the hands of a skilled artisan, it can and does happen; it''s just
that most of the shit out there is built by people who''d be better
suited to making sure that my burger is cooked thoroughly."  -- Jonathan
Patschke

On Fri, Apr 27, 2007 at 09:09:21AM +1200, Ian Collins
wrote:
> 
> Or an alternative CD1, for those of us who do network installs after
> booting from CD.
I have a question about that.  This is how I do all my installs, and
in fact I just did this on a machine at work (to be a temporary NFS
server so I could rebuild my desktop with ZFS Boot/Root action) and
while I do indeed have both a patched CD1 and a patched DVD image to
do the installs from, is the patched DVD really nessesary when booting
from the patched CD1?  I''m assuming so since nothing gets copied from
CD1 to the HDD during install, only from the "install media" which in
this case is the NFS mounted DVD image.

-brian
-- 
"Perl can be fast and elegant as much as J2EE can be fast and elegant.
In the hands of a skilled artisan, it can and does happen; it''s just
that most of the shit out there is built by people who''d be better
suited to making sure that my burger is cooked thoroughly."  -- Jonathan
Patschke

For Brian, et al: Thank you very much. I burned the DVD, and did some minor
tweaking to the profile, and it is up and running (now to just n00b admin
troubleshooting)

For everyone else who is new to this and trying it out, a couple things I
noticed:
1. Don''t waste your time trying to format the disk to match the profile
--
it does it for you. I spent about an hour on that before realizing
2. ZFS mirroring can work without the metadb, but if you want the dump
mirrored too, you need the metadb (I don''t know if it needs to be
mirrored,
but I wanted both disks to be identical in case one died)
3. Here''s the modified profile I used:

install_type initial_install
filesys mirror c1d0s1 c2d0s1 4096 swap
pool rootpool free / mirror c1d0s0 c2d0s0
dataset rootpool/BE1 auto /
dataset rootpool/BE1/usr auto /usr
dataset rootpool/BE1/opt auto /opt
dataset rootpool/BE1/var auto /var
dataset rootpool/BE1/export auto /export
metadb c1d0s7 size 8192 count 3
metadb c2d0s7 size 8192 count 3


As I said, might not be the best or even correct, but thanks to the patched
DVD, it is up and running :)

Malachi


On 4/25/07, Malachi de ?lfweald <malachid at gmail.com>
wrote:
>
> That''s awesome!
>
> So, to clarify... If I burn the b62_zfsboot.iso to a DVD and boot from it
> with the intention of doing a fresh install....
> What are the correct steps to do the setup with a zfs mirrored boot?
> Follow the installer? Follow the netinstall or Tom''s instructions?
>
> Thanks,
> Malachi
>
> On 4/25/07, Brian Hechinger <wonko at 4amlunch.net> wrote:
> >
> > As promised, here it is:
> >
> > https://jeffshare.jefferson.edu/users/blh008/Public/Solaris/
> >
> > b62_zfsboot.iso.bz2 is a bootable patched b62 DVD.
> >
> > b62_zfsboot_cd1.iso.bz2 is a bootable patched b63 CD1.  I''m
not
> > sure how useful this is unless you know how to tell pfinstall how
> > to look to an NFS server for install media and mount the dvd image
> > there.
> >
> > zfsboot.tar.bz2 is a vmware image made on a VMWare Server 1.0.1
> > machine.
> >
> > I did the install with no network setup, so you''ll have to
manually do
> > the network setup yourself.
> >
> > I originally set it up and was going to do a sys-unconfig before
tarring
> >
> > it up, but some broken logic in sys-unconfig sees a zfs root system as
> > being diskless and refuses to run.  That being the case I reinstalled
> > with no network setup and haven''t even done the first reboot
at this
> > point so expect to sit through the initial SMF import.
(didn''t take
> > long on the machine I was doing it on).
> >
> > Oh, btw, in /zfsboot on the dvd/cd (shows up under /cdrom/zfsboot when
> > you are booted into the installer) there is an example profile that
sets
> >
> > up a non-mirrored zfsboot system.  This is the exact one I used for
the
> > install of this VM, and I put it there so that if you need to change
it
> > you could copy it to /tmp and tweak it.  I found that pasting into the
> > vmware console didn''t work for me and I got tired of
hand-writing it. ;)
> >
> > Enjoy!!
> >
> > -brian
> >
> > ps: the iso''s will be up shortly, they are zipping now.  You
will be
> > able
> > to tell they are done because I won''t upload the cksum files
until after
> >
> > the iso images upload completes.  When you see .sum files, you know
they
> > are done.
> > --
> > "Perl can be fast and elegant as much as J2EE can be fast and
elegant.
> > In the hands of a skilled artisan, it can and does happen;
it''s just
> > that most of the shit out there is built by people who''d be
better
> > suited to making sure that my burger is cooked thoroughly."  --
Jonathan
> > Patschke
> > _______________________________________________
> > zfs-discuss mailing list
> > zfs-discuss at opensolaris.org
> > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20070427/4faf4710/attachment.html>

On Fri, Apr 27, 2007 at 02:44:02PM -0700, Malachi de ??lfweald
wrote:
> For Brian, et al: Thank you very much. I burned the DVD, and did some minor
> tweaking to the profile, and it is up and running (now to just n00b admin
> troubleshooting)
> 
> For everyone else who is new to this and trying it out, a couple things I
> noticed:
> 1. Don''t waste your time trying to format the disk to match the
profile --
> it does it for you. I spent about an hour on that before realizing
Aroo?  Man, I spent^H^H^H^H^H^wasted a lot of time doing that.  ;)
> 2. ZFS mirroring can work without the metadb, but if you want the dump
> mirrored too, you need the metadb (I don''t know if it needs to be
mirrored,
> but I wanted both disks to be identical in case one died)
I can''t think of any real good reason you would need a mirrored dump
device.
The only place that would help you is if your main disk died between panic
and next boot.  ;)
> As I said, might not be the best or even correct, but thanks to the patched
> DVD, it is up and running :)
It went on my destop at work today (Dell GX620 with a pair of 150G SATA
disks in it) and so far I''m very happy.  And it has nothing to do with
ZFS really.  B62 has some major improvements over B50 (what was on there
previously).  Mainly, XOrg 7,2 seems to be TONS faster than 6.9 was and
the newer thunderbird doesn''t piss me off nearly as much as the older
one
did (I''m a mutt user, so keep in mind I don''t like GUI mail
prgrams at all).

That being said, I did the zpool shuffle and got both disks in the pool
as whole disks (and moved the dump device elsewhere).  Will it help
performance at all?  We''ll never know as I never did any speed tests
before the migration.

3 scrubs later and no issues, so I''ll toy with that VM tomorrow and see
if I can figure out what''s wrong with it.

-brian
-- 
"Perl can be fast and elegant as much as J2EE can be fast and elegant.
In the hands of a skilled artisan, it can and does happen; it''s just
that most of the shit out there is built by people who''d be better
suited to making sure that my burger is cooked thoroughly."  -- Jonathan
Patschke

I also downloaded the .iso file, burned it, and started the install process.  I
followed these instructions for creating the profile.

[i]Here''s a quick-and-dirty way to do a profile-driven install:

1. Boot your system off the net or from the DVD in the usual manner.

2. Select "Interactive Install".  Then, at the first opportunity
   to exit out of it (which will be after you''ve answered the
   system configuration questions, such as whether you want
   Kerberos and what the root password will be), exit out to a shell.

3. Create a profile for the install in /tmp/profile.  (The contents
   of the profile are described below).

4. Execute the following:

   # pfinstall /tmp/profile

When it''s done, reboot.  You should get a GRUB menu.  Select the
entry with the title "Solaris <release-name> X86".  The failsave
entry should work too.


Creating a profile for the install
----------------------------------
The system profile you use should look something like this:

install_type initial_install
cluster SUNWCuser
filesys c0t0d0s1 auto swap
pool mypool free / mirror c0t0d0s0 c0t1d0s0
dataset mypool/BE1 auto /
dataset mypool/BE1/usr auto /usr
dataset mypool/BE1/opt auto /opt
dataset mypool/BE1/var auto /var
dataset mypool/BE1/export auto /export[/i]

Obviously I changed the drive''s as required.  Then ran the pfinstall on
the profile I created.  The install looked like it worked correctly, but after a
reboot I''m having issues.

I get to the grub menu, which only has one entry "Solaris".  Which
when you edit the line is the following [b]kernel$
/platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS[/b].  When I pick this option
all it sits there for a second, then boot loops and comes back to the grub menu.

Any suggestions?  Any way I can see what its doing when it pauses before the
reboot?  I''m kinda new at this OpenSolaris stuff, so any debugging
tips/tricks would be greatly appreciated.

Mike
 
 
This message posted from opensolaris.org

I also downloaded the .iso file, burned it, and started the install process.  I
followed these instructions for creating the profile.

[i]Here''s a quick-and-dirty way to do a profile-driven install:

1. Boot your system off the net or from the DVD in the usual manner.

2. Select "Interactive Install".  Then, at the first opportunity
   to exit out of it (which will be after you''ve answered the
   system configuration questions, such as whether you want
   Kerberos and what the root password will be), exit out to a shell.

3. Create a profile for the install in /tmp/profile.  (The contents
   of the profile are described below).

4. Execute the following:

   # pfinstall /tmp/profile

When it''s done, reboot.  You should get a GRUB menu.  Select the
entry with the title "Solaris <release-name> X86".  The failsave
entry should work too.


Creating a profile for the install
----------------------------------
The system profile you use should look something like this:

install_type initial_install
cluster SUNWCuser
filesys c0t0d0s1 auto swap
pool mypool free / mirror c0t0d0s0 c0t1d0s0
dataset mypool/BE1 auto /
dataset mypool/BE1/usr auto /usr
dataset mypool/BE1/opt auto /opt
dataset mypool/BE1/var auto /var
dataset mypool/BE1/export auto /export[/i]

Obviously I changed the drive''s as required.  Then ran the pfinstall on
the profile I created.  The install looked like it worked correctly, but after a
reboot I''m having issues.

I get to the grub menu, which only has one entry "Solaris".  Which
when you edit the line is the following [b]kernel$
/platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS[/b].  When I pick this option
all it sits there for a second, then boot loops and comes back to the grub menu.

Any suggestions?  Any way I can see what its doing when it pauses before the
reboot?  I''m kinda new at this OpenSolaris stuff, so any debugging
tips/tricks would be greatly appreciated.

Mike
 
 
This message posted from opensolaris.org

The only big difference I see between what you did and what I did was I
didn''t have the cluster line.
On reboot, mine said something like ''Solaris nv_b62''

Is it possible there were any errors while it was installing?
If it generates a log during install, maybe you can ftp it away before the
reboot.

Mal

On 4/30/07, Mike Walker <michael_walker at ymp.gov>
wrote:
>
> I also downloaded the .iso file, burned it, and started the install
> process.  I followed these instructions for creating the profile.
>
> [i]Here''s a quick-and-dirty way to do a profile-driven install:
>
> 1. Boot your system off the net or from the DVD in the usual manner.
>
> 2. Select "Interactive Install".  Then, at the first opportunity
>    to exit out of it (which will be after you''ve answered the
>    system configuration questions, such as whether you want
>    Kerberos and what the root password will be), exit out to a shell.
>
> 3. Create a profile for the install in /tmp/profile.  (The contents
>    of the profile are described below).
>
> 4. Execute the following:
>
>    # pfinstall /tmp/profile
>
> When it''s done, reboot.  You should get a GRUB menu.  Select the
> entry with the title "Solaris <release-name> X86".  The
failsave
> entry should work too.
>
>
> Creating a profile for the install
> ----------------------------------
> The system profile you use should look something like this:
>
> install_type initial_install
> cluster SUNWCuser
> filesys c0t0d0s1 auto swap
> pool mypool free / mirror c0t0d0s0 c0t1d0s0
> dataset mypool/BE1 auto /
> dataset mypool/BE1/usr auto /usr
> dataset mypool/BE1/opt auto /opt
> dataset mypool/BE1/var auto /var
> dataset mypool/BE1/export auto /export[/i]
>
> Obviously I changed the drive''s as required.  Then ran the
pfinstall on
> the profile I created.  The install looked like it worked correctly, but
> after a reboot I''m having issues.
>
> I get to the grub menu, which only has one entry "Solaris". 
Which when
> you edit the line is the following [b]kernel$
> /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS[/b].  When I pick this
> option all it sits there for a second, then boot loops and comes back to
the
> grub menu.
>
> Any suggestions?  Any way I can see what its doing when it pauses before
> the reboot?  I''m kinda new at this OpenSolaris stuff, so any
debugging
> tips/tricks would be greatly appreciated.
>
> Mike
>
>
> This message posted from opensolaris.org
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20070430/a87ddcc2/attachment.html>

no errors that i could see.  I''m going to re-try it w/o the cluster
line.  i''m not sure if that line is required or not.
> <div id="jive-html-wrapper-div">
> The only big difference I see between what you did
> and what I did was I didn''t have the cluster
> line.<br>On reboot, mine said something like
> ''Solaris nv_b62''<br><br>Is it possible there
> were any errors while it was installing?
> <br>If it generates a log during install, maybe you
> can ftp it away before the
> reboot.<br><br>Mal<br><br><div><span
> class="gmail_quote">On 4/30/07, <b
> class="gmail_sendername">Mike Walker</b> <<a
> href="mailto:michael_walker at ymp.gov">
> michael_walker at ymp.gov</a>>
> wrote:</span><blockquote class="gmail_quote"
> style="border-left: 1px solid rgb(204, 204, 204);
> margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I also
> downloaded the .iso file, burned it, and started the
> install process.  I followed these
> instructions for creating the profile.
> <br><br>[i]Here''s a quick-and-dirty way to do a
> profile-driven install:<br><br>1. Boot your system
> off the net or from the DVD in the usual
> manner.<br><br>2. Select "Interactive
> Install".  Then, at the first
> opportunity
> <br>   to exit out of it (which will be
> after you''ve answered the<br>   system
> configuration questions, such as whether you
> want<br>   Kerberos and what the root
> password will be), exit out to a shell.<br><br>3.
> Create a profile for the install in
> /tmp/profile.  (The contents
> <br>   of the profile are described
> below).<br><br>4. Execute the
> following:<br><br>   # pfinstall
> /tmp/profile<br><br>When it''s done,
> reboot.  You should get a GRUB
> menu.  Select the<br>entry with the title
> "Solaris <release-name>
> X86".  The failsave
> <br>entry should work too.<br><br><br>Creating a
> profile for the
> install<br>----------------------------------<br>The
> system profile you use should look something like
> this:<br><br>install_type initial_install<br>cluster
> SUNWCuser
> <br>filesys c0t0d0s1 auto swap<br>pool mypool free /
> mirror c0t0d0s0 c0t1d0s0<br>dataset mypool/BE1 auto
> /<br>dataset mypool/BE1/usr auto /usr<br>dataset
> mypool/BE1/opt auto /opt<br>dataset mypool/BE1/var
> auto /var<br>dataset mypool/BE1/export auto
> /export[/i]
> <br><br>Obviously I changed the drive''s as
> required.  Then ran the pfinstall on the
> profile I created.  The install looked like
> it worked correctly, but after a reboot I''m
> having issues.<br><br>I get to the grub menu, which
> only has one entry
> "Solaris".  Which when you edit
> the line is the following [b]kernel$
> /platform/i86pc/kernel/$ISADIR/unix -B
> $ZFS-BOOTFS[/b].  When I pick this option
> all it sits there for a second, then boot loops and
> comes back to the grub menu.
> <br><br>Any suggestions?  Any way I can see
> what its doing when it pauses before the
> reboot?  I''m kinda new at this
> OpenSolaris stuff, so any debugging tips/tricks would
> be greatly
appreciated.<br><br>Mike<br><br><br>
> This message posted from <a
>
href="http://opensolaris.org">opensolaris.org</a><br>_
> ______________________________________________<br>zfs-
> discuss mailing list<br><a
> href="mailto:zfs-discuss at opensolaris.org">zfs-discuss@
> opensolaris.org
> </a><br><a
> href="http://mail.opensolaris.org/mailman/listinfo/zfs
> -discuss">http://mail.opensolaris.org/mailman/listinfo
> /zfs-discuss</a><br></blockquote></div><br>
> 
> </div>_______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discu
> ss
 
 
This message posted from opensolaris.org

I tried it and it worked great.  Even cloned my boot environment, and
BFU''d the clone and it seemed to work (minus a few unrelated annoyances
I haven''t tracked down yet).  I''m quite excited about the
possibilities :)

I am wondering though, is it possible to skip the creation of the pool and have
it install to an empty filesystem(s) in an existing pool (assume the pool is
already setup w/ grub and the like)?   I''m thinking installing new
builds (no upgrades), etc, as time goes on until the new installer is here.
 
 
This message posted from opensolaris.org

It looks to me like what you did should have worked.
The "cluster" line is fine.  I almost always include one
in my profiles.

So here''s a couple things to try:

1.  After the install completes, but before you reboot, look at
    the GRUB menu file:

    #  mount -F zfs mypool /mnt
    #  cat /mnt/boot/grub/menu.lst

    The tail of the file should look like this:

#---------- ADDED BY BOOTADM - DO NOT EDIT ----------
title Solaris Nevada snv_62 X86
kernel$ /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS
module$ /platform/i86pc/$ISADIR/boot_archive
#---------------------END BOOTADM--------------------
#---------- ADDED BY BOOTADM - DO NOT EDIT ----------
title Solaris failsafe
kernel /boot/platform/i86pc/kernel/unix -s
module /boot/x86.miniroot-safe
#---------------------END BOOTADM--------------------

   If it doesn''t, something has gone wrong.  Although, as long as you
have
   the first of those two entries, it should still boot.

2.  You can edit the first kernel$ line above to add "-kd" to it. 
That
   will cause the system to boot into kmdb (assuming it boots at all).
   If it gets that far, you can either poke around in kmdb if you know it,
   or just type ":c" to complete rebooting, at which point maybe
you''ll
   get some useful error messages.

3.  When you did the install, were there any error messages? 

Offhand, I don''t have any ideas as to what the problem is.  But these
are some of the things I''d do to debug it.  Let me know how it goes.

Lori

Mike Walker wrote:
> I also downloaded the .iso file, burned it, and started the install
process.  I followed these instructions for creating the profile.
>
> [i]Here''s a quick-and-dirty way to do a profile-driven install:
>
> 1. Boot your system off the net or from the DVD in the usual manner.
>
> 2. Select "Interactive Install".  Then, at the first opportunity
>    to exit out of it (which will be after you''ve answered the
>    system configuration questions, such as whether you want
>    Kerberos and what the root password will be), exit out to a shell.
>
> 3. Create a profile for the install in /tmp/profile.  (The contents
>    of the profile are described below).
>
> 4. Execute the following:
>
>    # pfinstall /tmp/profile
>
> When it''s done, reboot.  You should get a GRUB menu.  Select the
> entry with the title "Solaris <release-name> X86".  The
failsave
> entry should work too.
>
>
> Creating a profile for the install
> ----------------------------------
> The system profile you use should look something like this:
>
> install_type initial_install
> cluster SUNWCuser
> filesys c0t0d0s1 auto swap
> pool mypool free / mirror c0t0d0s0 c0t1d0s0
> dataset mypool/BE1 auto /
> dataset mypool/BE1/usr auto /usr
> dataset mypool/BE1/opt auto /opt
> dataset mypool/BE1/var auto /var
> dataset mypool/BE1/export auto /export[/i]
>
> Obviously I changed the drive''s as required.  Then ran the
pfinstall on the profile I created.  The install looked like it worked
correctly, but after a reboot I''m having issues.
>
> I get to the grub menu, which only has one entry "Solaris". 
Which when you edit the line is the following [b]kernel$
/platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS[/b].  When I pick this option
all it sits there for a second, then boot loops and comes back to the grub menu.
>
> Any suggestions?  Any way I can see what its doing when it pauses before
the reboot?  I''m kinda new at this OpenSolaris stuff, so any debugging
tips/tricks would be greatly appreciated.
>
> Mike
>  
>  
> This message posted from opensolaris.org
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>

Jason King wrote:
> I tried it and it worked great.  Even cloned my boot environment, and
BFU''d the clone and it seemed to work (minus a few unrelated annoyances
I haven''t tracked down yet).  I''m quite excited about the
possibilities :)
>
> I am wondering though, is it possible to skip the creation of the pool and
have it install to an empty filesystem(s) in an existing pool (assume the pool
is already setup w/ grub and the like)?   I''m thinking installing new
builds (no upgrades), etc, as time goes on until the new installer is here.
>  
>   
Yes, eventually, we should be able to do that.  But the version
of pfinstall you have right now doesn''t support it.

Lori

Mike makes a good point.  We have some severe problems
with build 63.  I''ve been hoping to get an answer for what''s
going on with it, but so far, I don''t have one.

So, note to everyone:  for zfs boot purposes, build 63 appears
to be DOA.  We''ll get out information on that as soon as possible,
and try it get it fixed for build 64, but until then, stick with build 62.

Lori

Mike Dotson wrote:
> Lori,
>
> Couldn''t tell but is he running build 63?
>
> On Tue, 2007-05-01 at 08:16 -0600, Lori Alt wrote:
>   
>> It looks to me like what you did should have worked.
>> The "cluster" line is fine.  I almost always include one
>> in my profiles.
>>
>> So here''s a couple things to try:
>>
>> 1.  After the install completes, but before you reboot, look at
>>     the GRUB menu file:
>>
>>     #  mount -F zfs mypool /mnt
>>     #  cat /mnt/boot/grub/menu.lst
>>
>>     The tail of the file should look like this:
>>
>> #---------- ADDED BY BOOTADM - DO NOT EDIT ----------
>> title Solaris Nevada snv_62 X86
>> kernel$ /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS
>> module$ /platform/i86pc/$ISADIR/boot_archive
>> #---------------------END BOOTADM--------------------
>> #---------- ADDED BY BOOTADM - DO NOT EDIT ----------
>> title Solaris failsafe
>> kernel /boot/platform/i86pc/kernel/unix -s
>> module /boot/x86.miniroot-safe
>> #---------------------END BOOTADM--------------------
>>
>>    If it doesn''t, something has gone wrong.  Although, as long
as you have
>>    the first of those two entries, it should still boot.
>>
>> 2.  You can edit the first kernel$ line above to add "-kd" to
it.  That
>>    will cause the system to boot into kmdb (assuming it boots at all).
>>    If it gets that far, you can either poke around in kmdb if you know
it,
>>    or just type ":c" to complete rebooting, at which point
maybe you''ll
>>    get some useful error messages.
>>
>> 3.  When you did the install, were there any error messages? 
>>
>> Offhand, I don''t have any ideas as to what the problem is. 
But these
>> are some of the things I''d do to debug it.  Let me know how it
goes.
>>
>> Lori
>>
>> Mike Walker wrote:
>>     
>>> I also downloaded the .iso file, burned it, and started the install
process.  I followed these instructions for creating the profile.
>>>
>>> [i]Here''s a quick-and-dirty way to do a profile-driven
install:
>>>
>>> 1. Boot your system off the net or from the DVD in the usual
manner.
>>>
>>> 2. Select "Interactive Install".  Then, at the first
opportunity
>>>    to exit out of it (which will be after you''ve answered
the
>>>    system configuration questions, such as whether you want
>>>    Kerberos and what the root password will be), exit out to a
shell.
>>>
>>> 3. Create a profile for the install in /tmp/profile.  (The contents
>>>    of the profile are described below).
>>>
>>> 4. Execute the following:
>>>
>>>    # pfinstall /tmp/profile
>>>
>>> When it''s done, reboot.  You should get a GRUB menu. 
Select the
>>> entry with the title "Solaris <release-name> X86". 
The failsave
>>> entry should work too.
>>>
>>>
>>> Creating a profile for the install
>>> ----------------------------------
>>> The system profile you use should look something like this:
>>>
>>> install_type initial_install
>>> cluster SUNWCuser
>>> filesys c0t0d0s1 auto swap
>>> pool mypool free / mirror c0t0d0s0 c0t1d0s0
>>> dataset mypool/BE1 auto /
>>> dataset mypool/BE1/usr auto /usr
>>> dataset mypool/BE1/opt auto /opt
>>> dataset mypool/BE1/var auto /var
>>> dataset mypool/BE1/export auto /export[/i]
>>>
>>> Obviously I changed the drive''s as required.  Then ran the
pfinstall on the profile I created.  The install looked like it worked
correctly, but after a reboot I''m having issues.
>>>
>>> I get to the grub menu, which only has one entry
"Solaris".  Which when you edit the line is the following [b]kernel$
/platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS[/b].  When I pick this option
all it sits there for a second, then boot loops and comes back to the grub menu.
>>>
>>> Any suggestions?  Any way I can see what its doing when it pauses
before the reboot?  I''m kinda new at this OpenSolaris stuff, so any
debugging tips/tricks would be greatly appreciated.
>>>
>>> Mike
>>>  
>>>  
>>> This message posted from opensolaris.org
>>> _______________________________________________
>>> zfs-discuss mailing list
>>> zfs-discuss at opensolaris.org
>>> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>>>   
>>>       
>> _______________________________________________
>> zfs-discuss mailing list
>> zfs-discuss at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>>

> sits there for a second, then boot loops and comes back to the grub menu.
I noticed this too when I was playing... using
kernel$ /platform/i86pc/kernel/$ISADIR/unix -v -B $ZFS-BOOTFS
I could see vmunix loading, but it quickly NMIed around the
rootnex: [ID 349649 kern.notice] isa0 at root
point... changing "bootfs root/snv_62" to "bootfs
rootpool/snv_62"
and rebuilding the pool EXACTLY the same way fixed it.

try changing "dataset mypool...." to "dataset rootpool..."
and I bet it will work..

				Rob

i am attempting to install b62 from the b62_zfsboot.iso that was posted last
week.
> 
> Mike makes a good point.  We have some severe
> problems
> with build 63.  I''ve been hoping to get an answer for
> what''s
> going on with it, but so far, I don''t have one.
> 
> So, note to everyone:  for zfs boot purposes, build
> 63 appears
> to be DOA.  We''ll get out information on that as soon
> as possible,
> and try it get it fixed for build 64, but until then,
> stick with build 62.
> 
> Lori
> 
> Mike Dotson wrote:
> > Lori,
> >
> > Couldn''t tell but is he running build 63?
> >
> > On Tue, 2007-05-01 at 08:16 -0600, Lori Alt wrote:
> >   
> >> It looks to me like what you did should have
> worked.
> >> The "cluster" line is fine.  I almost always
> include one
> >> in my profiles.
> >>
> >> So here''s a couple things to try:
> >>
> >> 1.  After the install completes, but before you
> reboot, look at
> >>     the GRUB menu file:
> >>
> >>     #  mount -F zfs mypool /mnt
> >>     #  cat /mnt/boot/grub/menu.lst
> >>
> >>     The tail of the file should look like this:
> >>
> >> #---------- ADDED BY BOOTADM - DO NOT EDIT
> ----------
> >> title Solaris Nevada snv_62 X86
> >> kernel$ /platform/i86pc/kernel/$ISADIR/unix -B
> $ZFS-BOOTFS
> >> module$ /platform/i86pc/$ISADIR/boot_archive
> >> #---------------------END
> BOOTADM--------------------
> >> #---------- ADDED BY BOOTADM - DO NOT EDIT
> ----------
> >> title Solaris failsafe
> >> kernel /boot/platform/i86pc/kernel/unix -s
> >> module /boot/x86.miniroot-safe
> >> #---------------------END
> BOOTADM--------------------
> >>
> >>    If it doesn''t, something has gone wrong.
>  Although, as long as you have
> >    the first of those two entries, it should still
> boot.
> >>
> >> 2.  You can edit the first kernel$ line above to
> add "-kd" to it.  That
> >>    will cause the system to boot into kmdb
> (assuming it boots at all).
> >>    If it gets that far, you can either poke around
> in kmdb if you know it,
> >>    or just type ":c" to complete rebooting, at
> which point maybe you''ll
> >>    get some useful error messages.
> >>
> >> 3.  When you did the install, were there any error
> messages? 
> >>
> >> Offhand, I don''t have any ideas as to what the
> problem is.  But these
> >> are some of the things I''d do to debug it.  Let me
> know how it goes.
> >>
> >> Lori
> >>
> >> Mike Walker wrote:
> >>     
> >>> I also downloaded the .iso file, burned it, and
> started the install process.  I followed these
> instructions for creating the profile.
> >>>
> >>> [i]Here''s a quick-and-dirty way to do a
> profile-driven install:
> >>>
> >>> 1. Boot your system off the net or from the DVD
> in the usual manner.
> >>>
> >>> 2. Select "Interactive Install".  Then, at the
> first opportunity
> >>>    to exit out of it (which will be after you''ve
> answered the
> >>>    system configuration questions, such as
> whether you want
> >>>    Kerberos and what the root password will be),
> exit out to a shell.
> >>>
> >>> 3. Create a profile for the install in
> /tmp/profile.  (The contents
> >>>    of the profile are described below).
> >>>
> >>> 4. Execute the following:
> >>>
> >>>    # pfinstall /tmp/profile
> >>>
> >>> When it''s done, reboot.  You should get a GRUB
> menu.  Select the
> >>> entry with the title "Solaris <release-name>
> X86".  The failsave
> >>> entry should work too.
> >>>
> >>>
> >>> Creating a profile for the install
> >>> ----------------------------------
> >>> The system profile you use should look something
> like this:
> >>>
> >>> install_type initial_install
> >>> cluster SUNWCuser
> >>> filesys c0t0d0s1 auto swap
> >>> pool mypool free / mirror c0t0d0s0 c0t1d0s0
> >>> dataset mypool/BE1 auto /
> >>> dataset mypool/BE1/usr auto /usr
> >>> dataset mypool/BE1/opt auto /opt
> >>> dataset mypool/BE1/var auto /var
> >>> dataset mypool/BE1/export auto /export[/i]
> >>>
> >>> Obviously I changed the drive''s as required.
> Then ran the pfinstall on the profile I created.
> The install looked like it worked correctly, but
>  after a reboot I''m having issues.
> >>
> >>> I get to the grub menu, which only has one entry
> "Solaris".  Which when you edit the line is the
> following [b]kernel$
> /platform/i86pc/kernel/$ISADIR/unix -B
> $ZFS-BOOTFS[/b].  When I pick this option all it sits
> there for a second, then boot loops and comes back to
> the grub menu.
> >>>
> >>> Any suggestions?  Any way I can see what its
> doing when it pauses before the reboot?  I''m kinda
> new at this OpenSolaris stuff, so any debugging
> tips/tricks would be greatly appreciated.
> >>>
> >>> Mike
> >>>  
> >>>  
> >>> This message posted from opensolaris.org
> >>> _______________________________________________
> >>> zfs-discuss mailing list
> >>> zfs-discuss at opensolaris.org
> >>>
> http://mail.opensolaris.org/mailman/listinfo/zfs-discu
> ss
> >>>   
> >>>       
> >> _______________________________________________
> >> zfs-discuss mailing list
> >> zfs-discuss at opensolaris.org
> >>
> http://mail.opensolaris.org/mailman/listinfo/zfs-discu
> ss
> >>     
> 
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discu
> ss
>
 
 
This message posted from opensolaris.org

That''s a good catch - I had indeed changed mine to rootpool, but
didn''t
think the chosen name mattered.

On 5/1/07, Rob Logan <Rob at logan.com> wrote:
>
> > sits there for a second, then boot loops and comes back to the grub
> menu.
>
> I noticed this too when I was playing... using
> kernel$ /platform/i86pc/kernel/$ISADIR/unix -v -B $ZFS-BOOTFS
> I could see vmunix loading, but it quickly NMIed around the
> rootnex: [ID 349649 kern.notice] isa0 at root
> point... changing "bootfs root/snv_62" to "bootfs
rootpool/snv_62"
> and rebuilding the pool EXACTLY the same way fixed it.
>
> try changing "dataset mypool...." to "dataset
rootpool..."
> and I bet it will work..
>
>                                 Rob
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20070501/7e82cc00/attachment.html>

The name of the pool should not matter.

Lori

Malachi de ?lfweald wrote:
> That''s a good catch - I had indeed changed mine to rootpool, but 
> didn''t think the chosen name mattered.
>
> On 5/1/07, *Rob Logan* < Rob at logan.com <mailto:Rob at
logan.com>> wrote:
>
>     > sits there for a second, then boot loops and comes back to the
>     grub menu.
>
>     I noticed this too when I was playing... using
>     kernel$ /platform/i86pc/kernel/$ISADIR/unix -v -B $ZFS-BOOTFS
>     I could see vmunix loading, but it quickly NMIed around the
>     rootnex: [ID 349649 kern.notice] isa0 at root
>     point... changing "bootfs root/snv_62" to "bootfs
rootpool/snv_62"
>     and rebuilding the pool EXACTLY the same way fixed it.
>
>     try changing "dataset mypool...." to "dataset
rootpool..."
>     and I bet it will work..
>
>                                     Rob
>     _______________________________________________
>     zfs-discuss mailing list
>     zfs-discuss at opensolaris.org <mailto:zfs-discuss at
opensolaris.org>
>     http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>

Brian Hechinger wrote:
> On Fri, Apr 27, 2007 at 02:44:02PM -0700, Malachi de ??lfweald wrote:
>   
>
>> 2. ZFS mirroring can work without the metadb, but if you want the dump
>> mirrored too, you need the metadb (I don''t know if it needs to
be mirrored,
>> but I wanted both disks to be identical in case one died)
>>     
>
> I can''t think of any real good reason you would need a mirrored
dump device.
> The only place that would help you is if your main disk died between panic
> and next boot.  ;)
>   
If you lose the primary drive, and your dump device points to the 
metadevice, then you wouldn''t have to reset it. Also, most folks use
the
swap device for dumps. You wouldn''t want to lose that on a live box. 
(Though honestly I''ve never just yanked the swap device and seen if the
system keels over.

On Tue, May 01, 2007 at 09:56:04PM -0400, Torrey McMahon
wrote:
> 
> If you lose the primary drive, and your dump device points to the 
> metadevice, then you wouldn''t have to reset it. Also, most folks
use the
Eh, that''s true, not something I''ve really ever had to think
about due
to your next point.
> swap device for dumps. You wouldn''t want to lose that on a live
box.
> (Though honestly I''ve never just yanked the swap device and seen
if the
> system keels over.
Neither have I, but mirroring swap is something I commonly do, so
haven''t
ever gotten myself into a situation to find out what happens.

I bet it''s ugly though.  ;)

-brian
-- 
"Perl can be fast and elegant as much as J2EE can be fast and elegant.
In the hands of a skilled artisan, it can and does happen; it''s just
that most of the shit out there is built by people who''d be better
suited to making sure that my burger is cooked thoroughly."  -- Jonathan
Patschke