Hello

We are deploying some HP Compaq 8000 Elite PC's. These PC's are high-end
and are being used to do graphics stuff (Adobe video editing type of
stuff I think).

The PC's have an Intel SATA RAID controller which I believe is some kind
of blend of software and hardware RAID? The required configuration is to
have the two disks in a striped RAID so two 160GB disks present as a
single 320 GB disk to the OS with the data striped over the two disks to
give good I/O performance.

I have tried uploading an image from this device and I get a segmentation
fault (much as described in a 2008 post "imaging hp xw6600 raid
workstation"). The point that author made and that I'm making now is that
these types of PC's are out there and people are expecting to be able to
deploy them using ZENworks - it isn't really good enough to glibly say
that this is not supported - that just makes people decide to purchase
Ghost licences and ditch ZEN?

I have found that SLES 11 (same kernel as ZCM10 boot disk I think)
supports this software RAID device very well and that I can install SLES
11 onto this PC. The two SATA disks are visible as /dev/sda and /dev/sdb
but the OS is installed to the RAID (not direct to the SATA disks) at /
dev/mapper/Disk_Name. This can all be controlled by using the dmsetup
command (e.g. dmsetup info, dmsetup status Disk_Name).

If I boot from the ZEN boot CD I can issue the dmsetup commands and build
the RAID, once I do that I am able to see the RAID device as one disk,
but uploading an image still results in a segmentation fault.

Details of the two SATA disks
ZEN:~ # fdisk -l /dev/sda
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xb119b119
Device Boot Start End Blocks Id System
/dev/sda1 * 1 38913 312568641 7 HPFS/NTFS
ZEN:~ # fdisk -l /dev/sdb
Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3b2b3b2b
Device Boot Start End Blocks Id System
ZEN:~ #
Set up the software RAID
ZEN:/bin # dmsetup create DISK --table "0 625154048 striped 2 256 /dev/
sda 0 /dev/sdb 0"
ZEN:~ # dmsetup info
Name: DISK
State: ACTIVE
Read Ahead: 256
Tables present: LIVE
Open count: 0
Event number: 0
Major, minor: 253, 0
Number of targets: 1
ZEN:~ #
ZEN:~ # dmsetup status DISK
0 625154048 striped 2 8:0 8:16 1 AA
ZEN:~ #
ZEN:~ # fdisk -l /dev/mapper/DISK
Disk /dev/mapper/DISK: 320.1 GB, 320078872576 bytes
255 heads, 63 sectors/track, 38914 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xb119b119
Device Boot Start End Blocks Id System
/dev/mapper/DISK1 * 1 38913 312568641 7 HPFS/NTFS
ZEN:~ #

Does anyone have any ideas/advice regarding this? I think, given that the
core Linux OS supports this kind of hardware, that ZCM really ought to
play nice with it too?

I have noticed in the above that the number of blocks and the end
cylinder is wrong for the RAID and will continue to look into that but I
guess Novell should be providing documentation/advice on this if they
want customers to continue to use the product?

Simon