Did you say at the end you installed OSCAR 4 on top of an existing OSCAR 3.0 installation? I am fairly sure this could cause strange results. When it is possible, I always start with a clean OS terminal install, then put in OSCAR. I am a long time Windows user though, so I have never been fully able to trust that my OS hasn't gotten into some weird state after I install and uninstall a complex program, especially if that install doesn't work.
OSCAR 4.0 wasn't really designed to upgrade from older versions as I understand it. If you ran the start_over script from OSCAR 3.0 before you started on OSCAR 4, that might be enough. On Wed, 29 Dec 2004 16:24:25 +0100, Ivan Porro <[EMAIL PROTECTED]> wrote: > Hi, > > after several problem (and day spent) installing a little cluster (HP DL380Gr > head, 5 DL140 compute nodes) with Oscar 3.0, I'm trying with Oscar 4.0 which > have fixed the kernel problem with Tigoon3/broadcom driver. > > The system TFTP boot ok, download the image and ask me for reboot. At the > reboot, the system hang to a booting 2.4.20-8smp. (just only one dot at the > end...nothing else :-) > > I did another install, and this time I've pressed CTRL-C to stop "beeping" and > access a console. I've mounted / in /mnt and /boot in /boot (uh :-) > partitions, chroot /mnt /bin/sh and I manually reinstalled lilo (/sbin/lilo) > At the reboot, the system hang to a booting 2.4.20-8smp. Same as above. The > same with other images. > > I've noticed that suggested partition table is strange, only 24 MB for boot, > and 128MB for swap (1Gig RAM): I copied default disks.ide to a custom file. > Rebuiliding image failed...so I modified conf file for node 00 manually. It > look like the original buth with boot = $start + 128, swap = $latest + 2048 > and / = $disksize - 32768 (I've 80gig ide disks) > > Where's the problem? Wrong kernel? wrong LILO conf? wrong fstab? how can I fix > it? > > notice: > > installing Oscar 4 over an Oscar 3, unless with a step_over and rm > -rf /opt/oscar hang at Step 3: installing server packages. I've found a > workaround installing manually some server packages with > > rpm -ivh --force oscar* torque*686* > > and then restarting step 3. Hope this havn't broken my Oscar installation ;-) > > thank you in advance > > ivan > > -- > ______________________ > www.bio.dist.unige.it > +39 010 353.2789 (tel) > +39 010 353.2948 (fax) > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Oscar-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oscar-users > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Oscar-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-users
