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@opensolaris.org
> >>>
> http://mail.opensolaris.org/mailman/listinfo/zfs-discu
> ss
> >>>   
> >>>       
> >> _______________________________________________
> >> zfs-discuss mailing list
> >> zfs-discuss@opensolaris.org
> >>
> http://mail.opensolaris.org/mailman/listinfo/zfs-discu
> ss
> >>     
> 
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss@opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discu
> ss
>
 
 
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to