Prev: FreeNIX 09 conference, Saturday November 21 Stockholm Sweden
Next: Logout logging
From: Dave on 10 Nov 2009 08:11
I've got an Ultra 27 running OpenSolaris 06/2009. I got an error while trying to
using the Package Manager to update some packages. It indicated it could not
clone the boot environment. So I tried this manually, but get the following.

# beadm create opensolaris-1
WARNING: menu.lst file none/boot/grub/menu.lst does not exist,
generating a new menu.lst file
Unable to create opensolaris-1.
Unknown external error.

And running a second time:

# beadm create opensolaris-1
WARNING: menu.lst file none/boot/grub/menu.lst does not exist,
generating a new menu.lst file
Unable to create opensolaris-1.
Unknown external error.

The disk layout is this

* 500 GB disk for root pool - not mirrored.
* 500 GB disk *intending* to be used to mirror the root pool, but I've not
actually done that yet. (I only put the disk in a couple of days back, and have
been tied up with other things).
* 2 x 2 TB disks, which are mirrored.

I'm posting the output of a few commands that I've seen others ask for, when
people had problems with the Package Manager being unable to clone the boot
environment.

bash-3.2$ cat /etc/release
OpenSolaris 2009.06 snv_111b X86
Copyright 2009 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 07 May 2009

# zfs list -o name,mountpoint,mounted
NAME MOUNTPOINT MOUNTED
bpool /bpool yes
bpool/local /usr/local yes
bpool/users /export/home/drkirkby yes
bpool/users/jas /export/home/jas yes
bpool/zones /zones yes
bpool/zones/apache /zones/apache yes
rpool none no
rpool/ROOT legacy no
rpool/ROOT/opensolaris / yes
rpool/dump - -
rpool/export /export yes
rpool/export/home /export/home yes
rpool/swap - -



# zpool list
NAME SIZE USED AVAIL CAP HEALTH ALTROOT
bpool 1.81T 33.6G 1.78T 1% ONLINE -
rpool 464G 37.6G 426G 8% ONLINE -

# zoneadm list -vc
ID NAME STATUS PATH BRAND IP
0 global running / native shared

# /usr/sbin/beadm list
BE Active Mountpoint Space Policy Created
-- ------ ---------- ----- ------ -------
opensolaris NR / 6.98G static 2009-10-26 17:16




# cat /etc/vfstab
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
#
/devices - /devices devfs - no -
/proc - /proc proc - no -
ctfs - /system/contract ctfs - no -
objfs - /system/object objfs - no -
sharefs - /etc/dfs/sharetab sharefs - no -
fd - /dev/fd fd - no -
swap - /tmp tmpfs - yes -

/dev/zvol/dsk/rpool/swap - - swap - no -
#

--
I respectfully request that this message is not archived by companies as
unscrupulous as 'Experts Exchange' . In case you are unaware,
'Experts Exchange' take questions posted on the web and try to find
idiots stupid enough to pay for the answers, which were posted freely
by others. They are leeches.
From: Bruce Esquibel on 10 Nov 2009 09:14
Dave <foo(a)coo.com> wrote:

> I've got an Ultra 27 running OpenSolaris 06/2009. I got an error while trying to
> using the Package Manager to update some packages. It indicated it could not
> clone the boot environment. So I tried this manually, but get the following.

> # beadm create opensolaris-1
> WARNING: menu.lst file none/boot/grub/menu.lst does not exist,
> generating a new menu.lst file
> Unable to create opensolaris-1.
> Unknown external error.

This is just a shot in the dark but have you tried something else besides
"opensolaris-1"?

The beadm seems to be a python script and maybe it's just a parsing error.

Just saying the "-" is throwing something off possibly.

-bruce
bje(a)ripco.com
From: Dave on 10 Nov 2009 09:33
Bruce Esquibel wrote:
> Dave <foo(a)coo.com> wrote:
>
>> I've got an Ultra 27 running OpenSolaris 06/2009. I got an error while trying to
>> using the Package Manager to update some packages. It indicated it could not
>> clone the boot environment. So I tried this manually, but get the following.
>
>> # beadm create opensolaris-1
>> WARNING: menu.lst file none/boot/grub/menu.lst does not exist,
>> generating a new menu.lst file
>> Unable to create opensolaris-1.
>> Unknown external error.
>
> This is just a shot in the dark but have you tried something else besides
> "opensolaris-1"?
>
> The beadm seems to be a python script and maybe it's just a parsing error.
>
> Just saying the "-" is throwing something off possibly.
>
> -bruce
> bje(a)ripco.com

I had not. I chose that, since that was the name of the BE the Package Manager
was attempting to create. But it seems to fail with other things too.

# beadm create testing123
WARNING: menu.lst file none/boot/grub/menu.lst does not exist,
generating a new menu.lst file
Unable to create testing123.
Unknown external error.

--
I respectfully request that this message is not archived by companies as
unscrupulous as 'Experts Exchange' . In case you are unaware,
'Experts Exchange' take questions posted on the web and try to find
idiots stupid enough to pay for the answers, which were posted freely
by others. They are leeches.
From: hume.spamfilter on 10 Nov 2009 10:07
Dave <foo(a)coo.com> wrote:
> Unknown external error.

This implies that perhaps beadm is calling another command and that's
failing. Have you tried trussing and seeing if you see any errors?

Also, you could try asking on opensolaris.org, perhaps in the forums.

--
Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/
From: cindy on 10 Nov 2009 10:17
On Nov 10, 7:33 am, Dave <f...(a)coo.com> wrote:
> Bruce Esquibel wrote:
> > Dave <f...(a)coo.com> wrote:
>
> >> I've got an Ultra 27 running OpenSolaris 06/2009. I got an error while trying to
> >> using the Package Manager to update some packages. It indicated it could not
> >> clone the boot environment. So I tried this manually, but get the following.
>
> >> # beadm create opensolaris-1
> >> WARNING: menu.lst file none/boot/grub/menu.lst does not exist,
> >> generating a new menu.lst file
> >> Unable to create opensolaris-1.
> >> Unknown external error.
>
> > This is just a shot in the dark but have you tried something else besides
> > "opensolaris-1"?
>
> > The beadm seems to be a python script and maybe it's just a parsing error.
>
> > Just saying the "-" is throwing something off possibly.
>
> > -bruce
> > b...(a)ripco.com
>
> I had not. I chose that, since that was the name of the BE the Package Manager
> was attempting to create. But it seems to fail with other things too.
>
> # beadm create testing123
> WARNING: menu.lst file none/boot/grub/menu.lst does not exist,
> generating a new menu.lst file
> Unable to create testing123.
> Unknown external error.
>
> --
> I respectfully request that this message is not archived by companies as
> unscrupulous as 'Experts Exchange' . In case you are unaware,
> 'Experts Exchange' take questions posted on the web and try to find
> idiots stupid enough to pay for the answers, which were posted freely
> by others. They are leeches.

Hi Dave,

I think this error condition has been associated with an EFI label on
the root pool disk. Since this is your primary (only) root pool disk,
I don't see how you could boot a system with an EFI-label disk.

Check the disk label and make sure it is an SMI disk label.

Cindy
 |  Next  |  Last
Pages: 1 2
Prev: FreeNIX 09 conference, Saturday November 21 Stockholm Sweden
Next: Logout logging