Ahh! Just the person I was hoping would to get a comment from! The python
error is from an attempt
at 7.1...
I just got mail from Mr. Alford....Im using the 'install' list and I have a
lenghty list of packages
to be installed....Thats an interesting point you've raised about an upgrade
though...Ive noticed that
on systems that I run mkkickstart from, if there are any 3rd party packages
installed, they get listed and you
have to comment them out appropriatly...the system I ran mkkickstart from in
this case to get a list for 7.1
was an upgraded system from a 6.1 install and installed from cd....so some of
the packages that RedHat no
longer packages, or 3rd party stuff that I put in had to be excluded by hand
until the package read wouldnt
fail...
oh, and yes, the list includes 'rpm'
The 6.1 error is strange just because it completes the install and gets you to
the 'pre-reboot' screen that prompts
you for an "ok". Behind that prompt box, I get an error along the lines of
"geo_comp_addr: Cylinder number is too big"...
When I reboot, it locks at "LI"
..hrmm... more /usr/doc/lilo-0.21/README
""
LI The first stage boot loader was able to load the second stage boot
loader, but has failed to execute it. This can either be caused by a
geometry mismatch or by moving /boot/boot.b without running the map
installer.
""
Upon further investigation, it installing as hde rather than hda....why? I
think ive seen something about
2.2.12 w/o the CERN patch mapping drives starting at hde....Am I off base here?
aside from kickstart, just me ranting.....:
the BIOS doesnt have any option to turn on LBA support or even anything along
the lines of autodetecting the
geometry of the disks....
uhh, ive noticed that the have this interesting daughter-card/riser sort of a
setup in these 1U boxs for the UIDE/100
cards....model #CSA-649U
i dunno....this is really getting to me...My 6.1/6.2 setup works great on any
other system....What other info should I
provide to be helpful??
thank you guys, ohh so much!
-johnny
"Taylor, ForrestX" wrote:
> I guess I'll take a stab at this.
>
> > No-one really has any input on this problem below...I hate to resend,
> > but...
> > Its clear where the problem lies, but why???? How can I beat this?
> >
> > -johnny
> >
> > (ps) i also have another interesting problem w/ kickstart 6.1
> > on a Compaq
> > proliant DL320 machine
> > that has partitions crossing cylinder boundaries when
> > kickstarted, and even
> > worse it tries to boot
> > on hde instead of hda during the reboot so it plain out
> > fails....open for
> > suggestions...tried grub, boot
> > disk, post install scripts,...i just wish i could specify an
> > 'ondisk' sorta
> > feature....
>
> What do your partitions look like before you install? What does your ks.cfg
> look like?
>
> >
> >
> > Johnny Lopes wrote:
> >
> > > Hi All,
> > >
> > > I seem to be having some strange issue immediately after anaconda
> > > determines what packages to upgrade..
> > >
> > > Heres the error:
> > >
> > > python: header.c: 511: headerLoad: Assertion `rdlen == dl` failed.
> > > install exited abnormally
> > >
> > > This is w/ Redhat 7.1, and ive already wrestled w/ the anaconda
> > > errors...after all that I end up w/ this....#*@#%)&!!!!!
> > >
> > > Well, alls well until this, obviously.... Ive successfully gotten
> > > kickstart to work under 6.1 and 6.2, is there
> > > some known issue here? I belive I have all of the required
> > fields in my
> > > ks.cfg, and got the bootnet.img from
> > > the RedHat 7.1 disk.....
> > >
> > > tia,
> > > -johnny
>
> This is an upgrade, not install? Is that the only error you get? Did you
> change anaconda in any way? What kind of installation (NFS, HTTP, FTP) are
> you doing? Are you certain that you have permissions to get the packages?
>
> Forrest
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list@xxxxxxxxxx
> https://listman.redhat.com/mailman/listinfo/kickstart-list
