Thanks to Andrea I got things with cciss disks going on my dl360s with RHEL4. He made a patch to Server.pm and I discovered I had the wrong verion of the kernel running. As a result of my experiences I'd like to make some suggestions for enhancements that I don't believe would take very much work: - the autoinstall script (or whereever people think makes the most sense) should check that the version of the kernel matches what boel was built against. In my case I had a 2.4 kernel and the modules were located in a 2.6 directory! - logmsg assume there is a disk to write to and when there isn't, you get errors that in the logging and do ever see the indented message. my vote would be for logmsg to first make sure there IS a disk mounted and if not print the message it intended to write to the disk to the terminal so it doesn't get lost as it currently does - I'm getting other error messages on the clients console while the autoinstall script is running that I believe are simply untrapped messages that while not necessarily harmful can cause a lot of anxiety, at least they do for me. who's so know whether an 'error' message is significant or not? The ones that I saw were: - open_sock no such device [right after "Detecting Hardware" which follows autodetect_hardware_and_load_modules] - a number of 'insmod: cannot insert `/lib/modules/2.6.16-boel_v3.7.3/kernel/drivers/md/md-mod.ko`: File exists (-1):File exists
but other than that it looks like cciss disks are now properly recognized! -mark Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Sisuite-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-devel
