Yup, adding "--initlabel msdos" to the clearpart directive did the trick. Not the world's most descriptive switch. Digging through the anaconda code, this results in a call to "parted --initlabel msdos", which, according to the parted man pages, "creates a new disklabel (partition table)". Maybe it's just me, but I've never considered the disk label equivalent to the partition table. Probably something steeped in ancient history. Anyway, mucho gracias for the pointer -- my mindset never would've equated a disk label with a partition table. > -----Original Message----- > From: Robert P. J. Day [mailto:rpjday@xxxxxxxxxxxxxx] > Sent: Saturday, October 05, 2002 8:44 PM > To: 'kickstart-list@xxxxxxxxxx' > Subject: Re: Force initialization of drive? > > > On Sat, 5 Oct 2002, HILL,ANDY (HP-Boise,ex1) wrote: > > > Howdy, all! > > > > When my kickstart installer encounters a brand-spanking-new > drive (no > > Windoze or Linux pre-installed), I get the following message: > > > > "The partition table on device sda was unreadable. To create new > > partitions it must be initialized, causing the loss of ALL > DATA on this > > drive. > > > > Would you like to initialize this drive? > > > > YES NO" > > > > Works fine (totally hands-off) as long as there are > pre-existing partitions > > on the disk. > > > > While this isn't a show-stopper, it requires manual > intervention. I'd like > > some way to force the initialization of the drive. Any ideas? > > isn't this what the > > clearpart ... --initlabel > > directive in a ks.cfg file is for? if you run ksconfig, you would > select to "Initialize the disk label". or is this for something > else that i just don't understand? > > rday >
