Guys, this can well be done manually, but doesn't make sense in SC. Because one should let some reasonable software detect the BIOS order of drives.
Could somebody please explain why "grub" fails to detect the cciss drives? Does "grub" fail or does only "grub-install" fail? Why is "the logic of grub busted"? The most we can do currently is to not re-create the device.map file if an old one already exists and contains some cciss device. If there is any method to detect the cciss drives reliably (and the correct BIOS ordering), we can of course improve SC to do it right. Thanks, best regards, Erich On Sunday 09 July 2006 22:10, Mark Seger wrote: > Thanks to some serious chatting with Andrea this morning, it looks like > we've at least identified the problem and I'll have to leave it to the > grub experts to figure out what the next steps are. The bottom line is > using SystemConfigurator as is does not work. The device.map gets > mis-written and even when replaced with a valid one the boot environment > is not set up correctly. > > That said, and at Andrea's suggestion, I wrote a very simply and > NOT-general post-install script that does the following: > > #!/bin/sh > > echo "This is ccissHandler!!!" > > tmp=/tmp/device.map > rm -f $tmp > > echo "(fd0) /dev/fd0" >$tmp > echo "(hd0) /dev/cciss/c0d0" >>$tmp > echo "(hd1) /dev/cciss/c0d1" >>$tmp > > cp -f $tmp /boot/grub/device.map > > echo "Executing 'grub-install'" > grub-install --force-lba /dev/cciss/c0d0 > > I suppose something that would be more general would be to have a > pre-install script that saves a copy of the current device.map and then > the post-install script could just replace it and call grub-install as > shown above. But I was being lazy... > > The key problem as I've said before, is SystemConfigurator cannot ask > grub to generate a new device map because the logic in grub to do this > is busted. Either generate one in SC independent of grub or use the one > that's already there. As far as the --force-lba switch on grub-install, > I'll have to let Andrea explain why that's needed as I'm not a grub person. > > As an aside, even thought the post-install script seems to have worked, > I couldn't find it on the client! The README says it should be in > /tmp/post-install but that directory doesn't even exist! Does all this > get removed after execution? > > Anyhow, as I said it all works and I'll await a version of Grub.pm that > does the right thing and eliminates the need for post-install. > > Just give a holler if anyone needs me to do anything else... > > -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
