There was a known bug in RHEL5.1 and (I believe) 5.2 where if the target disks already contained a filesystem, anaconda hung before it actually got into doing anything. During my last round of testing, I had to reformat the disks before repeating the kickstart.
I just tested with 5.3, and it appears to be working. It's formatting over the old filesystems. -----Original Message----- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Shawn Wells Sent: Wednesday, June 10, 2009 12:49 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] To kick or to clone ... that is the question Hall, Ken (GTS) wrote: > Which distro/version? Apparently this was a known problem with RHEL5, but > might have been fixed by now. > I haven't heard of this one. I'd love to hear about any details if you have them still. Actually, I lie. I've heard of customers taking a non-Linux formatted DASD to install Linux on and having issues. You can use the 'zerombr' to clear out pre-existing partition information. Especially useful on new disks, since the partition table on them is bogus (if one is present) -- Shawn Wells Global System z Platform Manager Cell: (+1) 443-534-0130 (GMT -5) ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -------------------------------------------------------------------------- This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. --------------------------------------------------------------------------
