(Previous submission of this "feature" failed afaik) 
 
I presume hardware related are normally beyond the scope of the beta tests. 
However, in this case the hardware was recognized by elder releases and not 
recognized anymore (10.0 beta-1, beta-2, both 32/64) 
 
HARDWARE DESCRIPTION: 
System: HP-proliant (blade) DL360, 3Ghz Xeon-64, 2048MB mem 
CD/DVD on first primary IDE interface, hda 
Two 146GB ultra 320 SCSI disks connected via HP Smart Array 6i controller 
 
SYMPTOMS: 
After booting installationprograms (V1.9.8) starts up 
Routine questions are asked (language, agreement...) 
 
Finally you get an error message: 
++++++++++++++++++++++++++++++++++++++ 
+ No hardware disks were found for the installation + 
+ Please check your hardware                              + 
++++++++++++++++++++++++++++++++++++++ 
 
 
FURTHER ANALYSIS: 
9.3: As said, the system runs Prof-9.3 
9.3: (no special handling during installation required) 
9.3:  
9.3: The installer/yast had appended a kernel option for startup: 
9.3: "resume=/dev/cciss/c0d0p1 
9.3: lsmod showed the use of the module "cciss" 
9.3: Root partition was mounted on /dev/cciss/c0d0p2 
9.3: From messages i learned: 
9.3: HPCISS driver v2.6.4 
9.3: Device 0x46 found 
9.3: CCISS: Using DAC cycles 
 
With this information, i tried again (10.0/b2-64) 
10.0/b2: After booting from CD1, i provided same option: 
10.0/b2: "resume=/dev/cciss/c0d0p1" 
10.0/b2: 
10.0/b2 This yielded the same results 
10.0/b2 Manually trying: fdisk /dev/cciss/c0d0p2  
10.0/b2 returned: unable to open 
10.0/b2 Manually tried: "insmod ccis" without result 
 
Needles to say that before burning md5sums were checked, 
Difefrent sets of media were used and identical results were found on three 
difefrent blade servers. 
 
Will perform same test with 10.0/B3 asap