Thanks to Richard Pace, Jay Lessert, Matthew Stier, Ronald Loftin, all of whom informed me that this is a well known issue. You need to turn off auto-boot "setenv auto-boot? false" and reset the hardware or probe-scsi will hang. (This didn't make a lot of sense to me since the OS is down anyway, but it certainly proved to be true. :) Tim Evans mentioned that he has dealt with Enterprise 3x00 and 4x00 boxes in which not all the internal bays had SCSI connectors, and John McNab mentioned that I might be lacking device files for some of the SCSI ID's. Jay Lessert also pointed me to a tool called "scsiinfo" ( ftp://ftp.cs.toronto.edu/pub/jdd/scsiinfo/ <ftp://ftp.cs.toronto.edu/pub/jdd/scsiinfo/> ), which I have not looked at yet. Thanks to all the folks who told me how to get a scsi probe to run, I was able to verify that the hardware knew all the disks were there. From there it was almost certainly an OS issue, so I checked the device files, and sure enough, those three SCSI ID's were missing device files. Thanks for helping an HP gimp out (I'm used to turning the box on, whacking the space bar a couple times, then typing "sea" =) --ChrisReceived on Fri Jul 6 14:16:41 2001
This archive was generated by hypermail 2.1.8 : Wed Mar 23 2016 - 16:24:58 EDT