Sponsored Content
Full Discussion: boot log files
Operating Systems Solaris boot log files Post 302131767 by zafyil on Monday 13th of August 2007 03:59:25 PM
Old 08-13-2007
boot log files

Hello,

I am working on a liveupgrade

bash-2.05# lustatus
Boot Environment Is Active Active Can Copy
Name Complete Now On Reboot Delete Status
-------------------------- -------- ------ --------- ------ ----------
first_disk yes yes no no -
second_disk yes no yes no -


I am trying to boot from the second_disk

luactivate second_disk
init 6

But it boots from the first_disk... There is a problem for sure but I can't find the log files so I don't know what went wrong.

Do you know where can I find the log files for that boot attempt? Would they be on the first_disk or second_disk?

Thanks,
Zafer
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Replacing root / boot files

Hi everybody, I am running SCO-V openserver platform running on P-100. How can I replace root / boot files ? I want to do this because, if my system is not getting booted or my root is corrupted, I want to just replace this with the back up taken or boot/root floppy. Usually I am restoring... (1 Reply)
Discussion started by: skant
1 Replies

2. SuSE

/var/log/boot.msg

I have a Dell Latitude c840 that runs SuSE 8.0 Enterprise server that hangs on bootup on trying to create /var/log/boot.msg. It boots in rescue mode just fine. I've tried deleting the old boot.msg file that was in there, but that did no good. Does anyone have any advice/know of a website with... (3 Replies)
Discussion started by: Jody
3 Replies

3. UNIX for Dummies Questions & Answers

boot / reboot log info

hi guys, i know some commands to check last boot information in solaris and redhat. #last -10 | grep boot #who -b #cat /var/adm/messages | grep signal but how do i check for boot info in hp-ux other than from the "shutdownlog" #last -10| reboot has rebooted my hp-ux server ! ... (2 Replies)
Discussion started by: cromohawk
2 Replies

4. Solaris

System boot up log file

Hi, where can I check the system boot up log file like those message when the system booting up.... Thanks. (14 Replies)
Discussion started by: efang
14 Replies

5. UNIX for Dummies Questions & Answers

Not able to generate boot.log.

Hi I m not able to find anything under boot.log file. Here is the output of boot.log files. As you can see nothing is getting written inside the boot.log files . How can i make all the events to be logged under boot.log file? # ls -ltr /var/log | grep boot -rw------- 1 root root 0... (6 Replies)
Discussion started by: pinga123
6 Replies

6. Boot Loaders

Reboot and Select Proper Boot device or insert Boot media in select Boot device and press a key

Hello, I have kubuntu on my laptop and now I decided to switch to Windows 7. I made the bios settings properly (first choice is boot from cd\vd) but I see the error " reboot and select proper Boot device or insert Boot media in select Boot device and press a key " I have tried CD and... (0 Replies)
Discussion started by: rpf
0 Replies

7. AIX

Replaying log stuck during boot

I had some problems with NFS see here: https://www.unix.com/302790997-post9.html and now I cannot boot the partition when I boot I get stuck here Saving Base Customize Data to boot disk Starting the sync daemon ... (7 Replies)
Discussion started by: filosophizer
7 Replies

8. Red Hat

Customized boot log messages

Hi all Many years ago, I found online this script that was incredibly funny and I had blogged it Unfortunately because of my poor record-keeping, I seem to have lost the shell script Would somebody be kind enough to tell me how to replicate this? Thank you! (0 Replies)
Discussion started by: hedkandi
0 Replies

9. Shell Programming and Scripting

Redirecting log files to null writing junk into log files

Redirecting log files to null writing junk into log files. i have log files which created from below command exec <processname> >$logfile but when it reaches some size i am redirecting to null while process is running like >$logfile manually but after that it writes some junk into... (7 Replies)
Discussion started by: greenworld123
7 Replies

10. UNIX for Advanced & Expert Users

Knowing the boot files

