> A<4A30
0bf2.9040...@redhat.com>
From: "Hall, Ken (GTS)" <ken_h...@ml.com>
To: "Linux on 390 Port" <LINUX-390@VM.MARIST.EDU>
X-OriginalArrivalTime: 10 Jun 2009 19:50:42.0238 (UTC)
FILETIME=[BCA3A5E0:01C9EA04]
X-Barracuda-Connect: mlnya404er.ml.com[199.43.38.102]
X-Barracuda-Start-Time: 1244663473
X-Barracuda-Encrypted: AES256-SHA
X-Barracuda-Bayes: INNOCENT GLOBAL 0.5000 1.0000 0.0000
X-Barracuda-Virus-Scanned: by Barracuda Spam & Virus Firewall at marist.edu
X-Barracuda-Spam-Score: 0.00
X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=3.5
QUARANTINE_LEVEL00.0 KILL_LEVEL=5.5 testsX-Barracuda-Spam-Report: Code version
3.2, rules version 3.2.2.540
Rule breakdown below
pts rule name description
---- ----------------------
--------------------------------------------------
Zerombr doesn't work, I get the same error.
As I said, it's peculiar because I don't believe there's a partition
table on the disk.
-----Original Message-----
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Brad Hinson
Sent: Wednesday, June 10, 2009 3:40 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] To kick or to clone ... that is the question
Hall, Ken (GTS) wrote:
> Tried zerombr, according to the doc, "yes" is deprecated.
>
> Doesn't help.
>
Try zerombr yes. iirc it behaved differently on DASD than just zerombr
alone. I know.. not a good doc.
> zerombr
> clearpart --all --initlabel
> part /boot --asprimary --bytes-per-inode=4096 --fstype="ext3" --grow
> --ondisk=dasda --size=88
> part / --asprimary --bytes-per-inode=4096 --fstype="ext3" --grow
> --ondisk=dasdb --size=1
> part /var --asprimary --bytes-per-inode=4096 --fstype="ext3" --grow
> --ondisk=dasdc --size=1
> part swap --asprimary --bytes-per-inode=4096 --fstype="swap" --grow
> --ondisk=dasdd --size=1
> part pv.01 --asprimary --grow --ondisk=dasde --size=1
> part pv.02 --asprimary --grow --ondisk=dasdf --size=1
> part pv.03 --asprimary --grow --ondisk=dasdg --size=1
>
> From the kickstart documentation:
>
> zerombr (optional)
>
> If zerombr is specified any invalid partition tables found on disks
are
> initialized. This destroys all of the contents of disks with invalid
> partition tables.
> Note that in previous versions of Red Hat Enterprise Linux, this
command
> was specified as zerombr yes. This form is now deprecated; you should
> now simply specify zerombr in your kickstart file instead.
>
> ------
>
> The problem at the moment is that dasdb was partially formatted, so
> there actually shouldn't be any partition table there (so why is it
> asking?). Admittedly this isn't a "normal" situation, but it could
come
> up where there was residual data in the minidisk space, or something
> crashed.
>
> And for Doug's point, by that logic, I can reduce my build time to
zero
> by simply cloning a ready system over every disk instead of
formatting.
> We configure instances on first-boot anyway. But this doesn't work
> unless you're using full volumes.
>
> Those of us using minidisks don't have the option of preformatting, so
> this becomes an apples-to-oranges comparison.
>
Not sure I follow. On this guest, assuming zerombr yes works and the
installer dasdfmt's the disks, after the installation finishes, you can
change zerombr to 'no' (or leave it off altogether), and change
clearpart to --all only. Then when you install again to the same disks,
the dasdfmt will not happen.
Is this completely off from what you're saying?
>
> -----Original Message-----
> From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
> Brad Hinson
> Sent: Wednesday, June 10, 2009 1:28 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: [LINUX-390] To kick or to clone ... that is the question
>
> Hall, Ken (GTS) wrote:
>> Even if you "preformat" the DASD, it still has to be done, so it does
>> take time. And if you're using minidisks, you have to format it at
> the
>> point where the guest is created.
>>
>> On a related note, anyone know how to eliminate the prompt during
>> kickstart?:
>>
>> Can't have a question in command line mode!
>>
>> Warning
>>
>> The partition table on device dasdb (0.0.0101) was unreadable. To
> create
>> new par
>> titions it must be initialized, causing the loss of ALL DATA on this
>> drive.
>>
>>
>> This operation will override any previous installation choices about
>> which drive
>> s to ignore.
>>
>>
>>
>> Would you like to initialize this drive, erasing ALL DATA?
>>
>> yesno []
>>
>>
>>
>> I tried to format over a partially formatted minidisk, and got this.
>> There doesn't seem to be an option to override and just go ahead and
>> write.
>>
>> This is RHEL5.3.
>>
>
> The combination of kickstart options:
>
> clearpart --all --initlabel
> zerombr yes
>
> will instruct the installer to go ahead and format the DASD without
> prompting.
>
> To your first point, I think Doug was pointing out that you don't have
> to do this format every time. If you have a DASD that was formatted
for
> Linux use in the past, you can just specify:
>
> clearpart --all
>
> and Anaconda will happily skip the dasdfmt. This works great for DASD
> used by Linux in the past. For unknown or new DASD, it's best to use
> the slow approach (dasdfmt during install), that way you know for
sure.
>
> -Brad
>
>
>
>
------------------------------------------------------------------------
--
> 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. Sec
urities 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.
>
------------------------------------------------------------------------
--
>
>
> ----------------------------------------------------------------------
> 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
--
Brad Hinson <bhin...@redhat.com>
Sr. Support Engineer Lead, System z
Red Hat, Inc.
(919) 754-4198
www.redhat.com/z
----------------------------------------------------------------------
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
----------------------------------------------------------------------
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
