Login or Register to Ask a Question and Join Our Community


AIX

has bosboot command changed characteristics of boot image?

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems AIX has bosboot command changed characteristics of boot image?
# 1  
Old 09-23-2008
has bosboot command changed characteristics of boot image?
hi all

i just found one of my p650 server showing a warning message when i
tried to run bosboot command after upgrading TL to AIX 530803.

i also tried to run chpv -c hdisk0 and chpv -c hdisk1 to clear out the
old boot info in hdisk0 and hdisk1 and rerun bosboot -a. it still
showed the warning.

any idea?

Test:root.common:/>bosboot -a

0301-177 A previous bosdebug command has changed characteristics of
this
boot image. Use bosdebug -L to display what these changes
are.

bosboot: Boot image is 38058 512 byte blocks.
Test:root.common:/>bootlist -m normal -o
hdisk1 blv=hd5
hdisk0 blv=hd5
Test:root.common:/>bosdebug -L
Memory debugger off
Memory sizes 0
Network memory sizes 0
Kernel debugger off
Real Time Kernel off
Backtracking fault log on
Kernext Memory Tracking off

thanks in advance,
Frank
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Red Hat

Custom-Spin doesnt boot to GUI when /etc/skel is changed

Heyas So i have my custom Fedora with AwesomeWM spin with alots of customizations using the kickstart method for a liveimage. A few weeks (2-3 months) ago, i've done some changes i cannot remember. Those changes made the image from bootable to gui, to not booting to gui any more. Just... (3 Replies)
Discussion started by: sea
3 Replies

2. AIX

Boot image for VIO

i've installed vios 2.2 on blade PS700 there are 2 disk, hdisk0 dan hdisk1 and i want to mirror it but blv (boot logic volume) does not appear on hdisk1 (bootlist -mode normal -ls) only on hdisk0 i've already did command (bootlist -mode normal hdisk0 hdisk1" does anyone know the command to... (1 Reply)
Discussion started by: jpmei
1 Replies

3. Solaris

flar restore with svm mirrors failing to create boot image

In a Solaris9 environment I'm trying to restore flash archive (flar) with SVM mirrored devices to same server via jumpstart server and it is failing to create boot file and drops down to a command prompt in single user mode, metastat -i and metastat -p output looks good when compared to the ones... (0 Replies)
Discussion started by: mbak
0 Replies

4. UNIX for Advanced & Expert Users

Making one binary image containing boot loader and linux

Hi, I want to have one binary image that contains both my boot loader as well as the OS(linux) image at pre defined offsets which i can use to program flash . Can anyone help in this direction? Regards Subrata (0 Replies)
Discussion started by: subratasaharia
0 Replies

5. Red Hat

Boot Messages changed after mondorestore

Hello All, I backed up my RHEL 4 as an image. Then I restored the image (by mondorestore) on my machine. Everything went fine but I dont get the normal boot sequence as it used to come when I freshly installed RHEL4. The messages that are shown when the system boots are something like- "... (13 Replies)
Discussion started by: shamik
13 Replies

6. Filesystems, Disks and Memory

Boot Sequence changed After Image Restore

Hello All, I backed up my RHEL 4 as an image. Then I restored the image on my machine. Everything went fine but I dont get the normal boot sequence as it used to come when I freshly installed RHEL4. The messages that are shown when the system boots are something like- " ..... EXT3-fs:... (2 Replies)
Discussion started by: shamik
2 Replies

7. Red Hat

redhat xen will not boot winXP cdrom image

I'm running redhat linux: 2.6.18-128.1.6.el5xen #1 SMP Tue Mar 24 12:28:27 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux as my Dom0. I have several other DomU's running on this system, but for this test I've shut them down. I'm attempting to boot winXP from an image. Here is my config file: #... (3 Replies)
Discussion started by: willjw1
3 Replies

8. AIX

bosboot: Boot image is 22995 512 byte blocks.

My mksysb scripts gives the following text on standard error: bosboot: Boot image is 22995 512 byte blocks. How come on a Aix 5200-07 aix-system. I thought this message meant that the tape (/dev/rmt0) is not bootable, but I read about a limit of 12 MB and 22995 block is less than 12 MB ... (0 Replies)
Discussion started by: frankwiel
0 Replies

9. AIX

mksysb and boot.image

hello i saved my system this morning, mksysb tape, and i have the message: "boot.image exceeded the size....." i have not the end because the message is disappeared. where can i find the mksysb message in a log ? the message is scary ? thank you (6 Replies)
Discussion started by: pascalbout
6 Replies

10. Filesystems, Disks and Memory

Boot Diskette Image

Where can I find the boot floppy disk image file(*.vfd)of SCO UNIX 5.0.5?:confused: (1 Reply)
Discussion started by: whiteknight
1 Replies
Login or Register to Ask a Question

LEARN ABOUT HPUX

clear_clearinghouse

clear clearinghouse(1m) 												   clear clearinghouse(1m)

NAME

       clear clearinghouse - Removes knowledge of the specified clearinghouse from the server's memory

SYNOPSIS

       cdscp clear clearinghouse clearinghouse-name

ARGUMENTS

       clearinghouse-name The full name of the clearinghouse.

DESCRIPTION

       The  clear clearinghouse command removes knowledge of the specified clearinghouse from the server's memory. The clearinghouse files are not
       deleted.  This ensures that the clearinghouse is not automatically enabled on server restarts.  If you issue a list clearinghouse  command,
       the clearinghouse will be listed.

       Before  you can delete a cleared clearinghouse, you must use the  create clearinghouse command to recreate it.  After recreating the clear-
       inghouse, you can use the  delete clearinghouse command to remove it.

       This command is part of the process of relocating a clearinghouse.  See the OSF DCE Administration Guide for more information.

   Privilege Required
       You must have write permission to the server on which the clearinghouse resides.

NOTE

       This command is replaced at Revision 1.1 by the dcecp command and may not be provided in future releases of DCE.

EXAMPLES

       The following command clears the clearinghouse /.:/Paris2_CH before moving it to another server: cdscp> clear clearinghouse /.:/Paris2_CH

RELATED INFORMATION

       Books: OSF DCE Administration Guide

       Commands: create clearinghouse(1m), delete clearinghouse(1m), list clearinghouse(1m), set cdscp	preferred  clearinghouse(1m),  show  cdscp
       preferred clearinghouse(1m), show clearinghouse(1m)

															   clear clearinghouse(1m)