Hi, I have experienced a situation whereby after rebooting the server, we were not able to bring it up. After further troubleshooting it was found that it was an issue with the "boot" image/file permission. Have you experienced such an issue? I was not the one who did the troubleshooting... (1 Reply)
Discussion started by: anaigini45
1 Replies
ludesc(1M)                                                                                                                              ludesc(1M)

NAME
ludesc - display or set boot environment description SYNOPSIS
/usr/sbin/ludesc -A BE_description | -f {filename | -} [-l error_log] [-o outfile] [-X] /usr/sbin/ludesc -n BE_name [-f filename | -] [-l error_log] [-o outfile] [-X] /usr/sbin/ludesc -n BE_name [-l error_log] [-o outfile] [-X] BE_description DESCRIPTION
The ludesc 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 ludesc command allows you to manipulate boot environment (BE) descriptions. A BE description is an optional attribute of a BE. It can be text or binary data. For example, it might be a string such as "S9 beta test BE" or it be a file that contains 8-bit multi-byte charac- ters. The ludesc command in general and the options to manipulate binary-format descriptions in particular are suitable for use in pro- grams. You create a BE description using ludesc or lucreate(1M). Only ludesc allows you to change a BE description or add a description following BE creation. While a BE description is associated with a BE name, it is not interchangeable with that name. No Live Upgrade command allows you to spec- ify a BE description instead of a BE name when performing an operation on a BE. A shell might restrict what you enter for a BE description (in both ludesc and lucreate(1M)). In entering a description, use the following guidelines: o Always enclose a description in single quotes ('), unless the description includes a single quote. o If your description includes a single quote, enclose the description in double quotes ("). You then must use an escape sequence (usu- ally a backslash []) to enter a character that is special to the shell. See sh(1) for a list of special characters and a description of the escape sequence mechanism. Descriptions that include many special characters might be more conveniently inserted in a file (-f option) than entered on a command line (-A option). When ludesc outputs a BE description, it does so exactly as the description was entered. Because of this feature, a description that is a text string does not have a concluding newline, which means the system prompt immediately follows the last character of the description. The ludesc command requires root privileges. OPTIONS
The ludesc command has the following options: -A BE_description Displays the BE name associated with BE_description. -f {filename | -} Specify the BE description contained in filename or read from stdin. When used without -n, displays the BE name associated with the specified BE description. Used with -n, changes the description for the specified BE to the description specified with -f. -l error_log Error and status messages are sent to error_log, in addition to where they are sent in your current environment. -n BE_name With no other arguments, displays the BE description for the specified BE. With the -f option or the BE_description operand, changes the description for the specified BE to that specified with -f or BE_description. -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_description Used only with the -n option. BE_description replaces the current BE description for the specified BE. EXAMPLES
The following are examples of the use of ludesc. Example 1: Basic Use The first command, below, assigns a description to a BE. The second command returns the name of the BE associated with the specified description. The last command returns the description associated with a specified BE. # ludesc -n first_disk 'Test disk' Setting description for boot environment <first_disk>. Propagating the change of BE description to all BEs. # ludesc -A 'Test disk' first_disk # # ludesc -n first_disk Test disk# As seen above and noted in the DESCRIPTION, ludesc does not append a newline to the display of BE description that is a text string. Example 2: Using Binary Files The following commands are analogs of the preceding examples, substituting a binary file-here, a file containing a description in Russian, using the Cyrillic alphabet--for a text string. In the third command, note the use of a file to capture output. Sending output of a binary file to the console can produce erratic results. # ludesc -n first_disk -f arrayBE.ru Setting description for boot environment <first_disk>. Propagating the change of BE description to all BEs. # ludesc -f arrayBE.ru first_disk # ludesc -n first_disk > /tmp/arrayBE.out 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), ludelete(1M), lufslist(1M), lumake(1M), lumount(1M), lurename(1M), lus- tatus(1M), luupgrade(1M), lutab(4), attributes(5), live_upgrade(5) SunOS 5.10 24 Jan 2002 ludesc(1M)
All times are GMT -4. The time now is 05:22 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy