DILX does not operate on physical disks - it operates on units. But you can create a single-disk unit and then run DILX on it ;-)
I would individually INITIALIZE the physical members, e.g.:
> INIT DISK10000
> INIT DISK20000
and then create the storage set like:
> ADD MIRROR M1 DISK10000 DISK20000
> INIT M1
as I have found that sometimes the storage set INIT can fail even if the disks are fine. If a single physical disk fails the INIT - throw it away or better sell it so somebody else has some fun, too ;-)
You need to be very careful not to DILX the wrong units in write mode, obviously. But as far as I am aware, the HSG80 cannot deal with predictive failure warnings - a disk in a HSG-based storage system is not covered by a pre-failure warranty :-(
"TRANSPORTABLE" means that a disk has no space reserved for meta-data. Assume you have a single disk sticking in a server on a simple SCSI adapter (no backplane RAID). You can:
- remove the disk from this server
- 'transport' it to the HSG-based storage
- plug it in
- add the disk entry
- set it to "TRANSPORTABLE"
- put a unit on top of it
The disk with all data is now presented 'as-is'. You can mount it on a different server attached to the SAN and transfer the data to a different unit. Or you can put data _on_ the "TRANSPORTABLE" disk to make it available for the server that has no SAN attach. It could be, for example, a system disk from a server that does not even have a tape drive for backup/restore. It can be useful for _many_ things.
Indeed you can 'abuse' the "TRANSPORTABLE" setting to make all blocks accessible for a different server and, perhaps, erase the whole disk to get rid of a backplane RAID controller's meta-data (clever idea).
.
