zfs discuss - Apr 2008 - lucreate error: Cannot determine the physical boot device ...

# lucreate -n B85
Analyzing system configuration.
Hi,

after typing 

  # lucreate -n B85

I get the following error:

No name for current boot environment.
INFORMATION: The current boot environment is not named - assigning name
<BE1>.
Current boot environment is named <BE1>.
Creating initial configuration for primary boot environment <BE1>.
ERROR: Unable to determine major and minor device numbers for root device
<tank/BE1>.
ERROR: Cannot determine the physical boot device for the current boot
environment <BE1>.
Use the <-C> command line option to specify the physical boot device for
the current boot environment <BE1>.
ERROR: Cannot create configuration for primary boot environment.


I tried to use the -C option like:

lucreate -C c0d0s0 -n B85 but also without 
success and got this:

# lucreate -C c0d0s0 -n B85
ERROR: No such file or directory: cannot stat <c0d0s0>
ERROR: cannot use <c0d0s0> as a boot device because it is not a block
device
Usage: lucreate -n BE_name [ -A BE_description ] [ -c BE_name ]
        [ -C ( boot_device | - ) ] [ -f exclude_list-file [ -f ... ] ] [ -I ]
        [ -l error_log-file ] [ -M slice_list-file [ -M ... ] ]
        [ -m mountPoint:devicePath:fsOptions [ -m ... ] ] [ -o out_file ]
        [ -s ( - | source_BE_name ) ] [ -x exclude_dir/file [ -x ... ] ] [ -X ]
        [ -y include_dir/file [ -y ... ] ] [ -Y include_list-file [ -Y ... ] ]
        [ -z filter_list-file ]


Could someone please tell me how to use lucreate?

Roman
 
 
This message posted from opensolaris.org

Roman

I didn''t think that we had live upgrade support for zfs root filesystem
yet.

T

Roman Morokutti wrote:
> # lucreate -n B85
> Analyzing system configuration.
> Hi,
> 
> after typing 
> 
>   # lucreate -n B85
> 
> I get the following error:
> 
> No name for current boot environment.
> INFORMATION: The current boot environment is not named - assigning name
<BE1>.
> Current boot environment is named <BE1>.
> Creating initial configuration for primary boot environment <BE1>.
> ERROR: Unable to determine major and minor device numbers for root device
<tank/BE1>.
> ERROR: Cannot determine the physical boot device for the current boot
environment <BE1>.
> Use the <-C> command line option to specify the physical boot device
for the current boot environment <BE1>.
> ERROR: Cannot create configuration for primary boot environment.
> 
> 
> I tried to use the -C option like:
> 
> lucreate -C c0d0s0 -n B85 but also without 
> success and got this:
> 
> # lucreate -C c0d0s0 -n B85
> ERROR: No such file or directory: cannot stat <c0d0s0>
> ERROR: cannot use <c0d0s0> as a boot device because it is not a block
device
> Usage: lucreate -n BE_name [ -A BE_description ] [ -c BE_name ]
>         [ -C ( boot_device | - ) ] [ -f exclude_list-file [ -f ... ] ] [ -I
]
>         [ -l error_log-file ] [ -M slice_list-file [ -M ... ] ]
>         [ -m mountPoint:devicePath:fsOptions [ -m ... ] ] [ -o out_file ]
>         [ -s ( - | source_BE_name ) ] [ -x exclude_dir/file [ -x ... ] ] [
-X ]
>         [ -y include_dir/file [ -y ... ] ] [ -Y include_list-file [ -Y ...
] ]
>         [ -z filter_list-file ]
> 
> 
> Could someone please tell me how to use lucreate?
> 
> Roman
>  
>  
> This message posted from opensolaris.org
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

I further found out that there exists a nearly similar
problem described in Bug-Id: 6442921.

lubootdev reported:

# /etc/lib/lu/lubootdev -b
/dev/dsk/c0d0p0

Using this info for -C I got the following:

# lucreate -C /dev/dsk/c0d0p0 -n B85
Analyzing system configuration.
No name for current boot environment.
INFORMATION: The current boot environment is not named - assigning name
<BE1>.
Current boot environment is named <BE1>.
Creating initial configuration for primary boot environment <BE1>.
INFORMATION: Unable to determine size or capacity of slice
</dev/zvol/dsk/tank/swapvol>.
ERROR: Unable to determine major and minor device numbers for root device
<tank/BE1>.
INFORMATION: Unable to determine size or capacity of slice <>.
ERROR: Internal Configuration File </etc/lu/ICF.1> exists but has no
contents.
ERROR: The file </etc/lu/ICF.1> specified by the <-f> option is not
a valid ICF file.
ERROR: Cannot update boot environment configuration file with the current BE
<BE1> information.
ERROR: Cannot create configuration for primary boot environment.

Roman
 
 
This message posted from opensolaris.org

> I didn''t think that we had live upgrade support for
> zfs root filesystem yet.
> 
Original quote from Lori Alt:

"ZFS is ideally suited to making ?clone and
modify? fast, easy, and space-efficient. Both
?clone and modify? tools will work much better
if your root file system is ZFS. (The new install
tool will require it for some features.)"

Roman
 
 
This message posted from opensolaris.org

Hi,

This was taken from where? From liveupgrade??? As long as I know, liveupgrade
works only with ufs. At the time of my first install I choose ufs exactly for
the reason to be able to do liveupgrade.

What you have there is something that I agree but NOT for liveupgrade but yes to
work with intensive operations under ZFS. Lots of clones, changing the pools
struts and so on ...

Best regards
Ether.pt
> 
> "ZFS is ideally suited to making ?clone and
> modify? fast, easy, and space-efficient. Both
> ?clone and modify? tools will work much better
> if your root file system is ZFS. (The new install
> tool will require it for some features.)"
> 
> Roman
 
 
This message posted from opensolaris.org

It''s true that liveupgrade doesn''t support zfs yet.  That
support will become available in the build 89 or 90
time frame, at the same time that zfs as a root file system
is supported.

Lori

Ether.pt wrote:
> Hi,
>
> This was taken from where? From liveupgrade??? As long as I know,
liveupgrade works only with ufs. At the time of my first install I choose ufs
exactly for the reason to be able to do liveupgrade.
>
> What you have there is something that I agree but NOT for liveupgrade but
yes to work with intensive operations under ZFS. Lots of clones, changing the
pools struts and so on ...
>
> Best regards
> Ether.pt
>
>   
>> "ZFS is ideally suited to making ?clone and
>> modify? fast, easy, and space-efficient. Both
>> ?clone and modify? tools will work much better
>> if your root file system is ZFS. (The new install
>> tool will require it for some features.)"
>>
>> Roman
>>     
>  
>  
> This message posted from opensolaris.org
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>

> Support will become available in the build 89 or 90
> time frame, at the same time that zfs as a root file
> system is supported.
I greatly appreciate this and there is nothing more to do
than to wait for zfs being capable of live upgrading.

Roman
 
 
This message posted from opensolaris.org