Original Message:
Sent: Wed May 22, 2024 04:54 AM
From: Virgile VATIN
Subject: PARTITION ACTIVATION FAILED
Hi Jos,
Thank for the tip, I just verify on a lpar which is not yet migrated, and yes cloud init WAITTIME is on 5 minutes.
I now know what i have to do for the next lpar.
Regards
------------------------------
Virgile VATIN
Original Message:
Sent: Wed May 22, 2024 03:24 AM
From: Jozef Thijs
Subject: PARTITION ACTIVATION FAILED
Hello,
Yes, this CPF9897 - partition activation failed ... I encountered this message already multiple times. In fact, you may ignore as you're busy with migrations to new Power & storage servers. According to IBM Support .... This issue has been reported several times. Full system flash copies or FSR switchovers, ... can result with "CPF9897 PARTITION ACTIVATION FAILED" when there is a different UUID (a unique internal system ID) on the target system as the IPL is occurring. So this is to be expected.
About the other topic ... 'When I start the lpar on the new server, the first IPL goes well but the console stops just before the signon screen'. Yes, I encountered a similar problem ... but after all, the signon screen appeared after a 5 minutes delay.
Please verify the cloud enablement settings. Run the command : CALL PGM(QSYS/QCLTDSP) and you will get a message about the wait-time. A message like ...
CURRENT CLOUDINIT ENABLE WAITTIME IS 5 MINUTES .
You can change this timing, put it to 0 or 1 minute ... en the signon screen (on your console) should pop-up much quicker .
Use the command to define 0 min waittime : CALL PGM(QSYS/QAENGCHG) PARM('WAITTIME=0')
Kind Regards,
Jos
------------------------------
Jos (Jozef) Thijs
Kyndryl Belgium
Original Message:
Sent: Wed May 15, 2024 08:59 AM
From: Virgile VATIN
Subject: PARTITION ACTIVATION FAILED
[Resolved]
This message and code seems to be normal for the first start and may be to be caused by DB2 Mirror during cloud-init even if DB2 mirror is no used
Hello,
I'm doing some migration tests (changing SAN and Server from Power 9 to Power 10), as I'm changing san I'm not using LPM for LPAR migration between servers, I've created a new profile for LPAR on the power 10 and the new profil are mapped via npiv to the SAN
For disks, I've set up a remote copy with a consistency group (i'll stop copy and let R/W access on auxiliary disks.)
When I start the lpar on the new server, the first IPL goes well but the console stops just before the signon screen. When I reboot the machine once or twice, the system starts normally and then I see a PARTITION ACTIVATION FAILED (CPF9897) message in the log without any further explanation. Have you ever encountered this problem?
Regards
Virgile
------------------------------
Virgile VATIN
------------------------------