Sponsored Content
Full Discussion: bosboot problem please help!
Top Forums UNIX for Dummies Questions & Answers bosboot problem please help! Post 3063 by jericho on Tuesday 19th of June 2001 05:53:02 AM
Old 06-19-2001
bosboot problem please help!

each time I try to do a bosboot or a mksysb the cpu says that he doesn't find /unix... I don't understand cause the kernel is here on the computer and at this exact place with the right name. I tried to force with -k /unix but it doesn't do anything. He doesn't find it and it is here...
Do you have any idea or explanation?
thnax
 

10 More Discussions You Might Find Interesting

1. 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

2. AIX

installp -C error: 'bosboot verification failed'

Hi, I'm a noob with AIX, can anybody help me solve this issue I'm stuck with on an 5.3 box. bash# installp -C 0503-409 installp: bosboot verification starting... 0503-497 installp: An error occurred during bosboot verification processing. Thanks. (4 Replies)
Discussion started by: thebytegrill
4 Replies

3. AIX

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... (0 Replies)
Discussion started by: rs6000er
0 Replies

4. AIX

bosboot issue

bosboot -ad hdisk0 give the following error .. malloc failed 0301-177 A previous bosdebug command has changed characteristics of this boot image. Use bosdebug -L to display what these changes are. 0301-106 /usr/lib/boot/bin/mkboot_chrp: The malloc call failed for size: 216174592 ... (1 Reply)
Discussion started by: b_manu78
1 Replies

5. AIX

user login problem & Files listing problem.

1) when user login to the server the session got colosed. How will resolve? 2) While firing the command ls -l we are not able to see the any files in the director. but over all view the file system using the command df -g it is showing 91% used. what will be the problem? Thanks in advance. (1 Reply)
Discussion started by: pernasivam
1 Replies

6. AIX

Cannot uninstall powerpath - bosboot issues

Hi Guys, I have a problem while trying to upgrade to more current EMC powerpath software on AIX 5.3 - respectively uninstalling the existing one. I tried to deinstall the powerpath software with removed disks - was working perfectly fine on 12 servers - but number 13 is failing with errors: ... (4 Replies)
Discussion started by: zxmaus
4 Replies

7. IP Networking

Problem with forwarding emails (SPF problem)

Hi, This is rather a question from a "user" than from a sys admin, but I think this forum is apropriate for the question. I have an adress with automatic email forwarding and for some senders (two hietherto), emails are bouncing. This has really created a lot of problems those two time so I... (0 Replies)
Discussion started by: carwe
0 Replies

8. AIX

bosboot issue

Hi i wanted to know for what reasons, bosboot fails with the error below.? # /usr/sbin/bosboot.dp -a -p /usr/lib/boot/chrp.disk.proto -d /dev/ipldevice dd: 0511-053 The write failed. : There is a request to a device or address that does not exist. 65893+1 records in. 1029+1 records out. ... (1 Reply)
Discussion started by: gnakul
1 Replies

9. AIX

Problem with bosboot

This is my problem: I couldn't create boot image for hdisk7 test02:/]lspv hdisk2 00c8ac36cfdf99b4 old_rootvg hdisk5 00c8abd6d05f83ca newvg active hdisk6 00c8abd6d4ad141f rootvg active... (4 Replies)
Discussion started by: bobochacha29
4 Replies

10. UNIX for Dummies Questions & Answers

sed Or Grep Problem OR Terminal Problem?

I don't know if you guys get this problem sometimes at Terminal but I had been having this problem since yesterday :( Maybe I overdid the Terminal. Even the codes that used to work doesn't work anymore. Here is what 's happening: * I wanted to remove lines containing digits so I used this... (25 Replies)
Discussion started by: Nexeu
25 Replies
LVRENAME(8)						      System Manager's Manual						       LVRENAME(8)

NAME
lvrename - rename a logical volume SYNOPSIS
lvrename [-A|--autobackup {y|n}] [-d|--debug] [-h|--help] [-v|--verbose] [--version] {OldLogicalVolumePath NewLogicalVolume{Path|Name} | VolumeGroupName OldLogicalVolumeName NewLogicalVolumeName} DESCRIPTION
lvrename renames an existing logical volume from OldLogicalVolume{Name|Path} to NewLogicalVolume{Name|Path}. OPTIONS -A, --autobackup {y|n} Controls automatic backup of VG metadata after the change (see vgcfgbackup(8)). Default is yes. -d, --debug Enables additional debugging output (if compiled with DEBUG). -h, --help Print a usage message on standard output and exit successfully. -v, --verbose Gives verbose progress messages. EXAMPLE
To rename lvold in volume group vg02 to lvnew: lvrename /dev/vg02/lvold /dev/vg02/lvnew An alternate syntax to rename this logical volume is lvrename vg02 lvold lvnew DIAGNOSTICS
lvrename returns an exit code of 0 for success or > 0 for error: 1 invalid logical volume name 2 error checking existence of volume group 3 volume group inactive 4 new logical volume special file already exists 5 old logical volume doesn't exist 6 volume group names are different 7 new logical volume already exist 9 error reading volume group 10 error getting index of old logical volume 11 error renaming logical volume in kernel 12 error creating new logical volume in kernel 13 error writing VGDA to physical volume(s) 14 error creating device special for new logical volume 15 invalid volume group name 95 driver/module not in kernel 96 invalid I/O protocol version 97 error locking logical volume manager 98 invalid lvmtab (run vgscan(8)) 99 invalid command line ENVIRONMENT VARIABLES
LVM_AUTOBACKUP If this variable is set to "no" then the automatic backup of VG metadata is turned off. LVM_VG_MAX_BACKUPS This variable determins the backup history depth of kept VGDA copy files in /etc/lvmconf. It can be set to a positive number between 0 and 999. The higher this number is the more steps are you able to backup with vgcfgrestore(8) from the changes you make to your volume groups. LVM_VG_NAME The default Volume Group Name to use. Setting this variable enables you to enter just the Logical Volume Name rather than its com- plete path. SEE ALSO
lvm(8), lvchange(8), vgcreate(8), vgrename(8) AUTHOR
Heinz Mauelshagen <Linux-LVM@Sistina.com> Heinz Mauelshagen LVM TOOLS LVRENAME(8)
All times are GMT -4. The time now is 05:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy