Sponsored Content
Operating Systems Solaris Solaris not booting with new BE after performing Liveupgrade. Post 302968634 by fpmurphy on Saturday 12th of March 2016 02:31:25 AM
Old 03-12-2016
You did not give a boot environment argument, i.e. New_zfs, to luactivate.
 

7 More Discussions You Might Find Interesting

1. Solaris

Solairs 9 to Solaris 10 liveupgrade issue

Hello, I started the upgrade using LiveUpgrade. I am using Solaris 10 instalation CDs (5 CDs). My server is Enterprise 3500 - SPARC. 1) lucreate -c first_disk -m /:/dev/dsk/c0t11d0s7:ufs -n second_disk ... luupgrade -u -n second_disk -s /cdrom/cdrom0/s0 WARNING: <5> packages failed to... (0 Replies)
Discussion started by: zafyil
0 Replies

2. Solaris

Solaris m/c not booting

My Solaris machine is not booting.It just stops at the point Boot device: /pci@1e,600000/ide@d/disk@0,0:a File and args: Whether i try boot or boot -s it is stopping at this point.. I tried boot cdom -s.It went into single user mode but I am not able to run a fsck in this mode. Right... (1 Reply)
Discussion started by: lydiaEd
1 Replies

3. Solaris

solaris 10 liveupgrade issues

I got this output from a system running solaris 10 : # lustatus BE_name Complete Active ActiveOnReboot CopyStatus -------------------------------------------------------------------------------- oldvol yes yes yes - newvol no no no - bigvol no no no - # How do i remove (or... (1 Reply)
Discussion started by: ibroxy
1 Replies

4. Solaris

Solaris liveupgrade will NOT boot into new BE

OK, latest in a loooong trail of errors with no information. I've finally gotten a new BE created on another drive, run liveupgrade on it to bring it from sol10u3 to sol10u8 I luactivate sol10u8 lustatus shows the sol10u8 as the active one init 6 system just starts into 10u3 again. I'm... (4 Replies)
Discussion started by: awoodby
4 Replies

5. UNIX for Dummies Questions & Answers

Help with booting Solaris 9

Folks; I have a Solaris 9 server that after power outage it won't come fully up and i was able to bring it up in single user mode and checked "/var/log/messages" & "/var/adm/messages" with nothing showing since Sept. 17. i ran fsck and no luck. I ran all tests from the OK prompt with no luck... (2 Replies)
Discussion started by: Katkota
2 Replies

6. Solaris

Booting Solaris 10/09

What type of communication does Solaris 10/09 need to do with it's default gateway before it can boot up? (7 Replies)
Discussion started by: bstauffer
7 Replies

7. Solaris

Solaris 10 liveupgrade/ABE advice

Hi all, I have got a few questions on the above topic -> q1) if my intention for creating an ABE is just to use for patching / patchset update - e.g. ./installpatchset -B secondboot --s10patchset luactivate secondboot What is the recommendation that my ABE should consist of ?... (5 Replies)
Discussion started by: javanoob
5 Replies
ludelete(1M)															      ludelete(1M)

NAME
ludelete - delete a boot environment SYNOPSIS
/usr/sbin/ludelete [-l error_log] [-o outfile] BE_name [-X] DESCRIPTION
The ludelete command is part of a suite of commands that make up the Live Upgrade feature of the Solaris operating environment. See live_upgrade(5) for a description of the Live Upgrade feature. The ludelete command deletes all records associated with a boot environment (BE) on all defined complete BEs. A complete BE is one that is not participating in an lucreate(1M), luupgrade(1M), or lucompare(1M) operation. Use lustatus(1M) to determine a BE's status. You can delete neither the current BE, nor the BE that will become current upon the next reboot. Also, you cannot delete a BE that has file systems mounted with lumount(1M) or mount(1M). ludelete does not alter any files on the BE being deleted. The ludelete command requires root privileges. OPTIONS
The ludelete command has the following options: -l error_log Error and status messages are sent to error_log, in addition to where they are sent in your current environment. -o outfile All command output is sent to outfile, in addition to where it is sent in your current environment. -X Enable XML output. Characteristics of XML are defined in DTD, in /usr/share/lib/xml/dtd/lu_cli.dtd.<num>, where <num> is the version number of the DTD file. OPERANDS
BE_name Name of the BE to be deleted. EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. FILES
/etc/lutab list of BEs on the system /usr/share/lib/xml/dtd/lu_cli.dtd.<num> Live Upgrade DTD (see -X option) ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWluu | +-----------------------------+-----------------------------+ SEE ALSO
lu(1M), luactivate(1M), lucancel(1M), lucompare(1M), lucreate(1M), lucurr(1M), ludesc(1M), lufslist(1M), lumake(1M), lumount(1M), lure- name(1M), lustatus(1M), luupgrade(1M), lutab(4), attributes(5), live_upgrade(5) SunOS 5.10 24 Jan 2002 ludelete(1M)
All times are GMT -4. The time now is 04:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy