@abbasi2: "Hi,
I am running AIX 5.2 ML03, I am receving following Attention msg during the
mksysb
****ATTENTION****
The boot image you created might fail to boot because the size exceeds the
system limit. For information about fixes or workarounds,
see/usr/lpp/bos.sysmgt/README.
****ATTENTION****
.
Creating list of files to back up..
Backing up 569000 files.................................
What am I missing in it? any help or hints or tips will be of great value to
me. Thanks
Riz"
    @b79xan: ""Rizwan Abbasi" <email_address> schrieb im Newsbeitrag
news:<email_address>
<quote>
the
to
Hallo Riz,
did you check /usr/lpp/bos.sysmgt/README? All you need to know should be
explained there. IIRC this message comes up if the boot image becomes too
big after too many devices are detected (and thus driver support for them is
included into boot image). However I think that with AIX 5.2 ML03 this
message is rather for information but will not cause real problems. (Think
it was fixed with ML02  - the system will still display that error but boot
from the mksysb anyway. IIRC on early 5.2 oslevel it could cause system
hangs during boot or lead to boot devices being skipped). So while writing
from memory I am pretty sure that your system is not affected. If the README
does not supply enough information you could simply try to boot from your
mksysb to find out yourself. Well, for ease of mind this is always a good
idea ;-)
Regards,
Andreas"
    @fred: "<quote>
This problem still exists under 5.2ML4. I understood from IBM that this 
is more a firmware problem which can not easily be fixed without 
breaking backward compatibility.
If your boot image is too large, you should boot from a cdrom, which has 
the same OS version, and restore the mksysb from there. Not a big deal, 
but can be very annoying of the system is at a remote location."
    @b79xan: ""James A. Dennis" <email_address> schrieb im Newsbeitrag
news:LIwjd.20653$<email_address>
<quote>
is
the
firmware
Hallo Jamie,
that will not work on server types: 7028,7029, 7038 and 7040. For those
servers the AIX 5.2 problem was fixed with ML2 (or APAR IY40975). On 5.1
systems the APAR is IY40824.
Fred, if you happen to encounter that problem with one of the servers given
above and a higher 5.2 RML than 02 you might check your server's firmware.
I'd suspect it is too old then for the oslevel you use.
Regards,
Andreas"
{'source': 'USENET', 'other_information': '{"reply_count": 3, "forum_name": "comp.unix.aix.20140616.mbox"}', 'file': 'data/output/usenet-comp.unix.parquet'}