Problem with live upgrade creation: Telling me metadevices do not exist
Hi
I am having a problem creating my live upgrade environment.
Here is the error I get:
Code:
root@server:/# lucreate -c SOL10_18May -n SOL10_19May -z /lu_excludelist -m /:dev/md/dsk/d0:ufs -m /var:/dev/md/dsk/d4:ufs -m /export/home:/dev/md/dsk/d6:ufs -m -:/dev/md/dsk/d3:swap -C /dev/dsk/c1t3d0s0
Discovering physical storage devices
Discovering logical storage devices
Cross referencing storage devices with boot environment configurations
Determining types of file systems supported
Validating file system requests
ERROR: device <dev/md/dsk/d0> does not exist
ERROR: device <dev/md/dsk/d0> is not available for use with mount point </>
ERROR: cannot create new boot environment using file systems as configured
ERROR: please review all file system configuration options
ERROR: cannot create new boot environment using options provided
I have created all those metadevices prior to running the lucreate command.
I have also installed all the required packages and patches.
Can any please help me find a solution?
Thanks
---------- Post updated 05-20-10 at 09:51 AM ---------- Previous update was 05-19-10 at 02:46 PM ----------
Oh my word, I was such a fool. I left a slash out....
dev/md/dsk/d0 does not excist, but /dev/md/dsk/d0 does...
Last edited by pludi; 05-19-2010 at 09:57 AM..
Reason: code tags, please...
Hi,
I upgraded solaris 10 x86 from update 3 to update 7 with zones installed n UFS file system . The global zone was updated but the non global zone still shows update 3 what could be the reason for this and how can i update the local zones to update 7 (0 Replies)
I want to basically update an ABE that someone created a few months back.
I'm sure stuff has changed since it was made, and I was going to delete it and create a new one.
But from what I'm looking at, the lumake appears like it would be a faster approach.
I want to use live upgrade to... (0 Replies)
I tried a live upgrade for one my solaris 10u8 server which didnt go sucessfull and after that i now have following mounts in memory.
df: cannot statvfs /.alt.sol10u8_2/var: No such file or directory
df: cannot statvfs /.alt.sol10u8_2/var/run: No such file or directory
df: cannot statvfs... (0 Replies)
Hi Guys, having an issue with running Live Upgrade on a t5240 runiing Solaris 10 5/08.
The system has the required patches 121430, and Live upgrade was updated from the install media sol-10-u10-ga2-sparc-dvd.iso
The following boot environments were created
solenv1 and solenv2 with the... (8 Replies)
I am upgrading Solaris-9 Update-7 to Solaris-9 Update-9 through live upgrade. I am able to create another boot environment and have OS DVD inside server. But i am confused for, what command/path should I give for luupgrade.
OS DVD is mounted on /mnt
Boot environments are Solaris9old (Active now)... (2 Replies)
Hi All,
Is it possible to use external san disk for creating alternate boot environment and boot from it.My root disk is about 70 gb and i want to use external san disk for 272gb to create alternate boot environment.If this is possible can you please redirect me some good documents, i had... (1 Reply)
Hi
I am new to live upgrade.
I would like to tell you about my new setup, where my boot disk(c0d0) is mirrored with secondary disk(c0d1). I have remove the secondary whole disk(C0d1) from the mirror, so that I can do live upgrade on this secondary disk.
I have done live upgrade on s0 partition... (3 Replies)
Hello Guys,
I am a little confused about the first step in the live upgrade process. I will be glad if someone can clarify this for me.
The pre-live upgrade patch, when do you add this patch to the OS you want to upgrade?
1. before creating the new boot environment? or
2. after creating... (1 Reply)
Discussion started by: cjashu
1 Replies
LEARN ABOUT OPENSOLARIS
lutab
lutab(4)lutab(4)NAME
lutab - list of boot environments
SYNOPSIS
/etc/lutab
DESCRIPTION
The file /etc/lutab is a list of the boot environments (BEs) configured on a system. There are two entries for each BE. These entries have
the following form:
BE_id:BE_name:completion_flag:0
BE_id:root_slice:root_device:1
The fields in the lutab entries are described as follows:
BE_id A unique, internally generated id for a BE.
BE_name The user-assigned name of a BE.
completion_flag Indicates whether the BE is complete (C) or incomplete (NC). A complete BE is one that is not involved in any copy or
upgrade operation. A BE can be activated or compared only when it is complete.
0 Indicates first of two lines.
BE_id As described above.
root_slice Designation of the root slice.
root_device Device on which the root slice is mounted.
1 Indicates second of two lines.
The lutab file must not be edited by hand. Any user modification to this file will result in the incorrect operation of live upgrade.
SEE ALSO lu(1M), luactivate(1M), lucreate(1M), lucurr(1M), lufslist(1M), lustatus(1M), luupgrade(1M), attributes(5), live_upgrade(5)WARNINGS
The lutab file is not a public interface. The format and contents of lutab are subject to change. Use lufslist(1M) and lustatus(1M) to
obtain information about BEs.
SunOS 5.10 8 Jun 2001 lutab(4)
05-20-2010
