You may have noticed that I have been trying to install OSCAR 5.1 on a small cluster for a couple of weeks. So far I haven't completed a net boot. It's been one thing after another. The subject line of the message changes from time to time as I move from one roadblock to the next.
In the last episode, it was confirmed that the BOEL kernel couldn't deal with the ethernet interface on the client. I worked up my courage and tried OSCAR's UYOK (Use Your Own Kernel) option. It's not as hard as I thought. I just seems to package up the kernel from the server, which is OK with me. It solved the network problem. The new problem comes a little later in the net boot. It has to do with some device driver files which are links to directories that don't exist. First comes a transcript of the session, then the commentary and questions. ------------Begin transcript, lightly edited for clarity------------ We have connectivity to your SystemImager server! Monitoring initialized. start_syslogd get_boel_binaries_tarball rsync -av 192.168.0.100::boot/x86_64/standard/boel_binaries.tar.gz /tmp/boel_binaries receiving file list ... done boel_binaries.tar.gz sent 133 bytes received 6297936 bytes 12596138.00 bytes/sec total size is 6297035 speedup is 1.00 chown: /lib/modules/2.6.18-194.8.1.el5/weak-updates/powernow-k8/powernow-k8.ko: No such file or directory chown: /lib/modules/2.6.18-194.8.1.el5/weak-updates/kmod-kvm/ksm.ko: No such file or directory chown: /lib/modules/2.6.18-194.8.1.el5/weak-updates/kmod-kvm/kvm-amd.ko: No such file or directory chown: /lib/modules/2.6.18-194.8.1.el5/weak-updates/kmod-kvm/kvm.ko: No such file or directory chown: /lib/modules/2.6.18-194.8.1.el5/weak-updates/kmod-kvm/kvm-intel.ko: No such file or directory chown: /lib/modules/2.6.18-194.8.1.el5/weak-updates/gfs/gfs.ko: No such file or directory chown: /lib/modules/2.6.18-194.8.1.el5/weak-updates/gnbd/gnbd.ko: No such file or directory Killing off running processes. write_variables <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> This is the SystemImager autoinstall system Your autoinstall has failed. You can use the shell prompt to try and see what happened. You may be able to use the <Shift>+<Page Up> keys to scroll <snip some text> Installation failed!! Stopping report task. /my_modules # cd /lib/modules/2.6.18-194.8.1.el5/weak-updates/gnbd/ # ls -l lrwxrwxrwx 1 root root 46 Aug 5 10:38 gnbd.ko -> /lib/modules/2.6.18-128.el5/extra/gnbd/gnbd.ko # ls /lib/modules/2.6.18-128.el5 ls: /lib/modules/2.6.18-128.el5: No such file or directory # ls /lib/modules 2.6.18-194.8.1.el5 2.6.21-boel_v4.0.2 ---------------End of transcript ------------------------------------- It tries to chown some device driver files under /lib/modules/2.6.18-194.8.1.el5/weak-updates.. That version number is correct for the kernel on the server, which is the one that was downloaded. I checked one of them, and it's a link pointing to another directory, for version 2.6.18-128.el5. As you can see, that version doesn't exist in /lib/modules. I also checked the missing powernow-k8 file, and it is a link to the -92 directory. I'm stumped. I don't know how it gets the idea that these other versions exist and should be used. Well, almost. In my first attempt at UYOK, I used the RPM repos for CentOS 5.2, which does have kernel version -92. That doesn't explain -128 though. Before this latest attempt I ran the OSCAR start_over script which removes almost everything. I grepped every oscar- and SIS-related file I could find for the string 2.6.18-92, and it wasn't there. ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Oscar-users mailing list Oscar-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oscar-users
