Prev: FreeNIX 09 conference, Saturday November 21 Stockholm Sweden
Next: Logout logging
From: Oscar del Rio on 10 Nov 2009 10:49
Dave wrote:
> # beadm create opensolaris-1
> WARNING: menu.lst file none/boot/grub/menu.lst does not exist,

The menu.lst path is supposed to be
/rpool/boot/grub/menu.lst

> # zfs list -o name,mountpoint,mounted
> NAME MOUNTPOINT MOUNTED
> rpool none no
> rpool/ROOT legacy no
> rpool/ROOT/opensolaris / yes

The rpool mount doesn't look right. On my (opensolaris) system it is

NAME MOUNTPOINT MOUNTED
rpool /rpool yes
rpool/ROOT legacy no
rpool/ROOT/opensolaris-126 / yes

That might be where "none/boot/grub/menu.lst" is coming from in your
case. Did you change any of the rpool mount options?
From: David Kirkby on 11 Nov 2009 13:33
On Nov 10, 3:17 pm, cindy <cindy.swearin...(a)sun.com> wrote:
> 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

Thank you Cindy. I do not have access to the machine now, so are
unable to check. I've not changed the layout of the 500 GB disk - it
still have the diagnostic partition on it, that it was supplied with.
I think Oscar (next post) has probably found the problem in fact.
From: David Kirkby on 11 Nov 2009 13:42
On Nov 10, 3:49 pm, Oscar del Rio <del...(a)mie.utoronto.ca> wrote:
> Dave wrote:
> > # beadm create opensolaris-1
> > WARNING: menu.lst file none/boot/grub/menu.lst does not exist,
>
> The menu.lst path is supposed to be
> /rpool/boot/grub/menu.lst
>
> > # zfs list -o name,mountpoint,mounted
> > NAME                    MOUNTPOINT             MOUNTED
> > rpool                   none                        no
> > rpool/ROOT              legacy                      no
> > rpool/ROOT/opensolaris  /                          yes
>
> The rpool mount doesn't look right. On my (opensolaris) system it is
>
> NAME                           MOUNTPOINT           MOUNTED
> rpool                          /rpool                   yes
> rpool/ROOT                     legacy                    no
> rpool/ROOT/opensolaris-126     /                        yes
>
> That might be where "none/boot/grub/menu.lst" is coming from in your
> case.  Did you change any of the rpool mount options?

Thank you.

You may have found the problem there. I did indeed mess around with
the mount points somewhat, as I wanted to to move /export/home, which
was originally on the root pool (500 GB disk) , to another pool made
of two 2 TB mirrored disks. See my post "Where should I mount home
directories on new disk ?? "

http://groups.google.com/group/alt.solaris.x86/browse_thread/thread/7f1862e7270d0fc1/f01f2faea685151f?hl=en&lnk=gst&q=export+Ultra+27+mount+zfs#f01f2faea685151f

The actual commands I executed were:

zfs snapshot rpool/export/home/drkirkby(a)move

zfs send rpool/export/home/drkirkby(a)move | zfs recv bpool/users -F

zfs set mountpoint=none rpool/export/home/drkirkby

zfs set mountpoint=/export/home/drkirkby bpool/users


The fact this updating worked at one time, but no longer does, rather
indicates I have messed something up since, rather than an issue such
as the wrong label on the disk. I can't however be sure exactly when
this problem occured, and therefore whether it was a result of messing
with the mount points. But I think you are probably on the right track
there.

The question is, how is the best way to get around this? I really want
to keep user directories off of the root pool.

Dave
From: Oscar del Rio on 11 Nov 2009 14:39
David Kirkby wrote:
> On Nov 10, 3:49 pm, Oscar del Rio <del...(a)mie.utoronto.ca> wrote:
>> Dave wrote:
>>> # beadm create opensolaris-1
>>> WARNING: menu.lst file none/boot/grub/menu.lst does not exist,
>> The menu.lst path is supposed to be
>> /rpool/boot/grub/menu.lst
>>
>>> # zfs list -o name,mountpoint,mounted
>>> NAME MOUNTPOINT MOUNTED
>>> rpool none no
>>> rpool/ROOT legacy no
>>> rpool/ROOT/opensolaris / yes
>> The rpool mount doesn't look right. On my (opensolaris) system it is
>>
>> NAME MOUNTPOINT MOUNTED
>> rpool /rpool yes
>> rpool/ROOT legacy no
>> rpool/ROOT/opensolaris-126 / yes
>>
>> That might be where "none/boot/grub/menu.lst" is coming from in your
>> case. Did you change any of the rpool mount options?

> The fact this updating worked at one time, but no longer does, rather
> indicates I have messed something up since, rather than an issue such
> as the wrong label on the disk. I can't however be sure exactly when
> this problem occured, and therefore whether it was a result of messing
> with the mount points. But I think you are probably on the right track
> there.
>
> The question is, how is the best way to get around this? I really want
> to keep user directories off of the root pool.

I would guess:

zfs set mountpoint=/rpool rpool

you (and beadm) should be able to see /rpool/boot/grub/menu.lst
From: Dave on 11 Nov 2009 23:56
Oscar del Rio wrote:
> David Kirkby wrote:
>> On Nov 10, 3:49 pm, Oscar del Rio <del...(a)mie.utoronto.ca> wrote:
>>> Dave wrote:
>>>> # beadm create opensolaris-1
>>>> WARNING: menu.lst file none/boot/grub/menu.lst does not exist,
>>> The menu.lst path is supposed to be
>>> /rpool/boot/grub/menu.lst
>>>
>>>> # zfs list -o name,mountpoint,mounted
>>>> NAME MOUNTPOINT MOUNTED
>>>> rpool none no
>>>> rpool/ROOT legacy no
>>>> rpool/ROOT/opensolaris / yes
>>> The rpool mount doesn't look right. On my (opensolaris) system it is
>>>
>>> NAME MOUNTPOINT MOUNTED
>>> rpool /rpool yes
>>> rpool/ROOT legacy no
>>> rpool/ROOT/opensolaris-126 / yes
>>>
>>> That might be where "none/boot/grub/menu.lst" is coming from in your
>>> case. Did you change any of the rpool mount options?
>
>> The fact this updating worked at one time, but no longer does, rather
>> indicates I have messed something up since, rather than an issue such
>> as the wrong label on the disk. I can't however be sure exactly when
>> this problem occured, and therefore whether it was a result of messing
>> with the mount points. But I think you are probably on the right track
>> there.
>>
>> The question is, how is the best way to get around this? I really want
>> to keep user directories off of the root pool.
>
> I would guess:
>
> zfs set mountpoint=/rpool rpool
>
> you (and beadm) should be able to see /rpool/boot/grub/menu.lst

Thank you, that works. I can't say I understand exactly what went wrong, but it
is ok now.

dave

--
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.
First  |  Prev  | 
Pages: 1 2
Prev: FreeNIX 09 conference, Saturday November 21 Stockholm Sweden
Next: Logout logging