I have a machine with attached storage which is about 2TB that I imaged, but I umounted it before preparing the image and using --my-modules. When I tried to image another machine, the install script blew up because it tried to build an lvm volume set out of the attached storage! My 'quick fix' was to remove the stanza in autoinstallscript.conf and remake the install script. This time the image installed and the system rebooted, except the system never came back, sitting at the console message that it was booting from the hard drive. This leads to a couple of things: - what do I have to do to tell systemimager NOT to try and recreate a particular lvm volume or can't I do that? what should I have done? this particular volume is actually constructed out of for separate luns. part of me thinks if something isn't mounted at 'prepareimage' time, it shouldn't be recreated on the new client, but there's probably also a lot more going on I'm not aware of - did my hacking of the autoinstallscript file cause my booting woes? should there have been other edits made to it as well? if not is there something else I should have done to make the image bootable? I'll certainly try a few other things (not really sure what yet) but if someone has any suggestions I'm ready to try them too.
-mark ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ sisuite-devel mailing list sisuite-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-devel
