We're trying to research an issue with our kickstarting that cropped up in
RHEL6.4 (worked perfectly in RHEL6.2). RedHat support has asked us to wait
till the kickstart fails then issue CNTL+ALT+F1 to get into pdb mode so
they can debug the anaconda stuff, but since we boot in z/VM, the
We're trying to research an issue with our kickstarting that cropped up in
RHEL6.4 (worked perfectly in RHEL6.2). RedHat support has asked us to
wait till the kickstart fails then issue CNTL+ALT+F1 to get into pdb mode
so they can debug the anaconda stuff, but since we boot in z/VM, the
inline: velologo.gifinline: Facebook.jpginline: LinkedIn.jpginline: TwitterL.jpginline: XingButt.jpg
On 07/16/2013 05:25 PM, David Boyes wrote:
We're trying to research an issue with our kickstarting that cropped up in
RHEL6.4 (worked perfectly in RHEL6.2). RedHat support has asked us to
wait till the kickstart fails then issue CNTL+ALT+F1 to get into pdb mode
so they can debug the anaconda
I'm actually using both of those (RUNKS=1 and cmdline) already. And I think we
know where in the code there's a problem--the clearpart --initlabel
--all/zerombr is not getting run against all disks, just disks mentioned later
in the kickstart. In 6.2, we could use it to wipe out the header
FWIW and if I've understood the original problem as being Kickstart was
not formatting disks even though you specify --clearpart
I had a similar problem to this in the past.
The issue was the volumes being used where not wiped so still contained
formatted data which kickstart interpreted as
David
I would think you would have to modify the inittab so that a signal sent
would emulate the key sequence RH is asking for, I recall doing that some
time back for something else I was working on.
You're probably thinking about the cntrl-alt-del hack that SIGNAL SHUTDOWN
uses. That works
