Forum Discussion
Volker_Hermin1
18 years agoLevel 4
The error occurs when vxdisksetup is run for disks that do not appear to be SCSI disks. I say "appear to" because the method used to find this out relies on a rather kludgy "grep 'SCSI'" on the output of the disk inquiry command. So it is well possible that it vxdisksetup fails even on SCSI disks, especially if they're iSCSI or similar.
The reason why vxdisksetup doesn't like non-SCSI-disks is because it is assumed that non-SCSI means IDE/ATA/SATA, which in turn means the disk geometry cannot be reliably determined. This is due to LBA-adressing and other ancient PC cruft.
How to fix it? Not sure. Technically speaking, you could certainly hack vxdisksetup (it's a script) to ignore the error and just go on, but I wouldn't run an investment bank's production on the result ;-)
The reason why vxdisksetup doesn't like non-SCSI-disks is because it is assumed that non-SCSI means IDE/ATA/SATA, which in turn means the disk geometry cannot be reliably determined. This is due to LBA-adressing and other ancient PC cruft.
How to fix it? Not sure. Technically speaking, you could certainly hack vxdisksetup (it's a script) to ignore the error and just go on, but I wouldn't run an investment bank's production on the result ;-)
Related Content
- 14 years ago
- 13 years ago