Mark,

cciss problems should be definitely fixed in 3.7.3, you can find RPMs here:

http://sourceforge.net/project/showfiles.php?group_id=259&package_id=37046&release_id=423836

In this version there are the udev rules to properly create cciss
devices using the standard syntax (I mean the one reported in
/usr/src/linux-2.6.13-15.8/Documentation/devices.txt).

Moreover to be sure to use the right name in /dev you can try also to
run si_mkautoinstallscript again using --autodetect-disks option, but
unfortunately this option is only in 3.7.3 version...

Regards,
-Andrea

Mark Seger wrote:
> I guess I managed to confuse myself with what's going on but am now 
> getting a clearer picture so let me back up a couple of steps and ask a 
> few questions at the same time...
> 
> When I try to install an image, it gets to the point where it downloads 
> the installation script and begins executing it.  One of the first 
> things it does after making sure no filesystems are mounted is
> 
> DISKORDER=
> 
> [ -z $DISKORDER ] || {
>   logmsg enumerate_disks
>   etc...
> 
> so if DISKORDER isn't empty, it executes the code.  DISKORDER is empty 
> and so none of this code gets executes and if simply falls through the 
> block.  Is also skips the error message that says no disks were found 
> because it's part of this block as well!  Maybe this is what it's 
> supposed to do?  I have no idea.  maybe some extra comments in the code 
> would help.  The output from running the script looks like:
> 
> logmsg: No such file or directory
> logmsg: No such file or directory
> Error: Could not stat device /dev/cciss/disk0/disk
> etc...
> 
> and I have no idea where any of this comes from.  With some additional 
> debugging code of my own I figured out that $DISK0 has been set to 
> '/dev/cciss/disc0/disk' - why didn't the "logmsg Partitioning $DISK0" 
> print anything?  I basically did the exact same thing with an 'echo' and 
> it did work.  I then executed the 'parted' command and saw the 'could 
> not stat device" error so that's obviously the third error line listed 
> above.  So where did the 'logmsg' errors come from?  Are there bugs in 
> the error reporting code?
> 
> So back to the question at hand - does anyone have a clue as to what's 
> going on here?  I've been trying to figure out if there as a way to copy 
> files off the client machine for posting but can't figure out how.  I 
> tried using rsync to copy back the image server but that didn't work.
> 
> As I've said before /dev/cciss doesn't exist and feels like it could be 
> the root of the problem.
> 
> -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-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Reply via email to