ibmtech is absolutely correct: this "altinst_rootvg" might be named like it was created by alt_disk_copy, but it has either been tampered with or created by different means (i can create a Vg called "altinst_rootvg", but that will not make it a eligible target for alt_disk-operations at all).
I suggest to remove the VG and recreate it, this time using correct procedures:
then proceed from there.
Just as an aside: even when using the correct command which ibmtech told you and assuming that whatever you have on hdisk7 is bootable and legit to boot AIX at all (i doubt that, but lets assume it for the sake of the argument) you need to use "hdisk7" in the bosboot command, not "/dev/hdisk7", because you need to name the disk, not its device file (which is just a driver construct representing the disk).
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... (6 Replies)
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)
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)
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)
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)
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)
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)
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)
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)
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
LEARN ABOUT ULTRIX
ppmtosixel
ppmtosixel(1) General Commands Manual ppmtosixel(1)NAME
ppmtosixel - convert a portable pixmap into DEC sixel format
SYNOPSIS
ppmtosixel [-raw] [-margin] [ppmfile]
DESCRIPTION
Reads a portable pixmap as input. Produces sixel commands (SIX) as output. The output is formatted for color printing, e.g. for a DEC
LJ250 color inkjet printer.
If RGB values from the PPM file do not have maxval=100, the RGB values are rescaled. A printer control header and a color assignment table
begin the SIX file. Image data is written in a compressed format by default. A printer control footer ends the image file.
OPTIONS -raw If specified, each pixel will be explicitly described in the image file. If -raw is not specified, output will default to com-
pressed format in which identical adjacent pixels are replaced by "repeat pixel" commands. A raw file is often an order of magni-
tude larger than a compressed file and prints much slower.
-margin
If -margin is not specified, the image will be start at the left margin (of the window, paper, or whatever). If -margin is speci-
fied, a 1.5 inch left margin will offset the image.
PRINTING
Generally, sixel files must reach the printer unfiltered. Use the lpr -x option or cat filename > /dev/tty0?.
BUGS
Upon rescaling, truncation of the least significant bits of RGB values may result in poor color conversion. If the original PPM maxval was
greater than 100, rescaling also reduces the image depth. While the actual RGB values from the ppm file are more or less retained, the
color palette of the LJ250 may not match the colors on your screen. This seems to be a printer limitation.
SEE ALSO ppm(5)AUTHOR
Copyright (C) 1991 by Rick Vinci.
26 April 1991 ppmtosixel(1)